RSENSOR(1)                                                          RSENSOR(1)



NNAAMMEE
       rsensor - compute sensor signal from a RADIANCE scene

SSYYNNOOPPSSIISS
       rrsseennssoorr  [  --nn nnpprrooccss ][ --hh ][ rreennddeerr ooppttiioonnss ] [ $$EEVVAARR ] [ @@ffiillee ] { [
       --rrdd nnrraayyss ][ --ddnn nnssrrcc ][ sseennssoorr__vviieeww ] sseennssoorr__ffiillee ....  } ooccttrreeee
       rrsseennssoorr [[ ooppttiioonnss ]] --ddeeffaauullttss

DDEESSCCRRIIPPTTIIOONN
       _R_s_e_n_s_o_r traces rays outward from one  or  more  specified  illumination
       sensors  into  the RADIANCE scene given by _o_c_t_r_e_e_, sending the computed
       sensor value to the standard output.  (The octree may be given  as  the
       output  of a command enclosed in quotes and preceded by a `!'.)  In the
       second form, the default values for  the  options  (modified  by  those
       options present) are printed with a brief explanation.

       Options  may be given on the command line and/or read from the environ-
       ment and/or read from a file.  A command argument beginning with a dol-
       lar  sign  ('$')  is  immediately replaced by the contents of the given
       environment variable.  A command argument beginning  with  an  at  sign
       ('@') is immediately replaced by the contents of the given file.

       The  sensor files themselves will be searched for in the path locations
       specified by the _R_A_Y_P_A_T_H environment variable, similar to  other  types
       of  Radiance auxiliary files.  If the sensor file path begins with '/',
       '.' or '~', no search will take place.  Before each sensor file, a sep-
       arate  view may be specified.  In this case, the view origin and direc-
       tion will correspond to the position and orientation of the sensor, and
       the  view  up vector will determine the zero azimuthal direction of the
       sensor.  The fore clipping distance may be used as well, but other view
       options will be ignored.  (See _r_p_i_c_t_(_1_) for details on how to specify a
       view.)  The actual data contained in the sensor file corresponds to the
       _S_P_O_T  tab-separated  matrix  specification, where the column header has
       "degrees" in the leftmost column, followed by  evenly-spaced  azimuthal
       angles.   Each  row begins with the polar angle, and is followed by the
       relative sensitivity values for each direction.  A low-resolution exam-
       ple of a sensor file is given below:

            degrees   0    90   180  270
            0    .02  .04  .02  .04
            45   .01  .02  .01  .02
            90   .001 .002 .001 .002

       As  well  as  different  views,  the  number  of samples may be changed
       between sensors, where the _-_r_d option controls the number of  ray  sam-
       ples  sent  at  random,  and the _-_d_n option controls the number of rays
       sent to each light source per sensor.

       The _-_h option toggles header output, which defaults to  "on."   The  _-_n
       option may be used to specify multiple calculation processes on systems
       with more than one CPU.  For additional options, consult the  _r_t_r_a_c_e_(_1_)
       man  page.  The final _o_c_t_r_e_e argument must be given, as the octree can-
       not be read from the standard input.

EEXXAAMMPPLLEESS
       To compute values for the same sensor with two different positions:

         rsensor -ab 2 -vf posA.vf mysens.dat -vf posB.vf mysens.dat scene.oct

EENNVVIIRROONNMMEENNTT
       RAYPATH        the directories to check for auxiliary files.

AAUUTTHHOORR
       Greg Ward for Architectural Energy Corporation

SSEEEE AALLSSOO
       oconv(1), rpict(1), rtcontrib(1), rtrace(1)



RADIANCE                           4/11/2008                        RSENSOR(1)
