Scope Project Responsibilities

[medley56]

Context

Based on a discussion we had internally at LASP, there are a lot of things that could be added to Curryer but it's not totally clear if they fit within the package scope because the package scope isn't totally defined. We don't have to stick 100% to whatever is decided but I think taking a stab would give us direction in prioritizing development work.

Suggestions

In the short description of the package in the Readme, be explicit about what the package does. e.g.

• SPICE SPK and CK creation using MKSPK and MSOPCK
• Abstraction of the MSOPCK and MKSPK interfaces via use of standardized dict configs (these need to be specified clearly somewhere too).
• Kernel downloading and caching from URLs (S3 and NAIF)? @medley56 can contribute this code.
• Geolocation and time conversion utilities building on top of SpiceyPy for common python use cases
• Kernel inspection tools for determining time ranges, predict status, etc based on standard file naming conventions (would need to define these standard naming conventions and they may be of limited use for missions that don't use them)

These are the specific notes I wrote down from our meeting on 9/30/24