Fixed native_msg calibration problem and added env var to change the … #219
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…calibration coefficients from nominal to gsics
|
I couldn't find a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixed native_msg calibration problem, calibrated data from calibration function wasnt being assigned on return, and added an env var (CAL_MODE) to change the calibration coefficent values , in the Level1.5 header from NOMINAL to GSICS.
Change was made to the native_msg.py reader.
I also added a new area definition in areas.def, msg_resample_area which has a lon0 of 20.75. We can use this to resample /validate MET8 and MET11 (or 9 or 10) in the overlap area.