YAAW - Yet Another Argyll Wrapper

[riclin]

Well, I think both sides have valid arguments. For me it's merely out of interest how far my printed target is away from the expected values. Using an i1pro with the standard ruler/jig doesn't give much room for user created mis-measurement, but that might be completely different with other devices. Way off values might indicate reading errors, but also - perhaps - problems with the printer (i. e. nozzles not firing). Ultimately it's a personal preference, how one would like to interpret the values. As you already stated: No big effort to run a shell script afterwards and also append the data to the existent log file.

Don't forget also that by default, YAAW does not suppress chartread unexpected delta-E warnings so unusual readings will be exposed there - although admittedly this information does not appear in the logfile since chartread runs in its own terminal window.

 

[riclin]

Don't forget also that by default, YAAW does not suppress chartread unexpected delta-E warnings so unusual readings will be exposed there - although admittedly this information does not appear in the logfile since chartread runs in its own terminal window.

Further to the above:

I remain of the view that highlighting ΔE values could be misleading, but appreciate that YAAW's failure to log misreads and similar warnings was a limitation. I have placed a new version onto github which whilst not doing as Ron requested (sorry Ron) responds instead a little differently. The "Read Target" (chartread) phase no longer launches an external terminal, but instead runs in an embedded psuedo-terminal window with a virtual terminal only being used as fallback the pseodo-terminal cannot be activated. This now simplifies the chartread messages being captured by YAAW and filtered in real time for warnings or errors, which are then also recorded in the logfile along with the patch strip where any error or warning occured for subsequent attention. A "View Log" button has been added to the bottom of the Execution screen which toggles between a recorded logfile and the current live display - this allows the same main window to be used for both current real-time information and also the persistent logfile.

The quality of the profile can be reasonably assessed with the profcheck results - generally, average and max errors of less than about 1.5 & 2.5-3.0 respectively indicate reasonably sound results.

yaaw-3.40.11 resides at:

https://github.com/riclin-au/YAAW-Yet-Another-ArgyllCMS-Wrapper-Workflow

r/

 

[rjanowsky]

I remain of the view that highlighting ΔE values could be misleading, but appreciate that YAAW's failure to log misreads and similar warnings was a limitation. I have placed a new version onto github which whilst not doing as Ron requested (sorry Ron) responds instead a little differently. The "Read Target" (chartread) phase no longer launches an external terminal, but instead runs in an embedded psuedo-terminal window with a virtual terminal only being used as fallback the pseodo-terminal cannot be activated. This now simplifies the chartread messages being captured by YAAW and filtered in real time for warnings or errors, which are then also recorded in the logfile along with the patch strip where any error or warning occured for subsequent attention. A "View Log" button has been added to the bottom of the Execution screen which toggles between a recorded logfile and the current live display - this allows the same main window to be used for both current real-time information and also the persistent logfile.

Good improvement! Without an external terminal window the look and feel is cleaner. Getting chartread output onto screen and in the log is really helpful. The "View Log" button is also valuable. No more reason to open a shell to get the log file. And if I really wanted to get the worst patches, a shell script is the way to go.

The quality of the profile can be reasonably assessed with the profcheck results - generally, average and max errors of less than about 1.5 & 2.5-3.0 respectively indicate reasonably sound results.

Yes, for sure that info is most often all you need to evaluate the quality.