| 1 |
.\" RCSid "$Id: rsensor.1,v 1.4 2010/09/26 15:41:46 greg Exp $" |
| 2 |
.TH RSENSOR 1 4/11/2008 RADIANCE |
| 3 |
.SH NAME |
| 4 |
rsensor - compute sensor signal from a RADIANCE scene |
| 5 |
.SH SYNOPSIS |
| 6 |
.B rsensor |
| 7 |
[ |
| 8 |
.B -n nprocs |
| 9 |
][ |
| 10 |
.B -h |
| 11 |
][ |
| 12 |
.B render options |
| 13 |
] |
| 14 |
[ |
| 15 |
.B $EVAR |
| 16 |
] |
| 17 |
[ |
| 18 |
.B @file |
| 19 |
] |
| 20 |
{ |
| 21 |
[ |
| 22 |
.B -rd nrays |
| 23 |
][ |
| 24 |
.B -dn nsrc |
| 25 |
][ |
| 26 |
.B sensor_view |
| 27 |
] |
| 28 |
.B sensor_file .. |
| 29 |
} |
| 30 |
.B octree |
| 31 |
.br |
| 32 |
.B rsensor |
| 33 |
[ |
| 34 |
.B -h |
| 35 |
] |
| 36 |
{ |
| 37 |
[ |
| 38 |
.B -rd nrays |
| 39 |
][ |
| 40 |
.B sensor_view |
| 41 |
] |
| 42 |
.B sensor_file .. |
| 43 |
} |
| 44 |
.B "." |
| 45 |
.br |
| 46 |
.B "rsensor [ options ] \-defaults" |
| 47 |
.SH DESCRIPTION |
| 48 |
.I Rsensor |
| 49 |
traces rays outward from one or more specified illumination |
| 50 |
sensors into the RADIANCE scene given by |
| 51 |
.I octree, |
| 52 |
sending the computed sensor value to the standard output. |
| 53 |
(The octree may be given as the output of a command enclosed in quotes |
| 54 |
and preceded by a `!'.)\0 |
| 55 |
In the second form, a single period ('.') is given in place of an |
| 56 |
octree, and the origin and directions of the specified |
| 57 |
number of rays will be printed on the standard output. |
| 58 |
If these rays are later traced and added together, the results |
| 59 |
will sum to a signal proportional to the given sensor distribution. |
| 60 |
In the third form, the default values |
| 61 |
for the options (modified by those options present) |
| 62 |
are printed with a brief explanation. |
| 63 |
.PP |
| 64 |
Options may be given on the command line and/or read from the |
| 65 |
environment and/or read from a file. |
| 66 |
A command argument beginning with a dollar sign ('$') is immediately |
| 67 |
replaced by the contents of the given environment variable. |
| 68 |
A command argument beginning with an at sign ('@') is immediately |
| 69 |
replaced by the contents of the given file. |
| 70 |
.PP |
| 71 |
The sensor files themselves will be searched for in the path |
| 72 |
locations specified by the |
| 73 |
.I RAYPATH |
| 74 |
environment variable, similar to other types of Radiance |
| 75 |
auxiliary files. |
| 76 |
If the sensor file path begins with '/', '.' or '~', no search |
| 77 |
will take place. |
| 78 |
Before each sensor file, a separate view may be specified. |
| 79 |
In this case, the view origin and direction will correspond to |
| 80 |
the position and orientation of the sensor, and the view up |
| 81 |
vector will determine the zero azimuthal direction of the sensor. |
| 82 |
The fore clipping distance may be used as well, but other view |
| 83 |
options will be ignored. |
| 84 |
(See |
| 85 |
.I rpict(1) |
| 86 |
for details on how to specify a view.)\0 |
| 87 |
The actual data contained in the sensor file corresponds to the |
| 88 |
.I SPOT |
| 89 |
tab-separated matrix specification, where the |
| 90 |
column header has "degrees" in the leftmost column, followed |
| 91 |
by evenly-spaced azimuthal angles. |
| 92 |
Each row begins with the polar angle, and is followed by the |
| 93 |
relative sensitivity values for each direction. |
| 94 |
A low-resolution example of a sensor file is given below: |
| 95 |
.sp |
| 96 |
.nf |
| 97 |
degrees 0 90 180 270 |
| 98 |
0 .02 .04 .02 .04 |
| 99 |
45 .01 .02 .01 .02 |
| 100 |
90 .001 .002 .001 .002 |
| 101 |
.fi |
| 102 |
.sp |
| 103 |
As well as different views, the number of samples may be changed between |
| 104 |
sensors, where the |
| 105 |
.I \-rd |
| 106 |
option controls the number of ray samples sent at random, and the |
| 107 |
.I \-dn |
| 108 |
option controls the number of rays sent to each light source per sensor. |
| 109 |
.PP |
| 110 |
The |
| 111 |
.I \-h |
| 112 |
option toggles header output, which defaults to "on." |
| 113 |
The |
| 114 |
.I \-n |
| 115 |
option may be used to specify multiple calculation processes on |
| 116 |
systems with more than one CPU. |
| 117 |
For additional options, consult the |
| 118 |
.I rtrace(1) |
| 119 |
man page. |
| 120 |
The final |
| 121 |
.I octree |
| 122 |
argument must be given, as the octree cannot be read from the |
| 123 |
standard input. |
| 124 |
.SH EXAMPLES |
| 125 |
To compute values for the same sensor with two different positions: |
| 126 |
.IP "" .2i |
| 127 |
rsensor -ab 2 -vf posA.vf mysens.dat -vf posB.vf mysens.dat scene.oct |
| 128 |
.PP |
| 129 |
To generate a set of rays corresponding to a given sensor and compute |
| 130 |
the resulting signal with rtrace: |
| 131 |
.IP "" .2i |
| 132 |
rsensor -h -vf posC.vf mysens.dat . | rtrace -h scene.oct | total -m |
| 133 |
.SH ENVIRONMENT |
| 134 |
RAYPATH the directories to check for auxiliary files. |
| 135 |
.SH AUTHOR |
| 136 |
Greg Ward for Architectural Energy Corporation |
| 137 |
.SH "SEE ALSO" |
| 138 |
oconv(1), rpict(1), rcontrib(1), rtrace(1) |