[Radiance-general] Three-Phase Method - subdivision of window with sensor located close to the window

[Greg Ward]

Hi Anne,

I believe David is correct.  I should have looked at your command more closely.  The -I+ switch does not belong.  If you remove it (or set -I-), then the computed radiance values will be accumulated according to the distributed rays out of rsensor, then split again into Klems direction bins by rtcontrib.  The *.vmx files will each contain a single row of 145 RGB coefficients, which processed through dctimestep with the window's BTDF file will ultimately yield a single sensor value at each time step.

I hope this makes sense.  I find it a bit confusing, myself!

Best,
-Greg

> From: David Geisler-Moroder <david.moroder at gmail.com>
> Date: May 2, 2011 2:41:44 AM PDT
> 
> Hi Anne,
> 
> another thing that came to my mind...
> 
> You are calling rtcontrib for the VMX using rsensor in your script like that:
>     rsensor -h -rd 1000 -vf views/luxstat.vf sensors/WattStopper_LS-290C.dat . |\
>        rtcontrib -c 1000 -f klems_int.cal -bn Nkbins -fo -o results/"$vmxname"_%s.vmx \
>        -b kbinS -m windowlight -b kbinS -m windowlightsens \
>        -I+ -ab 3 -ad 2000 -ds .15 -lw 1e-4 model_vmx.oct
> 
> Do you want to obtain the sensor signal split up into the Klems bins?
> If yes, I'm not sure if it works like that...
> 
> You are using rsensor to generate 1000 rays (i.e. origin and direction) according to the sensor-file. 
> These points and directions are then given to rtcontrib, where you use -c 1000 to accumulate all 
> 1000 results and -I+ to switch to irradiances.
> However, this means that rtcontrib calculates irradiances for 1000 pairs of points and directions as
> if it was e.g. a grid for illuminance calculations. So you do not obtain the sensor signal, but a mean 
> of the 1000 calculated irradiances. 
> 
> I hope I'm not missing anything...
> 
> Cheers,
> David