rsensor/rcontrib

Dear all,

trying to compare illuminance values on a single point on the working surface located in the middle of a south facing room, three methods have been used (rtrace, rsensor and 3phase method using rsensor>rcontrib to estimate the view matrix) with the results difference been explainable. Sensor file represents spatial resonse file of a cosine corrected sensor.
When I have changed the sensor file with one having a narrow filed of view (2x10 degrees) illuminance value using the 3phase approach was the same (~1% difference) as in the case of the cosine corrected sensor.
The command was :
rsensor -h -rd 5000 -vf view_test.vf narrow10.dat . |rcontrib -c 5000 -f klems_int.cal -bn Nkbins -b kbinS -m glazing -I+ -ab 11 -ad 50000 -ds .1 -lw 1e-5 test_r.oct>narrow10.vmx

Repeating the calculation with rsensor command only (again narrow versus cosine corrected sensor file):

rsensor -h -rd 5000 -ab 5 -ad 2500 -ar 300 -aa 0.1 -i -vf view_test.vf narrow10.dat overcast.oct|rcalc -e "$1=179*($1*0.265+$2*0.670+$3*0.065)">overcast_rsensor_10.dat

results differ 98%. Any hint would be appreciated.
I've examine the ray directions coming out from rsensor for both the sensor files and are in accordance with the spatial response. Using NREL's R4.2.a.4 on Windows.

Thanx,

Aris Tsangrassoulis

Hi Aris,

I am puzzled by your use of the -I+ option to rcontrib (first command) and -i option to rsensor (second command). These options are very different from each other, and I don't think you really want to use either. The -I+ option tells rtrace to interpret its 6 input values as virtual illuminance point and orientation, rather than ray origin and direction as produced by rsensor. Using the -i option in the second rsensor command tells the program to evaluate surfaces in your scene as if they were all Lambertian with 314% reflectance. Again, probably not what you had in mind.

Try taking these options off and seeing what you get. The rest of it looks OK as far as I can see.

Cheers,
-Greg

···

From: Aris Tsangrassoulis <[email protected]>
Subject: [Radiance-general] rsensor/rcontrib
Date: April 29, 2014 9:43:44 AM PDT

Dear all,

trying to compare illuminance values on a single point on the working surface located in the middle of a south facing room, three methods have been used (rtrace, rsensor and 3phase method using rsensor|rcontrib to estimate the view matrix) with the results difference been explainable. Sensor file represents spatial resonse file of a cosine corrected sensor.
When I have changed the sensor file with one having a narrow filed of view (2x10 degrees) illuminance value using the 3phase approach was the same (~1% difference) as in the case of the cosine corrected sensor.
The command was :
rsensor -h -rd 5000 -vf view_test.vf narrow10.dat . |rcontrib -c 5000 -f klems_int.cal -bn Nkbins -b kbinS -m glazing -I+ -ab 11 -ad 50000 -ds .1 -lw 1e-5 test_r.oct>narrow10.vmx

Repeating the calculation with rsensor command only (again narrow versus cosine corrected sensor file):

rsensor -h -rd 5000 -ab 5 -ad 2500 -ar 300 -aa 0.1 -i -vf view_test.vf narrow10.dat overcast.oct|rcalc -e "$1=179*($1*0.265+$2*0.670+$3*0.065)">overcast_rsensor_10.dat

results differ 98%. Any hint would be appreciated.
I've examine the ray directions coming out from rsensor for both the sensor files and are in accordance with the spatial response. Using NREL's R4.2.a.4 on Windows.

Thanx,

Aris Tsangrassoulis

Dear Greg,

thanks a lot for the reply. So, piping data from rsensor to contrib with
-I+ , makes rcontrib to use measurement point position and direction from
the view file (as expected) but ignores the rays emitted in accordance to
the sensor file. That explains the fact that the results remained more or
less the same when sensor file was replaced. Now comparing the results
(narrow versus cosine corrected sensor, overcast sky) using rsensor/rcontrib
3phase method, without -I+, there is a difference (58%), but it is
much-much less than the difference observed using rsensor only command.
Consequently, calculation of illuminance values with 3phase method can be
done either using the standard method (measurement points to rcontrib with
-I+ ) or with the combination of rsensor (cosine corrected sensor file)
/rcontrib without using -I+ but with some "handling" of the rays emitted in
order to get similar view matrix files.

Best,
Aris

···

-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Wednesday, April 30, 2014 10:00 PM
To: [email protected]
Subject: Radiance-general Digest, Vol 122, Issue 33

Send Radiance-general mailing list submissions to
         [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
         http://www.radiance-online.org/mailman/listinfo/radiance-general
or, via email, send a message with subject or body 'help' to
         [email protected]

You can reach the person managing the list at
         [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Radiance-general digest..."

Today's Topics:

    1. Re: rsensor/rcontrib (Greg Ward)

----------------------------------------------------------------------

Message: 1
Date: Wed, 30 Apr 2014 10:21:38 -0700
From: Greg Ward <[email protected]>
To: Radiance general discussion <[email protected]>
Subject: Re: [Radiance-general] rsensor/rcontrib
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Hi Aris,

I am puzzled by your use of the -I+ option to rcontrib (first command) and
-i option to rsensor (second command). These options are very different from
each other, and I don't think you really want to use either. The -I+ option
tells rtrace to interpret its 6 input values as virtual illuminance point
and orientation, rather than ray origin and direction as produced by
rsensor. Using the -i option in the second rsensor command tells the
program to evaluate surfaces in your scene as if they were all Lambertian
with 314% reflectance. Again, probably not what you had in mind.

Try taking these options off and seeing what you get. The rest of it looks
OK as far as I can see.

Cheers,
-Greg

From: Aris Tsangrassoulis <[email protected]>
Subject: [Radiance-general] rsensor/rcontrib
Date: April 29, 2014 9:43:44 AM PDT

Dear all,

trying to compare illuminance values on a single point on the working

surface located in the middle of a south facing room, three methods have
been used (rtrace, rsensor and 3phase method using rsensor|rcontrib to
estimate the view matrix) with the results difference been explainable.
Sensor file represents spatial resonse file of a cosine corrected sensor.

When I have changed the sensor file with one having a narrow filed of view

(2x10 degrees) illuminance value using the 3phase approach was the same (~1%
difference) as in the case of the cosine corrected sensor.

The command was :
rsensor -h -rd 5000 -vf view_test.vf narrow10.dat . |rcontrib -c 5000

-f klems_int.cal -bn Nkbins -b kbinS -m glazing -I+ -ab 11 -ad 50000 -ds .1
-lw 1e-5 test_r.oct>narrow10.vmx

Repeating the calculation with rsensor command only (again narrow versus

cosine corrected sensor file):

rsensor -h -rd 5000 -ab 5 -ad 2500 -ar 300 -aa 0.1 -i -vf view_test.vf

narrow10.dat overcast.oct|rcalc -e
"$1=179*($1*0.265+$2*0.670+$3*0.065)">overcast_rsensor_10.dat

results differ 98%. Any hint would be appreciated.
I've examine the ray directions coming out from rsensor for both the

sensor files and are in accordance with the spatial response. Using NREL's
R4.2.a.4 on Windows.

Thanx,

Aris Tsangrassoulis

------------------------------

_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general

End of Radiance-general Digest, Vol 122, Issue 33
*************************************************
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3462 / Virus Database: 3722/7270 - Release Date: 03/30/14
Internal Virus Database is out of date.

Hi Aris,

I'm having some trouble understanding what you wrote. Perhaps it would be better if you sent me your commands, what you expected to get from them, and what you got. If everything is as you expected, then we're done. If not, then perhaps there is still a problem with your commands.

The rcontrib command knows nothing about view files, only measurement coordinates. So, I lost your meaning in your very first sentence.

Cheers,
-Greg

···

From: Aris Tsangrassoulis <[email protected]>
Subject: [Radiance-general] rsensor/rcontrib
Date: May 2, 2014 2:19:38 AM PDT

Dear Greg,

thanks a lot for the reply. So, piping data from rsensor to contrib with
-I+ , makes rcontrib to use measurement point position and direction from
the view file (as expected) but ignores the rays emitted in accordance to
the sensor file. That explains the fact that the results remained more or
less the same when sensor file was replaced. Now comparing the results
(narrow versus cosine corrected sensor, overcast sky) using rsensor/rcontrib
3phase method, without -I+, there is a difference (58%), but it is
much-much less than the difference observed using rsensor only command.
Consequently, calculation of illuminance values with 3phase method can be
done either using the standard method (measurement points to rcontrib with
-I+ ) or with the combination of rsensor (cosine corrected sensor file)
/rcontrib without using -I+ but with some "handling" of the rays emitted in
order to get similar view matrix files.

Best,
Aris