[Radiance-general] Hard-coding .cal and data files

[Greg Ward]

Hi Sarith,

There is no way to incorporate the luminaire data directly in the Radiance file other than some kind of reference.  What is your concern, exactly?  If you don't want to have the full path name, you can store the data files in the same file as source.cal and take off the leading directory, or add a new directory to your $RAYPATH (or %RAYPATH%) environment variable and put the data files there.

Having many sources refer to a common data file is one way Radiance saves memory when you have many light sources sharing the same distribution.

Best,
-Greg

> From: "Sarith Subramaniam" <sarith at psu.edu>
> Subject: [Radiance-general] Hard-coding .cal and data files
> Date: May 20, 2015 6:00:28 PM GMT+02:00
> 
> Hi,
>  
>  
> Is it possible to hard-code a data or .cal file inside a rad definition ?
>  
> I am generating a few luminaire definitions using a batch file and was wondering if it is possible to avoid linking rad files to external files. For example, in the luminaire definition below, is it possible to code the .dat and .cal file inside the rad file ?
>  
> void brightdata 2RT8S_2_32_LP735_dist
> 5 flatcorr C:/rm/ies/2RT8S_2_32_LP735.dat source.cal src_phi4 src_theta
> 0
> 1 1.54935
>  
>  
> Thanks,
> Sarith
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.radiance-online.org/pipermail/radiance-general/attachments/20150520/ef113f66/attachment.html>