Jupiter flyby data cannot use spiceinit

[mashenghan]

ISIS version(s) affected: 7.1.0

Description
We can convert the .qub file into a .cub file with the vims2isis. However, the data at Saturn can be well processed by spiceinit, but most of the data during the Jupiter flyby cannot, because of the lack of necessary camera information in ck files.

How to reproduce
Jupiter flyby data from 2000-321(2000.11.16) to 2001-059(2000.02.28) For example: one of the Jupiter flyby raw data ……/covims_0002/data/2001057T093056_2001058T051230/v1361942552_3.qub. Use vim2sisis: vims2isis from=v1361942552_3.qub vis=v1361942552_3_vis.cub ir=v1361942552_3_ir.cub Use spiceinit: spiceinit from=v1361942552_3_ir.cub

outputs:

**Group = Kernels NaifFrameCode = -82371 LeapSecond = $base/kernels/lsk/naif0012.tls TargetAttitudeShape = ($base/kernels/pck/pck00009.tpc, $cassini/kernels/pck/cpck30Sep2004_jupiter.tpc) TargetPosition = ($base/kernels/spk/de430.bsp, $base/kernels/spk/jup310.bsp) InstrumentPointing = ($cassini/kernels/ck/01058_01063ra.bc, $cassini/kernels/fk/cas_v40_usgs.tf) Instrument = Null SpacecraftClock = $cassini/kernels/sclk/cas00172.tsc InstrumentPosition = $cassini/kernels/spk/010420R_SCPSE_EP1_JP83.bsp InstrumentAddendum = $cassini/kernels/iak/vimsAddendum04.ti ShapeModel = Null InstrumentPositionQuality = Reconstructed InstrumentPointingQuality = Reconstructed CameraVersion = 1 Error = "No pointing available at requested time [36522677.919562] for frame code [10015]" End_Group

Group = Kernels NaifFrameCode = -82371 LeapSecond = $base/kernels/lsk/naif0012.tls TargetAttitudeShape = ($base/kernels/pck/pck00009.tpc, $cassini/kernels/pck/cpck30Sep2004_jupiter.tpc) TargetPosition = ($base/kernels/spk/de430.bsp, $base/kernels/spk/jup310.bsp) InstrumentPointing = ($cassini/kernels/ck/01001_01091rc.bc, $cassini/kernels/fk/cas_v40_usgs.tf) Instrument = Null SpacecraftClock = $cassini/kernels/sclk/cas00172.tsc InstrumentPosition = $cassini/kernels/spk/010420R_SCPSE_EP1_JP83.bsp InstrumentAddendum = $cassini/kernels/iak/vimsAddendum04.ti ShapeModel = Null InstrumentPositionQuality = Reconstructed InstrumentPointingQuality = Reconstructed CameraVersion = 1 Error = "No pointing available at requested time [36522677.919562] for frame code [10015]" End_Group

Group = Kernels NaifFrameCode = -82371 LeapSecond = $base/kernels/lsk/naif0012.tls TargetAttitudeShape = ($base/kernels/pck/pck00009.tpc, $cassini/kernels/pck/cpck30Sep2004_jupiter.tpc) TargetPosition = ($base/kernels/spk/de430.bsp, $base/kernels/spk/jup310.bsp) InstrumentPointing = ($cassini/kernels/ck/010227_010301rb.bc, $cassini/kernels/fk/cas_v40_usgs.tf) Instrument = Null SpacecraftClock = $cassini/kernels/sclk/cas00172.tsc InstrumentPosition = $cassini/kernels/spk/010420R_SCPSE_EP1_JP83.bsp InstrumentAddendum = $cassini/kernels/iak/vimsAddendum04.ti ShapeModel = Null InstrumentPositionQuality = Reconstructed InstrumentPointingQuality = Reconstructed CameraVersion = 1 Error = "No pointing available at requested time [36522677.919562] for frame code [10015]" End_Group ERROR Unable to initialize camera model.**

Any solution ?

[github-actions[bot]]

Thank you for your contribution!

Unfortunately, this issue hasn't received much attention lately, so it is labeled as 'stale.'

If no additional action is taken, this issue will be automatically closed in 180 days.

If you want to participate in our support prioritization meetings or be notified when support sprints are happening, you can sign up the support sprint notification emails here.

Read more about our support processs here

[lwellerastro]

I took a look at this and confirmed the VIMS data noted above can not be spiced (under isis8.1.0-RC2). I also confirmed that VIMS data of Titan was successfully spiced. Data is available under my users work area Isis3Tests/Vims2Isis/ (top level is the above failing file and the Other/ directory has successful Titan and Jupiter images).

Best I can tell we have kept up with the available kernels. This may simply be a case where the particular flyby/image has no kernels available. I'm not 100% sure and would encourage the author to look at various README files and other kernels documents associated with the mission here for further information.

[acpaquette]

Hello @mashenghan,

Apologies for such a late reply on this issue. If you are still working with the vims data the issue seems to reside with the pck file used. Namely, $base/kernels/pck/pck00009.tpc. This file contains nutation/precession angles for Jupiter, but only has 10 instead of the 15 that c_spice requires to use to compute the body rotation.

To get this working right now try running any spiceinit command with the following option set pck=$ISISDATA/base/kernels/pck/pck00008.tpc.

So a full command would be something like: spiceinit from=my_vims_image.cub pck=$ISISDATA/base/kernels/pck/pck00008.tpc

[acpaquette]

@mashenghan To add to this see the pck readme from NAIF about the current PCKs. ISIS only has up to pck00009.tpc for various reason, largely historical.

In looking over pointing/position information in some vims data, testing pck00008.tpc, pck00009.tpc, and the custom PCK that is selected from the kernel.db file. They all have very similar body positions so any of them would be good choices to process against.

I was mistaken in thinking it was specifically pck00009.tpc being the problem. Rather it was loading the two PCKs you indicate above in the PVL group. The suggestion to define the PCK youself is a band aid and needs a proper fix in the cassini kernel.db file, which I am working on.

[acpaquette]

As a final note here. This problem was also present in the cassini ISS data which is much higher resolution and I was able to get a better idea of the offset between all of the PCKs:

From left to right I used pck00010, pck00008, pck00009, and cpck30Sep2004_jupiter.tpc. The 8, 9 and custom align fairly well and 10 has about a 2ish pixel sample shift which is quite large for the distances and resolutions we are dealing with. As to what is correct, I am not sure.

[acpaquette]

I have updated the cassini PCKs to use pck00008. This should work over wed if the server is working correctly and should work locally if you update your local area with a the downloadIsisData script.