-
Notifications
You must be signed in to change notification settings - Fork 24
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
Feature 1824 pb2nc MLCAPE2 #2060
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hsoh-u thanks for working on this. I carefully diffed the nam and ndas files that were flagged by the regression test. Please see below before merging this PR.
- There are no unexpected diffs in the "ndas" output files - only the addition of MLCAP obs.
- Comparing the "nam" output files, 4 HBPL observations with a value 0 are now missing.
Rscript pntnc2ascii.R nam.20210311.t00z.prepbufr.tm00.pbl_TRUTH.nc | sed -r 's/ $/00 /g' > nam.20210311.t00z.prepbufr.tm00.pbl_TRUTH.txtRscript pntnc2ascii.R nam.20210311.t00z.prepbufr.tm00.pbl_OUTPUT.nc | egrep -v MLCAPE > nam.20210311.t00z.prepbufr.tm00.pbl_OUTPUT.txt
diff nam.20210311.t00z.prepbufr.tm00.pbl_TRUTH.txt nam.20210311.t00z.prepbufr.tm00.pbl_OUTPUT.txt
There are 4 HBPL observations from TRUTH that no longer appear in OUTPUT:
74,75d73
< ADPUPA 30119A 20210310_232900 36.10 -128.10 9300 HPBL NA 0 2 0.000000
< ADPUPA 30120A 20210310_235300 35.80 -125.10 9450 HPBL NA 0 2 0.000000
165,166d162
< ADPUPA 30122A 20210311_001700 37.90 -125.50 9450 HPBL NA 0 2 0.000000
< ADPUPA 30125A 20210311_003300 37.30 -123.80 9450 HPBL NA 0 2 0.000000
I compared the many other HPBL obs and these values of 0 are the only ones missing. So I assume that that was an intentional change included in this PR.
If that change was intentional, please merge this PR. If not and those HPBL obs = 0 should remain, please take a closer look.
This was reported as the difference at Docker build. It turned out this happening when the merged PTQ and UV record is only: The computed PBL value is 0 at one system and filtered out (negative or greater than MAX) at other system. This is a comment at PR #2057
|
And one more data at ndas.20120409.t12z.prepbufr.tm00.var_all.nc (one MLCAPE value is added to the unit test of all variable)_. |
Co-authored-by: Julie Prestopnik <[email protected]> Co-authored-by: johnhg <[email protected]> Co-authored-by: Seth Linden <[email protected]> Co-authored-by: John Halley Gotway <[email protected]> Co-authored-by: j-opatz <[email protected]> Co-authored-by: Howard Soh <[email protected]> Co-authored-by: John Halley Gotway <[email protected]> Co-authored-by: jprestop <[email protected]> Co-authored-by: Howard Soh <[email protected]> Co-authored-by: Seth Linden <[email protected]> Co-authored-by: hsoh-u <[email protected]> Co-authored-by: George McCabe <[email protected]> Co-authored-by: John Halley Gotway <[email protected]> Co-authored-by: MET Tools Test Account <[email protected]> Co-authored-by: mo-mglover <[email protected]> Co-authored-by: davidalbo <[email protected]> Co-authored-by: lisagoodrich <[email protected]>
Expected Differences
Fixed the difference at CAPE after activating MLCAPE
Do these changes introduce new tools, command line arguments, or configuration file options? [No]
If yes, please describe:
Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
If yes, please describe:
Pull Request Testing
Run unit test and compare the PBL and CAPE values
Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]
Do these changes include sufficient testing updates? [No]
Will this PR result in changes to the test suite? [No]
If yes, describe the new output and/or changes to the existing output:
Please complete this pull request review by [Fill in date].
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s)
Select: Organization level software support Project or Repository level development cycle Project
Select: Milestone as the version that will include these changes