[Radiance-general] rtcontrib - funky error when using -n

[Michael Martinez]

Thanks Greg - that did it. Everything is working smoothly now. 




On Jul 20, 2011, at 2:41 PM, Greg Ward wrote:

> Hi Michael,
> 
> Everyone was so busy on your second question, looks like the first one was neglected:
> 
>> Multi-core runs question:
>> The following command uses 8 processors and successfully generates a bin of 578 .hdr images based on test.oct made of scene geometry, material descriptions and an isotropic sky:
>> 
>> vwrays -ff -vf view.vf -x 800 -y 800 | rtcontrib -n 8 -ab 3 -ad 4000 -as 1000 -dt .05 -ds .1 -dc .17 -lw 9e-19 -e MF:2 -ffc $(vwrays -d -vf view.vf -x 800 -y 800)  -f reinhart.cal -b rbin -o bin/%0d.hdr -m sky_glow  -w tmp/test.oct
> 
> I can't be sure, but most likely you've run into the "bin counting problem."  Quoting the rtcontrib man page:
> 
> 	The actual bin number is computed at run time based
>       on ray direction and surface intersection, as described below.  If  the
>       number of bins is known in advance, it should be specified with the -bn
>       option, and this is critical for output files containing multiple  val-
>       ues  per  record.   A  variable  or constant name may be given for this
>       parameter if it has been defined via a previous -f or -e option.  Since
>       bin numbers start from 0, the bin count is always equal to the last bin
>       plus 1.  Set the this value to 0 if  the  bin  count  is  unknown  (the
>       default).
> 
> Not having the -bn option causes trouble in a lot of cases where there isn't always a ray striking the last bin.
> 
> Hope this fixes it!
> 
> -Greg
> _______________________________________________
> Radiance-general mailing list
> Radiance-general at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-general