Fix bug introduced for SLSTR cloud flags when naming convention changed #482
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
|
Thanks to @dr1315 and @barnabysandeford for identifying issue. |
Codecov Report
@@ Coverage Diff @@
## master #482 +/- ##
=======================================
Coverage 74.15% 74.15%
=======================================
Files 136 136
Lines 18070 18070
=======================================
Hits 13400 13400
Misses 4670 4670Continue to review full report at Codecov.
|
mraspaud
changed the title
|
Thanks for spotting and fixing this! |
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.
In #458 the name of the longitude and latitude elements in the YAML file was updated to have the sufixes for the stripes and views. This was not migrated to the cloud masks that are subsequently using this. No change in Python code.