Skip to content
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

Support Circular Restricted Three Body problems #96

Open
ChristopherRabotin opened this issue Dec 11, 2022 · 0 comments
Open

Support Circular Restricted Three Body problems #96

ChristopherRabotin opened this issue Dec 11, 2022 · 0 comments
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

Comments

@ChristopherRabotin
Copy link
Member

High level description

A normalized Earth-Moon barycenter frame is needed for libration point orbit studies.

By Matt Bolliger:

  1. Two gravitational point masses only.
  2. The point masses move about their mutual barycenter in circular orbits.
  3. The x-axis of the rotating frame points from the barycenter to the smaller point mass.
  4. The z-axis points along the angular momentum vector of the system.
  5. Third body is the massless s/c.
  6. Congrats

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.

@ChristopherRabotin ChristopherRabotin added Status: Design Issue at Design phase of the quality assurance process Kind: New feature This is a proposed new feature Topic: Mission Design Priority: normal labels Dec 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant