# HG changeset patch
# User Axel Jacobs <axel@jaloxa.eu>
# Date 1309103860 -3600
# Node ID a5d25b4668ace60fee8529c72bd3e7ccc37a1acb
# Parent  d960df03359f06c8d51c56b4409eb16c283886b0
Added all existing man pages from HEAD-20110626.

diff -r d960df03359f -r a5d25b4668ac man/man1/compamb.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/compamb.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,53 @@
+.\" RCSid "$Id: compamb.1,v 1.3 2007/09/04 17:36:40 greg Exp $"
+.TH COMPAMB 1 1/23/98 RADIANCE
+.SH NAME
+compamb - compute good ambient value for a rad input file
+.SH SYNOPSIS
+.B compamb
+[
+.B \-c
+][
+.B \-e
+]
+.B rad_input_file
+.SH DESCRIPTION
+.I Compamb
+computes a good ambient value for the specified
+.I rad(1)
+variable file and appends it to the file as a "render= \-av" option.
+If the
+.I \-c
+option is specified, then
+.I compamb
+includes color information in the computed ambient value, rather than
+estimating a grey value to avoid rendering color shifts.
+If the
+.I \-e
+option is specified, then
+.I compamb
+also computes a good exposure value for this scene, and appends it to
+the
+.I rad
+file as well.
+.PP
+.I Compamb
+is a shell script that makes calls to other RADIANCE programs and utilities
+to do the actual work.
+A substantial amount of time may be required to complete this script, since
+.I compamb
+calls
+.I rpict(1)
+to render low resolution frames for each view in the
+.I rad
+file, setting "QUALITY=High" to compute interreflections.
+The resulting ambient file is thrown away, since it would disagree
+with the new \-av setting used for the final renderings.
+This method is preferable to setting the
+.I \-aw
+option of
+.I rpict,
+which frequently results in splotchy artifacts.
+.SH AUTHOR
+Greg Ward Larson
+.SH "SEE ALSO"
+lookamb(1), rad(1), rpict(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/dayfact.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/dayfact.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,25 @@
+.\" RCSid "$Id: dayfact.1,v 1.2 2003/12/09 15:59:06 greg Exp $"
+.TH DAYFACT 1 11/15/93 RADIANCE
+.SH NAME
+dayfact - compute illuminance and daylight factor on workplane
+.SH SYNOPSIS
+.B dayfact
+[
+falsecolor options
+]
+.SH DESCRIPTION
+.I Dayfact
+is an interactive script for computing workplane illuminance,
+and daylight factors and potential daylight savings using
+.I rtrace(1).
+The script
+.I falsecolor(1)
+is then used to draw contour lines on the resulting Radiance
+picture.
+.SH AUTHOR
+Greg Ward
+.SH ACKNOWLEDGEMENT
+Work on this program was initiated and sponsored by the LESO
+group at EPFL in Switzerland.
+.SH "SEE ALSO"
+falsecolor(1), glare(1), rtrace(1), ximage(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/falsecolor.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/falsecolor.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,160 @@
+.\" RCSid "$Id: falsecolor.1,v 1.8 2010/10/05 01:07:16 greg Exp $"
+.TH FALSECOLOR 1 11/15/93 RADIANCE
+.SH NAME
+falsecolor - make a false color RADIANCE picture
+.SH SYNOPSIS
+.B falsecolor
+[
+.B "\-i input"
+][
+.B "\-p picture"
+][
+.B "\-cb | \-cl"
+][
+.B \-e
+][
+.B "\-s scale"
+][
+.B "\-l label"
+][
+.B "\-n ndivs"
+][
+.B "\-lw lwidth"
+][
+.B "\-lh lheight"
+][
+.B "\-log decades"
+][
+.B "\-m mult"
+][
+.B "\-pal palette"
+][
+.B "\-r redv"
+][
+.B "\-g grnv"
+][
+.B "\-b bluv"
+]
+.SH DESCRIPTION
+.I Falsecolor
+produces a false color picture for lighting analysis.
+Input is a rendered Radiance picture.
+.PP
+By default, luminance is displayed on a linear scale from 0 to 1000 nits, where
+dark areas are blue and brighter areas move through the spectrum to red.
+A different scale can be given with the
+.I \-s
+option.
+If the argument given to
+.I \-s
+begins with an "a" for "auto," then the maximum is used for scaling the result.
+The default multiplier is 179, which converts from radiance or irradiance
+to luminance or illuminance, respectively.
+A different multiplier can be given with
+.I \-m
+to get daylight factors or whatever.
+For a logarithmic rather than a linear mapping, the
+.I \-log
+option can be used, where
+.I decades
+is the number of decades below the maximum scale desired.
+.PP
+A legend is produced for the new image with a label given by the
+.I \-l
+option.
+The default label is "Nits", which is appropriate for standard Radiance
+images.
+If the
+.I -i
+option of
+.I rpict(1)
+was used to produce the image, then the appropriate label would be "Lux".
+.PP
+If contour lines are desired rather than just false color, the
+.I \-cl
+option can be used.
+These lines can be placed over another Radiance picture using the
+.I -p
+option.
+If the input picture is given with
+.I \-ip
+instead of
+.I \-i,
+then it will be used both as the source of values and as the picture
+to overlay with contours.
+The
+.I \-cb
+option produces contour bands instead of lines, where the thickness of
+the bands is related to the rate of change in the image.
+The
+.I \-n
+option can be used to change the number of contours (and corresponding
+legend entries) from the default value of 8.
+The
+.I \-lw
+and
+.I \-lh
+options may be used to change the legend dimensions from the default width
+and height of 100x200.
+A value of zero in either eliminates the legend in the output.
+.PP
+The
+.I \-e
+option causes extrema points to be printed on the brightest and
+darkest pixels of the input picture.
+.PP
+The
+.I "\-pal"
+option provides different color palettes for
+.I falsecolor.
+The current choices are
+.I spec
+for the old spectral mapping,
+.I hot
+for a thermal scale, and
+.I pm3d
+for a variation of the default mapping,
+.I def.
+The remaining options,
+.I "\-r, \-g,"
+and
+.I \-b
+are for changing the mapping of values to colors.
+These are expressions of the variable 
+.I v,
+where
+.I v
+varies from 0 to 1.
+These options are not recommended for the casual user.
+.PP
+If no
+.I \-i
+or
+.I \-ip
+option is used, input is taken from the standard input.
+The output image is always written to standard output, which should
+be redirected.
+.SH EXAMPLES
+To create a false color image directly from
+.I rpict(1):
+.IP "" .2i
+rpict \-vf default.vp scene.oct | falsecolor > scene.hdr
+.PP
+To create a logarithmic contour plot of illuminance values on a
+Radiance image:
+.IP "" .2i
+rpict \-i \-vf default.vp scene.oct > irrad.hdr
+.br
+rpict \-vf default.vp scene.oct > rad.hdr
+.br
+falsecolor \-i irrad.hdr \-p rad.hdr \-cl \-log 2 \-l Lux > lux.hdr
+.SH AUTHOR
+Greg Ward
+.br
+Axel Jacobs (Perl translation and -pal options)
+.SH ACKNOWLEDGEMENT
+Work on this program was initiated and sponsored by the LESO
+group at EPFL in Switzerland.
+.SH "SEE ALSO"
+getinfo(1), pcomb(1), pcompos(1), pextrem(1), pfilt(1), pflip(1), protate(1),
+psign(1), rpict(1), ximage(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/fieldcomb.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/fieldcomb.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,64 @@
+.\" RCSid "$Id: fieldcomb.1,v 1.4 2008/11/10 19:08:17 greg Exp $"
+.TH FIELDCOMB 1 9/6/2005 RADIANCE
+.SH NAME
+fieldcomb - combine two or more field frames for video animation
+.SH SYNOPSIS
+.B fieldcomb
+[
+.B "-e|-o"
+][
+.B \-r
+]
+[
+.B "-f combined.hdr"
+]
+.B "field0.hdr field1.hdr .."
+.SH DESCRIPTION
+.I Fieldcomb
+combines two or more field frames into half as many final video frames
+for field-based animations.
+Normally, the even scanlines in the output are given over to the first,
+third, fifth, etc. pictures given on the input, and the odd scanlines are
+given over to the second, fourth, sixth, etc. pictures on the input.
+This behavior corresponds to the
+.I \-e
+option, which is set by default.
+To reverse this ordering, the
+.I \-o
+option must be specified.
+.PP
+Normally,
+.I fieldcomb
+will name output frames by dividing the numbers on the input field
+file names by 2, inserting a 'C' right before the number, adding
+leading zeroes to make it always four digits.
+For example, the command:
+.IP "" .2i
+fieldcomb anim12.hdr anim13.hdr anim14.hdr anim15.hdr
+.PP
+will produce two output pictures:
+.IP "" .2i
+animC0006.hdr & animC0007.hdr
+.PP
+If an odd number of input files is given on the command line, the last file
+is held over and used as the first file in the next invocation of
+.I fieldcomb
+in the same directory.
+In this way, the program works well with the "TRANSFER" facility of
+.I ranimate(1),
+which does not guarantee an even number of frames will be passed every time.
+.PP
+If only two input files are given, the
+.I \-f
+option may be used to specify a different output name of the user's choosing.
+.PP
+If the
+.I \-r
+option is specified, then the input files will be removed once they have
+been combined.
+.SH AUTHOR
+Greg Ward
+.SH ACKNOWLEDGEMENT
+Work on this program was sponsored by Iebele Abel.
+.SH "SEE ALSO"
+getinfo(1), pcomb(1), pfilt(1), phisto(1), ran2tiff(1), ranimate(1), rpict(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/glare.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/glare.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,46 @@
+.\" RCSid "$Id: glare.1,v 1.2 2003/12/09 15:59:06 greg Exp $"
+.TH GLARE 1 5/2/95 RADIANCE
+.SH NAME
+glare - perform glare and visual comfort calculations
+.SH SYNOPSIS
+.B glare
+[
+.B glarefile
+[
+.B picture
+[
+.B octree
+]
+]
+]
+.SH DESCRIPTION
+.I Glare
+is an interactive script for executing programs used to locate
+glare sources and compute glare indices and visual comfort probability.
+If no
+.I glarefile
+is given, the program prompts the user for a one.
+If the file does not exist,
+.I glare
+asks the user some questions about the scene in question then runs
+.I findglare(1)
+to compute values to store in the file.
+.I Glare
+then presents the user a menu of available glare index calculations.
+After choosing a calculation,
+.I glare
+offers to store the result (usually not useful) or plot the information
+(but only for multiple glare angles).
+.PP
+If you are creating a new
+.I glarefile,
+it usually works best to start with a displayed image for reference
+during the interrogation.
+.SH AUTHOR
+Greg Ward
+.SH ACKNOWLEDGEMENT
+Work on this program was initiated and sponsored by the LESO
+group at EPFL in Switzerland.
+.SH "SEE ALSO"
+dayfact(1), findglare(1), glarendx(1), igraph(1),
+rpict(1), xglaresrc(1), ximage(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/normpat.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/normpat.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,50 @@
+.\" RCSid "$Id: normpat.1,v 1.2 2003/12/09 15:59:06 greg Exp $"
+.TH NORMPAT 1 11/15/93 RADIANCE
+.SH NAME
+normpat - normalize RADIANCE pictures for use as patterns.
+.SH SYNOPSIS
+.B normpat
+[
+.B \-v
+][
+.B \-b
+][
+.B \-f
+][
+.B "\-r maxres"
+]
+.B "picture .."
+.SH DESCRIPTION
+.I Normpat
+normalizes one or more RADIANCE pictures to an average brightness of 1.0
+and optionally removes fundamental frequencies and blends the edges
+of the image.
+The original images are overwritten during this process, and it is
+recommended that the program work on copies of the pictures for this reason.
+.PP
+The
+.I \-r
+option can be used to set the maximum horizontal or vertical resolution
+of the final result, which should not be greater than 256 for most
+patterns (due to the associated memory burden during rendering).
+The
+.I \-f
+option uses a Fourier transform to remove the lowest frequencies
+from the image, reducing the noticeability of pattern repitition.
+The
+.I \-b
+option can be used to blend the edges of the image so that when
+it is tiled, the seams are less apparent.
+The
+.I \-v
+option turns on the verbose flag, which prints on the standard output
+progress messages as the script runs.
+.PP
+.I Normpat
+is a shell script that makes calls to other RADIANCE programs
+that do the actual work.
+.SH AUTHOR
+Greg Ward
+.SH "SEE ALSO"
+getinfo(1), pcomb(1), pcompos(1), pfilt(1), pflip(1), protate(1),
+psign(1), ra_bn(1), ra_pr(1), ra_t8(1), ra_t16(1), rpict(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/objline.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/objline.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,49 @@
+.\" RCSid "$Id: objline.1,v 1.4 2008/11/10 19:08:17 greg Exp $"
+.TH OBJLINE 1 10/27/95 RADIANCE
+.SH NAME
+objline - create metafile line drawings of RADIANCE object(s)
+.SH SYNOPSIS
+.B objline
+[input ..]
+.SH DESCRIPTION
+.I Objline
+takes one or more RADIANCE scene files and produces four parallel
+line projections using calls to
+.I rad2mgf(1)
+and
+.I mgf2meta(1).
+The output must be redirected to a suitable destination for
+.I metafile(5)
+2-d graphics, such as
+.I x11meta(1)
+or
+.I psmeta(1).
+.PP
+The four projections presented are along the X-axis (displayed in the
+upper left quadrant), along the Y-axis (upper right), along the Z-axis
+(lower left) and an oblique view (lower right).
+If multiple RADIANCE input files are given, they are shown in
+different colors and line styles.
+(Materials are ignored, so materials files are best left out.)\0
+If no input files are given on the command line, the standard input
+is read.
+.SH EXAMPLES
+To create a line drawing of the RADIANCE file "myfile.rad" and
+display under X11:
+.IP "" .2i
+objline myfile.rad | x11meta \-r &
+.PP
+To create a line drawing of three objects in different colors
+and send to the printer:
+.IP "" .2i
+objline obj1.rad obj2.rad obj3.rad | psmeta | lpr
+.PP
+To create a line drawing of a room and convert into a 1024x1024 RADIANCE
+picture:
+.IP "" .2i
+objline room.rad | meta2tga \-x 1024 \-y 1024 | ra_t8 \-r > drawing.hdr
+.SH AUTHOR
+Greg Ward
+.SH "SEE ALSO"
+meta2tga(1), metafile(5), mgf2meta(1), psmeta(1), ra_t8(1),
+rad2mgf(1), x11meta(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/objview.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/objview.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,47 @@
+.\" RCSid "$Id: objview.1,v 1.3 2004/01/01 19:31:45 greg Exp $"
+.TH OBJVIEW 1 6/10/98 RADIANCE
+.SH NAME
+objview - view RADIANCE object(s)
+.SH SYNOPSIS
+.B objview
+[
+.B "\-u updirection"
+][
+rad options
+]
+input ..
+.br
+.B objview
+[
+.B \-g
+][
+.B "\-u updirection"
+][
+glrad options
+]
+input ..
+.SH DESCRIPTION
+.I Objview
+renders a RADIANCE object interactively using
+.I rad(1)
+or
+.I glrad(1).
+This program is merely a shell script that adds some light
+sources to a scene then calls
+.I rad(1)
+or
+.I glrad(1)
+to make an octree and view the scene interactively.
+.PP
+If the default up vector (+Z) is inappropriate
+for this object, then specify a different one using the
+.I \-u
+option to
+.I objview.
+.PP
+Any number of material and scene files may be given,
+but no in-line commands or standard input.
+.SH AUTHOR
+Greg Ward Larson
+.SH "SEE ALSO"
+glrad(1), oconv(1), rad(1), rvu(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/pdfblur.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/pdfblur.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,137 @@
+.\" RCSid "$Id: pdfblur.1,v 1.7 2008/11/10 19:08:17 greg Exp $"
+.TH PDFBLUR 1 1/24/96 RADIANCE
+.SH NAME
+pdfblur - generate views for depth-of-field blurring
+.SH SYNOPSIS
+.B pdfblur
+.B aperture
+.B nsamp
+.B viewfile
+.SH DESCRIPTION
+.I Pdfblur
+takes the given
+.I viewfile
+and computes
+.I nsamp
+views based on an aperture diameter of
+.I aperture
+(in world coordinate units) and a focal distance equal to the length of the
+.I \-vd
+view direction vector.
+When rendered and averaged together, these views will result in
+a picture with the specified depth of field.
+Either
+.I pinterp(1)
+or
+.I rpict(1)
+may be called to do the actual work.
+(The given
+.I viewfile
+must also be passed on the command line to the chosen renderer, since
+.I pdfblur
+provides supplemental view specifications only.)\0
+.PP
+For
+.I pinterp,
+feed the output of
+.I pdfblur
+to the standard input of
+.I pinterp
+and apply the
+.I \-B
+option to blur views together.
+In most cases, a single picture with z-buffer is all that is required
+to get a satisfactory result, though the perfectionist may wish to
+apply three pictures arranged in a triangle about the aperature, or
+alternatively apply the
+.I \-ff
+option together with the
+.I \-fr
+option of
+.I pinterp.
+(The latter may actually work out to be faster, since rendering
+three views takes three times as long as a single view, and the
+.I \-fr
+option will end up recomputing relatively few pixels by
+comparison.)\0
+.PP
+To use
+.I pdfblur
+with
+.I rpict,
+apply the
+.I \-S
+option to indicate a rendering sequence, and set the
+.I \-o
+option with a formatted file name to save multiple output
+pictures.
+When all the renderings are finished, combine them with the
+.I pcomb(1)
+program, using appropriate scalefactors to achieve an average.
+Note that using
+.I rpict
+is MUCH more expensive than using
+.I pinterp,
+and it is only recommended if the scene and application
+absolutely demand it (e.g. there is prominent refraction that
+must be modeled accurately).
+.PP
+For both
+.I pinterp
+and
+.I rpict,
+the computation time will be proportional to the number of views from
+.I pdfblur.
+We have found a
+.I nsamp
+setting somewhere between 5 and 10 to be adequate for most images.
+Relatively larger values are appropriate for larger aperatures.
+.PP
+The
+.I \-pd
+option of
+.I rpict
+may be used instead or in combination with or instead of
+.I pdfblur
+to blur depth-of-field.
+If used in combination,
+it is best to set the
+.I \-pd
+option to the overall
+.I aperture
+divided by
+.I nsamp
+to minimize ghosting in the output.
+.PP
+To simulate a particular camera's aperture, divide the focal length of
+the lens by the f-number, then convert to the corresponding
+world coordinate units.
+For example, if you wish to simulate a 50mm lens at f/2.0 in
+a scene modeled in meters, then you divide 50mm by 2.0 to get 25mm,
+which corresponds to an effective aperture of 0.025 meters.
+.SH EXAMPLES
+To use
+.I pinterp
+to simulate an aperture of 0.5 inches on a lens focused at a
+distance of 57 inches:
+.IP "" .2i
+rpict \-vf myview \-x 640 \-y 480 \-z orig.zbf scene.oct > orig.hdr
+.br
+pdfblur 0.5 57 8 orig.hdr | pinterp \-B \-vf orig.hdr \-x 640 \-y 480
+orig.hdr orig.zbf > blurry.hdr
+.PP
+To use
+.I rpict
+exclusively to do the same:
+.IP "" .2i
+pdfblur .5 57 5 myview | rpict \-S 1 \-vf myview \-x 640 \-y 480
+\-o view%d.hdr scene.oct
+.br
+pcomb \-s .2 view1.hdr \-s .2 view2.hdr \-s .2 view3.hdr \-s .2
+view4.hdr \-s .2 view5.hdr > blurry.hdr
+.SH AUTHOR
+Greg Ward
+.SH BUGS
+This program really only works with perspective views.
+.SH "SEE ALSO"
+pcomb(1), pinterp(1), pmblur(1), pmdblur(1), rcalc(1), rpict(1), vwright(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/phisto.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/phisto.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,40 @@
+.\" RCSid "$Id: phisto.1,v 1.4 2008/11/10 19:08:17 greg Exp $"
+.TH PHISTO 1 3/12/98 RADIANCE
+.SH NAME
+phisto - compute a luminance histogram from one or more RADIANCE pictures
+.SH SYNOPSIS
+.B phisto
+.B "picture .."
+.SH DESCRIPTION
+.I Phisto
+is a script that calls
+.I pfilt(1),
+.I rcalc(1)
+and
+.I histo(1)
+to compute a histogram of log luminance values for foveal samples in
+the given picture files.
+A foveal sample covers approximately 1 degree, though this script does
+not use this exact area.
+The minimum and maximum values are determined, and 100 histogram bins
+are uniformly divided between these extrema.
+Foveal samples less than 1e-7 candelas/sq.meter are silently ignored.
+If no picture is named on the command line, the standard input is read.
+.PP
+The primary function of this script is to precompute histograms for the
+.I pcond(1)
+program, which may then be used to compute multiple, identical exposures.
+This is especially useful for animations and image comparisons.
+.SH EXAMPLE
+.PP
+To compute two identical tone mappings for image1.hdr and image2.hdr:
+.IP "" .2i
+phisto image1.hdr image2.hdr > both.histo
+.br
+pcond \-I \-h image1.hdr < both.histo > image1m.hdr
+.br
+pcond \-I \-h image2.hdr < both.histo > image2m.hdr
+.SH AUTHOR
+Greg Ward Larson
+.SH "SEE ALSO"
+histo(1), pcond(1), pfilt(1), pvalue(1), rcalc(1), total(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/pmblur.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/pmblur.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,120 @@
+.\" RCSid "$Id: pmblur.1,v 1.5 2008/11/10 19:08:17 greg Exp $"
+.TH PMBLUR 1 3/3/98 RADIANCE
+.SH NAME
+pmblur - generate views for camera motion blurring
+.SH SYNOPSIS
+.B pmblur
+.B speed
+.B nsamp
+.B v0file
+.B v1file
+.SH DESCRIPTION
+.I Pmblur
+takes two viewfiles and generates
+.I nsamp
+views starting from
+.I v0file
+and moving towards
+.I v1file.
+When rendered and averaged together, these views will result in
+a picture with motion blur due to a camera changing from v0 to v1
+in a relative time unit of 1, whose shutter is open starting at v0 for
+.I speed
+of these time units.
+Either
+.I pinterp(1)
+or
+.I rpict(1)
+may be called to do the actual work.
+(The given
+.I v0file
+must also be passed on the command line to the chosen renderer, since
+.I pmblur
+provides supplemental view specifications only.)\0
+.PP
+For
+.I pinterp,
+feed the output of
+.I pmblur
+to the standard input of
+.I pinterp
+and apply the
+.I \-B
+option to blur views together.
+In most cases, two pictures with z-buffers at v0 and v1 will
+get a satisfactory result, though the perfectionist may wish to
+apply the
+.I \-ff
+option together with the
+.I \-fr
+option of
+.I pinterp.
+.PP
+To use
+.I pmblur
+with
+.I rpict,
+apply the
+.I \-S
+option to indicate a rendering sequence, and set the
+.I \-o
+option with a formatted file name to save multiple output
+pictures.
+When all the renderings are finished, combine them with the
+.I pcomb(1)
+program, using appropriate scalefactors to achieve an average.
+Note that using
+.I rpict
+is MUCH more expensive than using
+.I pinterp,
+and it is only recommended if the scene and application
+absolutely demand it (e.g. there is prominent refraction that
+must be modeled accurately).
+.PP
+For both
+.I pinterp
+and
+.I rpict,
+the computation time will be proportional to the number of views from
+.I pmblur.
+We have found a
+.I nsamp
+setting somewhere between 5 and 10 to be adequate for most images.
+Relatively larger values are appropriate for faster camera motion.
+.PP
+The
+.I \-pm
+option of
+.I rpict
+may be used instead or in combination to blur animated frames, with
+the added advantage of blurring reflections and refractions according
+to their proper motion.
+However, this option will result in more noise and expense than using
+.I pmblur
+with
+.I pinterp
+as a post-process.
+If both blurring methods are used, a smaller value should be given to the
+.I rpict
+.I \-pm
+option equal to the shutter speed divided by the number of pmblur views.
+This will be just enough to blur the boundaries of the ghosts
+which may appear using
+.I pmblur
+with a small number of time samples.
+.SH EXAMPLES
+To use
+.I pinterp
+to simulate motion blur between two frames of a walk-through
+animation, where the camera shutter is open for 1/4 of the
+interframe distance:
+.IP "" .2i
+pmblur .25 8 fr1023.hdr fr1024.hdr | pinterp \-B \-vf fr1023.hdr \-x 640 \-y 480
+fr1023.hdr fr1023.zbf fr1024.hdr fr1024.zbf > fr1023b.hdr
+.SH AUTHOR
+Greg Ward
+.SH BUGS
+Changes in the view shift and lift vectors or the fore and aft
+clipping planes are not blurred.
+.SH "SEE ALSO"
+pcomb(1), pdfblur(1), pinterp(1), pmdblur(1), rcalc(1), rpict(1), vwright(1)
diff -r d960df03359f -r a5d25b4668ac man/man1/pmdblur.1
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/man/man1/pmdblur.1	Sun Jun 26 16:57:40 2011 +0100
@@ -0,0 +1,133 @@
+.\" RCSid "$Id: pmdblur.1,v 1.4 2008/11/10 19:08:17 greg Exp $"
+.TH PMDBLUR 1 1/17/05 RADIANCE
+.SH NAME
+pmdblur - generate views for combined camera motion and depth blurring
+.SH SYNOPSIS
+.B pmdblur
+.B speed
+.B aperture
+.B nsamp
+.B v0file
+.B v1file
+.SH DESCRIPTION
+.I Pmdblur
+takes two viewfiles and generates
+.I nsamp
+views starting from
+.I v0file
+and moving towards
+.I v1file,
+simulating an aperture of diameter
+.I aperture
+in world coordinate units.
+When rendered and averaged together, these views will result in
+a picture with motion and depth-of-field
+blur due to a camera changing from v0 to v1
+in a relative time unit of 1, whose shutter is open starting at v0 for
+.I speed
+of these time units.
+Either
+.I pinterp(1)
+or
+.I rpict(1)
+may be called to do the actual work.
+(The given
+.I v0file
+must also be passed on the command line to the chosen renderer, since
+.I pmdblur
+provides supplemental view specifications only.)\0
+.PP
+For
+.I pinterp,
+feed the output of
+.I pmdblur
+to the standard input of
+.I pinterp
+and apply the
+.I \-B
+option to blur views together.
+In most cases, two pictures with z-buffers at v0 and v1 will
+get a satisfactory result, though the perfectionist may wish to
+apply the
+.I \-ff
+option together with the
+.I \-fr
+option of
+.I pinterp.
+.PP
+To use
+.I pmdblur
+with
+.I rpict,
+apply the
+.I \-S
+option to indicate a rendering sequence, and set the
+.I \-o
+option with a formatted file name to save multiple output
+pictures.
+When all the renderings are finished, combine them with the
+.I pcomb(1)
+program, using appropriate scalefactors to achieve an average.
+Note that using
+.I rpict
+is MUCH more expensive than using
+.I pinterp,
+and it is only recommended if the scene and application
+absolutely demand it (e.g. there is prominent refraction that
+must be modeled accurately).
+.PP
+For both
+.I pinterp
+and
+.I rpict,
+the computation time will be proportional to the number of views from
+.I pmdblur.
+We have found a
+.I nsamp
+setting somewhere between 7 and 15 to be adequate for most images.
+Relatively larger values are appropriate for faster camera motion.
+.PP
+The
+.I \-pm
+and/or
+.I \-pd
+options of
+.I rpict
+may be used instead or in combination to blur animated frames, with
+the added advantage of blurring reflections and refractions according
+to their proper motion.
+However, this option will result in more noise and expense than using
+.I pmdblur
+with
+.I pinterp
+as a post-process.
+If both blurring methods are used, a smaller value should be given to the
+.I rpict
+.I \-pm
+option equal to the shutter speed divided by the number of samples, and the
+.I \-pd
+option equal to the aperture divided by the number of samples.
+This will be just enough to blur the boundaries of the ghosts
+which may appear using
+.I pmdblur
+with a small number of time samples.
+.PP
+To simulate a particular camera's aperture, divide the focal length of
+the lens by the f-number, then convert to the corresponding
+world coordinate units.
+For example, if you wish to simulate a 50mm lens at f/2.0 in
+a scene modeled in meters, then you divide 50mm by 2.0 to get 25mm,
+which corresponds to an effective aperture of 0.025 meters.
+.SH EXAMPLES
+To use
+.I pinterp
+to simulate motion blur between two frames of a walk-through
+animation, where the camera shutter is open for 1/4 of the
+interframe distance with an aperture of 0.1 world units:
+.IP "" .2i
+pmdblur .25 .1 8 fr1023.hdr fr1024.hdr | pinterp \-B \-vf fr1023.hdr \-x 640 \-y 480
+fr1023.hdr fr1023.zbf fr1024.hdr fr1024.zbf > fr1023b.hdr
+.SH AUTHOR
+Greg Ward
+.SH "SEE ALSO"
+pcomb(1), pdfblur(1), pinterp(1), pmblur(1), rcalc(1), rpict(1), vwright(1)