Support Circular Restricted Three Body problems #96
Labels
Kind: New feature
This is a proposed new feature
Priority: normal
Status: Design
Issue at Design phase of the quality assurance process
Topic: Mission Design
High level description
A normalized Earth-Moon barycenter frame is needed for libration point orbit studies.
By Matt Bolliger:
The rotating aspect is probably more important. Nondimensionalization helps generalize the system to any pair of bodies, and can help with computation, but I think the most important thing is that your rotating frame is correct. (edited)
10:19
Section 2.1 has some more details: https://engineering.purdue.edu/people/kathleen.howell.1/Publications/Masters/2019_Bolliger.pdf
Requirements
The purpose of this section is to fill out the Requirements of the QA process.
Requirements answer the question: what does the system need to do? It does not answer the question of how does the system do this?
Test plans
How do we test that these requirements are fulfilled correctly? What are some edge cases we should be aware of when developing the test code.
Design
This is the design section. Each subsection has its own subsection in the quality assurance document.
Algorithm demonstration
If this issue requires a change in an algorithm, it should be described here. This algorithm should be described thoroughly enough to be used as documentation. This section may also simply refer to an algorithm in the literature or in another piece of software that has been validated. The quality of that reference will be determined case by case.
API definition
Define how the Nyx APIs will be affect by this: what are new functions available, do any previous function change their definition, why call these functions by that name, etc.
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 Nyx 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: