$ voy2isis from=C1625003_CALIB.LBL to=foo.cubUSER ERROR Input file [C1625003_CALIB.LBL] does not appear to be a Voyager EDR.

$ voy2isis from=C1625003_CALIB.IMG to=foo.cubUSER ERROR Unable to set PDS file. Decompressed input file [C1625003_CALIB.IMG] does not appear to be a PDS product.

$ voy2isis from=C1625003.IMQ to=foo.cub
(works)

It looks like the PDS split out the label information from the IMQ files to LBL files, and uncompressed the images to IMG files.

I've been using the IMG/LBL files in a project and just started using ISIS - if it's an involved fix then I'll see if I can switch to using the IMQ files, though the archives are organized differently.

History

I am not familiar with the "PDS rings node" version of Voyager "ISS", and, I suspect that ISIS3 voy2isis isn't either: A _CALIB.LBL and .IMG filename sounds suspiciously like processed images (modified keyword labels) that ISIS3 voy2isis currently does not expect at ingestion. I will have to ask our internal PDS node staff here in Astro what this version is all about.

As you have already pointed out, the "PDS Imaging node" version
(on volume vg_0017/jupiter/c1625003.imq) with voy2isis works fine; in fact the suite of applications including radiometric calibration seems to work ok:

I will network with our internal PDS staff as well as developer staff regarding voy2isis. This most likely will require a modification to the translation table that voy2isis refers to. This modification would have to be done very carefully in order to avoid causing a problem with the imaging node version (.imq).

When this gets addressed will depend on our developer resources. We will keep you posted through this ticket. In the meantime, I hope processing the pds imaging node version will be sufficient??!

Yes, I'll see if I can switch to using the IMQ files, unless it happened to be an easy fix - I guess no one has been using ISIS with the reorganized/processed Voyager datasets, as it looks like they were created in 2012. They include four versions of each image - RAW, CLEANED (reseau marks removed), CALIB (flatfield correction), and GEOMED (geometric distortion removed).

I would need to redownload the IMG/LBL archives anyway, as I hadn't kept the LBL files, so it wouldn't be too much trouble to get the IMQ archives - the main issue is that the organization is different, but I'll see if I can work around that. If I'd known about ISIS I would have started with the IMQ archives though!

For completeness I'll include the labels from an IMQ file and a corresponding LBL file - they do seem to have changed a bit...

/usgs/shareall/tbecker/VoyagerRingsNode/ = A collection of test data from the PDS rings node archive. Some files in this directory represent a number of problems we have encountered from the original PDS archive that are being addressed by a separate voy2isis ticket (#4421). We are interested in seeing if this processed archive has dealt with the corrupted or unavailable keywords we have encountered with the original set.

Also, it will be extremely important to note the stage of processing these ringsnode-archive images have been through in order for ISIS to recognize..as an example, if a user has imported a C0261155_CALIB.IMG, this image version has been calibrated, so please don't apply the ISIS voycal, or the C0261155_GEOMED.IMG, geometrically corrected (distortion correction), don't apply the ISIS noproj application and treat this image as an "ideal camera". voycal and noproj might need to recognize a keyword label?

An example document archived with this ringsnode data describing the versions of images:

I have tested voy2isis on the Raw version of the 'rings node version' and it creates an output cub, but there is no output instrument group on the labels. It seems there is no translation at all. With the Raw version a full ingestion should be possible to proceed with spiceinit.

I have also tested the other versions (CALIB, GEOMED, etc) and the voy2isis failure with clear message that these versions are currently not supported is sufficient for now.

work area: /work/users/tbecker/IsisTesting/M04421_voy2isis/vg_0024/europa/C2062524_RAW.cub

The input is locate: /usgs/shareall/tbecker/VoyagerRingsNode/C2062524_RAW.LBL, IMG

I have tested the most recent voy2isis and it now functions as planned for now. Currently, ISIS3 will only ingest the _RAW version of the RingsNodeArchive. Upon the attempt to ingest the other processed versions from this archive, the user will be notified with a message explaining that ISIS3 does not currently support it.

The _CALIB, _CLEANED, _GEOMA, _GEOMB and _RESLOC will not be supported until resources are available to handle these processed versions appropriately within the ISIS3 environment.

This will be considered a new development and design that will need to be requested in a separate request/ticket with appropriate funding.