thanks for your explanation about the weights for computing luminance. That has helped.
Now, our next problem deals with the exposure value:
If you use rview on the octree, trace returns among other values a luminance value. As far as we understand the octree should be free of any image processing stuff, like exposure values. So, we regard this luminance value as a reflection of the reading of a photometer.
If we then use ximage on the picture, generated from the very same octree, we read the very same luminance value as under rview, even though getinfo returns an exposure value (Note, we have not set any exposure values in rpict and pfilt (apart from the default values).
According to the luminance equation and other notes, one should actually divide each radiance value by the exposure value, or divide the luminance reading by the exposure value.
So, which luminance reading is the 'right' one in ximage? The one returned from the image or the one that one obtains by dividing the returned one by the exposure value?
And how do I avoid any exposure setting or correction when producing a picture (radiance picture that is)?
THanks for all your help in the hectic pre-christmas time.......
alexa and marina
=dumb and dumber
Alexa Ruppertsberg <A.I.Ruppertsberg@Bradford.ac.uk>
From: Greg Ward <firstname.lastname@example.org>
Date: Tue, 16 Dec 2003 08:35:38 -0800
To: M BLOJ <M.Bloj@Bradford.ac.uk>
The weights correspond to the conversion matrix between Radiance's RGB color space and CIE XYZ (the Y channel, specifically). This is not very well correlated to the V-lambda curve, because the conversion depends so strongly on the exact choice of red, green, and blue primaries. In the case of Radiance and most standard RGB systems, the red primary is much closer to the peak of V-lambda than is the blue primary. Thus, the contribution of the blue channel to luminance is much reduced.
I hope this explains things for you.