<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>profcheck</title> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> <meta name="author" content="Graeme Gill"> </head> <body> <h2><b>profile/profcheck</b></h2> <h3>Summary</h3> Check an <a href="File_Formats.html#ICC">ICC</a> profile against <a href="File_Formats.html#.ti3">.ti3</a> test chart data.<br> <h3>Usage Summary</h3> <small><span style="font-family: monospace;">profcheck [-options] data.ti3 iccprofile.icm</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span></small><small><span style="font-family: monospace;">-v [level] Verbosity level (default 1), 2 to print each DE</span></small><small><span style="font-family: monospace;"></span><br style="font-family: monospace;"> <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 VRML visualization (iccprofile.wrl)</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -x Use VRML axes<br> -m Make VRML lines a minimum of 0.5<br style="font-family: monospace;"> </span><span style="font-family: monospace;"> -e Color vectors acording to delta E</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -d devval1,deval2,devvalN</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> Specify a device value to sort against</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -p Sort device value by PCS/Lab target</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -i illum Choose illuminant for print/transparency spectral data:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> A, C, D50 (def.), D65, F5, F8, F10 or file.sp</span><br style="font-family: monospace;"> <span style="font-family: monospace;"> -o observ Choose CIE Observer for spectral data:</span><br style="font-family: monospace;"> <span style="font-family: monospace;"></span></small><small><span style="font-family: monospace;"> 1931_2 </span></small><small><span style="font-family: monospace;">(def.)</span></small><small><span style="font-family: monospace;">, 1964_10, S&B 1955_2, shaw, J&V 1978_2</span></small><br style="font-family: monospace;"> <small><span style="font-family: monospace;"> -f Use Fluorescent Whitening Agent compensation<br> -I intent r = relative colorimetric, a = absolute (default)<br style="font-family: monospace;"> </span><i style="font-family: monospace;"> data.ti3</i><span style="font-family: monospace;"> Test point data file</span><br style="font-family: monospace;"> <i style="font-family: monospace;"> iccprofile.icm</i><span style="font-family: monospace;"> Profile to check</span></small> <br> <h3>Usage Details and Discussion</h3> <b> profcheck</b> provides a way of checking how well an <a href="File_Formats.html#ICC">ICC</a> profile conforms to the test sample data that was used to create it (or other test samples that are from the same device). This is the same sort of check done within the profile making tool (<a href="colprof.html">colprof</a>), but having a separate tool provides some flexibility. The absolute forward table in the profile is used to create PCS values from the sample points, and the profiles PCS value then compared to the PCS values of the measured sample points. Note the lower delta E values are not always a better measure of how good a profile is. The aim of a profile is to model the underlying characteristics of a device, not to slavishly reproduce the sampled data point values. Sampled data point values contain device variation and instrument reading inaccuracies, and a good profiler will try and filter out this noise, resulting in some deliberate differences between the profile and the sample points used to create it.<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>-c</b> option causes the differences between the test values and the profile prediction of the color for each device value 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 differences between the test values and the profile prediction of the color for each device value 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#VRML">VRML</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 VRML output.<br> <br> The <b>-m</b> flag makes each error line a minimum of 0.5 delta E long, so that all the points are visible. This makes it easier to view the distribution of test points in the reference set.<br> <br> The <span style="font-weight: bold;">-e</span> flag causes the error vectors in the VRML output to be color coded according to their lengths, from longest to shortest: yellow, red, magenta, blue, cyan and green.<br> <br> The <b>-d</b> parameters allow the specification of a particular device value, and the test point by test point output will be sorted by distance from the given device value. This can be useful in determining how well "supported" the profile is in a particular area of the colorspace.<br> <br> If the <b>-p </b>flag is used in combination with the <b>-d</b> parameters, then the test point by test point output will be sorted by distance in PCS (Lab) space rather than distance in device space.<br> <br> The <b>-i</b> flag allows specifying a standard or custom illumination spectrum, applied to the spectral test point values, to compute CIE tristimulus values. <b>A</b>, <b>D50</b>, <b>D65</b>, <b>F5</b>, <b>F8</b>, <b>F10</b> are a selection of standard illuminant spectrums, with <b>D50</b> being the default. If a filename is specified instead, it will be assumed to be an Argyll specific <a href="File_Formats.html#.sp">.sp</a> spectrum file. The same value should be used as was used during the creation of the profile.<br> <br> <a name="o"></a> The <b>-o</b> flag allows specifying a tristimulus observer, and is used to compute PCS (Profile Connection Space) tristimulus values. The following choices are available:<br> <b> 1931_2</b> selects the standard CIE 1931 2 degree observer. The default.<br> <b>1964_10</b> selects the standard CIE 1964 10 degree observer.<br> <b>1955_2</b> selects the Stiles and Birch 1955 2 degree observer<br> <b>1978_2 </b>selects the Judd and Voss 1978 2 degree observer<br> <b>shaw</b> selects the Shaw and Fairchild 1997 2 degree observer<br> <br> The same parameter value should be used as was used during the creation of the profile.<br> <br> The <b>-f</b> flag enables Fluorescent Whitening Agent compensation, which compensates for the effect a different illuminant will have, on any Fluorescent Whitening Agent present in the reflective media. The same setting should be used as was used during the creation of the profile.<br> <br> The <span style="font-weight: bold;">-I</span> parameter allows changing the intent used in looking up the ICC profile colors to relative colorimetric. This would <span style="text-decoration: underline;">not</span> be used if you are checking a profile against the .ti3 file that was used to create it, since, since profiles are always made from absolute colorimetric measurement values.<br> <br> <br> <br> <br> <br> </body> </html>
