What this measurement-file inspector checks
The parser inventories the file identifier and each table's headers, field list, and data rows. It compares NUMBER_OF_FIELDS and NUMBER_OF_SETS with what is actually present, detects duplicate fields and sample IDs, preserves quoted or blank values, validates recognized numeric measurement columns, and reports incomplete Lab, XYZ, RGB, or CMYK groups. Multiple tables remain separate.
Colorimetric and spectral columns
Recognized groups include LAB_L/A/B, XYZ_X/Y/Z, common RGB/CMYK device fields, density fields, and wavelength-labelled spectral columns. For each predominantly numeric field, the report shows count, invalid values, minimum, maximum, and arithmetic mean. Spectral fields are checked for duplicate wavelengths, ascending order, and uniform spacing. These checks validate representation, not the instrument, illuminant, observer, calibration, or physical sample.
CGATS, IT8, and Argyll variants
CGATS-style files use a file identifier, keyword/value headers, a BEGIN_DATA_FORMAT field list, and a matching BEGIN_DATA table. ArgyllCMS uses compatible structures with identifiers such as CTI3 and additional required keywords for its workflows. This inspector keeps unfamiliar headers but does not pretend every vendor extension has standardized meaning.
Color workflow boundary
A structurally clean file is not proof of correct color data or a valid profile target. This tool does not calculate ΔE, derive missing values, apply chromatic adaptation, integrate spectra, infer scale, validate chart layout, detect swapped patches, or create an ICC profile. Check the device class, instrument settings, illuminant/observer, measurement condition, reference target, software requirements, and expected value scale in the actual profiling workflow.
Frequently asked questions
Does this calculate color differences?
No. A single table may contain device and measured values but not the intended reference for each patch. The page audits structure and descriptive ranges only; it does not manufacture a reference or claim pass/fail color accuracy.
Why are INCLUDE directives not opened?
Following a filename or URL would make inspection depend on external state and could expose local paths or fetch untrusted content. The directive is reported, and each referenced file must be inspected explicitly.
Can it inspect spectral measurements?
It inventories wavelength fields and their numeric ranges, ordering, and interval. It does not integrate spectra into XYZ/Lab or validate the spectral scale, instrument bandwidth, observer, or illuminant.
Does it rewrite malformed files?
No. Silent normalization can lose vendor headers, blank fields, table boundaries, or significant numeric formatting. Use the audit to correct the source deliberately in the originating measurement software.
Format references
ArgyllCMS documents CTI3 as an ASCII CGATS-compatible format containing device and CIE or spectral value pairs, with workflow-specific required keywords. Little CMS documents a general CGATS parser with CGATS.17 and multi-table support. See the ArgyllCMS TI3 format reference and the Little CMS tutorial.
Check image print resolution · Pick colors from an image · Browse design and color tools