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

Need documentation on expected input units #3

Open
ReeceHumphreys opened this issue Mar 30, 2022 · 0 comments
Open

Need documentation on expected input units #3

ReeceHumphreys opened this issue Mar 30, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Milestone

Comments

@ReeceHumphreys
Copy link
Owner

Currently there is no documentation on expected input units. Currently the units are as follows:

Current units for input:

  • Satellite mass [km]
  • Min. Characteristic Length [m]
  • Position [m]
  • Velocity [m/s]

There needs to be documentation to indicate this. Additionally, ODAP and other python packages tend to use kilometers for position and kilometers per second for velocity. There needs to be a better way to handle this other than changing the units on the Satellite implementation.

@ReeceHumphreys ReeceHumphreys added documentation Improvements or additions to documentation enhancement New feature or request labels Mar 30, 2022
@ReeceHumphreys ReeceHumphreys added this to the 0.0.2 release milestone Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant