issues in running spiceinit on Chandrayaan2 OHRC image

[Aaranay]

Hi, although this issue is in isis, Would you happen to know any fix for it?

I'm trying to run spiceinit on an OHRC image that I converted to cub using isisimport command. Apparently the translation file in MissionName2DataDir within the latest isis3 env had no mention of chandrayaan 2 mission. However, I was able to find that line in the github repo. After pasting that in the original file, I ran into the error: PVL keyword [Chandrayaan2] does not exist in [Group = DataDirectory].

I believe that this is because there isn't a single translation file for this mission in the environment, which is actually true because all the missions are listed in /appdata/translations/, except chandrayaan2. I tried searching for these files in the github repo too, but they weren't available. For a temporary fix, I tried copying and renaming the chandrayaan1 files to chandrayaan2 files. But that didn't work. 

Would you happen to know where I can find the translation files for chandrayaan2? Or if there's an alternate fix?

for reference, I also checked the files within the latest isis3 env (~8.3.0), but there were no files for this mission.

[Oleg Alexandrov]

Our Chandrayaan 2 doc says in the intro that this workflow is not ready for general use (https://stereopipeline.readthedocs.io/en/latest/examples/chandrayaan2.html#chandrayaan2).

The issue is that ISIS does not yet distribute the needed code or data. 

It is suggested you also file this as an issue with ISIS. ISIS and ASP are part of different organizations, and ISIS has its own planning and scheduling. Last I recall they were still in negotiation with the Indian space agency about how to properly share their data. 

I think you will need to build ISIS from source, likely fetch the latest ALE from coda (which I think is quite new), download the SPICE kernels from the ISRO (which is a big pain), and I could share my own addendum iak data which is not shipped with the kernels.

Sorry about this. This spring it looked as if the ISIS people were close to fully having this orbiter supported, also potentially with an official release, but then I had no contact with their team and when they were planning to finish up.

Filing an issue on their site is still likely the best way of figuring out what they are up to.

--
You received this message because you are subscribed to the Google Groups "Ames Stereo Pipeline Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ames-stereo-pipeline...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ames-stereo-pipeline-support/13d3bf1e-bb7e-42eb-98ac-640513c346c6n%40googlegroups.com.