You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
The sources for some kernel groups within the rclone config file included with ISIS 8.0.0 and up have change reflecting how NAIF archives the kernel groups. Bellow are some of the changes I had to make to get the correct kernels from upstream sources:
[messenger_naifKernels]
type = combine
-upstreams = kernels=naif:/pub/naif/pds/data/mess-e_v_h-spice-6-v1.0/messsp_1000/data/kernels/
+upstreams = kernels=naif:/pub/naif/pds/data/mess-e_v_h-spice-6-v1.0/messsp_1000/data/
[mgs_naifKernels]
type = combine
-upstreams = kernels=naif:/pub/naif/pds/data/mgs-m-spice-6-v1.0/mgsp_1000/data/kernels/
+upstreams = kernels=naif:/pub/naif/pds/data/mgs-m-spice-6-v1.0/mgsp_1000/data/
[newhorizons_naifKernels]
type = combine
-upstreams = kernels=naif:/pub/naif/NEWHORIZONS/kernels/
+upstreams = kernels=naif:/pub/naif/pds/data/nh-j_p_ss-spice-6-v1.0/nhsp_1000/data/
How to reproduce
Attempt to download any of the above kernel sets and compare it to the isis_data area under the asc_data S3 bucket.
Possible Solution
There may be a better way to manage the kernel downloads. I think this is why in the past we have acted as an intermediary between naif and the kernels that are specific to ISIS. This ensures that users are not exposed to this particular issue. We already duplicate the kernels under the S3 bucket so I don't know why that can't be the record/source for all ISIS kernels.
The text was updated successfully, but these errors were encountered:
ISIS version(s) affected: 8.0.0+
Description
The sources for some kernel groups within the rclone config file included with ISIS 8.0.0 and up have change reflecting how NAIF archives the kernel groups. Bellow are some of the changes I had to make to get the correct kernels from upstream sources:
How to reproduce
Attempt to download any of the above kernel sets and compare it to the
isis_data
area under theasc_data
S3 bucket.Possible Solution
There may be a better way to manage the kernel downloads. I think this is why in the past we have acted as an intermediary between naif and the kernels that are specific to ISIS. This ensures that users are not exposed to this particular issue. We already duplicate the kernels under the S3 bucket so I don't know why that can't be the record/source for all ISIS kernels.
The text was updated successfully, but these errors were encountered: