Hi Francesco and all,
I've read through the mailing list archives and experimented with "rad
-N" and rpiece. I'm using multiple CPUs and multiple machines on
'standard' linux distros - cannot use openmosix.
If I do this:
rad -v single_view -N 5 myscene.rif
Rad will *not* split up my scene for me (using rpiece). However, if I
specify multiple views, rad *will* run rpict multiple times
simultaneously (ie. as forked/backgrounded processes).
Is this expected behaviour? I was hoping it would split my scene!
Usually I use RIF files to store my "scene=", "illum=", "zone="
variables, and to let rad handle calling oconv/rpict/pfilt/etc correctly
with appropriate settings.
To divide up a scene, it seems I must use rpiece which calls rpict.
(Let's *assume* my NFS lockd is working okay). Therefore I cannot use
rad and my rif files? So I have to do what rad does *manually* and
incorporate rpiece into this process?
HSBC Building Level 20
300 Queen Street
Brisbane QLD 4000
tel: +61 (0)7 3023 5048
fax: +61 (0)7 3023 4000
[mailto:firstname.lastname@example.org] On Behalf Of
Sent: 22 November 2005 18:55
To: Radiance general discussion
Subject: Re: [Radiance-general] multiple processors
There are many ways to run Radiance with multiple processors
and multiple machines. Some programs like rad and rholo have
support for multiple processors (-N option), rpiece can be used
to split a picture into tiles and have them rendered by different
processors or computers over a network (for instance sharing
the scene files with nfs).
Personally, I like to use openmosix with Radiance, and you can
read about my experience in a previous message to this mailing list:
Radiance-general mailing list
Important Notice. Use of this email and any attachments is subject to
the terms on www.cundall.com.au.
Please read that notice before proceeding.
If you cannot access these terms please telephone (02) 8424 7000 or
reply to this email and we will send you a copy.