-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Load SPICE metakernel #123
Labels
good first issue
Good for newcomers
Kind: new feature
Kind: spice-interop
SPICE interoperability
Status: draft
Issue is at draft stage
Status: scheduled
Comments
ChristopherRabotin
added
good first issue
Good for newcomers
Kind: spice-interop
SPICE interoperability
Status: draft
Issue is at draft stage
Kind: new feature
labels
Oct 15, 2023
ChristopherRabotin
removed this from the Version 0.2: User interfaces + Python milestone
Dec 29, 2023
@GregoireHENRY In your opinion, is this still a required feature, or is the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
Kind: new feature
Kind: spice-interop
SPICE interoperability
Status: draft
Issue is at draft stage
Status: scheduled
High level description
SPICE metakernels are really useful for ensuring that the same data is always loaded correctly. The purpose of this issue is to implement a way to load and append a given Almanac from a SPICE metakernel.
Requirements
Test plans
Design
This is the design section. Each subsection has its own subsection in the quality assurance document.
API definition
Maybe something like this:
Metakernel would implement
FromStr
to be build from the string of the metakernel I think. It would also reuse theparse
function currently used to parse all other KPL files.Example input:
High level architecture
Document, discuss, and optionally upload design diagram into this section.
Detailed design
The detailed design *will be used in the documentation of how ANISE works.
Feel free to fill out additional QA sections here, but these will typically be determined during the development, including the release in which this issue will be tackled.
The text was updated successfully, but these errors were encountered: