-
Notifications
You must be signed in to change notification settings - Fork 22
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
The PBL value derived by PB2NC does not match VSDB. #1199
Comments
John pulled down the sample files from WCOSS to dakota: [johnhg@dakota]% ls /d3/projects/MET/MET_Help/shafran_data_20190920 |
PB2NC should derive PBL observations only for ADPUPA and AIRCFT message types. From John on 9/27/2019: From Perry on 9/27/2019: |
Howard, I picked a single ADPUPA observation to test more: 70398, where MET's PBL = 84.607 while VSDB's PBL = 140. Then I reconfigured PB2NC to only process ADPUPA... and only process that station: But that run yielded 2 PBL values (-10034 and 174.05) for that station!? Perhaps you could start by debugging that discrepancy? Why processing all the stations vs a single station yields a different result. They should definitely be the same! FYI, this test data is all on dakota in /d3/projects/MET/MET_Help/shafran_data_20190920. |
Reassigned this from met-8.1.2 to met-9.0 since it was taking too long to be included in a bugfix release. |
The PBL is computed only for ADPUPA.
|
We need to update PB2NC to make sense of the discrepancies in PBL values computed in VSDB and MET.
Perry is generating test output on WCOSS.
Input PrepBUFR file:
/gpfs/dell1/nco/ops/com/nam/prod/nam.20190919/nam.t06z.prepbufr.tm06
And when the run is complete, you'll be able to find files in this directory:
/stmpp1/Perry.Shafran/tmpnwpara/verf_gridtobs_nam_00/00
The prepfit.out.nam file will contain the profile, with station ID, of the Z, T, U, V, and P that goes into the calculation of the PBL height. Search for "staid".
The gto.nam.00 file will contain the PBL values for each station. Search for "PBL".
The text was updated successfully, but these errors were encountered: