Possibility to convert csv-file with only L*A*B* values into a ArgyllCMS ti3 file

[Epatcola]

I just started scanning 800 patches, and the PowerShell GUI isn't working for them

My guess would be a bug in your script. Did you compare generated .ti3 files from your script and the working awk script?

 

[superjudge]

My guess would be a bug in your script. Did you compare generated .ti3 files from your script and the working awk script?

Maybe? Is converting 200, 300, and 450 patches different than 800 in some way I should look for?

Fortunately, it keeps the temp folder until it successfully finishes Colprof, and the process sticks on Colprof.

My guess was Start-Process, Start-Thread, Start-Job—the CSV to TI3 is relatively easy to do in Powershell, and I got that working consistently with little trouble. But, anytime you start a cmd process, which is required to run colprof, consistency and expectation go out the window. I wanted to background the job so the UI wouldn’t freeze, and that didn’t work. The logging would suddenly dump out after the ICC was completed, in either PS5 or PS7, and it hates the way you have to pass arguments to colprof.exe—which is _relatively_ standard.

Nothing should be more complicated, but sometimes it just is. At any rate, it should be easy enough to run a CSV through the GUI until it hangs, then run the TI3 through Colprof to verify it actually works, then work my way back through why more definitively.

 

[Epatcola]

Maybe? Is converting 200, 300, and 450 patches different than 800 in some way I should look for?

Maybe more than 26 columns?

I don't have much experience with colprof. It uses loads of memory and CPU. I have a feeling when fed inconsistent data it will barf or take an inordinate amount of time trying to make sense of it.

 

[superjudge]

We’re not trying to make conjecture, I’m asking if your AWK identified a change in behavior over a certain amount of lines that I should be expecting when dealing with CSV, since you suspect I ran into CSV > TI3 issues as opposed to issues with colprof, which likely would have given an error attempting to read an incorrectly formatted TI3, and spit an error out quickly. “CGATS”, I think is the term I ran in to most frequently getting the arguments in an acceptable format for PS to even execute colprof correctly.

I’m going to do a bit more testing in the interest of verifying I’m not malforming a TI3 tomorrow—I’ll at least see if the TI3 from the PS works with colprof in CMD.

 

[Epatcola]

We’re not trying to make conjecture, I’m asking if your AWK identified a change in behavior over a certain amount of lines that I should be expecting when dealing with CSV, since you suspect I ran into CSV > TI3 issues as opposed to issues with colprof

If you mess up the 'un-randomizing' you can give colprof a well formed ti3 file with measurements associated with the wrong patches. SAMPLE_LOC gets an extra character after 26 columns. Just guessing.

 

[superjudge]

It was a really good guess, it's exactly what's happening; I just eyeballed it and came back here to report exactly what you said. I've been sick the last week, and I'm not sure I have the energy to fix this yet.

That being said, it'll irritate me until I do fix it. Thanks for that nudge.