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 ionospheric models in orbit determination #91

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

Support ionospheric models in orbit determination #91

ChristopherRabotin opened this issue Dec 11, 2022 · 0 comments
Labels
Kind: New feature This is a proposed new feature Status: Design Issue at Design phase of the quality assurance process Topic: Orbit Determination

Comments

@ChristopherRabotin
Copy link
Member

High level description

This implementation should be validated against this NASA page:https://ccmc.gsfc.nasa.gov/modelweb/models/iri_vitmo.php .

Implementation should be based on GMAT's: https://github.com/ChristopherRabotin/GMAT/blob/80bde040e12946a61dae90d9fc3538f16df34190/plugins/EstimationPlugin/src/base/measurement/Ionosphere/Ionosphere.cpp .

Check out Navipedia: https://gssc.esa.int/navipedia/index.php/Klobuchar_Ionospheric_Model . And the NeQuick model: https://www.gsc-europa.eu/support-to-developers/nequick-g-source-code (which seems more relevant to Galileo because it transmits these coefficients).

Requirements

(Kinda useless result by ChatGPT)

Test plans

  • Test that the ionosphere model correctly computes the ionosphere delay for a given set of input parameters, such as geodetic latitude, longitude, and altitude of the receiver, and time of day.
  • Test that the ionosphere model correctly incorporates the ionosphere delay into the measurement model, such that it affects the accuracy of the orbit determination results.
  • Test that the ionosphere model can handle edge cases, such as near the magnetic poles, where the ionosphere delay is expected to be large and variable.
  • Test that the ionosphere model produces reasonable results when compared to known datasets, such as those provided by the NASA and ESA ionosphere models.
  • Test that the ionosphere model produces consistent results when used with different GNSS systems, such as GPS, Galileo, and GLONASS.

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: Orbit Determination 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 Status: Design Issue at Design phase of the quality assurance process Topic: Orbit Determination
Projects
None yet
Development

No branches or pull requests

1 participant