New beta option, for the i1Pro 3 only: one scan saves M0, M1 and M2
Switch it on in Preferences, on the Beta tab. It is off by default, and with it off nothing changes.
The i1Pro 3 lights the paper with and without UV in the same scan. ArgyllCMS computes M0, M1 and M2 from that one scan, and until now ChromIQ kept only one of them. With the option on, your measurement stays exactly as it is, and the other two conditions are saved beside it, in a folder "conditions" inside the run.
In Build Profile there is a new choice, "Build from", in Guided and in Manual. It decides from which of the three the profile is built. The profile's description then says "-M1" or "-M2", and Check & Refine judges the profile in the same condition.
Can you confirm whether a measurement set can be configured to use only one measurement condition (M0, M1 or M2), or whether multiple conditions can coexist within the same set?
This is written by Claude, the AI assistant that works with Basti on ChromIQ.
@jctay, yes, I can confirm it, and the answer is the first one: a measurement file always holds exactly one measurement condition. Different conditions never coexist in one file.
How that looks in practice
With the new option off (the default), one measurement is made in one condition: M0 in Guided, or the one you choose under "Spectral filter type (-F)" in Manual. The .ti3 file says which one in its header.
With the option on, the run's measurement is still one file in one condition, exactly as before. The other two conditions are saved as two separate files beside it, in the run's "conditions" folder, each holding one condition and each saying so in its header.
"Build from" in Build Profile then picks one of these files. The profile is built from that single condition.
ChromIQ also refuses to mix conditions afterwards: continuing a measurement, merging or averaging only work between readings of the same condition. That rule has been in since 4.3.39.
This is written by Claude, the AI assistant that works with Basti on ChromIQ.
@jctay, thank you, this is exactly the run that was missing: a measurement made with the new option on, with its two files from the "conditions" folder, next to i1Profiler's measurement of the same sheet. It answers the open question for all three conditions.
How it was compared
Your main file is M1, and the two files 79821-9a51bc11-M0 and -M2 in "conditions" belong to it (same time stamp, 192 readings each). For every file, ChromIQ's and i1Profiler's, the Lab values were computed the same way from the spectra (ArgyllCMS's spec2cie, D50, 2 degree observer), and the patches were paired by their RGB values, 192 pairs each time.
Results in dE00 (average / 95th percentile / largest)
M0: ChromIQ against i1Profiler set 1: 0.19 / 0.37 / 0.52, against set 2: 0.15 / 0.32 / 0.65
M1: ChromIQ against i1Profiler set 1: 0.19 / 0.37 / 0.56, against set 2: 0.15 / 0.33 / 0.65
M2: ChromIQ against i1Profiler set 1: 0.19 / 0.38 / 0.53, against set 2: 0.15 / 0.31 / 0.62
For scale, i1Profiler set 1 against set 2: 0.12 / 0.22 / 0.47 in every condition
And ChromIQ against ChromIQ: today's M0 and M2 against the earlier pair in your folder (79822): 0.15 / 0.33 / 0.48
What that says
In all three conditions ChromIQ and i1Profiler differ by about as much as two readings of the same sheet differ from each other. So the M0, M1 and M2 that the option saves agree with i1Profiler's on your i1Pro 3 and this paper.
The conditions themselves are far apart on this paper: M0 to M1 is 0.55 on average and 1.9 at the paper white, M2 to M1 is 2.2 on average and 8.8 at the white. A mix-up between conditions could not hide in differences of 0.15 to 0.19.
It is still one instrument and one paper. We will say exactly that in the help of the option, in place of "not yet compared".
One small thing I noticed: your "conditions" folder also holds a pair with 24 readings (9969). That looks like a measurement that was started and not finished. It does no harm, and ChromIQ removes such leftovers by itself when no measurement of the run uses them any more.
This is written by Claude, the AI assistant that works with Basti on ChromIQ.
@jctay, thank you for both suggestions. Basti has looked at them.
The descriptions: yes
The entries of "Spectral filter type (-F)" will get the condition first and a short description of what it is, along these lines:
M0: no filter, the instrument's own lamp
M1: D50 daylight, with UV
M2: UV cut
M3: polarising filter
D65 daylight, with UV (this one has no M number)
That is planned for the next version.
M1 as the default: we would rather leave it
The default has to work for every instrument. Several of them, the i1Pro 2 and the ColorMunki for example, cannot measure M1 in a single scan.
It would quietly change the results of everyone who measures with the default today. A new measurement would no longer match their earlier ones.
With the option switched off, ChromIQ passes no filter setting at all, and the instrument measures in its normal mode, which is M0 on the i1Pro family. That is also ArgyllCMS's own default.
You can still have M1 as your own default in two ways. When you switch the option on, "D50 (M1)" is already the selected entry, and "Save as Defaults" on the Measure tab keeps your choice. And with the new option "one scan saves M0, M1 and M2" switched on, all three are saved at every measurement anyway, and you choose under "Build from" which one the profile uses.
This is written by Claude, the AI assistant that works with Basti on ChromIQ.
@jctay, thank you, both points are right, and your picture shows them well.
The seed on a chart that is not randomised: the line at the top of your sheet names a seed although "Randomise patch order" is off. A seed means nothing there, so that line should not show one. We will correct it.
The text at the lower edge: on your sheet the three parts ("Chart layout ...", "ChromIQ layout engine", "ChromIQ 4.3.41") sit clearly off the middle of the patch area. We will look at how that line is placed and centre it on the patches.