Hi all, for those that are interested I have made available my own PVM
patch for POV-Ray3.5 and may (or may not) provide support for it until
the sourceforge version is released. It is only designed to work with the
3.50c Unix source code, but I would be interested to here if anyone
successfully applies the patch to other distributions...
This is basically the previous pvmpov3.1g patch modified and updated for
3.50c, with similar commandline support. I have documented many of the
source code changes in the archive, and the release notes should ensure
hassle free installation. If you are familiar with pvmpov, you should
have no problems (excepting my own bugs...) getting this up and running
(if not, get the pvmpov archive if only for the documentation). If you
don't know what PVM is, then this is of no use to you...

http://www.karekare.co.nz/matthewg/povrayindex.html
(! 240kb+ of images on page !)

Enjoy,
Matthew Grove.

Post a reply to this message

Since I don't have anything to do with the maintenance of these Sparc
computers at work, I have no idea whether PVM is installed here or not.
Is there some way of looking whether this is so or not?
  When trying to compile the pvm-patched version, the compiler chokes on:

#include "pvm3.h"

and says that file doesn't exist. Does this mean PVM is not installed here?
(But shouldn't it be '#include <pvm3.h>' if it's supposed to be a system-wide
library and not a file in the current directory?)

  By the way, I wouldn't like to start a sermon about programming guidelines,
but I noticed that you have lots of stuff in pvm.h which are used only
in pvm.cpp and are clearly just "configuring" it.
  In C and C++ a header file is supposed to be a definition of the
*public interface* of that module. It's not a configuration file for the
module or anything like that.
  A public interface should be minimal and contain only those things which
are purposed to be used by other modules. Everything that is only an
internal implementation detail of pcm.cpp and not even supposed to be used
anywhere else, should go inside pvm.cpp, nowhere else. (If they are things
that can be configured, you can put them at the very beginning of pvm.cpp
for easy access.)

  For some reason many programmers have the odd idea that a header file is
a file where you declare all types and constants, regardless of where they
are used. This is certainly not the purpose of a header file.

  Sorry, couldn't help myself... :)

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

I successfully installed PVM for myself and compiled pvmpovray35.

  Using 12 sparcs benchmark.pov (with the suggested options) rendered in 34
minutes. Not bad.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

>   For some reason many programmers have the odd idea that a header file is
> a file where you declare all types and constants, regardless of where they
> are used. This is certainly not the purpose of a header file.
>
>   Sorry, couldn't help myself... :)

Peopla at university taught me this very thing: put types and constants in
header file.

Post a reply to this message

On Thu, 12 Dec 2002 01:29:58 +1300, Warp wrote:

>   I successfully installed PVM for myself and compiled pvmpovray35.
> 
>   Using 12 sparcs benchmark.pov (with the suggested options) rendered in
>   34
> minutes. Not bad.

Nice to hear that it actually works for someone else :-)
It would be nice to see more parallel benchmark results on
povbench/tabsnet, so I encourage all to post their results.

Matthew.

Post a reply to this message

On Wed, 11 Dec 2002 23:14:04 +1300, Warp wrote:

>   By the way, I wouldn't like to start a sermon about programming
>   guidelines,
... 
>   For some reason many programmers have the odd idea that a header file
>   is
> a file where you declare all types and constants, regardless of where
> they are used. This is certainly not the purpose of a header file.
> 
>   Sorry, couldn't help myself... :)

I didn't write the original, I just did enough to get the thing to work
with 3.5. Quite frankly, POV-Ray and the PVM patch have enough holes to
drive a fairly large truck through.
However, I do agree that in theory, only 'public' stuff should go in the
header files, but sometimes it is not always that simple...

Matthew.

Post a reply to this message

In article <3df7e833@news.povray.org> , "Apache" 
<apa### [at] yahoocom> wrote:

> Peopla at university taught me this very thing: put types and constants in
> header file.

Which is completely wrong:  Only put types and constants used in more than
one source file into a header file.  Otherwise you just clutter the
namespace, regardless of the language being used.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Agreed! I had some trouble with those people more than once about this kind
of things.

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3df8585a$1@news.povray.org...
> In article <3df7e833@news.povray.org> , "Apache"
> <apa### [at] yahoocom> wrote:
>
> > Peopla at university taught me this very thing: put types and constants
in
> > header file.
>
> Which is completely wrong:  Only put types and constants used in more than
> one source file into a header file.  Otherwise you just clutter the
> namespace, regardless of the language being used.
>
>     Thorsten
>
> ____________________________________________________
> Thorsten Froehlich, Duisburg, Germany
> e-mail: tho### [at] trfde
>
> Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Apache <apa### [at] yahoocom> wrote:
> Peopla at university taught me this very thing: put types and constants in
> header file.

  Then change university. :)

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote:
>   Using 12 sparcs benchmark.pov (with the suggested options) rendered in 34
> minutes. Not bad.

  With 29 sparcs benchmark.pov rendered in 21 minutes.

  One problem is that it takes almost 6 minutes to parse benchmark.pov
regardless of the amount of computers, so the time will never go under
that no matter how many sparcs I use (except if I use faster sparcs,
of course).

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message