| 1 |
< |
$Id$ |
| 1 |
> |
trad.hlp 2.18 10/20/98 |
| 2 |
|
|
| 3 |
|
This help file is associated with the trad interface to the Radiance |
| 4 |
|
rad(1) program. Trad consists of trad.wsh and one do_*.tcl file for |
| 5 |
< |
each screen. There are currently seven such screens: Action, File, |
| 6 |
< |
Options, Results, Scene, Views and Zone. |
| 5 |
> |
each screen. There are currently seven such screens: File, Scene, |
| 6 |
> |
Zone, Views, Options, Action and Results. |
| 7 |
|
|
| 8 |
|
.Trad.Intro |
| 9 |
|
|
| 48 |
|
curiosity in the main trad window. |
| 49 |
|
(In general, only active windows are given help file links -- click |
| 50 |
|
on these rather than the text labels.) |
| 51 |
+ |
Additional search capabilities are available over all topics using |
| 52 |
+ |
the "Grep" button. |
| 53 |
|
|
| 54 |
|
For help on the help facility itself, Control-click on the problem |
| 55 |
|
help widget or on the window title in the upper right corner for |
| 57 |
|
(To get back to trad-specific help, press the "HELP" button in the |
| 58 |
|
main trad window or Control-click on a trad widget.) |
| 59 |
|
|
| 58 |
– |
Once the help window has been displayed, it is usually best to |
| 59 |
– |
lower or iconify it rather than dismissing it if further help is |
| 60 |
– |
needed. |
| 61 |
– |
This way, you will not have to wait for the help file to be read in |
| 62 |
– |
all over again every time you have a question. |
| 63 |
– |
|
| 60 |
|
.Trad.Messages |
| 61 |
|
|
| 62 |
< |
Informative messages, commands executed by rad, and errors |
| 62 |
> |
Informative messages, commands executed by rad, and errors |
| 63 |
|
appear in the message window at the bottom of the trad frame. |
| 64 |
< |
Growing the trad window means growing this message window, and |
| 64 |
> |
Growing the trad window means growing this message window, and |
| 65 |
|
not much else. |
| 66 |
|
This is not really necessary, since the window will be grown |
| 67 |
|
automatically if the message requires it. |
| 335 |
|
|
| 336 |
|
.Scene.Revert |
| 337 |
|
|
| 338 |
< |
The "Revert" button is a convenient way to revert to the original |
| 338 |
> |
The "Revert" button is a convenient way to revert to the original |
| 339 |
|
values in the rad input file. |
| 340 |
|
Only the variables on the Scene screen will be affected, but any changes |
| 341 |
|
to these variables since the last save will be lost. |
| 349 |
|
walls, as it is used primarily to set rendering parameters and |
| 350 |
|
standard viewpoints. |
| 351 |
|
|
| 352 |
< |
An interior zone means that standard viewpoints will be selected |
| 352 |
> |
An interior zone means that standard viewpoints will be selected |
| 353 |
|
from the inside of this box. |
| 354 |
|
An exterior zone means that standard viewpoints will be selected |
| 355 |
|
from the outside of this box. |
| 356 |
< |
The default zone is an exterior one computed from the bounding box |
| 356 |
> |
The default zone is an exterior one computed from the bounding box |
| 357 |
|
of the entire scene. |
| 358 |
|
(Note that this is not usually desirable.) |
| 359 |
|
|
| 367 |
|
|
| 368 |
|
.Zone.Type |
| 369 |
|
|
| 370 |
< |
There are two types of zones understood by rad, "Interior" and |
| 370 |
> |
There are two types of zones understood by rad, "Interior" and |
| 371 |
|
"Exterior". |
| 372 |
< |
An interior zone is indicated when renderings generally take place |
| 372 |
> |
An interior zone is indicated when renderings generally take place |
| 373 |
|
inside a specified 3-d box. |
| 374 |
|
A typical example might be a single room or auditorium. |
| 375 |
|
An exterior zone is indicated when renderings generally take place |
| 398 |
|
size of the space. |
| 399 |
|
|
| 400 |
|
The Zone entry windows may be manipulated in the following ways. |
| 405 |
– |
Control-U clears the current window. |
| 401 |
|
Control-V pastes the contents of the current selection at the |
| 402 |
|
insertion point. |
| 403 |
|
Return moves the focus to the next window in the chain. |
| 404 |
|
|
| 405 |
+ |
The "Auto" button may be used to set these values based on the bounding |
| 406 |
+ |
box of one or more Radiance scene files. |
| 407 |
+ |
|
| 408 |
+ |
.Zone.Auto |
| 409 |
+ |
|
| 410 |
+ |
Use this button to automatically determine the bounding box for this |
| 411 |
+ |
zone, based on the output of the "getbbox" command run on one or |
| 412 |
+ |
more Radiance scene files. |
| 413 |
+ |
The appropriate scene files are entered via a file |
| 414 |
+ |
selection dialogue box, which comes up after the button is pressed. |
| 415 |
+ |
|
| 416 |
+ |
The reason for selecting specific files rather than running getbbox |
| 417 |
+ |
on the entire scene is that a zone usually does not include large |
| 418 |
+ |
external objects, which may be present in the complete scene |
| 419 |
+ |
description. |
| 420 |
+ |
|
| 421 |
|
.Zone.Detail |
| 422 |
|
|
| 423 |
|
The "Detail" setting indicates the relative level |
| 487 |
|
|
| 488 |
|
There are two basic ways to compute the exposure value. |
| 489 |
|
The first is by trial and error, where the value is adjusted up and |
| 490 |
< |
down within rview using the "e = value" command. |
| 490 |
> |
down within rvu using the "e = value" command. |
| 491 |
|
Though it sounds flaky, this is the most reliable way to set the |
| 492 |
|
exposure (and ambient level) in general lighting situations. |
| 493 |
|
|
| 505 |
|
(Divide total lumens by 179 lumens/watt to get watts.) |
| 506 |
|
|
| 507 |
|
The exposure value may either be given as a positive real value, or |
| 508 |
< |
as a real value preceeded by a '+' or '-' indicating a positive or |
| 508 |
> |
as a real value preceded by a '+' or '-' indicating a positive or |
| 509 |
|
negative number of f-stops (powers of two) from the original value. |
| 510 |
|
|
| 511 |
|
If no exposure is given, pfilt will automatically compute the |
| 516 |
|
|
| 517 |
|
The "Copy" button on the Zone screen takes all values for this |
| 518 |
|
screen from another rad input file, replacing the current values. |
| 519 |
< |
Specifically, the rad variables "ZONE, DETAIL, INDIRECT, |
| 519 |
> |
Specifically, the rad variables "ZONE, DETAIL, INDIRECT, |
| 520 |
|
VARIABILITY and EXPOSURE" will be copied from the named file. |
| 521 |
|
|
| 522 |
|
All other variables will be left untouched. |
| 523 |
|
|
| 524 |
|
.Zone.Revert |
| 525 |
|
|
| 526 |
< |
The "Revert" button is a convenient way to revert to the original |
| 526 |
> |
The "Revert" button is a convenient way to revert to the original |
| 527 |
|
values in the rad input file. |
| 528 |
|
Only the variables on the Zone screen will be affected, but any changes |
| 529 |
|
to these variables since the last save will be lost. |
| 535 |
|
"view" variable. |
| 536 |
|
Each view setting is listed by name, or by number if no name has |
| 537 |
|
been assigned. |
| 538 |
< |
To add a new view, enter a unique name and specify the view |
| 538 |
> |
To add a new view, enter a unique name and specify the view |
| 539 |
|
options, |
| 540 |
|
then press the "Add" or "Set Default" button. |
| 541 |
|
If a view with the same name already exists, it is unconditionally |
| 545 |
|
To remove an unwanted view, select it and press the "Delete" button. |
| 546 |
|
To undo this action, simply press the "Add" button again. |
| 547 |
|
|
| 548 |
< |
The first view in the list is the default given to rview during |
| 548 |
> |
The first view in the list is the default given to rvu during |
| 549 |
|
interactive rendering, and is the first view rendered in a batch run. |
| 550 |
|
To change the default view, select the newly desired view and press |
| 551 |
|
the "Set Default" button. |
| 580 |
|
|
| 581 |
|
Each view has a unique name, which may be chosen at the user's |
| 582 |
|
discretion or taken from a list of standard views, described below. |
| 583 |
< |
An invented name should be kept as short as possible, since it is |
| 583 |
> |
An invented name should be kept as short as possible, since it is |
| 584 |
|
added to the picture file name along with the standard ".pic" suffix. |
| 585 |
|
|
| 586 |
|
The standard views are specified by strings of the form |
| 587 |
< |
"[Xx]?[Yy]?[Zz]?[vlah]?". |
| 587 |
> |
"[Xx]?[Yy]?[Zz]?[vlahsc]?". |
| 588 |
|
(That is, an optional upper or lower case X followed by an optional |
| 589 |
|
upper or lower case Y followed by an optional upper or lower case Z |
| 590 |
< |
followed by an optional lower case V, L, A or H.) |
| 590 |
> |
followed by an optional lower case view type.) |
| 591 |
|
The letters indicate the desired view position, where upper case "X" |
| 592 |
|
means maximum X, lower case "y" means minimum Y and so on. |
| 593 |
|
The final letter is the view type, where 'v' is perspective (the |
| 594 |
< |
default), 'l' is parallel, 'a' is angular fisheye, and 'h' is |
| 595 |
< |
hemispherical fisheye. |
| 596 |
< |
A perspective view from maximum X, minimum Y would be "Xy" or |
| 597 |
< |
"Xyv". |
| 594 |
> |
default), 'l' is parallel, 'a' is angular fisheye, 'h' is |
| 595 |
> |
hemispherical fisheye, 's' is for planisphere (stereographic) fisheye, |
| 596 |
> |
and 'c' is for cylindrical panorama. |
| 597 |
> |
A perspective view from maximum X, minimum Y would be "Xy" or "Xyv". |
| 598 |
|
A parallel view from maximum Z would be "Zl". |
| 599 |
|
If "ZONE" is an interior zone, the standard views will |
| 600 |
|
be inside the perimeter. |
| 614 |
|
define a view. |
| 615 |
|
|
| 616 |
|
The simplest view specification is of the form "-vf viewfile", where |
| 617 |
< |
"viewfile" is a file created with the rview "view" command, or a |
| 617 |
> |
"viewfile" is a file created with the rvu "view" command, or a |
| 618 |
|
Radiance picture. |
| 619 |
|
This method of naming views, although convenient, is not the best |
| 620 |
|
since it is difficult to know exactly where such a view is by |
| 633 |
|
Consult the rpict(1) manual page for a full description of the various |
| 634 |
|
view options, all of which begin with "-v". |
| 635 |
|
Just briefly, the "-vt?" option sets the view type, where "?" is |
| 636 |
< |
replaced by one of the letters "v, l, a or h", corresponding to |
| 637 |
< |
perspective, parallel, angular and hemispherical fisheye, respectively. |
| 638 |
< |
The "-vp x y z" option sets the view position (eyepoint), where "x y z" |
| 636 |
> |
replaced by one of the letters "v, l, a, h, s or c", corresponding to |
| 637 |
> |
perspective, parallel, angular fisheye, hemispherical fisheye |
| 638 |
> |
and cylindrical panorama, respectively. |
| 639 |
> |
The "-vp x y z" option sets the view position (eyepoint), where "x y z" |
| 640 |
|
is replaced by the position in 3-space. |
| 641 |
|
The "-vd xd yd zd" option sets the view direction, where "xd yd zd" |
| 642 |
|
is a vector pointing in the desired direction. |
| 645 |
|
unnecessary.) |
| 646 |
|
The "-vh horiz" and "-vv vert" options set the horizontal and |
| 647 |
|
vertical view sizes, respectively. |
| 648 |
< |
For perspective views, these correspond to full camera angles in |
| 648 |
> |
For perspective views, these correspond to full camera angles in |
| 649 |
|
degrees. |
| 650 |
|
For parallel views (using the "-vtl" option), they correspond to |
| 651 |
|
image plane size in world coordinates. |
| 660 |
|
space between it and whatever follows. |
| 661 |
|
|
| 662 |
|
Hitting return in the "Options" window is equivalent to pressing the |
| 663 |
< |
"Add" button. |
| 663 |
> |
"Add" button followed by the "Clear" button. |
| 664 |
|
|
| 665 |
|
.Views.Add |
| 666 |
|
|
| 697 |
|
for the convenience of entering a new view. |
| 698 |
|
It has no effect on the rad input variables. |
| 699 |
|
|
| 688 |
– |
Note that Control-U will always clear an entry box whose cursor is |
| 689 |
– |
active. |
| 690 |
– |
|
| 700 |
|
.Views.Default |
| 701 |
|
|
| 702 |
|
The "Set Default" button may be used to make the selected view the |
| 703 |
|
default view for rendering. |
| 704 |
|
This simply moves the view to the top of the list in the rad input file. |
| 705 |
< |
The default view will be the one normally rendered by rview when rad |
| 705 |
> |
The default view will be the one normally rendered by rvu when rad |
| 706 |
|
is started interactively, and is the first view rendered in a batch |
| 707 |
|
process. |
| 708 |
|
|
| 719 |
|
the positive Y axis (+Y), the positive Z axis (+Z), the negative |
| 720 |
|
X axis (-X), the negative Y axis (-Y), or the negative Z axis (-Z). |
| 721 |
|
|
| 722 |
< |
This setting may always be overriden by the "-vu xd yd zd" option, |
| 722 |
> |
This setting may always be overridden by the "-vu xd yd zd" option, |
| 723 |
|
and will be altered for a particular view if it happens to be |
| 724 |
|
parallel to the view direction. |
| 725 |
|
|
| 726 |
+ |
.Views.Eyesep |
| 727 |
+ |
|
| 728 |
+ |
The eye separation is used for generating stereo views of |
| 729 |
+ |
the scene. |
| 730 |
+ |
It is the measured distance between a viewer's pupils in world |
| 731 |
+ |
coordinate units. |
| 732 |
+ |
It is not used directly by rad, but should be set for other programs |
| 733 |
+ |
that need it, such as rholo and glrad. |
| 734 |
+ |
|
| 735 |
|
.Views.Picture |
| 736 |
|
|
| 737 |
|
The root picture file name is given in the "Picture" entry window. |
| 767 |
|
|
| 768 |
|
The default value for this variable is "512". |
| 769 |
|
|
| 770 |
+ |
.Views.Rawfile |
| 771 |
+ |
|
| 772 |
+ |
The "Rawfile" entry window determines if and where the raw output picture |
| 773 |
+ |
from rpict will be saved. |
| 774 |
+ |
If the entry is empty, the file will be removed after rendering and |
| 775 |
+ |
filtering. |
| 776 |
+ |
This is the normal action, since the raw file |
| 777 |
+ |
takes up disk space and is not generally useful. |
| 778 |
+ |
However, if you wish to perform some special filtering function, |
| 779 |
+ |
this file can be renamed instead of removed by giving a |
| 780 |
+ |
root file name in this entry window. |
| 781 |
+ |
The final name in this case will be the given root plus and |
| 782 |
+ |
underscore plus the view name followed by a ".pic" suffix. |
| 783 |
+ |
|
| 784 |
+ |
In the special case when the raw file name and picture file name are |
| 785 |
+ |
the same, the raw file is saved and no filtering takes place. |
| 786 |
+ |
|
| 787 |
+ |
.Views.Zfile |
| 788 |
+ |
|
| 789 |
+ |
The "Zfile" entry window gives the root name of the file in which to |
| 790 |
+ |
store the raw (binary floating point) distances to pixels in the |
| 791 |
+ |
original generated image. |
| 792 |
+ |
If this entry is empty, then no z-file will be saved. |
| 793 |
+ |
|
| 794 |
+ |
The final z-file name will be the given root plus an underscore plus |
| 795 |
+ |
the view name plus a ".zbf" suffix. |
| 796 |
+ |
|
| 797 |
+ |
To convert this image to human-readable form, the program "od" will |
| 798 |
+ |
work on some systems, or the Radiance "pvalue" program may be used |
| 799 |
+ |
to first convert it to a greyscale Radiance picture using the |
| 800 |
+ |
options "-r -h -b -df `getinfo -d < pictname`" where "pictname" is |
| 801 |
+ |
replaced by the raw picture file name. |
| 802 |
+ |
(Getinfo simply gets the original image dimensions, which are not |
| 803 |
+ |
stored in the z-file.) |
| 804 |
+ |
|
| 805 |
|
.Views.Copy |
| 806 |
|
|
| 807 |
|
The "Copy" button in the Views screen permits those variables |
| 814 |
|
|
| 815 |
|
.Views.Revert |
| 816 |
|
|
| 817 |
< |
The "Revert" button is a convenient way to revert to the original |
| 817 |
> |
The "Revert" button is a convenient way to revert to the original |
| 818 |
|
values in the rad input file. |
| 819 |
|
Only the variables on the Views screen will be affected, but any changes |
| 820 |
|
to these variables since the last save will be lost. |
| 838 |
|
minutes) between progress reports. |
| 839 |
|
|
| 840 |
|
Other windows allow the user to customize the options to oconv(1), |
| 841 |
< |
mkillum(1), rview(1) and rpict(1), and pfilt(1). |
| 841 |
> |
mkillum(1), rvu(1) and rpict(1), and pfilt(1). |
| 842 |
|
|
| 843 |
|
.Options.Quality |
| 844 |
|
|
| 873 |
|
|
| 874 |
|
.Options.Penumbras |
| 875 |
|
|
| 876 |
< |
The "Penumbras" setting determines whether or not Radiance will |
| 876 |
> |
The "Penumbras" setting determines whether or not Radiance will |
| 877 |
|
make a special effort to generate soft shadows from area light sources. |
| 878 |
|
Since this is a potentially expensive calculation, penumbras should |
| 879 |
|
only be switched "On" when they are really needed. |
| 883 |
|
It only means that some accuracy and possibly some smoothness |
| 884 |
|
will be traded for speed in the shadow calculations. |
| 885 |
|
|
| 886 |
+ |
.Options.Pgmap |
| 887 |
+ |
|
| 888 |
+ |
The "Pgmap" specifies the file to hold the global photons computed |
| 889 |
+ |
by the "mkpmap" command, followed by the number of photons to generate |
| 890 |
+ |
(required). |
| 891 |
+ |
A typical photon count for a global map is on the order of 100-200K. |
| 892 |
+ |
By convention, photon map files are given a ".pmp" suffix. |
| 893 |
+ |
An optional third parameter specifies the bandwidth to use |
| 894 |
+ |
for the global photons during rendering, and this value should be |
| 895 |
+ |
around 50. |
| 896 |
+ |
|
| 897 |
+ |
.Options.PgmDelete |
| 898 |
+ |
|
| 899 |
+ |
The "Delete" button next to the "Pgmap" window on the Options |
| 900 |
+ |
screen allows you to remove the named global photon map file. |
| 901 |
+ |
This is usually done when a change is made to the "mkpmap" options, |
| 902 |
+ |
as the file will be regenerated automatically after most scene changes. |
| 903 |
+ |
|
| 904 |
+ |
.Options.Pcmap |
| 905 |
+ |
|
| 906 |
+ |
The "Pcmap" specifies the file to hold the caustic photons computed |
| 907 |
+ |
by the "mkpmap" command, followed by the number of photons to generate |
| 908 |
+ |
(required). |
| 909 |
+ |
A typical photon count for a global map is on the order of 1000K. |
| 910 |
+ |
By convention, photon map files are given a ".pmp" suffix. |
| 911 |
+ |
An optional third parameter specifies the bandwidth to use |
| 912 |
+ |
for the global photons during rendering, and this value should be |
| 913 |
+ |
around 50. |
| 914 |
+ |
|
| 915 |
+ |
.Options.PcmDelete |
| 916 |
+ |
|
| 917 |
+ |
The "Delete" button next to the "Pcmap" window on the Options |
| 918 |
+ |
screen allows you to remove the named caustic photon map file. |
| 919 |
+ |
This is usually done when a change is made to the "mkpmap" options, |
| 920 |
+ |
as the file will be regenerated automatically after most scene changes. |
| 921 |
+ |
|
| 922 |
|
.Options.Ambfile |
| 923 |
|
|
| 924 |
|
The "Ambfile" is the file used to store Radiance ambient values for |
| 937 |
|
|
| 938 |
|
.Options.AmbDelete |
| 939 |
|
|
| 940 |
< |
The "Delete" button next to the "Ambfile" window on the Options |
| 940 |
> |
The "Delete" button next to the "Ambfile" window on the Options |
| 941 |
|
screens allows you to remove the named ambient file. |
| 942 |
|
This is usually done when a change to one or more rad variables |
| 943 |
|
casts doubt on the accuracy of the values stored in this file. |
| 952 |
|
|
| 953 |
|
The "Optfile" setting assigns a file to hold rendering options, |
| 954 |
|
which may be a convenience when these options are reused for |
| 955 |
< |
rtrace(1) or rpiece(1), or manual invocations of rview or rpict. |
| 955 |
> |
rtrace(1) or rpiece(1), or manual invocations of rvu or rpict. |
| 956 |
|
Using an options file also reduces the size of the command line, |
| 957 |
|
making it a little easier on the eye. |
| 958 |
|
|
| 968 |
|
Normally, progress reports and errors during batch renderings |
| 969 |
|
are sent to the error file given by the root of the rad input |
| 970 |
|
file name followed by the ".err" suffix. |
| 971 |
< |
(See the "Errors" topic under the "Action" screen category.) |
| 971 |
> |
(See the "CheckErr" topic under the "Action" screen category.) |
| 972 |
|
If you wish these reports and errors to be directed to a different |
| 973 |
|
file, follow the time interval by a space and a file name. |
| 974 |
|
|
| 975 |
|
No setting on this variable means do not report rendering progress. |
| 976 |
< |
A zero setting means the same thing, and may be used when a |
| 976 |
> |
A zero setting means the same thing, and may be used when a |
| 977 |
|
separate error file is desired but progress reports are not. |
| 978 |
|
|
| 979 |
|
.Options.Oconv |
| 1003 |
|
.Options.Mkillum |
| 1004 |
|
|
| 1005 |
|
The "mkillum opts" window may be used to specify options to the |
| 1006 |
< |
mkillum(1) command, whose options are actually passed to rtrace(1). |
| 1006 |
> |
mkillum(1) command. |
| 1007 |
|
These options apply only if there are one or more "Illum" files |
| 1008 |
|
named on the Scene screen. |
| 1009 |
|
|
| 1010 |
|
It is very important to set mkillum options sensibly, |
| 1011 |
|
since rad does not have the intelligence to do it for you. |
| 1012 |
|
|
| 1013 |
+ |
.Options.Mkpmap |
| 1014 |
+ |
|
| 1015 |
+ |
The "mkpmap opts" window may be used to specify options |
| 1016 |
+ |
to the mkpmap(1) command. |
| 1017 |
+ |
There are no default values, and rad does not set these |
| 1018 |
+ |
options intelligently. |
| 1019 |
+ |
|
| 1020 |
|
.Options.Render |
| 1021 |
|
|
| 1022 |
|
The "render opts" window is used to specify additional options to |
| 1023 |
< |
the rview(1) and rpict(1) rendering programs. |
| 1024 |
< |
Most of the important parameters are computed by rad, so this |
| 1023 |
> |
the rvu(1) and rpict(1) rendering programs. |
| 1024 |
> |
Most of the important parameters are computed by rad, so this |
| 1025 |
|
window is usually used to override specific parameters or to give |
| 1026 |
|
additional information, such as which materials to exclude from the |
| 1027 |
|
interreflection calculation. |
| 1069 |
|
run, usually via rad(1). |
| 1070 |
|
The top row of buttons is used to update the octree following a |
| 1071 |
|
change to one or more input files. |
| 1072 |
< |
The "rview" button starts an interactive rendering in the |
| 1072 |
> |
The "rvu" button starts an interactive rendering in the |
| 1073 |
|
foreground. |
| 1074 |
|
The next set of buttons provides for the control of a batch |
| 1075 |
|
rendering process, taking place in the background. |
| 1076 |
|
Finally, the bottom set of buttons allows you to preview what would |
| 1077 |
< |
happen during a batch rendering, or (equivalently) make a script of |
| 1077 |
> |
happen during a batch rendering, or (equivalently) make a script of |
| 1078 |
|
UNIX commands for later execution. |
| 1079 |
|
|
| 1080 |
|
When the Action screen is first brought up, the message window |
| 1147 |
|
(This will still cause the ambient file to be removed, |
| 1148 |
|
unfortunately.) |
| 1149 |
|
|
| 1150 |
< |
.Action.Rview |
| 1150 |
> |
.Action.Rvu |
| 1151 |
|
|
| 1152 |
< |
The "rview" button on the Action screen starts an interactive |
| 1153 |
< |
rendering for the selected view, indicated by the menu button |
| 1152 |
> |
The "rvu" button on the Action screen starts an interactive |
| 1153 |
> |
rendering for the selected view, indicated by the menu button |
| 1154 |
|
just to the right. |
| 1155 |
< |
Other views may be accessed within rview using the "L name" |
| 1156 |
< |
command, and new views can be added with the "V name" |
| 1155 |
> |
Other views may be accessed within rvu using the "L name" |
| 1156 |
> |
command, and new views can be added with the "V name" |
| 1157 |
|
command. |
| 1062 |
– |
(See the rview(1) man page and the "View" topic in the current |
| 1063 |
– |
help category for more information.) |
| 1158 |
|
|
| 1159 |
< |
If the octree is out-of-date, it will be rebuilt before rendering |
| 1159 |
> |
When using the "V" command to change an existing view, do not |
| 1160 |
> |
give it an existing name because the previous view will not be overridden. |
| 1161 |
> |
Instead, give it a new name (or no name, which will show up as |
| 1162 |
> |
a number later), then use the Views screen to override the previous |
| 1163 |
> |
view definition with the new one. |
| 1164 |
> |
(See the "View" topic in the current |
| 1165 |
> |
help category, the "Change" topic under "Views" and the rvu(1) |
| 1166 |
> |
manual page for more information.) |
| 1167 |
> |
|
| 1168 |
> |
If the octree is out-of-date, it will be rebuilt before rendering |
| 1169 |
|
begins. |
| 1170 |
|
|
| 1171 |
|
.Action.View |
| 1172 |
|
|
| 1173 |
|
The Action screen contains two menus for selecting views. |
| 1174 |
< |
The top menu, next to the "rview" button, sets the view to start |
| 1175 |
< |
with in rview, and is selected from the current view list. |
| 1176 |
< |
The second view menu, next to the "Start" button for batch |
| 1174 |
> |
The top menu, next to the "rvu" button, sets the view to start |
| 1175 |
> |
with in rvu, and is selected from the current view list. |
| 1176 |
> |
The second view menu, next to the "Start" button for batch |
| 1177 |
|
rendering, selects the view or views to render in batch mode. |
| 1178 |
< |
If the special entry "ALL" is selected, then every view in the |
| 1178 |
> |
If the special entry "ALL" is selected, then every view in the |
| 1179 |
|
current list will be rendered if it hasn't been already. |
| 1180 |
|
|
| 1181 |
< |
The batch rendering view menu also selects the view or views |
| 1181 |
> |
The view menu next to the "rvu" button will be disabled if there |
| 1182 |
> |
is only one view to choose from. |
| 1183 |
> |
The view menu next to the "Start" button will be disabled if there |
| 1184 |
> |
is a batch job in progress, and thus the view cannot be changed. |
| 1185 |
> |
|
| 1186 |
> |
The batch rendering view menu also selects the view or views |
| 1187 |
|
to use in producing a script during a dry run. |
| 1188 |
|
|
| 1189 |
+ |
.Action.Processes |
| 1190 |
+ |
|
| 1191 |
+ |
The "Number of processes" slider controls how many independent |
| 1192 |
+ |
processes are initiated by the "rvu" and "Start" buttons above |
| 1193 |
+ |
and below. |
| 1194 |
+ |
This should be set no greater than the number of virtual cores |
| 1195 |
+ |
on your system. |
| 1196 |
+ |
|
| 1197 |
+ |
For interactive rendering, the "new" command within rvu may |
| 1198 |
+ |
be used to change the number of processes running. |
| 1199 |
+ |
|
| 1200 |
+ |
For rendering in the background, the number of processes will |
| 1201 |
+ |
never be greater than the number of views if all views are |
| 1202 |
+ |
being rendered. |
| 1203 |
+ |
If only a single view is selected for rendering, rad |
| 1204 |
+ |
will call rpiece to render it in tiles using the given |
| 1205 |
+ |
number of processes. |
| 1206 |
+ |
|
| 1207 |
|
.Action.Start |
| 1208 |
|
|
| 1209 |
< |
The "Start" button for batch rendering on the Action screen |
| 1210 |
< |
initiates a rad rendering process in the background using the |
| 1209 |
> |
The "Start" button for batch rendering on the Action screen |
| 1210 |
> |
initiates a rad rendering process in the background using the |
| 1211 |
|
selected view or views shown on the menu button to the right. |
| 1212 |
|
|
| 1213 |
|
If any of the rad variables have been changed since the |
| 1216 |
|
If you discard these changes, then the batch rendering will be |
| 1217 |
|
conducted using the previously saved values. |
| 1218 |
|
|
| 1219 |
< |
Once a background process is going, the "Start" button is |
| 1220 |
< |
disabled, and rendering progress can be monitored by checking |
| 1219 |
> |
Once a background process is going, the "Start" button is |
| 1220 |
> |
disabled, and rendering progress can be monitored by checking |
| 1221 |
|
the error file periodically. |
| 1222 |
< |
(This file is named by the root of the rad input file followed by |
| 1222 |
> |
(This file is named by the root of the rad input file followed by |
| 1223 |
|
".err".) |
| 1224 |
< |
When a batch process is started or already running, this button |
| 1225 |
< |
will be disabled. |
| 1224 |
> |
When a batch process is started or already running, or when a |
| 1225 |
> |
process is on another host and its status is unknown, |
| 1226 |
> |
this button will be disabled. |
| 1227 |
|
|
| 1228 |
< |
The background process can be killed during this or later |
| 1228 |
> |
The background process can be killed during this or later |
| 1229 |
|
invocations of trad using the "Kill" button. |
| 1230 |
+ |
If the process was started on another machine and the status is unknown, |
| 1231 |
+ |
it will be necessary to run trad from the other host or remove the error |
| 1232 |
+ |
file manually before starting a background process on this machine. |
| 1233 |
+ |
This is to protect you from the great confusion that results when two |
| 1234 |
+ |
machines are working from the same project file. |
| 1235 |
|
|
| 1236 |
|
.Action.Kill |
| 1237 |
|
|
| 1238 |
< |
The batch rendering "Kill" button kills the |
| 1238 |
> |
The batch rendering "Kill" button kills the |
| 1239 |
|
background process started earlier with the "Start" button. |
| 1240 |
< |
The rad process id is taken from the first line of the error file, |
| 1240 |
> |
The rad process id is taken from the first line of the error file, |
| 1241 |
|
and this process and all its children are killed when the |
| 1242 |
|
button is pressed. |
| 1243 |
|
|
| 1244 |
< |
So long as there is an ambient file specified in the Options |
| 1245 |
< |
screen, no data is lost by killing and restarting a batch |
| 1244 |
> |
So long as there is an ambient file specified in the Options |
| 1245 |
> |
screen, no data is lost by killing and restarting a batch |
| 1246 |
|
rendering, though some new startup costs will be incurred. |
| 1247 |
|
|
| 1248 |
< |
The "Kill" button is disabled if no running batch process is |
| 1249 |
< |
detected. |
| 1248 |
> |
The "Kill" button is disabled if no running batch process is |
| 1249 |
> |
detected on the current host machine. |
| 1250 |
|
|
| 1251 |
|
.Action.CheckErr |
| 1252 |
|
|
| 1253 |
|
Pressing the "Check errors" button |
| 1254 |
< |
displays the contents of the batch rendering error file, named |
| 1255 |
< |
by the root of the current rad input file followed by the ".err" |
| 1254 |
> |
displays the contents of the batch rendering error file, named |
| 1255 |
> |
by the root of the current rad input file followed by the ".err" |
| 1256 |
|
suffix. |
| 1257 |
< |
This file will contain the command lines executed by rad so far, |
| 1258 |
< |
and may or may not contain additional progress reports from |
| 1257 |
> |
This file will contain the command lines executed by rad so far, |
| 1258 |
> |
and may or may not contain additional progress reports from |
| 1259 |
|
rpict, depending on the initial setting of the "REPORT" variable. |
| 1260 |
|
|
| 1261 |
|
If no error file exists, this button will be disabled. |
| 1263 |
|
.Action.Script |
| 1264 |
|
|
| 1265 |
|
The dry run "Script" button runs rad with the |
| 1266 |
< |
"-n" option so that you may see the commands that would be |
| 1266 |
> |
"-n" option so that you may see the commands that would be |
| 1267 |
|
executed during a batch run without actually executing them. |
| 1268 |
< |
If a file is named in the window next to this button, the output |
| 1268 |
> |
If a file is named in the window next to this button, the output |
| 1269 |
|
will simply be written to that file. |
| 1270 |
< |
If no file is named, a temporary file is created and an editor |
| 1270 |
> |
If no file is named, a temporary file is created and an editor |
| 1271 |
|
window is opened on it. |
| 1272 |
|
|
| 1273 |
|
Producing a dry run also writes the "Optfile" if one is specified |
| 1275 |
|
This may be useful for computing rendering parameters for rtrace(1) |
| 1276 |
|
or rpiece(1). |
| 1277 |
|
|
| 1278 |
< |
The view or views are selected by the same menu used for |
| 1278 |
> |
The view or views are selected by the same menu used for |
| 1279 |
|
batch rendering. |
| 1280 |
< |
(See the "View" topic under the current help category for more |
| 1280 |
> |
(See the "View" topic under the current help category for more |
| 1281 |
|
information.) |
| 1282 |
|
|
| 1283 |
|
.Action.Edit |
| 1284 |
|
|
| 1285 |
< |
The dry run "Edit" button is used to edit the named script file |
| 1285 |
> |
The dry run "Edit" button is used to edit the named script file |
| 1286 |
|
created by pressing the "Script" button. |
| 1287 |
|
If no file is named, this button is ineffective. |
| 1288 |
|
|
| 1289 |
|
.Action.Delete |
| 1290 |
|
|
| 1291 |
< |
The "Delete" button removes the named script file, created by the |
| 1291 |
> |
The "Delete" button removes the named script file, created by the |
| 1292 |
|
"Script" button. |
| 1293 |
< |
If no file is named, or the named file does not exist, this button has |
| 1293 |
> |
If no file is named, or the named file does not exist, this button has |
| 1294 |
|
no effect. |
| 1295 |
|
|
| 1296 |
|
.Results.Intro |
| 1297 |
|
|
| 1298 |
|
This button selects the trad Results screen. |
| 1299 |
< |
This screen permits rendered pictures to be displayed, |
| 1299 |
> |
This screen permits rendered pictures to be displayed, |
| 1300 |
|
converted to other image formats, and printed. |
| 1301 |
< |
Only finished pictures may be converted or printed, but |
| 1302 |
< |
incomplete pictures (i.e. aborted renderings or renderings in |
| 1301 |
> |
Only finished pictures may be converted or printed, but |
| 1302 |
> |
incomplete pictures (i.e. aborted renderings or renderings in |
| 1303 |
|
progress) may be displayed interactively. |
| 1304 |
|
|
| 1305 |
|
The left-hand window shows a list of completed views, and the |
| 1306 |
< |
right-hand window shows views that have been started but not |
| 1306 |
> |
right-hand window shows views that have been started but not |
| 1307 |
|
finished. |
| 1308 |
< |
Note that other views may not even be started, thus may not |
| 1308 |
> |
Note that other views may not even be started, thus may not |
| 1309 |
|
appear in either list. |
| 1310 |
< |
Also, just because a view appears on the Results screen, it does |
| 1311 |
< |
not mean that view is up-to-date with respect to the Radiance |
| 1310 |
> |
Also, just because a view appears on the Results screen, it does |
| 1311 |
> |
not mean that view is up-to-date with respect to the Radiance |
| 1312 |
|
input files. |
| 1313 |
< |
(The best way currently to tell which pictures are out-of-date |
| 1314 |
< |
is to press the "Script" button on the Action screen and examine |
| 1313 |
> |
(The best way currently to tell which pictures are out-of-date |
| 1314 |
> |
is to press the "Script" button on the Action screen and examine |
| 1315 |
|
the output.) |
| 1316 |
|
|
| 1317 |
|
.Results.Finished |
| 1344 |
|
|
| 1345 |
|
.Results.Rescan |
| 1346 |
|
|
| 1347 |
< |
The "Rescan" button on the Results screen is used to update the |
| 1348 |
< |
finished and unfinished view lists, in case one or more pictures |
| 1347 |
> |
The "Rescan" button on the Results screen is used to update the |
| 1348 |
> |
finished and unfinished view lists, in case one or more pictures |
| 1349 |
|
has completed since the Results screen was brought up. |
| 1350 |
|
|
| 1351 |
|
.Results.Delete |
| 1352 |
|
|
| 1353 |
|
The "Delete" button on the Results screen is used to remove the |
| 1354 |
|
selected picture files from the filesystem. |
| 1355 |
+ |
Associated raw picture and z-buffer files |
| 1356 |
+ |
will also be deleted if they exist. |
| 1357 |
|
Verification is required before any action is taken. |
| 1358 |
|
|
| 1359 |
|
.Results.Display |
| 1441 |
|
The print command window on the Results screen contains the system |
| 1442 |
|
command to use in printing out finished Radiance pictures. |
| 1443 |
|
The "%s" format field, which must appear somewhere in the command, |
| 1444 |
< |
is replaced by the selected Radiance picture file name(s). |
| 1444 |
> |
is replaced by the selected Radiance picture file name. |
| 1445 |
> |
This command is executed multiple times if multiple files are |
| 1446 |
> |
selected. |
| 1447 |
|
|
| 1448 |
|
The default command is "ra_ps %s | lpr", which converts the Radiance |
| 1449 |
|
picture to a black and white PostScript file and sends it to the lpr |
| 1450 |
|
print spooler. |
| 1451 |
+ |
Add a "-c" option to "ra_ps" if the printer supports color. |
| 1452 |
|
If your printer does not understand PostScript, or your system does |
| 1453 |
|
not support lpr, this command must obviously be changed. |
