1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>viewgam</title>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<meta name="author" content="Graeme Gill">
</head>
<body>
<h2><b>gamut/viewgam</b></h2>
<h3>Summary</h3>
Convert one or more gamuts into a <a
href="File_Formats.html#X3DOM">X3DOM</a> 3D visualization file.
This allows visual comparison of several gamut surfaces.<br>
Also allows creating the intersection (overlap) between two gamuts.
This is useful in measuring and visualizing the coverage of one
gamut of another.<br>
<br>
See <a href="3dformat.html">3D Viewing Format</a> for switching to
VRML or X3D output format.<br>
<h3>Usage<br>
</h3>
<small><span style="font-family: monospace;">viewgam { [-c color]
[-t trans] [-w|s] </span><span style="font-style: italic;
font-family: monospace;">infile.gam</span><span
style="font-family: monospace;"> } ... </span><span
style="font-style: italic; font-family: monospace;">outfile.x3d.html</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">
For
each input gamut file:</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -c </span><i
style="font-family: monospace;">color</i><span
style="font-family: monospace;">
Color
to
make
gamut, r = red, g = green, b = blue</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">
c
= cyan, m = magenta, y = yellow, w = white</span><br
style="font-family: monospace;">
<span style="font-family: monospace;">
n
= natural color</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -t </span><i
style="font-family: monospace;">trans</i><span
style="font-family: monospace;">
Set
transparency
from
0.0 (opaque) to 1.0 (invisible)</span><br style="font-family:
monospace;">
<span style="font-family: monospace;"> -w
Show
as a wireframe</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -s
Show
as a solid surface</span><br style="font-family: monospace;">
<i style="font-family: monospace;"> infile.gam</i><span
style="font-family: monospace;">
Name of </span><i style="font-family: monospace;">infile</i><a
style="font-family: monospace;" href="File_Formats.html#.gam">.gam</a><span
style="font-family: monospace;"> file</span><br
style="font-family: monospace;">
<br style="font-family: monospace;">
<span style="font-family: monospace;"> -n
Don't
add Lab axes<br>
-i Compute and
print intersecting volume of first 2 gamuts<br>
-I isect.gam Same as -i, but save intersection
gamut to isect.gam<br style="font-family: monospace;">
</span><span style="font-family: monospace;"> </span><i
style="font-family: monospace;">outfile </i><span
style="font-family: monospace;"><i> </i>Base
name of output </span><i style="font-family: monospace;">outfile.x3d.html</i><span
style="font-family: monospace;"> file</span></small> <br>
<h3>Usage Details and Discussion</h3>
<b>viewgam</b> creates a X3DOM file that allows the viewing
and comparing of multiple gamut files by representing them as solid
surfaces, wireframes, etc. It takes as input a list of gamut files,
each file preceded by any options that are to apply to the display
of that particular gamut. <br>
<br>
The options that can be specified for each input gamut are:<br>
<br>
<b>-c</b> <i>color</i> allows the color of the surface or wireframe
to be specified. Any of a number of predefined colors (red, green,
blue, cyan, magenta, yellow, white) can be used, as well as allowing
the color to reflect the natural color of that point in the
colorspace.<br>
<br>
<b>-t</b> <i>trans</i> allows the transparency of the surface
to be specified. A value of 0.2 might be a good place to start.
Using transparency generally leads to a slower display than the
default opaque surface treatment, but can make it possible to see
within a solid gamut surface.<br>
<br>
<b>-w</b> forces the gamut surface to be rendered as a wireframe.<br>
<br>
<b>-s</b> forces the gamut surface to be rendered as a solid
surface.<br>
<br>
By default, the first gamut is treated as a solid with natural
coloring, with the second and subsequent gamuts being wireframes
with colors of white, red, cyan, yellow, green and blue, with
decreasing visibility.<br>
<br>
The <b>-n</b> flag turns off display of the default L*a*b* axes in
the output.<br>
<br>
The <span style="font-weight: bold;">-i</span> flag computes the
intersecting volume of the first two gamuts (in cubic color units,
usually L*a*b*), as well as the volumes of the two gamuts and the
percentage the intersection is of the two gamuts. This is a useful
measure of the coverage one gamut has of another. If <span
style="font-weight: bold;">-I</span> is used, then as well as
printing the volume, the intersecting gamut will be saved to the <span
style="font-style: italic;">isect.gam</span> file.<br>
<br>
The final argument is the base name of the X3DOM file to save the
resulting composite 3D visualization file to. If the name given
doesn't have an extension, one will be automatically added.<br>
<br>
</body>
</html>
|
