| 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 |
| 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 |
| 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) |
