-
Notifications
You must be signed in to change notification settings - Fork 176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spiceinit exits on Error "Unable to initialize camera model" on MRO CRISM TRDR IR sensor data, but works for the VNIR sensor. #5730
Comments
I get this error while I used CRISM IR sensor PDS data too:
|
@emresezer that the same issue reported in #5728, in your case, spiceinit Error refers to |
Hi @afrigeri, I found this issue as well. The problem is another library, ALE. I can get a change in and get a new build out the door |
Fix is up and just waiting on tests to come back. |
@afrigeri You should be able to run the following while your ISIS 8.X.X environment is active:
And that should fix the problem with the CRISM TRDR data |
I confirm that now also CRISM TRDR IR sensor data gets through spiceinit without errors:
Thanks, @acpaquette + ISIS dev team! |
ISIS version(s) affected: 8.0.3
Description
While discussing #5728 I've found that spiceinit works correctly on CRISM Targeted Reduced Data Record (TRDR) VNIR sensor (S code) cube but exits and returns error on the IR (L code) sensor file.
How to reproduce
crism2isis
bothspiceinit from=frt0001c558_07_if165s_trr3.cub
gets through and no errors.spiceinit from=frt0001c558_07_if165l_trr3.cub
exits with**ERROR** Unable to initialize camera model.
and returns:the error persists also after re-running spiceinit as reported in the error message.
Possible Solution
Somehow the INS-74018_FOCAL_LENGTH key/value (which is available in
$mro/kernels/iak/crismAddendum001.ti
) is not being attached into the IR channel cube (L sensor, ID 74018) byspiceinit
.For the VNIR case (S sensor, ID 74017), the INS-74017_FOCAL_LENGTH is read and attached to the ISIS cube by
spiceinit
:Additional context
I have checked and verified the same behavior on the
frt0000810d_07_if166[s/l]_trr3
cubes, did not do other tests yet.Did not check previous data versions (< 3)
The text was updated successfully, but these errors were encountered: