1
1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5
<meta http-equiv="content-type"
6
content="text/html; charset=ISO-8859-1">
7
<meta name="author" content="Graeme Gill">
10
<h2><b>tweak/refine</b></h2>
12
<span style="font-weight: bold;">Refine</span> creates an abstract
13
profile, by comparing CIE measurement values from two
14
test charts. The charts will usually be in <a
15
href="File_Formats.html#.ti3">.ti3</a>
16
format, but only XYZ, Lab or spectral values will be used. Typically
17
the charts would be printed on a target system (the one being emulated,
18
say a printing press), and the proofing system (the one that is being
19
profiled). The abstract profile that <span style="font-weight: bold;">refine</span>
20
produces will be a correction that makes the proofing system behave
22
like the target. This can then be used to recreate the proofing systems
23
ICC profile, or device link. By feeding a previous abstract correction
24
profile in as well, iterative improvement can be made to the proofing
27
<a href="verify.html">verify</a> is a useful tool to use on the two
28
test charts, to check how well the refinement is proceeding. If a white
29
point relative match is being created (refine -R), then use veryify -N.<br>
30
<h3>Usage Summary</h3>
31
<small><span style="font-family: monospace;">usage: refine [-options]
32
cietarget ciecurrent [outdevicc] [inabs] outabs</span><br
33
style="font-family: monospace;">
34
<span style="font-family: monospace;"> -v
35
Verbose</span><br style="font-family: monospace;">
36
<span style="font-family: monospace;"> -c
37
Create initial abstract correction profile</span><br
38
style="font-family: monospace;">
39
<span style="font-family: monospace;"> -g
40
Don't impose output device gamut limit</span><br
41
style="font-family: monospace;">
42
<span style="font-family: monospace;"> -r
43
res Set
44
abstract profile clut resolution (default 33)</span><br
45
style="font-family: monospace;">
46
<span style="font-family: monospace;"> -d
47
factor Override default
48
damping factor (default 0.950000)<br>
49
-R
50
Aim for white point relative match rather than absolute<br
51
style="font-family: monospace;">
52
</span><span style="font-family: monospace;"> -i
53
illum Choose illuminant for spectral data:</span><br
54
style="font-family: monospace;">
55
<span style="font-family: monospace;">
56
A, C, D50 (def.), D65, F5, F8, F10 or file.sp</span><br
57
style="font-family: monospace;">
58
<span style="font-family: monospace;"> -o
59
observ Choose CIE Observer
60
for spectral data:</span><br style="font-family: monospace;">
61
<span style="font-family: monospace;">
62
1931_2, 1964_10, S&B 1955_2, J&V 1978_2 (def.)</span><br
63
style="font-family: monospace;">
64
<span style="font-family: monospace;"> -f
65
Use Fluorescent Whitening Agent compensation on spectral data</span><br
66
style="font-family: monospace;">
67
<span style="font-family: monospace;"> </span><span
68
style="font-style: italic; font-family: monospace;">cietarget </span><span
69
style="font-family: monospace;"> Target CIE or
70
spectral values, CGATS file (e.g. .ti3)</span><br
71
style="font-family: monospace;">
72
<span style="font-family: monospace;"> </span><span
73
style="font-style: italic; font-family: monospace;">ciecurrent</span><span
74
style="font-family: monospace;"> Actual CIE or
75
spectral values, CGATS file (e.g. .ti3)</span><br
76
style="font-family: monospace;">
77
<span style="font-family: monospace;"> [</span><span
78
style="font-style: italic; font-family: monospace;">outdevicc</span><span
79
style="font-family: monospace;">] Output device ICC
80
profile to set gamut limit (not used if -g)</span><br
81
style="font-family: monospace;">
82
<span style="font-family: monospace;"> [</span><span
83
style="font-style: italic; font-family: monospace;">inabs</span><span
84
style="font-family: monospace;">]
85
Previous abstract correction ICC profile (not used if -c)</span><br
86
style="font-family: monospace;">
87
<span style="font-family: monospace;"> </span><span
88
style="font-style: italic; font-family: monospace;">outabs</span><span
89
style="font-family: monospace;">
90
Created/refined abstract correction ICC profile</span></small><br>
91
<h3>Usage Details</h3>
92
<b>refine</b> provides a way of improving the profile accuracy of a
95
The <b>-v</b> flag prints out extra information during the checking,
96
and prints each patch value, rather than just a summary.<br>
98
The <b>-c</b> option is used when refine is being used for the first
99
time, and there is no previous abstract profile to continue refining.
100
If <span style="font-weight: bold;">-c</span> is used, then the name
101
of the previous abstract correction profile should not be supplied.<br>
103
If the <b>-g </b>flag indicates that an output device profile is not
104
being supplied, and that corrections should be attempted, even if the
105
colors are outside the devices gamut. Normally an output device profile
106
is supplied, and corrections aren't applied to colors outside the
107
devices gamut, since this will not achieve anything useful, and can
108
distort the results.<br>
110
If the <b>-r </b>parameter overrides the resolution of the CLUT grid
111
used in the abstract profile. By default the value is 33, but other<br>
112
values can be chosen. An odd number is recommended. <br>
114
If the <b>-d </b>parameter sets how aggressively refine should try
116
correct errors. Normally it will try and exactly compensate for the
117
color errors revealed in comparing the two measurement files, but if
118
the device behaviour is unusual, or not very repeatable, this may
119
result in successive applications of refine making things worse, rather
120
than better. If this is the case, try using a smaller number, such as
123
If the <span style="font-weight: bold;">-R</span> flag is used, then
124
refine creates an abstract profile for improving the match of the patch
125
values when interpreted in a white point relative (ie. Relative
126
Colorimetric) intent. If used to create a corrected device link profile
127
using <a href="collink.html">collink</a>, remember to create a
128
Relative colorimetric intent device link profile.<br>
130
The <b>-i</b> flag allows specifying a standard or custom illumination
131
spectrum, applied to the spectral test point values, to compute CIE
133
values. <b>A</b>, <b>D50</b>, <b>D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b>
134
are a selection of standard illuminant spectrums, with <b>D50</b>
136
default. If a filename is specified instead, it will be assumed to be
138
Argyll specific <a href="File_Formats.html#.sp">.sp</a> spectrum file.<br>
140
The <b>-o</b> flag allows specifying a tristimulus observer, and is
142
to compute CIE tristimulus values. The following choices are available:<br>
143
<b> 1931_2</b> selects the standard CIE 1931 2 degree observer.<br>
144
<b>1964_10</b> selects the standard CIE 1964 10 degree observer.<br>
145
<b>1955_2</b> selects the Stiles and Birch 1955 2 degree
147
<b>1978_2 </b>selects the Judd and Voss 1978 2 degree observer<br>
148
<b>shaw</b> selects the Shaw and Fairchild 1997 2 degree
151
The <b>-f</b> flag enables Fluorescent Whitening Agent compensation,
152
which compensates for the effect a different illuminant will have, on
153
any Fluorescent Whitening Agent present in the reflective media.
154
Spectral patch information is needed for this to function.<br>
156
If both CIE and spectral values are present in the input files, the CIE
157
values will be used by default. Using the <span
158
style="font-weight: bold;">-i</span>, <span style="font-weight: bold;">-o</span>
159
or <span style="font-weight: bold;">-f</span> flag will force spectral
160
values to be used. The the <span style="font-weight: bold;">-i</span>,
161
<span style="font-weight: bold;">-o</span> or <span
162
style="font-weight: bold;">-f</span> flags will apply to both the
163
target and measured input files.<br>
165
<span style="font-style: italic; font-weight: bold;">cietarget</span>
166
Is the filename of the target CIE or spectral values. This is a <a
167
href="File_Formats.html#CGATS">CGATS</a> file (e.g. a <a
168
href="File_Formats.html#.ti3">.ti3</a> made using <a
169
href="chartread.html">chartread</a>). These are the color values
170
wanted for each patch in the test chart, typically the product of the
171
target print system.<br>
173
<span style="font-style: italic; font-weight: bold;">ciecurrent</span>
174
Is the filename of the
175
actual, current measured CIE or spectral values. This is a <a
176
href="File_Formats.html#CGATS">CGATS</a> file (e.g. a <a
177
href="File_Formats.html#.ti3">.ti3</a> made using <a
178
href="chartread.html">chartread</a>). The errors between these patches
179
and the patches in the <span
180
style="font-style: italic; font-weight: bold;">cietarget</span> file
181
will be used to create a correction profile.<br>
183
[<span style="font-style: italic; font-weight: bold;">outdevicc</span>]
184
If the <span style="font-weight: bold;">-g</span> flag is not used,
185
then the output device ICC profile should be supplied here, to allow <span
186
style="font-weight: bold;">refine</span> to limit its corrections to
187
colors that are within the gamut of the device.<br>
189
[<span style="font-weight: bold; font-style: italic;">inabs</span>]
190
After the first correction has been created, subsequent corrections
191
need to improve upon previous ones, so the previous correction profile
192
should be provided here. For the first correction, the <span
193
style="font-weight: bold;">-c</span> flag should be used, and this
194
argument is omitted.<br>
196
<span style="font-weight: bold; font-style: italic;">outabs</span>
197
The name of the created or refined abstract correction ICC profile<br>
200
<span style="font-weight: bold;">Refine</span> is typically used in a
201
proofing situation, in which a verification chart is being used to
202
check the accuracy of a proofing system. (It might also be used for
204
arbitrary color alterations by created two test chart files by hand.)
206
using the errors between the target chart and the measured values,
207
refine attempts to improve the match between the proofing system and
210
There is facility in <a href="collink.html">collink</a>, <a
211
href="colprof.html">colprof</a> and <a href="revfix.html">revfix</a>
212
to incorporate an abstract profile. <br>
214
For systems using two device profiles or a device
215
link to convert between the target space printing files and the
216
proofing device space, the following would be a typical scenario:<br>
218
<div style="margin-left: 40px;">We have a reference set of test chart
219
values, read from the target system <span style="font-weight: bold;">reference.ti3</span>.
220
The ICC profile for the target system is <span
221
style="font-weight: bold;">target.icm</span>. The ICC profile for the
222
proofing system is <span style="font-weight: bold;">proofer.icm</span>.
223
If using a device link, the device link used to print proofer test
224
charts is currently <span style="font-weight: bold;">target_proofer.icm</span>:<br>
227
First we print the test chart out on the proofing system and read it
228
in, resulting in a <span style="font-weight: bold;">chart1.ti3</span>
231
Lets check how well the proofing system current matches using verify:<br>
233
verify reference.ti3 chart1.ti3<br>
235
We then create our initial abstract correction fix profile <span
236
style="font-weight: bold;">fix1.icm</span> using refine:<br>
238
refine -v -c reference.ti3 chart1.ti3
239
proofer.icm fix1.icm<br>
241
Applying this to your process for creating the proofer device profile
243
target to proofing device link (choose one of the three options below,
244
depending whether you are using the proofer profile and just want to
245
alter its colorimetric B2A table using <span style="font-weight: bold;">revfix</span>,
246
whether you are going to recreate the proofer file from the original
247
measurement data using <span style="font-weight: bold;">colprof</span>,
248
or whether you are using a device link profile created using <span
249
style="font-weight: bold;">collink</span>):<br>
251
revfix -v -1 -ke -p fix1.icm proofer.icm
254
copy proofer.ti3 proofer_fix1.ti3<br>
255
colprof -v -p fix1.icm proofer_fix1<br>
257
collink -v -s -ia -oa -p fix1.icm target.icm
258
proofer.icm target_proofer_fix1.icm<br>
260
Note that the above example is a simple one - you should use all the
261
same options as you used to create your initial <span
262
style="font-weight: bold;"><span style="font-weight: bold;"></span>proofer.icm
263
</span>or <span style="font-weight: bold;">target_proofer.icm</span>,
264
with the addition of the "-p fix1.icm" option to specify the abstract
265
correction profile be applied.<br>
267
Use the <span style="font-weight: bold;">proofer_fix1.icm</span> or <span
268
style="font-weight: bold;">target_proofer_fix1.icm</span> to
269
print out the test chart again, and read it in, resulting in <span
270
style="font-weight: bold;">chart2.ti3</span> file.<br>
272
Lets check how well the proofing system matches after this first round
273
of refinement using verify:<br>
275
verify reference.ti3 chart2.ti3<br>
278
<span style="font-weight: bold;"><span style="font-weight: bold;">>>></span></span><br>
279
<span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><br>
280
<span style="font-weight: bold;"><span style="font-weight: bold;"> </span></span>We
281
can then start another round of improvement:<br>
283
We refine our previous abstract correction fix profile using refine:<br>
285
refine -v reference.ti3 chart2.ti3 proofer.icm
286
fix1.icm fix2.icm<br>
288
Applying this new abstract profile to our process for creating the
289
proofing device profile or link again:<br>
291
revfix -v -1 -ke -p fix2.icm proofer.icm
294
copy proofer.ti3 proofer_fix2.ti3<br>
295
colprof -v -p fix2.icm proofer_fix2<br>
297
collink -v -s -ia -oa -p fix2.icm target.icm
298
proofer.icm target_proofer_fix2.icm<br>
300
Use the <span style="font-weight: bold;">proofer_fix2.icm</span> or <span
301
style="font-weight: bold;">target_proofer_fix2.icm</span> to
302
print out the test chart again, and read it in, resulting in <span
303
style="font-weight: bold;">chart3.ti3</span> file.<br>
305
Check again how well the proofing system matches after this first round
306
of refinement using verify:<br>
308
verify reference.ti3 chart3.ti3<br>
310
Rounds of improvements can be continues by looping back to <span
311
style="font-weight: bold;">>>></span>, being careful to
313
names of the <span style="font-weight: bold;">fixN.icm</span>, <span
314
style="font-weight: bold;">proofer_fixN.icm</span> or <span
315
style="font-weight: bold;">target_proofer_fixN.icm</span> and <span
316
style="font-weight: bold;">chartN.ti3</span>files. Stop when
318
or if it looks like things are getting worse, rather than better. If
319
the latter happens, it might be good to revert to the results from a
5
<meta http-equiv="content-type" content="text/html;
7
<meta name="author" content="Graeme Gill">
10
<h2><b>tweak/refine</b></h2>
12
<span style="font-weight: bold;">Refine</span> creates an abstract
13
profile, by comparing CIE measurement values from two test charts.
14
The charts will usually be in <a href="File_Formats.html#.ti3">.ti3</a>
15
format, but only XYZ, Lab or spectral values will be used (ie. all
16
device space values are ignored). Typically the charts would be
17
printed on a target system (the one being emulated, say a printing
18
press), and the proofing system (the one that is being profiled).
19
The abstract profile that <span style="font-weight: bold;">refine</span>
20
produces will be a correction that makes the proofing system behave
21
more like the target. This can then be used to recreate the proofing
22
systems ICC profile, or device link. By feeding a previous abstract
23
correction profile in as well, iterative improvement can be made to
24
the proofing reproduction.<br>
26
<a href="verify.html">verify</a> is a useful tool to use on the two
27
test charts, to check how well the refinement is proceeding. If a
28
white point relative match is being created (refine -R), then use
30
<h3>Usage Summary</h3>
31
<tt><small>usage: refine [-options] cietarget ciecurrent [outdevicc]
33
-v
36
-c
39
initial abstract correction profile<br>
40
-g
43
impose output device gamut limit<br>
44
-r res Set
45
abstract profile clut resolution (default 33)<br>
46
-d factor Override default damping
47
factor (default 0.950000)<br>
48
-R
51
for white point relative match rather than absolute<br>
52
</small></tt><tt><small><small></small><small><small>-f
53
[illum] Use Fluorescent Whitening Agent
54
compensation [opt. simulated inst. illum.:<br>
55
58
M0, M1, M2, A, C, D50 (def.), D50M2, D65, F5, F8, F10 or
60
-i illum Choose
61
illuminant for computation of CIE XYZ from spectral data
63
66
A, C, D50 (def.), D50M2, D65, F5, F8, F10 or file.sp</small></small><br>
67
-o observ Choose CIE Observer for
69
72
1964_10, S&B 1955_2, J&V 1978_2 (def.)<br>
73
<span style="font-style: italic;">cietarget </span>
74
Target CIE or spectral values, CGATS file (e.g. .ti3)<br>
75
<span style="font-style: italic;">ciecurrent</span>
76
Actual CIE or spectral values, CGATS file (e.g. .ti3)<br>
77
[<span style="font-style: italic;">outdevicc</span>]
78
Output device ICC profile to set gamut limit (not used if -g)<br>
79
[<span style="font-style: italic;">inabs</span>]
82
abstract correction ICC profile (not used if -c)<br>
83
<span style="font-style: italic;">outabs</span>
86
abstract correction ICC profile</small></tt><br>
87
<h3>Usage Details</h3>
88
<b>refine</b> provides a way of improving the profile accuracy of a
91
The <b>-v</b> flag prints out extra information during the
92
checking, and prints each patch value, rather than just a summary.<br>
94
The <b>-c</b> option is used when refine is being used for the
95
first time, and there is no previous abstract profile to continue
96
refining. If <span style="font-weight: bold;">-c</span> is used,
97
then the name of the previous abstract correction profile should not
100
If the <b>-g </b>flag indicates that an output device profile is
101
not being supplied, and that corrections should be attempted, even
102
if the colors are outside the devices gamut. Normally an output
103
device profile is supplied, and corrections aren't applied to colors
104
outside the devices gamut, since this will not achieve anything
105
useful, and can distort the results.<br>
107
If the <b>-r </b>parameter overrides the resolution of the CLUT
108
grid used in the abstract profile. By default the value is 33, but
110
values can be chosen. An odd number is recommended. <br>
112
If the <b>-d </b>parameter sets how aggressively refine should try
113
and correct errors. Normally it will try and exactly compensate for
114
the color errors revealed in comparing the two measurement files,
115
but if the device behaviour is unusual, or not very repeatable, this
116
may result in successive applications of refine making things worse,
117
rather than better. If this is the case, try using a smaller number,
118
such as 0.8, or 0.5.<br>
120
If the <span style="font-weight: bold;">-R</span> flag is used,
121
then refine creates an abstract profile for improving the match of
122
the patch values when interpreted in a white point relative
123
(ie. Relative Colorimetric) intent. If used to create a corrected
124
device link profile using <a href="collink.html">collink</a>,
125
remember to create a Relative colorimetric intent device link
128
The <b>-f</b> flag enables Fluorescent Whitening Agent (FWA)
129
compensation. This only works if spectral data is available and, the
130
instrument is not UV filtered. FWA compensation adjusts the
131
spectral samples so that they appear to have been measured using an
132
illuminant that has a different level of Ultra Violet to the one the
133
instrument actually used in the measurement. The optional
134
illumination parameter allows specifying a standard or custom
135
illumination spectrum to be used as the similated instrument
136
illuminant, overriding the default <b>D50</b> or CIE computation
137
illuminant used for FWA (see <b>-i</b> below<b>). </b>See <a
138
href="file:///D:/src/argyll/doc/colprof.html#f">colprof -f</a> for
139
a fuller explanation. The same value should be used as was used
140
during the creation of the profile.<br>
142
The <b>-i</b> flag allows specifying a standard or custom
143
illumination spectrum, applied to the spectral test point values to
144
compute CIE tristimulus values. <b>A</b>, <b>D50</b>, <b>D50M2,
145
D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b> are a selection of
146
standard illuminant spectrums, with <b>D50</b> being the default.
147
If a filename is specified instead, it will be assumed to be an
149
href="file:///D:/src/argyll/doc/File_Formats.html#.sp">.sp</a>
150
spectrum file. If FWA compensation is used during measurement, this
151
illuminant will be used by default as the simulated instrument
152
illuminant. The same value should be used as was used during the
153
creation of the profile.<br>
155
The <b>-o</b> flag allows specifying a tristimulus observer, and is
156
used to compute CIE tristimulus values. The following choices are
158
<b> 1931_2</b> selects the standard CIE 1931 2 degree
160
<b>1964_10</b> selects the standard CIE 1964 10 degree
162
<b>1955_2</b> selects the Stiles and Birch 1955 2 degree
164
<b>1978_2 </b>selects the Judd and Voss 1978 2 degree
166
<b>shaw</b> selects the Shaw and Fairchild 1997 2 degree
169
If both CIE and spectral values are present in the input files, the
170
CIE values will be used by default. Using the <span
171
style="font-weight: bold;">-i</span>, <span style="font-weight:
172
bold;">-o</span> or <span style="font-weight: bold;">-f</span>
173
flag will force spectral values to be used. The the <span
174
style="font-weight: bold;">-i</span>, <span style="font-weight:
175
bold;">-o</span> or <span style="font-weight: bold;">-f</span>
176
flags will apply to both the target and measured input files.<br>
178
<span style="font-style: italic; font-weight: bold;">cietarget</span>
181
the filename of the target CIE or spectral values. This is a <a
182
href="File_Formats.html#CGATS">CGATS</a> file (e.g. a <a
183
href="File_Formats.html#.ti3">.ti3</a> made using <a
184
href="chartread.html">chartread</a>). These are the color values
185
wanted for each patch in the test chart, typically the product of
186
the target print system.<br>
188
<span style="font-style: italic; font-weight: bold;">ciecurrent</span>
189
Is the filename of the
190
actual, current measured CIE or spectral values. This is a <a
191
href="File_Formats.html#CGATS">CGATS</a> file (e.g. a <a
192
href="File_Formats.html#.ti3">.ti3</a> made using <a
193
href="chartread.html">chartread</a>). The errors between these
194
patches and the patches in the <span style="font-style: italic;
195
font-weight: bold;">cietarget</span> file will be used to create a
196
correction profile.<br>
198
[<span style="font-style: italic; font-weight: bold;">outdevicc</span>]
201
the <span style="font-weight: bold;">-g</span> flag is not used,
202
then the output device ICC profile should be supplied here, to allow
203
<span style="font-weight: bold;">refine</span> to limit its
204
corrections to colors that are within the gamut of the device.<br>
206
[<span style="font-weight: bold; font-style: italic;">inabs</span>]
209
the first correction has been created, subsequent corrections need
210
to improve upon previous ones, so the previous correction profile
211
should be provided here. For the first correction, the <span
212
style="font-weight: bold;">-c</span> flag should be used, and this
213
argument is omitted.<br>
215
<span style="font-weight: bold; font-style: italic;">outabs</span>
218
name of the created or refined abstract correction ICC profile<br>
221
<span style="font-weight: bold;">Refine</span> is typically used in
222
a proofing situation, in which a verification chart is being used to
223
check the accuracy of a proofing system. (It might also be used for
224
more arbitrary color alterations by created two test chart files by
225
hand.) By using the errors between the target chart and the measured
226
values, refine attempts to improve the match between the proofing
227
system and its target.<br>
229
There is facility in <a href="collink.html">collink</a>, <a
230
href="colprof.html">colprof</a> and <a href="revfix.html">revfix</a>
231
to incorporate an abstract profile. <br>
233
For systems using two device profiles or a device link to convert
234
between the target space printing files and the proofing device
235
space, the following would be a typical scenario:<br>
237
<div style="margin-left: 40px;">We have a reference set of test
238
chart values, read from the target system <span
239
style="font-weight: bold;">reference.ti3</span>. The ICC profile
240
for the target system is <span style="font-weight: bold;">target.icm</span>.
241
The ICC profile for the proofing system is <span
242
style="font-weight: bold;">proofer.icm</span>. If using a device
243
link, the device link used to print proofer test charts is
244
currently <span style="font-weight: bold;">target_proofer.icm</span>:<br>
247
First we print the test chart out on the proofing system and read
248
it in, resulting in a <span style="font-weight: bold;">chart1.ti3</span>
251
Lets check how well the proofing system current matches using
254
verify reference.ti3 chart1.ti3<br>
256
We then create our initial abstract correction fix profile <span
257
style="font-weight: bold;">fix1.icm</span> using refine:<br>
259
refine -v -c reference.ti3 chart1.ti3
260
proofer.icm fix1.icm<br>
262
Applying this to your process for creating the proofer device
263
profile or target to proofing device link (choose one of the three
264
options below, depending whether you are using the proofer profile
265
and just want to alter its colorimetric B2A table using <span
266
style="font-weight: bold;">revfix</span>, whether you are going
267
to recreate the proofer file from the original measurement data
268
using <span style="font-weight: bold;">colprof</span>, or
269
whether you are using a device link profile created using <span
270
style="font-weight: bold;">collink</span>):<br>
272
revfix -v -1 -ke -p fix1.icm proofer.icm
275
copy proofer.ti3 proofer_fix1.ti3<br>
276
colprof -v -p fix1.icm proofer_fix1<br>
278
collink -v -s -ia -oa -p fix1.icm target.icm
279
proofer.icm target_proofer_fix1.icm<br>
281
Note that the above example is a simple one - you should use all
282
the same options as you used to create your initial <span
283
style="font-weight: bold;"><span style="font-weight: bold;"></span>proofer.icm
285
</span>or <span style="font-weight: bold;">target_proofer.icm</span>,
286
with the addition of the "-p fix1.icm" option to specify the
287
abstract correction profile be applied.<br>
289
Use the <span style="font-weight: bold;">proofer_fix1.icm</span>
290
or <span style="font-weight: bold;">target_proofer_fix1.icm</span>
291
to print out the test chart again, and read it in, resulting in <span
292
style="font-weight: bold;">chart2.ti3</span> file.<br>
294
Lets check how well the proofing system matches after this first
295
round of refinement using verify:<br>
297
verify reference.ti3 chart2.ti3<br>
300
<span style="font-weight: bold;"><span style="font-weight: bold;">>>></span></span><br>
301
<span style="font-weight: bold;"><span style="font-weight: bold;"></span></span><br>
302
<span style="font-weight: bold;"><span style="font-weight: bold;"> </span></span>We
305
then start another round of improvement:<br>
307
We refine our previous abstract correction fix profile using
310
refine -v reference.ti3 chart2.ti3
311
proofer.icm fix1.icm fix2.icm<br>
313
Applying this new abstract profile to our process for creating the
314
proofing device profile or link again:<br>
316
revfix -v -1 -ke -p fix2.icm proofer.icm
319
copy proofer.ti3 proofer_fix2.ti3<br>
320
colprof -v -p fix2.icm proofer_fix2<br>
322
collink -v -s -ia -oa -p fix2.icm target.icm
323
proofer.icm target_proofer_fix2.icm<br>
325
Use the <span style="font-weight: bold;">proofer_fix2.icm</span>
326
or <span style="font-weight: bold;">target_proofer_fix2.icm</span>
327
to print out the test chart again, and read it in, resulting in <span
328
style="font-weight: bold;">chart3.ti3</span> file.<br>
330
Check again how well the proofing system matches after this first
331
round of refinement using verify:<br>
333
verify reference.ti3 chart3.ti3<br>
335
Rounds of improvements can be continues by looping back to <span
336
style="font-weight: bold;">>>></span>, being careful to
337
increment the names of the <span style="font-weight: bold;">fixN.icm</span>,
339
<span style="font-weight: bold;">proofer_fixN.icm</span> or <span
340
style="font-weight: bold;">target_proofer_fixN.icm</span> and <span
341
style="font-weight: bold;">chartN.ti3</span>files. Stop when
342
exhausted, or if it looks like things are getting worse, rather
343
than better. If the latter happens, it might be good to revert to
344
the results from a previous round.<br>
added
removed
doc/refine.html
