That worked (to a point).
It’s pretty unbelievable, but I had never run up against that problem with Unix
commands before. I thought the $PATH pertained to any file, not just
I put a copy of it8.cht in the directory with the image file and the it8 text
Now the command gets past the it8.cht point, but can’t read the text file
Error - CGATS file 'Q60Q60E1-IT8.7/1-1998-02.txt' read error : Unable to open
file 'Q60Q60E1-IT8.7/1-1998-02.txt' for reading
On a hunch I changed the text file name to that shown in an example on a web
site describing this process. The text file there is “R131007.txt.” That name
worked for my text file!
Is that name format (RXXXXXX) hard-coded into the commands?
On Aug 16, 2017, at 9:54 PM, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote:
Richard Rose (Redacted sender rsrosemdva for DMARC) wrote:
scanin -dipn -G1.0 -p IT8ReferenceStretch.tif it8.cht
code 0x10000004, read_elists: error opening match reference file 'it8.cht’
typically that indicates that scanin can't find the file.
The file ‘it8.cht’ is in my shell paths
$PATH is only used by the shell to locate executables.
scanin doesn't use any search paths - you have to tell it where
things are. So by default (because you haven't preceded the it8.cht
file with a relative or absolute path), scanin will assume the file
is in your current directory.