pvm povray help
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Luc Vereecken Luc.Vereecken at chem.kuleuven.ac.beThu Mar 21 02:39:24 PST 2002
- Previous message: pvm povray help
- Next message: Benchmarks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 12:32 21/03/02 +1100, Drake Diedrich wrote: >On Wed, Mar 20, 2002 at 08:11:33PM +0000, Heger The Horrible wrote: > The next problem you will likely encounter :) : povray with PVM still >reads the scene description file from the filesystem, and parses it in each >slave, so the input file also needs to be available from the same place on >all slave nodes. pvmpov is not terribly informative if the slaves fail to >read a scene file for whatever reason. The errors are actually found in the >logs in /tmp on each slave. > It would be much better if the master node did the parsing, and then >exported the parsed structures to all the slaves over PVM, but that would be >a very large project. That shouldn't be a very large project at all. Read the inputfile (including all the included files, which is basically a simple expansion), broadcast it to all slaves, and work on that copy (either in-memory, or have the slaves write is as (a) temporary inputfile(s) to minimize the amount of code change). Takes less than 50 lines of codes, even counting the file-inclusion. Luc
- Previous message: pvm povray help
- Next message: Benchmarks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
