Lenient qc as default behaviour #118
Merged
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
users will automatically get detailed fullness fraction attributes, can add False in config if not needed
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.
(some small formatting changes also present but) Mainly this PR is to include a more lenient QC as the default behaviour of halodrops.
This means instead of filtering out sondes that do not pass the QC thresholds of profile fullness or near surface coverage, the QC will allow all sondes to go from Level-1 to Level-2. However, the attributes of profile fullness & near surface coverage for all variables will be added as global attributes to the NC file, so that it is easier to filter out such sondes later on if needed during analyses.