To work with Cassini data under ISIS3, and with Voyager data (which requires ISIS2), I need to have both ISIS2 and ISIS3 functioning on the same machine. I have a current version of ISIS3 (just rsynced about two weeks ago), and also have ISIS2 on the same machine (last rsynced probably over a year ago).
I've downloaded some Voyager data from PDS, and am attempting to process it with ISIS2. Some questions:
+ Are the Voyager PDS data already in ISIS format? I can view the .img files with ISIS3 qview (I can't run qview through ISIS2, see below), which leads me to believe I do not need to run pds2isis as a first processing step for the Voyager data. However, I get errors when stepping through the subsequent Voyager-specific routines, e.g.
GROUP = VOYFIXLABEL
ISISVERSION = "2.3.4-REL_1_0"
ISISBUILDDATE = "2007-12-06T00:14:37"
VERSION_DATE = 1999-06-24
DATE_TIME = 2010-10-29T12:34:56
NODE_NAME = "callisto"
USER_NAME = "ebierhau"
"Refine the labels of a VOYAGER ISS image created by pds2isis"
GROUP = PARAMETERS
FROM = "c2684608.img"
END_GROUP = PARAMETERS
[PUINITLAB-INVVAL] (-4) RECORD_BYTES keyword value (836) invalid (expected
[POPEN-INVLAB] (-6) Error initializing existing file c2684608.img
[QOPEN-FILERR] (-4) Error opening qube file c2684608.img
[VOYFIXLABEL-OPNFAI] (-1) Error opening input file c2684608.img
[SHTAE-ABTERM] Abnormal termination forced by application program
+ Do tips/tricks/guidelines exist for running ISIS2 & 3 on the same machine? I've tried explicitly pointing to ISIS2 routines via absolute pathnames when running an executable, but get library errors, e.g.
/disk01/isis2/isisr/exe/qview: error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory
So right now I'm not sure if I'm dealing with problems caused by images that aren't in proper ISIS format, or problems caused by conflict between ISIS2 and 3, or a combination of both.
Thanks for your help,