[ViewVC] Diff of: Development/ray/doc/man/man1/rad.1

Comparing ray/doc/man/man1/rad.1 (file contents):
Revision 1.4 by greg, Thu Jan 1 19:31:45 2004 UTC vs.
Revision 1.11 by greg, Tue May 26 10:00:46 2015 UTC

+.B \-s
+][
-<
+.B "-n|-N npr"
->
+.B "-n | -N npr"
+][
+.B \-t
+][
+and
+.I pfilt,
+the exposure setting may be given either as a multiplier or as a
-<
+number of f-stop adjustments (eg. +2 or -1.5).
->
+number of f\-stop adjustments (eg. +2 or \-1.5).
+There is no default value for this variable.
+If it is not given, an average level will be computed by
+.I pfilt
+Also, there are several standard view identifiers defined by
+.I rad.
+These standard views are specified by strings of the form
-<
+"[Xx]?[Yy]?[Zz]?[vlcah]?".
->
+"[Xx]?[Yy]?[Zz]?[vlcahs]?".
+(That is, an optional upper or lower case X followed by an optional
+upper or lower case Y followed by an optional upper or lower case Z
+followed by an optional lower case V, L, C, A or H.)\0
+means maximum X, lower case means minimum and so on.
+The final letter is the view type, where 'v' is perspective (the
+default), 'l' is parallel, 'c' is a cylindrical panorama,
-<
+'a' is angular fisheye, and 'h' is hemispherical fisheye.
->
+'a' is angular fisheye, 'h' is hemispherical fisheye, and 's'
->
+is a planisphere (stereographic) fisheye.
+A perspective view from maximum X, minimum Y would be "Xy" or "Xyv".
+A parallel view from maximum Z would be "Zl".
+If "ZONE" is an interior zone, the standard views will
+.TP
+.BR UP
+The vertical axis for this scene.
-<
+A negative axis may be specified with a minus sign (eg. "-Y").
->
+A negative axis may be specified with a minus sign (eg. "\-Y").
+There is no default value for this variable, although the standard
+views assume Z is up if no other axis is specified.
+.TP
+.BR PICTURE
+This is the root name of the output picture file(s).
+This name will have appended the view identifier (or a number if no
-<
+id was used) and a ".pic" suffix.
->
+id was used) and a ".hdr" suffix.
+If a picture corresponding to a specific view exists and is not out
+of date with respect to the given octree, it will not be
+re-rendered.
+few places, it should be set to HIGH.
+The default value is "L".
+.TP
-+
+.BR PGMAP
-+
+This variable designates a global photon map to be generated by
-+
+.I mkpmap(1)
-+
+and used to accelerate rendering.
-+
+The file name must be followed by the number of photons to be stored
-+
+in the map, and this number may be followed by a bandwidth for rendering.
-+
+There is no default value, meaning that a global photon map will not
-+
+normally be created.
-+
+.TP
-+
+.BR PCMAP
-+
+This variable designates a caustic photon map to be generated by
-+
+.I mkpmap(1)
-+
+and used during renderings to model light transmission by reflecting
-+
+and refracting surfaces.
-+
+The file name must be followed by the number of photons to be stored
-+
+in the map, and this number may be followed by a bandwidth for rendering.
-+
+There is no default value, meaning that a caustic photon map will not
-+
+normally be created.
-+
+.TP
+.BR OPTFILE
+This is the name of a file in which
+.I rad
+.BR oconv
+This variable may be used to specify special options to
+.I oconv.
-+
+If the first word of the first instance of this variable is not an option,
-+
+it will be used in place of the default command path, "oconv".
+See the
+.I oconv(1)
+manual page for a list of valid options.
+.BR mkillum
+This variable may be used to specify additional options to
+.I mkillum.
-+
+If the first word of the first instance of this variable is not an option,
-+
+it will be used in place of the default command path, "mkillum".
+See the
+.I rtrace(1)
+manual page for a list of valid options.
+.TP
-+
+.BR mkpmap
-+
+This variable may be used to specify additional options to
-+
+.I mkpmap.
-+
+If the first word of the first instance of this variable is not an option,
-+
+it will be used in place of the default command path, "mkpmap".
-+
+See the
-+
+.I mkpmap(1)
-+
+manual page for a list of valid options.
-+
+.TP
+.BR render
+This variable may be used to specify additional options to
+.I rpict
+.I rad,
+and thus will override the default values.
+.TP
-+
+.BR rpict
-+
+This variable may be used to specify overriding options specific to
-+
+.I rpict.
-+
+If the first word of the first instance of this variable is not an option,
-+
+it will be used in place of the default command path, "rpict".
-+
+See the
-+
+.I rpict(1)
-+
+man page for a list of valid options.
-+
+.TP
-+
+.BR rvu
-+
+This variable may be used to specify overriding options specific to
-+
+.I rvu.
-+
+If the first word of the first instance of this variable is not an option,
-+
+it will be used in place of the default command path, "rvu".
-+
+See the
-+
+.I rvu(1)
-+
+man page for a list of valid options.
-+
+.TP
+.BR pfilt
+This variable may be used to specify additional options to
+.I pfilt.
-+
+If the first word of the first instance of this variable is not an option,
-+
+it will be used in place of the default command path, "pfilt".
+See the
+.I pfilt(1)
+manual page for details.
+.I rad
+would use without actually executing anything, we can invoke it thus:
+.IP "" .2i
-<
+rad -n -e sample.rif
->
+rad \-n \-e sample.rif
+.PP
+This will print the variables we have given as well as default
+values
+Different option combinations have specific uses, ie:
+.IP "" .2i
+.br
-<
+rad -v 0 sample.rif OPT=samp.opt        # build octree, put options in "sample.opt"
->
+rad \-v 0 sample.rif OPT=samp.opt       # build octree, put options in "sample.opt"
+.br
-<
+rad -n -e -s sample.rif > full.rif      # make a complete rad file
->
+rad \-n \-e \-s sample.rif > full.rif   # make a complete rad file
+.br
-<
+rad -n sample.rif > script.sh   # make a script of commands
->
+rad \-n sample.rif > script.sh  # make a script of commands
+.br
-<
+rad -V -v Zl -n -s sample.rif > plan.vf # make a plan view file
->
+rad \-V \-v Zl \-n \-s sample.rif > plan.vf     # make a plan view file
+.br
-<
+rad -t sample.rif               # update files after minor change to input
->
+rad \-t sample.rif              # update files after minor change to input
+.br
-<
+rad -s sample.rif &             # execute silently in the background
->
+rad \-s sample.rif &            # execute silently in the background
->
+.br
->
+rad \-N 2 sample.rif    # render views using two parallel rpict calls
->
+.br
->
+rad \-N 4 -v 1 sample.rif       # render first view with four rpiece calls
+.PP
+If we decide that the default values
+.I rad
+DET= low                # default was medium - our space is almost empty
+PEN= True               # we want to see soft shadows from our window
+VAR= hi         # daylight can result in fairly harsh lighting
-<
+view= XYa -vv 120       # let's try a fisheye view
-<
+PICT= tutor             # our picture name will be "tutor_XYa.pic"
->
+view= XYa \-vv 120      # let's try a fisheye view
->
+PICT= tutor             # our picture name will be "tutor_XYa.hdr"
+.fi
+.PP
+Note the use of abbreviations, and the modification of a standard
+to take a look at our scene interactively with
+.I rvu:
+.IP "" .2i
-<
+rad -o x11 sample.rif
->
+rad \-o x11 sample.rif
+.PP
+.I Rad
+will run
+We could add these to "sample.rif" like so:
+.IP "" .2i
+.nf
-<
+view= vw1 -vf view1.vp          # Our first view
-<
+view= vw2 -vf view2.vp          # Our second view
->
+view= vw1 \-vf view1.vp         # Our first view
->
+view= vw2 \-vf view2.vp         # Our second view
+RESOLUTION= 1024                # Let's go for a higher resolution result
+.fi
+.PP
+.I rvu
+again using vw2 instead of the default, we use:
+.IP "" .2i
-<
+rad -o x11 -v vw2 sample.rif
->
+rad \-o x11 \-v vw2 sample.rif
+.PP
+Once we are happy with the variable settings in our file, we can run
+.I rad
+.SH AUTHOR
+Greg Ward
+.SH BUGS
-+
+You cannot run more than one
-+
+.I rad
-+
+process at a time on the same input file,
-+
+as the second process will attempt to recover the output files
-+
+of the first process, damaging the results.
-+
+The exceptions to this are running interactively via the
-+
+.I \-o
-+
+option, or rendering different views using the
-+
+.I \-v
-+
+option.
-+
+.PP
+Incremental building of octrees is not supported as it would add
+considerable complexity to
+.I rad.
+The use of upper and lower case naming for the standard views may be
+problematic on systems that don't distinguish case in filenames.
+.SH "SEE ALSO"
-<
+glrad(1), make(1), mkillum(1), objview(1), oconv(1),
->
+glrad(1), make(1), mkillum(1), mkpmap(1), objview(1), oconv(1),
+pfilt(1), raddepend(1), ranimate(1),
-<
+rholo(1), rpict(1), rtrace(1), rvu(1), touch(1), vgaimage(1), ximage(1)
->
+rholo(1), rpict(1), rpiece(1), rtrace(1), rvu(1),
->
+touch(1), vgaimage(1), ximage(1)

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines (old)
->
+Changed lines (new)

Comparing ray/doc/man/man1/rad.1 (file contents): Revision 1.4 by greg, Thu Jan 1 19:31:45 2004 UTC vs. Revision 1.11 by greg, Tue May 26 10:00:46 2015 UTC

Diff Legend

Comparing ray/doc/man/man1/rad.1 (file contents):
Revision 1.4 by greg, Thu Jan 1 19:31:45 2004 UTC vs.
Revision 1.11 by greg, Tue May 26 10:00:46 2015 UTC