First time here? Check out the Help page!
1 | initial version |
This was posted simultaneously to the Radiance mailing list, which is a bit confusing. Do we have a standard way to cross-reference questions & answers between forums?
Anyway, here is the answer I posted there http://radiance-online.org/pipermail/radiance-general/2016-March/011585.html:
Hi Grigori,
This is an interesting test. Essentially, what you are seeing is light leaking via the ambient file from one zone to another. It also points out the fact that the -ab setting is not the only one that matters.
You have left all the other rtrace parameters to their defaults. Running rtrace [your options] -defaults, we can look at what these are. I am including all those that are relevant to your calculation, below:
-dt 0.030000 # direct threshold -dc 0.750000 # direct certainty -dj 0.000000 # direct jitter -ds 0.200000 # direct sampling -av 0.000000 0.000000 0.000000 # ambient value -aw 0 # ambient value weight -aa 0.100000 # ambient accuracy -ar 256 # ambient resolution -ad 1024 # ambient divisions -as 512 # ambient super-samples -lr -10 # limit reflection (Russian roulette) -lw 2.00e-03 # limit weight
In this case, you have a large ground plane and a shading plane behind the building, which means that the default -ar of 256 is on the low side. I would increase this to -ar 400 (divide scene size by desired detail scale).
The -aa setting of 0.1 means that you're shooting for roughly 10% error in your indirect calculations, which is what you are seeing in your results. Reducing this setting to -aa 0.05 increases calculation time substantially, but cuts your error roughly in half.
I determined these changes improve the result primarily by visualizing your calculation, rather than simply relying on the output. I always tell users that there's nothing more important than actually looking at your model. In this case, it's easy enough to visualize the point of view of your points:
p1: 0.5 0.5 0.1 0 0 1 -> -vth -vp .5 .5 .1 -vd 0 0 1 -vu 0 1 0 -vh 180 -vv 180
p2: -0.5 0.5 0.1 0 0 1 -> -vth -vp -.5 .5 .1 -vd 0 0 1 -vu 0 1 0 -vh 180 -vv 180
If you run rvu, you have to explicitly set the options (even the default ones) to match your rtrace calculation. That way, you can truly see what's going on and get a better idea of where errors may be creeping in.
Cheers, -Greg
From: Grigori Grozman Grigori.Grozman@equa.se Subject: [Radiance-general] Ambient files increase illiminance Date: March 15, 2016 7:24:44 AM PDT Dear Radiance experts.
I am professionally using radiance for calculating daylight factors and illuminance. It all works quite well. However, I can not fully understand how to use ambient files.
Question 1: Is there any comprehensive documentation on the topic?
Question 2: It seems to me that when rtrace is used with ambient files, a higher value of illuminance is calculated than when no ambient files are used. Is there any explanations to that? Which value is more correct?
I have put together a simple example that illustates the problem. I attach the files. The run.bat file needs to be run and the result is printed to the file res.txt.
Best regards
Grigori Grozman
2 | No.2 Revision |
This was posted simultaneously to the Radiance mailing list, which is a bit confusing. Do we have a standard way to cross-reference questions & answers between forums?
Anyway, here is the answer I posted there http://radiance-online.org/pipermail/radiance-general/2016-March/011585.html:
Hi Grigori,
This is an interesting test. Essentially, what you are seeing is light leaking via the ambient file from one zone to another. It also points out the fact that the -ab setting is not the only one that matters.
You have left all the other rtrace parameters to their defaults. Running rtrace [your options] -defaults, we can look at what these are. I am including all those that are relevant to your calculation, below:
-dt 0.030000 # direct threshold
threshold
-dc 0.750000 # direct certainty
certainty
-dj 0.000000 # direct jitter
jitter
-ds 0.200000 # direct sampling
sampling
-av 0.000000 0.000000 0.000000 # ambient value
value
-aw 0 # ambient value weight
weight
-aa 0.100000 # ambient accuracy
accuracy
-ar 256 # ambient resolution
resolution
-ad 1024 # ambient divisions
divisions
-as 512 # ambient super-samples
super-samples
-lr -10 # limit reflection (Russian roulette)
roulette)
-lw 2.00e-03 # limit weight
In this case, you have a large ground plane and a shading plane behind the building, which means that the default -ar of 256 is on the low side. I would increase this to -ar 400 (divide scene size by desired detail scale).
The -aa setting of 0.1 means that you're shooting for roughly 10% error in your indirect calculations, which is what you are seeing in your results. Reducing this setting to -aa 0.05 increases calculation time substantially, but cuts your error roughly in half.
I determined these changes improve the result primarily by visualizing your calculation, rather than simply relying on the output. I always tell users that there's nothing more important than actually looking at your model. In this case, it's easy enough to visualize the point of view of your points:
p1: 0.5 0.5 0.1 0 0 1 -> -vth -vp .5 .5 .1 -vd 0 0 1 -vu 0 1 0 -vh 180 -vv 180
p2: -0.5 0.5 0.1 0 0 1 -> -vth -vp -.5 .5 .1 -vd 0 0 1 -vu 0 1 0 -vh 180 -vv 180
If you run rvu, you have to explicitly set the options (even the default ones) to match your rtrace calculation. That way, you can truly see what's going on and get a better idea of where errors may be creeping in.
Cheers,
Cheers,
-Greg
From: Grigori Grozman Grigori.Grozman@equa.se Subject: [Radiance-general] Ambient files increase illiminance Date: March 15, 2016 7:24:44 AM PDT Dear Radiance experts.
I am professionally using radiance for calculating daylight factors and illuminance. It all works quite well. However, I can not fully understand how to use ambient files.
Question 1: Is there any comprehensive documentation on the topic?
Question 2: It seems to me that when rtrace is used with ambient files, a higher value of illuminance is calculated than when no ambient files are used. Is there any explanations to that? Which value is more correct?
I have put together a simple example that illustates the problem. I attach the files. The run.bat file needs to be run and the result is printed to the file res.txt.
Best regards
Grigori Grozman