RenderToolbox BatchRender Parameter Files


Non-geometric scene properties such as object reflectance, spectral power distributions for lights and rendering parameters are supplied to BatchRender for scenes through three text files--conditions.txt, objectProperties.txt and lightProperties.txt. Furthermore, for the radiance rendering path, a fourth file, rendererParams.txt specifies additional rendering parameters. All files are tab-delimited tables in which the first line specifies field names and subsequent lines specify field values. Field names must not contain spaces, though field names can.

Each line of field values in conditions.txt refers to one rendering of the scene to be carried out by BatchRender--that is, for each line, BatchRender will generate one set of hyperspectral, monitor and cone image files. Each line in objectProperties.txt and lightProperties.txt refer to one object or light. rendererParams.txt may only have one line of field values, specifying the rendering properties for all of the conditions to be rendered in the radiance rendering path. Any value in objectProperties.txt, lightProperties.txt or rendererParams.txt may be set to change for each condition to be rendered. For example, you can set the surface reflectance spectrum of an object (it's color) to change during each rendering. In order to set a property to be condition dependent, it is linked from objectProperties.txt, lightProperties.txt or rendererParams.txt to conditions.txt by placing an expression of the form 'c_[field_name]' in the properties file and the field 'field_name' in conditions.txt. The value of that on each line of conditions.txt will then replace '[c_field_name]' for each rendering. The following (simplified) example illustrates this case:

conditions.txt:
conditionName	surfaceColor
con1	1
con2	2

objectProperties.txt:
objectName	spectrumNumber	spectrumType
mysquare	c_surfaceColor	macbethPeter
mycircle	c_surfaceColor	macbethPeter

Here, mysquare and mycircle will both be rendered in the first macbethPeter color (see below for description of spectrumNumber and spectrumType) in the first condition, called con1, and in the second macbethPeter color in the second condition, called con2.

The conditions.txt file

Minimal example file contents, leaving most properties to default values:
sceneName	renderer	imageRes
pbrt_condition	pbrt	200
rad_condition	radiance	200


Example of file contents including most fields, not no fields linked from other parameter files:
sceneName	fileName	renderer	imageRes	wavelengthsStart	wavelengthsStep	wavelengthsNumSteps	viewFile	humanCones	tonemap	calibrationFile
d65_rad	scene_objects	radiance	100	400	10	31	view.vf	ss2	1	srgb
ramplgt_rad	scene_objects	radiance	100	400	10	31	view.vf	ss2	1	srgb
rampsur_rad	scene_objects	radiance	100	400	10	31	view.vf	ss2	1	srgb


Required Properties
Optional Properties

The objectProperties.txt file

Example file contents:
objectName	objectType	glossiness	roughness	spectrumNumber	spectrumType
backwall	ward	0	0	24	macbethPeter
floor	ward	0	0	13	macbethPeter
room	ward	0	0	20	macbethPeter
table	ward	0	0	19	macbethPeter
sphere	ward	0	0	c_sphereColor	macbethPeter

Required Fields

Optional Fields

The lightProperties.txt file

Example file contents:
lightName	spectrumType	lightType	
spotlight_light	D65	point

Required Field
Optional Fields

The rendererParams.txt file

Only required if 1 or more conditions are to be rendered in radiance, and applies only to those conditions. There are two ways of specifying parameters to Radiance through BatchRender: either by specifying each option used in Radiance RIF files, or by manually specifying the parameters to the Radiance binaries oconv and rpict. The first field, renderParamsType in rendererParams.txt specifies which of these two methods you are using, either rifFile or manual. If this field is omitted, BatchRender assumes that you are using the rifFile method.

The rifFile method
Each of these fields corresponds to fields in the .rif files used by radiance to render the images, except renderParamsType, described above, and ambientLightSpectrumType, ambientLightSpectrumNumber and ambientLightIllumGain, described below. See radiance documentation for information on the other parameters. The ambientLight parameters govern the -av render option, and so leave this option out of the render field value.

Example file contents, leaving ambientLight parameters to their defaults:
renderParamsType	zone	exposure	z	quality	penumbras	indirect	detail	variability	report	render
rifFile	Interior 0 40.1 0 25.5 0 19.4	1	Z	Medium	True	0	Medium	Medium	0.2	-dj 0.6 -dt 0.01 -dr 3 -ds 0.1 -sj 0.7 -st 0.15 -dc 0.5 -lr 1 -aw 0

Required Fields

Optional fields

The manual method
After the renderParamsType field, this file contains the fields oconv and rpict, in which you specify the command line arguments to these Radiance programs. You do not need to specify files names, as BatchRender will add them automatically to the command line call to oconv and rpict. Here's an example:

renderParamsType	oconv	rpict
manual	-w	-t 5 -vf view_files/center.vf  -ab 3  -x 512 -y 512

From these arguments, BatchRender might use the following calls to Radiance:
oconv -w your_materials.rad your_objects.rad your_lights.rad > this_condition.oct
rpict -t 5 -vf view_files/center.vf  -ab 3  -x 512 -y 512 this_condition.oct>this_condition.pic

Here, BatchRender has supplied "your_materials.rad your_objects.rad your_lights.rad > this_condition.oct" for the call to oconv and "this_condition.oct>this_condition.pic" for the call to rpict for each wavelength of each condition.

Note that the view file you specify will override the viewFile field in conditions.txt. The same is true for -x and -y resolution. Also, if you would like to specify no arguments to oconv or rpict, just insert a space in their place.

There are 3 comments on this page. [Display comments]

Valid XHTML 1.0 Transitional :: Valid CSS :: Powered by WikkaWiki