1 |
.\" |
2 |
.TH "LTVIEW" "1" "08/04/14" "RADIANCE" "" |
3 |
.SH "NAME" |
4 |
ltview \- view photometry of a light source |
5 |
.SH "SYNOPSIS" |
6 |
.B ltview |
7 |
[ |
8 |
.B \-i |
9 |
][ |
10 |
.B "\-b boxsize" |
11 |
][ |
12 |
.B "\-o device" |
13 |
] |
14 |
input |
15 |
.SH "DESCRIPTION" |
16 |
.I ltview |
17 |
renders a Radiance luminiare or IES photometry interactively using |
18 |
.I rad(1). |
19 |
.PP |
20 |
.I ltview |
21 |
accepts exactly one Radiance object or IES photometry |
22 |
file as input. No input is taken from STDIN. The |
23 |
.I \-i |
24 |
option tells it that the input file contains |
25 |
IES photometry rather then a Radiance description of a |
26 |
luminiare. In this case, Radiance's |
27 |
.I ies2rad(1) |
28 |
is called with its default settings to convert the IES file into a |
29 |
Radiance object. |
30 |
.PP |
31 |
Unlike |
32 |
.I objpict(1) |
33 |
or |
34 |
.I objview(1), |
35 |
no additional light sources are added to the scene, since it is |
36 |
assumed that the object is a luminaire. |
37 |
.PP |
38 |
.I ltview |
39 |
relies on Radiance's |
40 |
.I rad(1) |
41 |
command to compile an octree using |
42 |
.I oconv(1) |
43 |
and to call |
44 |
.I rvu(1) |
45 |
to display an interactive preview of the luminaire. |
46 |
The luminaire, or output from |
47 |
.I ies2rad(1), |
48 |
is moved so that its center is at world origin. |
49 |
.I ltview |
50 |
then generates an open box around the fitting that is ten times |
51 |
as big as the largest axis\-aligned dimension of the fitting. |
52 |
The \-y face of the box is left open so that |
53 |
the camera can look inside, facing +y. |
54 |
The overall dimensions of the enclosing box may be overwritten with the |
55 |
.I "\-b boxsize" |
56 |
option. Note that both the fitting and the box are always centred at the |
57 |
origin. |
58 |
.PP |
59 |
When |
60 |
.I ltview |
61 |
is run with the |
62 |
.I \-i |
63 |
option, i.e. the file is an IES photometry file, |
64 |
then the dimensions of the luminaire and intesity of its |
65 |
output are determined by |
66 |
.I ies2rad(1)'s |
67 |
default settings. If this is not acceptable, then it is best to run |
68 |
.I ies2rad(1) |
69 |
manually, and to feed |
70 |
.I ltview |
71 |
the hand\-crafted fitting, rather than the IES photometry. In any case, |
72 |
it is likely that the initial exposure within the |
73 |
.I rvu(1) |
74 |
window window needs to be adjusted before the distribution of the fitting |
75 |
can be fully appreciated. |
76 |
.PP |
77 |
The default |
78 |
.I rvu(1) |
79 |
output device is |
80 |
.I x11 |
81 |
on all platforms except for Windows, where it is set to |
82 |
.I qt. |
83 |
This may be overwritten with the |
84 |
.I "\-o output" |
85 |
option. |
86 |
|
87 |
.SH "EXAMPLES" |
88 |
To query available output devices |
89 |
.IP "" .2i |
90 |
rvu \-devices |
91 |
.PP |
92 |
To visualise an IES file with the qt driver |
93 |
.IP "" .2i |
94 |
ltview \-o qt ABC123.ies |
95 |
.PP |
96 |
To look at a typical fluorescent fitting that is modelled in millimeters |
97 |
.IP "" .2i |
98 |
ltview \-b 5000 XYZ_batten.rad |
99 |
.SH "AUTHOR" |
100 |
Axel Jacobs |
101 |
.SH "SEE ALSO" |
102 |
ltpict(1), ies2rad(1), oconv(1), rad(1), rvu(1) |