ViewVC Help
View File | Revision Log | Show Annotations | Download File | Root Listing
root/radiance/ray/doc/man/man1/rsensor.1
(Generate patch)

Comparing ray/doc/man/man1/rsensor.1 (file contents):
Revision 1.1 by greg, Tue Apr 15 00:14:22 2008 UTC vs.
Revision 1.5 by greg, Thu Jun 14 22:42:21 2012 UTC

# Line 7 | Line 7 | rsensor - compute sensor signal from a RADIANCE scene
7   [
8   .B -n nprocs
9   ][
10 < .B rtrace options
10 > .B -h
11 > ][
12 > .B render options
13   ]
14   [
15   .B $EVAR
# Line 27 | Line 29 | rsensor - compute sensor signal from a RADIANCE scene
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
# Line 36 | Line 52 | sensors into the RADIANCE scene given by
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, the default values
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
# Line 58 | Line 79 | Before each sensor file, a separate view may be specif
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
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
# Line 82 | Line 105 | 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 light sources per sensor.
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
118 > .I rtrace(1)
119   man page.
120   The final
121   .I octree
# Line 99 | Line 125 | standard input.
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), rtcontrib(1), rtrace(1)
138 > oconv(1), rpict(1), rcontrib(1), rtrace(1)

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines