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

[Greg Ward]

Well, if you make sure your luminaire (*.rad) and data (*.dat) files are uniquely named, you can just store everything together in a separate directory and put it in your RAYPATH environment variable as I suggested.  Since the xform command will look in your RAYPATH directories and so will Radiance, you don't need to have them in your current directory at all.  Everything can live somewhere else.  You can even use the "-l" option of ies2rad to put files there for you.

Cheers,
-Greg

> From: "Sarith Subramaniam" <sarith at psu.edu>
> Subject: Re: [Radiance-general] Hard-coding .cal and data files
> Date: May 20, 2015 8:15:26 PM GMT+02:00
> 
> Hi Greg,
>  
>  
> Thanks. I asked this question because I am interested in simplifying the organization of files in a project.
>  
> I have run into issues in the past with projects that have multiple luminaire definitions. The image below is a screenshot from the directory containing rad files for one such project. Add or removing luminaires, or even sky definitions with .cal files, in a scene will be easier if I could add or  replace rad files alone without worrying about the linking data files.
>  
>  
> 
>  
>  
> Thanks,
> Sarith
> From: Greg Ward [mailto:gregoryjward at gmail.com] 
> Sent: Wednesday, May 20, 2015 1:20 PM
> To: Radiance general discussion
> Subject: Re: [Radiance-general] Hard-coding .cal and data files
>  
> 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
> _______________________________________________
> Radiance-general mailing list
> Radiance-general at radiance-online.org
> http://www.radiance-online.org/mailman/listinfo/radiance-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.radiance-online.org/pipermail/radiance-general/attachments/20150520/803c1821/attachment.html>