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
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>invprofcheck</title>
<meta http-equiv="content-type"
content="text/html; charset=ISO-8859-1">
<meta name="author" content="Graeme Gill">
</head>
<body>
<h2><b>profile/invprofcheck</b></h2>
<h3>Summary</h3>
Check <a href="File_Formats.html#ICC">ICC</a> forward against reverse
lookup.
<br>
<h3>Usage Summary</h3>
<small><span style="font-family: monospace;">usage: invprofcheck
[-options] </span><span
style="font-style: italic; font-family: monospace;">profile.icm</span><br
style="font-family: monospace;">
<span style="font-family: monospace;"> -v [level]
verbosity level (default 1), 2 to print each DE</span><br
style="font-family: monospace;">
<span style="font-family: monospace;"> -l
limit set total ink
limit (estimate by default)<br>
</span></small><small><span style="font-family: monospace;"> -L
klimit set black channel ink
limit (estimate by default)</span></small><br
style="font-family: monospace;">
<small><span style="font-family: monospace;"></span><span
style="font-family: monospace;"> -h
high res test (27)</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -u
Ultra high res test (61)<br>
-R res Specific grid
resolution<br style="font-family: monospace;">
</span><span style="font-family: monospace;"> -c
Show CIE94 delta E values</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -k
Show CIEDE2000 delta E values</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -w
create X3DOM visualisation (profile.x3d.html)</span><br
style="font-family: monospace;">
<span style="font-family: monospace;"> -x
Use X3DOM axes</span><br style="font-family: monospace;">
<span style="font-family: monospace;"> -e
Color vectors acording to delta E</span><br
style="font-family: monospace;">
<span style="font-style: italic; font-family: monospace;"> profile.icm</span><span
style="font-family: monospace;">
Profile to check</span></small>
<br>
<h3>Usage Details and Discussion</h3>
<b>invprofcheck</b> provides a way of checking how well an <a
href="File_Formats.html#ICC">ICC</a> profile inverse transform inverts
the forward transform. For devices with more than 4 channels, a total
ink limit is assumed, and (if no <span style="font-weight: bold;">-l</span>
parameter is given) a reasonable number is deduced from the reverse
table. A grid of device values is created, and the transform from
PCS->device, and then device->PCS is computed in L*a*b* space.
The average, maximum and RMS error delta E values are computed and
displayed in the chosen delta E metric. A <a
href="File_Formats.html#X3DOM">X3DOM</a> plot of the error vectors can
be created. <span style="font-weight: bold;">invprofcheck</span> tries
to only test in-gamut color values. Note that because it scans a device
grid, for a CMYK device, the density of test points will be
progressively higher in the dark regions, and the average and RMS
values will be distorted by the denser sampling.<br>
<br>
The <b>-v</b> flag prints out extra information during the checking. A
value greater than 1 will print the color values of each test point.<br>
<br>
The <b>-l</b> flag allows setting a total ink limit (TAC) for printing
devices. If a device has a total ink limit, and hasn't been
characterised with device values above this limit, then plotting the
gamut in these areas will almost certainly be misleading. The ink limit
will be in final calibrated device values if the profile includes
calibration information.<br>
<br>
The <b>-L</b> flag allows setting a black channel ink limit for
printing
devices. If a device has a black ink limit, and hasn't been
characterised with device values above this limit, then plotting the
gamut in these areas will almost certainly be misleading. The black ink
limit
will be final calibrated device values if the profile
includes calibration information.<br>
<br>
The default device grid is relativy low, and 11 (ie. 11 x 11 x 11 for
an RGB device, 11 x 11 x 11 x 11 for a CMYK device etc.).<br>
<br>
The <span style="font-weight: bold;">-h</span> flag selects a higher
device grid resolution of 27.<br>
<br>
The <span style="font-weight: bold;">-u</span> flag selects an
extremely high device grid resolution of 61. This will probably take a
long time to run.<br>
<br>
The <span style="font-weight: bold;">-G res</span> option allows a
specific grid resolution to be used.<br>
<br>
The <b>-c</b> option causes the error differences to be
displayed
in CIE94 delta E, rather than plain L*a*b* delta E. CIE94 delta E has a
closer
correspondence with perceived color differences than the default CIE76
delta E values.<br>
<br>
The <b>-k</b> option causes the error differences to be
displayed
in CIEDE2000 delta E, rather than plain L*a*b* delta E. CIEDE2000 delta
E has a
closer
correspondence with perceived color differences than either CIE76 or
CIE94 delta E values.<br>
<br>
The <b>-w</b> creates a <a href="File_Formats.html#X3DOM">X3DOM</a> 3D
visualization
of the differences between the test points and the profiles prediction
of
the resulting colors.<br>
<br>
The <b>-x</b> flag adds Lab axes to the X3DOM output.<br>
<br>
The <span style="font-weight: bold;">-e</span> flag causes the error
vectors in the X3DOM output to be color coded according to their
lengths, from longest to shortest: yellow, red, magenta, blue, cyan and
green.<br>
<br>
<br>
<br>
</body>
</html>
|
