Addition of the RefNLPEP2D GNSSRO forward operator #77
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a new 2D GNSSRO forward operator based on refractivity that simulates a path-integrated variable called nonLocalPseudoExcessPhase.
Summary of changes:
Description
This PR provides a new GNSSRO forward operator called RefNLPEP2D. The RefNLPEP2D forward operator is a JEDI UFO implementation of the non-local pseudo excess phase approach of Sokolovskiy, et al, 2005. This is logically similar to the GPSEPH forward operator in WRFDA, but shares no code with that earlier implementation.
RefNLPEP2D is a 2D forward operator based integrating excess refractive index, computed from refractivity, over a predefined GNSS RO ray path that does not change during the data assimilation process. The same ray path is used to compute a derived observation of non-local pseudo excess phase from refractivity observations and the assumption of spherical symmetry. The operator allows a model's horizontal variations in refractivity to be used when simulating GNSS RO observations.
Issue(s) addressed
This is not associated with an issue number.
Dependencies
There are corresponding PRs in ufo-data and jedi-docs that include unit test data and documentation for this PR.
Impact
Most of the code is in new modules, and hence should have no impact on other subsystems.
The only two code changes are:
Checklist