[Met_help] [rt.rap.ucar.edu #82010] History for Verifying visibility and cloud ceiling height
John Halley Gotway via RT
met_help at ucar.edu
Thu Nov 9 11:21:31 MST 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I'm interested in verifying visibility and cloud ceiling height with Point Stat. With MET version 6.1 is it now possible to retrieve these types of observations using PB2NC? I spoke with Perry and the menumonics for visibility and cloud ceiling are HOVI and CEILING, respectively.
Thanks,
Ben
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: John Halley Gotway
Time: Thu Sep 14 13:12:29 2017
Ben,
Yes, met-6.1_beta1 includes the ability to extract additional
observation types. However, I have not actually exercised that new
functionality myself. I'd like to work up an example and send it to
you. And having you exercise it will be great testing.
What point observation dataset are you using? NDAS, GDAS?
Should I run point_stat to compare to GFS... or some other model?
While it's great to test this beta version, I'd caution you against
using it for anything official. We still need to add some new
statistics to the output lines... so they'll change in the official
version of met-6.1. Also, METViewer has not yet been updated to load
the output of met-6.1.
Thanks,
John
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: Benjamin Blake - NOAA Affiliate
Time: Thu Sep 14 13:21:47 2017
Hi John,
Sure, I'd be willing to test that out. I am using NDAS (the NAM
prepbufr
files) and was going to compare to the HREF members (which consists of
the
HiResWindows and the NAM).
And that's fine, I will hold off on using it for the project I'm
working
on. I can add C&V verification at a later date.
If I have additional questions about any of this we can meet in person
while you are at NCEP next week.
Thanks!
Ben
On Thu, Sep 14, 2017 at 3:12 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Ben,
>
> Yes, met-6.1_beta1 includes the ability to extract additional
observation
> types. However, I have not actually exercised that new
functionality
> myself. I'd like to work up an example and send it to you. And
having you
> exercise it will be great testing.
>
> What point observation dataset are you using? NDAS, GDAS?
>
> Should I run point_stat to compare to GFS... or some other model?
>
> While it's great to test this beta version, I'd caution you against
using
> it for anything official. We still need to add some new statistics
to the
> output lines... so they'll change in the official version of met-
6.1.
> Also, METViewer has not yet been updated to load the output of met-
6.1.
>
> Thanks,
> John
>
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: John Halley Gotway
Time: Fri Sep 15 11:01:32 2017
Hi Ben,
I tried to work through an example of using pb2nc and point_stat to
verify
visibility and ceiling. While it is *possible* using met-6.1_beta1,
it
isn't very intuitive. In particular, the settings in PB2NC are
confusing
because the developer enabled it to be run the "old way" or the "new
way".
To make the pb2nc config options simpler, I think we should only
support
the "new way". So we'll talk about that change today.
Because of this, I think it'd be a good idea to hold off until
met-6.1_beta2.
But since I'd already written it up, here's what I did using met-
6.1_beta1
to do C&V verification using PREPBUFR point observations and
point_stat.
# Pull a recent NDAS PREPBUFR file and a 24-hour NAM CONUS Nest
forecast
wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
am.20170914/nam.t00z.prepbufr.tm00.nr
wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
<ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
# Run PB2NC with the -index option to see what observations are
present.
# This takes a *VERY* long time to run but you'd only index the
variable
names once for each type of data (i.e. NDAS, GDAS, or some variety of
BUFR
file).
# I've listed the output from PB2NC at the end of this message, which
does
include HOVI and CEILING
met-6.1_beta1/bin/pb2nc \
nam.t00z.prepbufr.tm00.nr \
nam.t00z.prepbufr.tm00_pb2nc.nc \
PB2NCConfig_candv -index
# Run PB2NC (without the -index option) requesting HOVI and CEILING
using
the -vars command line option:
# -vars HOVI,CEILING
met-6.1_beta1/bin/pb2nc \
nam.t00z.prepbufr.tm00.nr \
nam.t00z.prepbufr.tm00_pb2nc.nc \
PB2NCConfig_candv -vars HOVI,CEILING
# Run Point-Stat to compare:
# 1: forecast VIS to obs HOVI using message type ANYSFC (i.e. ADPSFC +
SFCSHP)
# 2: forecast RETOP to obs CEILING using message type ANYSFC (i.e.
ADPSFC +
SFCSHP)
met-6.1_beta1/bin/point_stat \
nam.t00z.conusnest.hiresf24.tm00.grib2 \
nam.t00z.prepbufr.tm00_pb2nc.nc \
PointStatConfig_candv -outdir out \
-v 3
I wrote out the matched pair information and saw some interesting
behavior:
1: Model VIS has a max value of 24,100 while observed HOVI has a max
value
of 81,900. And the values look very "binned". Might want to do
categorical verification instead of continuous verification since the
data
doesn't look very continuous.
2: Model RETOP has a range of values from -5000 to 9247. Observed
CEILING
has a range of values from 30 to 20000. Again you might want to do
categorical vx instead of continuous.
I've attached the config files for PB2NC and Point-Stat along with the
matched pairs output file from Point-Stat.
Thanks,
John
------------------------------------------------------------
--------------------------------------
DEBUG 1: Default Config File: /var/autofs/mnt/dakota_d3/proj
ects/MET/MET_releases/met-
6.1_beta1/share/met/config/PB2NCConfig_default
DEBUG 1: User Config File: PB2NCConfig_candv
DEBUG 1:
DEBUG 1: Pre-processing Bufr File for metadata (BUFR variable names)
from
nam.t00z.prepbufr.tm00.nr
5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80% 85% 90%
95%
DEBUG 1:
DEBUG 1: Header variables:
DEBUG 1: SID: STATION IDENTIFICATION
DEBUG 1: XOB: LONGITUDE
DEBUG 1: YOB: LATITUDE
DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
DEBUG 1: ELV: STATION ELEVATION
DEBUG 1: TYP: PREPBUFR REPORT TYPE
DEBUG 1: T29: DATA DUMP REPORT TYPE
DEBUG 1: ITP: INSTRUMENT TYPE
DEBUG 1:
DEBUG 1: Observation variables:
DEBUG 1: POB: PRESSURE OBSERVATION
DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
DEBUG 1: TOB: TEMPERATURE OBSERVATION
DEBUG 1: ZOB: HEIGHT OBSERVATION
DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
DEBUG 1: D_DWP:
DEBUG 1: D_WDIR:
DEBUG 1: D_WIND:
DEBUG 1: D_RH:
DEBUG 1: D_MIXR:
DEBUG 1: D_PRMSL:
DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF LOWEST CLOUD
SEEN
DEBUG 1: CLTP: CLOUD TYPE
DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC HUMIDITY VALUE
DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM CODE
DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE VALUE
DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION (NOT
ASSIMILATED)
DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS (NOT
ASSIMILATED)
DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
DEBUG 1: POE: PRESSURE OBSERVATION ERROR
DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE VALUE
DEBUG 1: PRC: PRESSURE EVENT REASON CODE
DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL BASED ON
BALLOON
DFT)
DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL BASED ON
BALLOON
DFT)
DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR RAOB/PIBAL, BASED ON
B
DFT)
DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN (OBTAINED FROM
SCRIPT)
DEBUG 1: SQN: REPORT SEQUENCE NUMBER
DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN "DHR" WAS
CORRECTED
DEBUG 1: RPT: REPORTED OBSERVATION TIME
DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED RADIATION CORR.
INDICATOR
DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT ASSIMILATED)
DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB) OBSERVATION ERROR
DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT WIND VALUE
DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT WIND VALUE
DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB) EVENT REASON CODE
DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB) EVENT PROGRAM
CODE
DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB) (QUALITY) MARKER
DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or SOB) EVENT
REASON
CODE
DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or SOB) EVENT PGM
CODE
DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or SOB) (QUALITY)
MARKER
DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT ASSIMILATED)
DEBUG 1: CLAM: CLOUD AMOUNT
DEBUG 1: DGOT: DEGREE OF TURBULENCE
DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS MEANINGS DEPENDING
ON
TYPE)
DEBUG 1: RCT: RECEIPT TIME
DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK (ADDED BY PGM
PREPACQC)
DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
DEBUG 1: AFIC: AIRFRAME ICING
DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
DEBUG 1: PRWE: PRESENT WEATHER
DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS EXPECTED
ERROR
DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL INDX
W/O
FCST
DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL INDX
W/ FCST
DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS RECURSIVE
FILTER
FCN
DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT ASSIMILATED)
DEBUG 1: TOCC: CLOUD COVER (TOTAL)
DEBUG 1: HOVI: HORIZONTAL VISIBILITY
DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
DEBUG 1: MITM: MINIMUM TEMPERATURE
DEBUG 1: MXTM: MAXIMUM TEMPERATURE
DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY) MARKER
DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
DEBUG 1: TOSD: TOTAL SNOW DEPTH
DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC OBSERVATION)
DEBUG 1: PSW2: PAST WEATHER (2)
DEBUG 1: PSW1: PAST WEATHER (1)
DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER EQUIVALENT
DEBUG 1: DOFS: DEPTH OF FRESH SNOW
DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB - HGT OF CLOUD
BASE)
DEBUG 1: PKWDSP: PEAK WIND SPEED
DEBUG 1: PKWDDR: PEAK WIND DIRECTION
DEBUG 1: VTVI: VERTICAL VISIBILITY
DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
DEBUG 1: SST1: SEA TEMPERATURE
DEBUG 1: HOWW: HEIGHT OF WIND WAVES
DEBUG 1: POWW: PERIOD OF WIND WAVES
DEBUG 1: HOWV: HEIGHT OF WAVES
DEBUG 1: POWV: PERIOD OF WAVES
DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST 3 HOURS
DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE MEASUREMENT
DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
DEBUG 1: POSW: PERIOD OF SWELL WAVES
DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON CODE
DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM CODE
DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE OBSERVATION
DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS ONLY)
DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT REPORTS ONLY)
DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION (ASCAT REPORTS
ONLY)
DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT & ASCAT
REPORTS
ONLY)
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: John Halley Gotway
Time: Fri Sep 15 11:01:32 2017
VERSION MODEL DESC FCST_LEAD FCST_VALID_BEG FCST_VALID_END OBS_LEAD
OBS_VALID_BEG OBS_VALID_END FCST_VAR FCST_LEV OBS_VAR OBS_LEV OBTYPE
VX_MASK INTERP_MTHD INTERP_PNTS FCST_THRESH OBS_THRESH COV_THRESH
ALPHA LINE_TYPE TOTAL INDEX OBS_SID OBS_LAT OBS_LON OBS_LVL OBS_ELV
FCST OBS CLIMO OBS_QC
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: John Halley Gotway
Time: Fri Sep 15 11:16:35 2017
Ugh, the file attachment was too big. So I posted it on our anonymous
ftp
site:
ftp ftp.rap.ucar.edu
- anonymous
- your email address
cd incoming/irap/met_help/blake_data
get point_stat_240000L_20170914_000000V_mpr.txt
John
On Fri, Sep 15, 2017 at 11:09 AM, John Halley Gotway <johnhg at ucar.edu>
wrote:
> Ben,
>
> Sorry, that MPR file I sent was empty. Here's the real one.
>
> Thanks,
> John
>
> On Fri, Sep 15, 2017 at 11:01 AM, John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
>> Hi Ben,
>>
>> I tried to work through an example of using pb2nc and point_stat to
>> verify visibility and ceiling. While it is *possible* using met-
6.1_beta1,
>> it isn't very intuitive. In particular, the settings in PB2NC are
>> confusing because the developer enabled it to be run the "old way"
or the
>> "new way". To make the pb2nc config options simpler, I think we
should
>> only support the "new way". So we'll talk about that change today.
>>
>> Because of this, I think it'd be a good idea to hold off until
>> met-6.1_beta2.
>>
>> But since I'd already written it up, here's what I did using
>> met-6.1_beta1 to do C&V verification using PREPBUFR point
observations and
>> point_stat.
>>
>> # Pull a recent NDAS PREPBUFR file and a 24-hour NAM CONUS Nest
forecast
>>
>> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
>> am.20170914/nam.t00z.prepbufr.tm00.nr
>> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
>> am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
>>
<ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
>>
>> # Run PB2NC with the -index option to see what observations are
present.
>> # This takes a *VERY* long time to run but you'd only index the
variable
>> names once for each type of data (i.e. NDAS, GDAS, or some variety
of BUFR
>> file).
>> # I've listed the output from PB2NC at the end of this message,
which
>> does include HOVI and CEILING
>>
>> met-6.1_beta1/bin/pb2nc \
>> nam.t00z.prepbufr.tm00.nr \
>> nam.t00z.prepbufr.tm00_pb2nc.nc \
>> PB2NCConfig_candv -index
>>
>> # Run PB2NC (without the -index option) requesting HOVI and CEILING
using
>> the -vars command line option:
>> # -vars HOVI,CEILING
>>
>> met-6.1_beta1/bin/pb2nc \
>> nam.t00z.prepbufr.tm00.nr \
>> nam.t00z.prepbufr.tm00_pb2nc.nc \
>> PB2NCConfig_candv -vars HOVI,CEILING
>>
>> # Run Point-Stat to compare:
>> # 1: forecast VIS to obs HOVI using message type ANYSFC (i.e.
ADPSFC +
>> SFCSHP)
>> # 2: forecast RETOP to obs CEILING using message type ANYSFC (i.e.
ADPSFC
>> + SFCSHP)
>>
>> met-6.1_beta1/bin/point_stat \
>> nam.t00z.conusnest.hiresf24.tm00.grib2 \
>> nam.t00z.prepbufr.tm00_pb2nc.nc \
>> PointStatConfig_candv -outdir out \
>> -v 3
>>
>> I wrote out the matched pair information and saw some interesting
>> behavior:
>>
>> 1: Model VIS has a max value of 24,100 while observed HOVI has a
max
>> value of 81,900. And the values look very "binned". Might want to
do
>> categorical verification instead of continuous verification since
the data
>> doesn't look very continuous.
>>
>> 2: Model RETOP has a range of values from -5000 to 9247. Observed
>> CEILING has a range of values from 30 to 20000. Again you might
want to do
>> categorical vx instead of continuous.
>>
>> I've attached the config files for PB2NC and Point-Stat along with
the
>> matched pairs output file from Point-Stat.
>>
>> Thanks,
>> John
>>
>>
>>
>>
>> ------------------------------------------------------------
>> --------------------------------------
>>
>> DEBUG 1: Default Config File: /var/autofs/mnt/dakota_d3/proj
>> ects/MET/MET_releases/met-
6.1_beta1/share/met/config/PB2NCConfig_default
>>
>> DEBUG 1: User Config File: PB2NCConfig_candv
>>
>> DEBUG 1:
>>
>> DEBUG 1: Pre-processing Bufr File for metadata (BUFR variable
names) from
>> nam.t00z.prepbufr.tm00.nr
>>
>> 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80% 85%
90% 95%
>>
>>
>> DEBUG 1:
>>
>> DEBUG 1: Header variables:
>>
>> DEBUG 1: SID: STATION IDENTIFICATION
>>
>> DEBUG 1: XOB: LONGITUDE
>>
>> DEBUG 1: YOB: LATITUDE
>>
>> DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
>>
>> DEBUG 1: ELV: STATION ELEVATION
>>
>> DEBUG 1: TYP: PREPBUFR REPORT TYPE
>>
>> DEBUG 1: T29: DATA DUMP REPORT TYPE
>>
>> DEBUG 1: ITP: INSTRUMENT TYPE
>>
>> DEBUG 1:
>>
>> DEBUG 1: Observation variables:
>>
>> DEBUG 1: POB: PRESSURE OBSERVATION
>>
>> DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
>>
>> DEBUG 1: TOB: TEMPERATURE OBSERVATION
>>
>> DEBUG 1: ZOB: HEIGHT OBSERVATION
>>
>> DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
>>
>> DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
>>
>> DEBUG 1: D_DWP:
>>
>> DEBUG 1: D_WDIR:
>>
>> DEBUG 1: D_WIND:
>>
>> DEBUG 1: D_RH:
>>
>> DEBUG 1: D_MIXR:
>>
>> DEBUG 1: D_PRMSL:
>>
>> DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF LOWEST CLOUD
SEEN
>>
>> DEBUG 1: CLTP: CLOUD TYPE
>>
>> DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
>>
>> DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC HUMIDITY VALUE
>>
>> DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
>>
>> DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM CODE
>>
>> DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
>>
>> DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
>>
>> DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE VALUE
>>
>> DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
>>
>> DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
>>
>> DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
>>
>> DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION (NOT
ASSIMILATED)
>>
>> DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS (NOT
>> ASSIMILATED)
>>
>> DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
>>
>> DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
>>
>> DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
>>
>> DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
>>
>> DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
>>
>> DEBUG 1: POE: PRESSURE OBSERVATION ERROR
>>
>> DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE VALUE
>>
>> DEBUG 1: PRC: PRESSURE EVENT REASON CODE
>>
>> DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
>>
>> DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
>>
>> DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL BASED ON
BALLOON
>> DFT)
>>
>> DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL BASED ON
BALLOON
>> DFT)
>>
>> DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR RAOB/PIBAL, BASED
ON B
>> DFT)
>>
>> DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN (OBTAINED
FROM
>> SCRIPT)
>>
>> DEBUG 1: SQN: REPORT SEQUENCE NUMBER
>>
>> DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN "DHR" WAS
CORRECTED
>>
>> DEBUG 1: RPT: REPORTED OBSERVATION TIME
>>
>> DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED RADIATION CORR.
>> INDICATOR
>>
>> DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT
ASSIMILATED)
>>
>> DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB) OBSERVATION
ERROR
>>
>> DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT WIND VALUE
>>
>> DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT WIND VALUE
>>
>> DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB) EVENT REASON
CODE
>>
>> DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB) EVENT PROGRAM
CODE
>>
>> DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB) (QUALITY)
MARKER
>>
>> DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or SOB) EVENT
REASON
>> CODE
>>
>> DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or SOB) EVENT
PGM
>> CODE
>>
>> DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
(QUALITY)
>> MARKER
>>
>> DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT ASSIMILATED)
>>
>> DEBUG 1: CLAM: CLOUD AMOUNT
>>
>> DEBUG 1: DGOT: DEGREE OF TURBULENCE
>>
>> DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS MEANINGS
DEPENDING ON
>> TYPE)
>>
>> DEBUG 1: RCT: RECEIPT TIME
>>
>> DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK (ADDED BY PGM
>> PREPACQC)
>>
>> DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
>>
>> DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
>>
>> DEBUG 1: AFIC: AIRFRAME ICING
>>
>> DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
>>
>> DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
>>
>> DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
>>
>> DEBUG 1: PRWE: PRESENT WEATHER
>>
>> DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS EXPECTED
ERROR
>>
>> DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL
INDX W/O
>> FCST
>>
>> DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL
INDX W/
>> FCST
>>
>> DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS RECURSIVE
>> FILTER FCN
>>
>> DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
>>
>> DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT
ASSIMILATED)
>>
>> DEBUG 1: TOCC: CLOUD COVER (TOTAL)
>>
>> DEBUG 1: HOVI: HORIZONTAL VISIBILITY
>>
>> DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
>>
>> DEBUG 1: MITM: MINIMUM TEMPERATURE
>>
>> DEBUG 1: MXTM: MAXIMUM TEMPERATURE
>>
>> DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
>>
>> DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY) MARKER
>>
>> DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
>>
>> DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
>>
>> DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
>>
>> DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
>>
>> DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
>>
>> DEBUG 1: TOSD: TOTAL SNOW DEPTH
>>
>> DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC OBSERVATION)
>>
>> DEBUG 1: PSW2: PAST WEATHER (2)
>>
>> DEBUG 1: PSW1: PAST WEATHER (1)
>>
>> DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
>>
>> DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
>>
>> DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
>>
>> DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER EQUIVALENT
>>
>> DEBUG 1: DOFS: DEPTH OF FRESH SNOW
>>
>> DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
>>
>> DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB - HGT OF
CLOUD
>> BASE)
>>
>> DEBUG 1: PKWDSP: PEAK WIND SPEED
>>
>> DEBUG 1: PKWDDR: PEAK WIND DIRECTION
>>
>> DEBUG 1: VTVI: VERTICAL VISIBILITY
>>
>> DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
>>
>> DEBUG 1: SST1: SEA TEMPERATURE
>>
>> DEBUG 1: HOWW: HEIGHT OF WIND WAVES
>>
>> DEBUG 1: POWW: PERIOD OF WIND WAVES
>>
>> DEBUG 1: HOWV: HEIGHT OF WAVES
>>
>> DEBUG 1: POWV: PERIOD OF WAVES
>>
>> DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
>>
>> DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
>>
>> DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
>>
>> DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST 3 HOURS
>>
>> DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
>>
>> DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE MEASUREMENT
>>
>> DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
>>
>> DEBUG 1: POSW: PERIOD OF SWELL WAVES
>>
>> DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
>>
>> DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
>>
>> DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON CODE
>>
>> DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM CODE
>>
>> DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
>>
>> DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
>>
>> DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE OBSERVATION
>>
>> DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS ONLY)
>>
>> DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT REPORTS ONLY)
>>
>> DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION (ASCAT
REPORTS
>> ONLY)
>>
>> DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT & ASCAT
REPORTS
>> ONLY)
>>
>
>
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: Benjamin Blake - NOAA Affiliate
Time: Fri Sep 15 11:41:28 2017
Hi John,
Thanks for putting this example together. I retrieved the MPR file
off of
the FTP server and I will attempt to reproduce what you did on Monday
using
met6.1_beta1.
So for running PB2NC, the "old" way you referred to is mapping the
BUFR
variable name to GRIB, and the "new" way is using the MET variable
index
from the var_name variable?
Thanks,
Ben
On Fri, Sep 15, 2017 at 1:16 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Ugh, the file attachment was too big. So I posted it on our
anonymous ftp
> site:
>
> ftp ftp.rap.ucar.edu
> - anonymous
> - your email address
> cd incoming/irap/met_help/blake_data
> get point_stat_240000L_20170914_000000V_mpr.txt
>
> John
>
> On Fri, Sep 15, 2017 at 11:09 AM, John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
> > Ben,
> >
> > Sorry, that MPR file I sent was empty. Here's the real one.
> >
> > Thanks,
> > John
> >
> > On Fri, Sep 15, 2017 at 11:01 AM, John Halley Gotway
<johnhg at ucar.edu>
> > wrote:
> >
> >> Hi Ben,
> >>
> >> I tried to work through an example of using pb2nc and point_stat
to
> >> verify visibility and ceiling. While it is *possible* using
> met-6.1_beta1,
> >> it isn't very intuitive. In particular, the settings in PB2NC
are
> >> confusing because the developer enabled it to be run the "old
way" or
> the
> >> "new way". To make the pb2nc config options simpler, I think we
should
> >> only support the "new way". So we'll talk about that change
today.
> >>
> >> Because of this, I think it'd be a good idea to hold off until
> >> met-6.1_beta2.
> >>
> >> But since I'd already written it up, here's what I did using
> >> met-6.1_beta1 to do C&V verification using PREPBUFR point
observations
> and
> >> point_stat.
> >>
> >> # Pull a recent NDAS PREPBUFR file and a 24-hour NAM CONUS Nest
forecast
> >>
> >> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> >> am.20170914/nam.t00z.prepbufr.tm00.nr
> >> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> >> am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
> >> <ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/
> nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
> >>
> >> # Run PB2NC with the -index option to see what observations are
present.
> >> # This takes a *VERY* long time to run but you'd only index the
variable
> >> names once for each type of data (i.e. NDAS, GDAS, or some
variety of
> BUFR
> >> file).
> >> # I've listed the output from PB2NC at the end of this message,
which
> >> does include HOVI and CEILING
> >>
> >> met-6.1_beta1/bin/pb2nc \
> >> nam.t00z.prepbufr.tm00.nr \
> >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> >> PB2NCConfig_candv -index
> >>
> >> # Run PB2NC (without the -index option) requesting HOVI and
CEILING
> using
> >> the -vars command line option:
> >> # -vars HOVI,CEILING
> >>
> >> met-6.1_beta1/bin/pb2nc \
> >> nam.t00z.prepbufr.tm00.nr \
> >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> >> PB2NCConfig_candv -vars HOVI,CEILING
> >>
> >> # Run Point-Stat to compare:
> >> # 1: forecast VIS to obs HOVI using message type ANYSFC (i.e.
ADPSFC +
> >> SFCSHP)
> >> # 2: forecast RETOP to obs CEILING using message type ANYSFC
(i.e.
> ADPSFC
> >> + SFCSHP)
> >>
> >> met-6.1_beta1/bin/point_stat \
> >> nam.t00z.conusnest.hiresf24.tm00.grib2 \
> >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> >> PointStatConfig_candv -outdir out \
> >> -v 3
> >>
> >> I wrote out the matched pair information and saw some interesting
> >> behavior:
> >>
> >> 1: Model VIS has a max value of 24,100 while observed HOVI has a
max
> >> value of 81,900. And the values look very "binned". Might want
to do
> >> categorical verification instead of continuous verification since
the
> data
> >> doesn't look very continuous.
> >>
> >> 2: Model RETOP has a range of values from -5000 to 9247.
Observed
> >> CEILING has a range of values from 30 to 20000. Again you might
want
> to do
> >> categorical vx instead of continuous.
> >>
> >> I've attached the config files for PB2NC and Point-Stat along
with the
> >> matched pairs output file from Point-Stat.
> >>
> >> Thanks,
> >> John
> >>
> >>
> >>
> >>
> >> ------------------------------------------------------------
> >> --------------------------------------
> >>
> >> DEBUG 1: Default Config File: /var/autofs/mnt/dakota_d3/proj
> >> ects/MET/MET_releases/met-6.1_beta1/share/met/config/
> PB2NCConfig_default
> >>
> >> DEBUG 1: User Config File: PB2NCConfig_candv
> >>
> >> DEBUG 1:
> >>
> >> DEBUG 1: Pre-processing Bufr File for metadata (BUFR variable
names)
> from
> >> nam.t00z.prepbufr.tm00.nr
> >>
> >> 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80%
85% 90%
> 95%
> >>
> >>
> >> DEBUG 1:
> >>
> >> DEBUG 1: Header variables:
> >>
> >> DEBUG 1: SID: STATION IDENTIFICATION
> >>
> >> DEBUG 1: XOB: LONGITUDE
> >>
> >> DEBUG 1: YOB: LATITUDE
> >>
> >> DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
> >>
> >> DEBUG 1: ELV: STATION ELEVATION
> >>
> >> DEBUG 1: TYP: PREPBUFR REPORT TYPE
> >>
> >> DEBUG 1: T29: DATA DUMP REPORT TYPE
> >>
> >> DEBUG 1: ITP: INSTRUMENT TYPE
> >>
> >> DEBUG 1:
> >>
> >> DEBUG 1: Observation variables:
> >>
> >> DEBUG 1: POB: PRESSURE OBSERVATION
> >>
> >> DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
> >>
> >> DEBUG 1: TOB: TEMPERATURE OBSERVATION
> >>
> >> DEBUG 1: ZOB: HEIGHT OBSERVATION
> >>
> >> DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
> >>
> >> DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
> >>
> >> DEBUG 1: D_DWP:
> >>
> >> DEBUG 1: D_WDIR:
> >>
> >> DEBUG 1: D_WIND:
> >>
> >> DEBUG 1: D_RH:
> >>
> >> DEBUG 1: D_MIXR:
> >>
> >> DEBUG 1: D_PRMSL:
> >>
> >> DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF LOWEST
CLOUD SEEN
> >>
> >> DEBUG 1: CLTP: CLOUD TYPE
> >>
> >> DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
> >>
> >> DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC HUMIDITY
VALUE
> >>
> >> DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
> >>
> >> DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM CODE
> >>
> >> DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
> >>
> >> DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
> >>
> >> DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE VALUE
> >>
> >> DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
> >>
> >> DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
> >>
> >> DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
> >>
> >> DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION (NOT
ASSIMILATED)
> >>
> >> DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS (NOT
> >> ASSIMILATED)
> >>
> >> DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
> >>
> >> DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
> >>
> >> DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
> >>
> >> DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
> >>
> >> DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
> >>
> >> DEBUG 1: POE: PRESSURE OBSERVATION ERROR
> >>
> >> DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE VALUE
> >>
> >> DEBUG 1: PRC: PRESSURE EVENT REASON CODE
> >>
> >> DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
> >>
> >> DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
> >>
> >> DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL BASED ON
BALLOON
> >> DFT)
> >>
> >> DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL BASED ON
BALLOON
> >> DFT)
> >>
> >> DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR RAOB/PIBAL,
BASED ON B
> >> DFT)
> >>
> >> DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN (OBTAINED
FROM
> >> SCRIPT)
> >>
> >> DEBUG 1: SQN: REPORT SEQUENCE NUMBER
> >>
> >> DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN "DHR" WAS
CORRECTED
> >>
> >> DEBUG 1: RPT: REPORTED OBSERVATION TIME
> >>
> >> DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED RADIATION CORR.
> >> INDICATOR
> >>
> >> DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT
ASSIMILATED)
> >>
> >> DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB) OBSERVATION
ERROR
> >>
> >> DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT WIND
VALUE
> >>
> >> DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT WIND
VALUE
> >>
> >> DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB) EVENT REASON
CODE
> >>
> >> DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
PROGRAM CODE
> >>
> >> DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB) (QUALITY)
MARKER
> >>
> >> DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or SOB) EVENT
REASON
> >> CODE
> >>
> >> DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or SOB) EVENT
PGM
> >> CODE
> >>
> >> DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
(QUALITY)
> >> MARKER
> >>
> >> DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT
ASSIMILATED)
> >>
> >> DEBUG 1: CLAM: CLOUD AMOUNT
> >>
> >> DEBUG 1: DGOT: DEGREE OF TURBULENCE
> >>
> >> DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS MEANINGS
DEPENDING ON
> >> TYPE)
> >>
> >> DEBUG 1: RCT: RECEIPT TIME
> >>
> >> DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK (ADDED BY
PGM
> >> PREPACQC)
> >>
> >> DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
> >>
> >> DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
> >>
> >> DEBUG 1: AFIC: AIRFRAME ICING
> >>
> >> DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
> >>
> >> DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
> >>
> >> DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
> >>
> >> DEBUG 1: PRWE: PRESENT WEATHER
> >>
> >> DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS EXPECTED
ERROR
> >>
> >> DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL
INDX W/O
> >> FCST
> >>
> >> DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL
INDX W/
> >> FCST
> >>
> >> DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS
RECURSIVE
> >> FILTER FCN
> >>
> >> DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
> >>
> >> DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT
ASSIMILATED)
> >>
> >> DEBUG 1: TOCC: CLOUD COVER (TOTAL)
> >>
> >> DEBUG 1: HOVI: HORIZONTAL VISIBILITY
> >>
> >> DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
> >>
> >> DEBUG 1: MITM: MINIMUM TEMPERATURE
> >>
> >> DEBUG 1: MXTM: MAXIMUM TEMPERATURE
> >>
> >> DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
> >>
> >> DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY) MARKER
> >>
> >> DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
> >>
> >> DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
> >>
> >> DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
> >>
> >> DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
> >>
> >> DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
> >>
> >> DEBUG 1: TOSD: TOTAL SNOW DEPTH
> >>
> >> DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC OBSERVATION)
> >>
> >> DEBUG 1: PSW2: PAST WEATHER (2)
> >>
> >> DEBUG 1: PSW1: PAST WEATHER (1)
> >>
> >> DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
> >>
> >> DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
> >>
> >> DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
> >>
> >> DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER EQUIVALENT
> >>
> >> DEBUG 1: DOFS: DEPTH OF FRESH SNOW
> >>
> >> DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
> >>
> >> DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB - HGT OF
CLOUD
> >> BASE)
> >>
> >> DEBUG 1: PKWDSP: PEAK WIND SPEED
> >>
> >> DEBUG 1: PKWDDR: PEAK WIND DIRECTION
> >>
> >> DEBUG 1: VTVI: VERTICAL VISIBILITY
> >>
> >> DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
> >>
> >> DEBUG 1: SST1: SEA TEMPERATURE
> >>
> >> DEBUG 1: HOWW: HEIGHT OF WIND WAVES
> >>
> >> DEBUG 1: POWW: PERIOD OF WIND WAVES
> >>
> >> DEBUG 1: HOWV: HEIGHT OF WAVES
> >>
> >> DEBUG 1: POWV: PERIOD OF WAVES
> >>
> >> DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
> >>
> >> DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
> >>
> >> DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
> >>
> >> DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST 3 HOURS
> >>
> >> DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
> >>
> >> DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE
MEASUREMENT
> >>
> >> DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
> >>
> >> DEBUG 1: POSW: PERIOD OF SWELL WAVES
> >>
> >> DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
> >>
> >> DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
> >>
> >> DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON CODE
> >>
> >> DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM CODE
> >>
> >> DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
> >>
> >> DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
> >>
> >> DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE OBSERVATION
> >>
> >> DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS ONLY)
> >>
> >> DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT REPORTS
ONLY)
> >>
> >> DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION (ASCAT
REPORTS
> >> ONLY)
> >>
> >> DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT & ASCAT
REPORTS
> >> ONLY)
> >>
> >
> >
>
>
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: John Halley Gotway
Time: Fri Sep 15 12:01:46 2017
Ben,
Yes, that's exactly right.
The "old" way identifies observations by assigning them a GRIB code.
The "new" way identifies observations using strings. Instead of a
GRIB
code, we assign the observation a "var_id". That integer is an index
into
the "var_name" array in the NetCDF file which lists strings for the
variables present in the file.
In the old way, an observation of temperature would have GRIB code 11.
In the new way, an observation of temperature might have a var_id of
3...
and the "var_name" array would have the string "TMP" at index 3.
The variable name are taken from the PREPBUFR mnemonic tables.
However,
you can override their use by setting up the "obs_var_map". For
example,
perhaps you'd like to name the observations of "HOVI" as "VIS" instead
and
observations of "CEILING" to "RETOP" instead. You'd do that by
setting:
obs_var_map = [
{ key = "HOVI"; val = "VIS"; },
{ key = "CEILING"; val = "RETOP"; }
];
Thanks,
John
On Fri, Sep 15, 2017 at 11:41 AM Benjamin Blake - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82010 >
>
> Hi John,
>
> Thanks for putting this example together. I retrieved the MPR file
off of
> the FTP server and I will attempt to reproduce what you did on
Monday using
> met6.1_beta1.
>
> So for running PB2NC, the "old" way you referred to is mapping the
BUFR
> variable name to GRIB, and the "new" way is using the MET variable
index
> from the var_name variable?
>
> Thanks,
> Ben
>
> On Fri, Sep 15, 2017 at 1:16 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Ugh, the file attachment was too big. So I posted it on our
anonymous
> ftp
> > site:
> >
> > ftp ftp.rap.ucar.edu
> > - anonymous
> > - your email address
> > cd incoming/irap/met_help/blake_data
> > get point_stat_240000L_20170914_000000V_mpr.txt
> >
> > John
> >
> > On Fri, Sep 15, 2017 at 11:09 AM, John Halley Gotway
<johnhg at ucar.edu>
> > wrote:
> >
> > > Ben,
> > >
> > > Sorry, that MPR file I sent was empty. Here's the real one.
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, Sep 15, 2017 at 11:01 AM, John Halley Gotway
<johnhg at ucar.edu>
> > > wrote:
> > >
> > >> Hi Ben,
> > >>
> > >> I tried to work through an example of using pb2nc and
point_stat to
> > >> verify visibility and ceiling. While it is *possible* using
> > met-6.1_beta1,
> > >> it isn't very intuitive. In particular, the settings in PB2NC
are
> > >> confusing because the developer enabled it to be run the "old
way" or
> > the
> > >> "new way". To make the pb2nc config options simpler, I think
we
> should
> > >> only support the "new way". So we'll talk about that change
today.
> > >>
> > >> Because of this, I think it'd be a good idea to hold off until
> > >> met-6.1_beta2.
> > >>
> > >> But since I'd already written it up, here's what I did using
> > >> met-6.1_beta1 to do C&V verification using PREPBUFR point
observations
> > and
> > >> point_stat.
> > >>
> > >> # Pull a recent NDAS PREPBUFR file and a 24-hour NAM CONUS Nest
> forecast
> > >>
> > >> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > >> am.20170914/nam.t00z.prepbufr.tm00.nr
> > >> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > >> am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
> > >> <ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/
> > nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
> > >>
> > >> # Run PB2NC with the -index option to see what observations are
> present.
> > >> # This takes a *VERY* long time to run but you'd only index the
> variable
> > >> names once for each type of data (i.e. NDAS, GDAS, or some
variety of
> > BUFR
> > >> file).
> > >> # I've listed the output from PB2NC at the end of this message,
which
> > >> does include HOVI and CEILING
> > >>
> > >> met-6.1_beta1/bin/pb2nc \
> > >> nam.t00z.prepbufr.tm00.nr \
> > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > >> PB2NCConfig_candv -index
> > >>
> > >> # Run PB2NC (without the -index option) requesting HOVI and
CEILING
> > using
> > >> the -vars command line option:
> > >> # -vars HOVI,CEILING
> > >>
> > >> met-6.1_beta1/bin/pb2nc \
> > >> nam.t00z.prepbufr.tm00.nr \
> > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > >> PB2NCConfig_candv -vars HOVI,CEILING
> > >>
> > >> # Run Point-Stat to compare:
> > >> # 1: forecast VIS to obs HOVI using message type ANYSFC (i.e.
ADPSFC +
> > >> SFCSHP)
> > >> # 2: forecast RETOP to obs CEILING using message type ANYSFC
(i.e.
> > ADPSFC
> > >> + SFCSHP)
> > >>
> > >> met-6.1_beta1/bin/point_stat \
> > >> nam.t00z.conusnest.hiresf24.tm00.grib2 \
> > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > >> PointStatConfig_candv -outdir out \
> > >> -v 3
> > >>
> > >> I wrote out the matched pair information and saw some
interesting
> > >> behavior:
> > >>
> > >> 1: Model VIS has a max value of 24,100 while observed HOVI has
a max
> > >> value of 81,900. And the values look very "binned". Might
want to do
> > >> categorical verification instead of continuous verification
since the
> > data
> > >> doesn't look very continuous.
> > >>
> > >> 2: Model RETOP has a range of values from -5000 to 9247.
Observed
> > >> CEILING has a range of values from 30 to 20000. Again you
might want
> > to do
> > >> categorical vx instead of continuous.
> > >>
> > >> I've attached the config files for PB2NC and Point-Stat along
with the
> > >> matched pairs output file from Point-Stat.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >>
> > >>
> > >>
> > >> ------------------------------------------------------------
> > >> --------------------------------------
> > >>
> > >> DEBUG 1: Default Config File: /var/autofs/mnt/dakota_d3/proj
> > >> ects/MET/MET_releases/met-6.1_beta1/share/met/config/
> > PB2NCConfig_default
> > >>
> > >> DEBUG 1: User Config File: PB2NCConfig_candv
> > >>
> > >> DEBUG 1:
> > >>
> > >> DEBUG 1: Pre-processing Bufr File for metadata (BUFR variable
names)
> > from
> > >> nam.t00z.prepbufr.tm00.nr
> > >>
> > >> 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80%
85% 90%
> > 95%
> > >>
> > >>
> > >> DEBUG 1:
> > >>
> > >> DEBUG 1: Header variables:
> > >>
> > >> DEBUG 1: SID: STATION IDENTIFICATION
> > >>
> > >> DEBUG 1: XOB: LONGITUDE
> > >>
> > >> DEBUG 1: YOB: LATITUDE
> > >>
> > >> DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
> > >>
> > >> DEBUG 1: ELV: STATION ELEVATION
> > >>
> > >> DEBUG 1: TYP: PREPBUFR REPORT TYPE
> > >>
> > >> DEBUG 1: T29: DATA DUMP REPORT TYPE
> > >>
> > >> DEBUG 1: ITP: INSTRUMENT TYPE
> > >>
> > >> DEBUG 1:
> > >>
> > >> DEBUG 1: Observation variables:
> > >>
> > >> DEBUG 1: POB: PRESSURE OBSERVATION
> > >>
> > >> DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
> > >>
> > >> DEBUG 1: TOB: TEMPERATURE OBSERVATION
> > >>
> > >> DEBUG 1: ZOB: HEIGHT OBSERVATION
> > >>
> > >> DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
> > >>
> > >> DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
> > >>
> > >> DEBUG 1: D_DWP:
> > >>
> > >> DEBUG 1: D_WDIR:
> > >>
> > >> DEBUG 1: D_WIND:
> > >>
> > >> DEBUG 1: D_RH:
> > >>
> > >> DEBUG 1: D_MIXR:
> > >>
> > >> DEBUG 1: D_PRMSL:
> > >>
> > >> DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF LOWEST
CLOUD
> SEEN
> > >>
> > >> DEBUG 1: CLTP: CLOUD TYPE
> > >>
> > >> DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
> > >>
> > >> DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC HUMIDITY
VALUE
> > >>
> > >> DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
> > >>
> > >> DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM CODE
> > >>
> > >> DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
> > >>
> > >> DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
> > >>
> > >> DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE VALUE
> > >>
> > >> DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
> > >>
> > >> DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
> > >>
> > >> DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
> > >>
> > >> DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION (NOT
> ASSIMILATED)
> > >>
> > >> DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS (NOT
> > >> ASSIMILATED)
> > >>
> > >> DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
> > >>
> > >> DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
> > >>
> > >> DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
> > >>
> > >> DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
> > >>
> > >> DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
> > >>
> > >> DEBUG 1: POE: PRESSURE OBSERVATION ERROR
> > >>
> > >> DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE VALUE
> > >>
> > >> DEBUG 1: PRC: PRESSURE EVENT REASON CODE
> > >>
> > >> DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
> > >>
> > >> DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
> > >>
> > >> DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL BASED
ON
> BALLOON
> > >> DFT)
> > >>
> > >> DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL BASED
ON
> BALLOON
> > >> DFT)
> > >>
> > >> DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR RAOB/PIBAL,
BASED
> ON B
> > >> DFT)
> > >>
> > >> DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN (OBTAINED
FROM
> > >> SCRIPT)
> > >>
> > >> DEBUG 1: SQN: REPORT SEQUENCE NUMBER
> > >>
> > >> DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN "DHR" WAS
> CORRECTED
> > >>
> > >> DEBUG 1: RPT: REPORTED OBSERVATION TIME
> > >>
> > >> DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED RADIATION
CORR.
> > >> INDICATOR
> > >>
> > >> DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT
ASSIMILATED)
> > >>
> > >> DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB)
OBSERVATION ERROR
> > >>
> > >> DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT WIND
VALUE
> > >>
> > >> DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT WIND
VALUE
> > >>
> > >> DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
REASON CODE
> > >>
> > >> DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
PROGRAM
> CODE
> > >>
> > >> DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB) (QUALITY)
MARKER
> > >>
> > >> DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
EVENT
> REASON
> > >> CODE
> > >>
> > >> DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
EVENT PGM
> > >> CODE
> > >>
> > >> DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
(QUALITY)
> > >> MARKER
> > >>
> > >> DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT
ASSIMILATED)
> > >>
> > >> DEBUG 1: CLAM: CLOUD AMOUNT
> > >>
> > >> DEBUG 1: DGOT: DEGREE OF TURBULENCE
> > >>
> > >> DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS MEANINGS
DEPENDING
> ON
> > >> TYPE)
> > >>
> > >> DEBUG 1: RCT: RECEIPT TIME
> > >>
> > >> DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK (ADDED BY
PGM
> > >> PREPACQC)
> > >>
> > >> DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
> > >>
> > >> DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
> > >>
> > >> DEBUG 1: AFIC: AIRFRAME ICING
> > >>
> > >> DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
> > >>
> > >> DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
> > >>
> > >> DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
> > >>
> > >> DEBUG 1: PRWE: PRESENT WEATHER
> > >>
> > >> DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS
EXPECTED
> ERROR
> > >>
> > >> DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL
INDX
> W/O
> > >> FCST
> > >>
> > >> DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON EUMETSAT QUAL
INDX
> W/
> > >> FCST
> > >>
> > >> DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS
RECURSIVE
> > >> FILTER FCN
> > >>
> > >> DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
> > >>
> > >> DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT
ASSIMILATED)
> > >>
> > >> DEBUG 1: TOCC: CLOUD COVER (TOTAL)
> > >>
> > >> DEBUG 1: HOVI: HORIZONTAL VISIBILITY
> > >>
> > >> DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
> > >>
> > >> DEBUG 1: MITM: MINIMUM TEMPERATURE
> > >>
> > >> DEBUG 1: MXTM: MAXIMUM TEMPERATURE
> > >>
> > >> DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
> > >>
> > >> DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY) MARKER
> > >>
> > >> DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
> > >>
> > >> DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
> > >>
> > >> DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
> > >>
> > >> DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
> > >>
> > >> DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
> > >>
> > >> DEBUG 1: TOSD: TOTAL SNOW DEPTH
> > >>
> > >> DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC OBSERVATION)
> > >>
> > >> DEBUG 1: PSW2: PAST WEATHER (2)
> > >>
> > >> DEBUG 1: PSW1: PAST WEATHER (1)
> > >>
> > >> DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
> > >>
> > >> DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
> > >>
> > >> DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
> > >>
> > >> DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER
EQUIVALENT
> > >>
> > >> DEBUG 1: DOFS: DEPTH OF FRESH SNOW
> > >>
> > >> DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
> > >>
> > >> DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB - HGT
OF CLOUD
> > >> BASE)
> > >>
> > >> DEBUG 1: PKWDSP: PEAK WIND SPEED
> > >>
> > >> DEBUG 1: PKWDDR: PEAK WIND DIRECTION
> > >>
> > >> DEBUG 1: VTVI: VERTICAL VISIBILITY
> > >>
> > >> DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
> > >>
> > >> DEBUG 1: SST1: SEA TEMPERATURE
> > >>
> > >> DEBUG 1: HOWW: HEIGHT OF WIND WAVES
> > >>
> > >> DEBUG 1: POWW: PERIOD OF WIND WAVES
> > >>
> > >> DEBUG 1: HOWV: HEIGHT OF WAVES
> > >>
> > >> DEBUG 1: POWV: PERIOD OF WAVES
> > >>
> > >> DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
> > >>
> > >> DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
> > >>
> > >> DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
> > >>
> > >> DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST 3
HOURS
> > >>
> > >> DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
> > >>
> > >> DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE
MEASUREMENT
> > >>
> > >> DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
> > >>
> > >> DEBUG 1: POSW: PERIOD OF SWELL WAVES
> > >>
> > >> DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
> > >>
> > >> DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
> > >>
> > >> DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON CODE
> > >>
> > >> DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM CODE
> > >>
> > >> DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
> > >>
> > >> DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
> > >>
> > >> DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE OBSERVATION
> > >>
> > >> DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS ONLY)
> > >>
> > >> DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT REPORTS
ONLY)
> > >>
> > >> DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION (ASCAT
REPORTS
> > >> ONLY)
> > >>
> > >> DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT & ASCAT
> REPORTS
> > >> ONLY)
> > >>
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: Benjamin Blake - NOAA Affiliate
Time: Mon Sep 18 11:02:55 2017
Hi John,
I was able to reproduce what you did using met6.1_beta1 on WCOSS
(Gyre)
with pb2nc and point stat. I modified the point stat config file to
produce continuous and categorical statistics for HOVI/VIS and
CEILING/RETOP.
I've placed the output on this public FTP site if you'd like to take a
look:
ftp://ftp.emc.ncep.noaa.gov/mmb/bblake/met6.1_beta1/
Thanks again for setting this up.
Ben
On Fri, Sep 15, 2017 at 2:01 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Ben,
>
> Yes, that's exactly right.
>
> The "old" way identifies observations by assigning them a GRIB code.
>
> The "new" way identifies observations using strings. Instead of a
GRIB
> code, we assign the observation a "var_id". That integer is an
index into
> the "var_name" array in the NetCDF file which lists strings for the
> variables present in the file.
>
> In the old way, an observation of temperature would have GRIB code
11.
>
> In the new way, an observation of temperature might have a var_id of
3...
> and the "var_name" array would have the string "TMP" at index 3.
>
> The variable name are taken from the PREPBUFR mnemonic tables.
However,
> you can override their use by setting up the "obs_var_map". For
example,
> perhaps you'd like to name the observations of "HOVI" as "VIS"
instead and
> observations of "CEILING" to "RETOP" instead. You'd do that by
setting:
>
> obs_var_map = [
> { key = "HOVI"; val = "VIS"; },
> { key = "CEILING"; val = "RETOP"; }
>
> ];
>
> Thanks,
> John
>
> On Fri, Sep 15, 2017 at 11:41 AM Benjamin Blake - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82010 >
> >
> > Hi John,
> >
> > Thanks for putting this example together. I retrieved the MPR
file off
> of
> > the FTP server and I will attempt to reproduce what you did on
Monday
> using
> > met6.1_beta1.
> >
> > So for running PB2NC, the "old" way you referred to is mapping the
BUFR
> > variable name to GRIB, and the "new" way is using the MET variable
index
> > from the var_name variable?
> >
> > Thanks,
> > Ben
> >
> > On Fri, Sep 15, 2017 at 1:16 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Ugh, the file attachment was too big. So I posted it on our
anonymous
> > ftp
> > > site:
> > >
> > > ftp ftp.rap.ucar.edu
> > > - anonymous
> > > - your email address
> > > cd incoming/irap/met_help/blake_data
> > > get point_stat_240000L_20170914_000000V_mpr.txt
> > >
> > > John
> > >
> > > On Fri, Sep 15, 2017 at 11:09 AM, John Halley Gotway
<johnhg at ucar.edu>
> > > wrote:
> > >
> > > > Ben,
> > > >
> > > > Sorry, that MPR file I sent was empty. Here's the real one.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Fri, Sep 15, 2017 at 11:01 AM, John Halley Gotway <
> johnhg at ucar.edu>
> > > > wrote:
> > > >
> > > >> Hi Ben,
> > > >>
> > > >> I tried to work through an example of using pb2nc and
point_stat to
> > > >> verify visibility and ceiling. While it is *possible* using
> > > met-6.1_beta1,
> > > >> it isn't very intuitive. In particular, the settings in
PB2NC are
> > > >> confusing because the developer enabled it to be run the "old
way"
> or
> > > the
> > > >> "new way". To make the pb2nc config options simpler, I think
we
> > should
> > > >> only support the "new way". So we'll talk about that change
today.
> > > >>
> > > >> Because of this, I think it'd be a good idea to hold off
until
> > > >> met-6.1_beta2.
> > > >>
> > > >> But since I'd already written it up, here's what I did using
> > > >> met-6.1_beta1 to do C&V verification using PREPBUFR point
> observations
> > > and
> > > >> point_stat.
> > > >>
> > > >> # Pull a recent NDAS PREPBUFR file and a 24-hour NAM CONUS
Nest
> > forecast
> > > >>
> > > >> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > > >> am.20170914/nam.t00z.prepbufr.tm00.nr
> > > >> wget ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > > >> am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
> > > >> <ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/
> > > nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
> > > >>
> > > >> # Run PB2NC with the -index option to see what observations
are
> > present.
> > > >> # This takes a *VERY* long time to run but you'd only index
the
> > variable
> > > >> names once for each type of data (i.e. NDAS, GDAS, or some
variety
> of
> > > BUFR
> > > >> file).
> > > >> # I've listed the output from PB2NC at the end of this
message,
> which
> > > >> does include HOVI and CEILING
> > > >>
> > > >> met-6.1_beta1/bin/pb2nc \
> > > >> nam.t00z.prepbufr.tm00.nr \
> > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > >> PB2NCConfig_candv -index
> > > >>
> > > >> # Run PB2NC (without the -index option) requesting HOVI and
CEILING
> > > using
> > > >> the -vars command line option:
> > > >> # -vars HOVI,CEILING
> > > >>
> > > >> met-6.1_beta1/bin/pb2nc \
> > > >> nam.t00z.prepbufr.tm00.nr \
> > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > >> PB2NCConfig_candv -vars HOVI,CEILING
> > > >>
> > > >> # Run Point-Stat to compare:
> > > >> # 1: forecast VIS to obs HOVI using message type ANYSFC (i.e.
> ADPSFC +
> > > >> SFCSHP)
> > > >> # 2: forecast RETOP to obs CEILING using message type ANYSFC
(i.e.
> > > ADPSFC
> > > >> + SFCSHP)
> > > >>
> > > >> met-6.1_beta1/bin/point_stat \
> > > >> nam.t00z.conusnest.hiresf24.tm00.grib2 \
> > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > >> PointStatConfig_candv -outdir out \
> > > >> -v 3
> > > >>
> > > >> I wrote out the matched pair information and saw some
interesting
> > > >> behavior:
> > > >>
> > > >> 1: Model VIS has a max value of 24,100 while observed HOVI
has a max
> > > >> value of 81,900. And the values look very "binned". Might
want to
> do
> > > >> categorical verification instead of continuous verification
since
> the
> > > data
> > > >> doesn't look very continuous.
> > > >>
> > > >> 2: Model RETOP has a range of values from -5000 to 9247.
Observed
> > > >> CEILING has a range of values from 30 to 20000. Again you
might
> want
> > > to do
> > > >> categorical vx instead of continuous.
> > > >>
> > > >> I've attached the config files for PB2NC and Point-Stat along
with
> the
> > > >> matched pairs output file from Point-Stat.
> > > >>
> > > >> Thanks,
> > > >> John
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> ------------------------------------------------------------
> > > >> --------------------------------------
> > > >>
> > > >> DEBUG 1: Default Config File: /var/autofs/mnt/dakota_d3/proj
> > > >> ects/MET/MET_releases/met-6.1_beta1/share/met/config/
> > > PB2NCConfig_default
> > > >>
> > > >> DEBUG 1: User Config File: PB2NCConfig_candv
> > > >>
> > > >> DEBUG 1:
> > > >>
> > > >> DEBUG 1: Pre-processing Bufr File for metadata (BUFR variable
names)
> > > from
> > > >> nam.t00z.prepbufr.tm00.nr
> > > >>
> > > >> 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75%
80% 85%
> 90%
> > > 95%
> > > >>
> > > >>
> > > >> DEBUG 1:
> > > >>
> > > >> DEBUG 1: Header variables:
> > > >>
> > > >> DEBUG 1: SID: STATION IDENTIFICATION
> > > >>
> > > >> DEBUG 1: XOB: LONGITUDE
> > > >>
> > > >> DEBUG 1: YOB: LATITUDE
> > > >>
> > > >> DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
> > > >>
> > > >> DEBUG 1: ELV: STATION ELEVATION
> > > >>
> > > >> DEBUG 1: TYP: PREPBUFR REPORT TYPE
> > > >>
> > > >> DEBUG 1: T29: DATA DUMP REPORT TYPE
> > > >>
> > > >> DEBUG 1: ITP: INSTRUMENT TYPE
> > > >>
> > > >> DEBUG 1:
> > > >>
> > > >> DEBUG 1: Observation variables:
> > > >>
> > > >> DEBUG 1: POB: PRESSURE OBSERVATION
> > > >>
> > > >> DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
> > > >>
> > > >> DEBUG 1: TOB: TEMPERATURE OBSERVATION
> > > >>
> > > >> DEBUG 1: ZOB: HEIGHT OBSERVATION
> > > >>
> > > >> DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
> > > >>
> > > >> DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
> > > >>
> > > >> DEBUG 1: D_DWP:
> > > >>
> > > >> DEBUG 1: D_WDIR:
> > > >>
> > > >> DEBUG 1: D_WIND:
> > > >>
> > > >> DEBUG 1: D_RH:
> > > >>
> > > >> DEBUG 1: D_MIXR:
> > > >>
> > > >> DEBUG 1: D_PRMSL:
> > > >>
> > > >> DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF LOWEST
CLOUD
> > SEEN
> > > >>
> > > >> DEBUG 1: CLTP: CLOUD TYPE
> > > >>
> > > >> DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
> > > >>
> > > >> DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC HUMIDITY
VALUE
> > > >>
> > > >> DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
> > > >>
> > > >> DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM CODE
> > > >>
> > > >> DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
> > > >>
> > > >> DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
> > > >>
> > > >> DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE VALUE
> > > >>
> > > >> DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
> > > >>
> > > >> DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
> > > >>
> > > >> DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
> > > >>
> > > >> DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION (NOT
> > ASSIMILATED)
> > > >>
> > > >> DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS (NOT
> > > >> ASSIMILATED)
> > > >>
> > > >> DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
> > > >>
> > > >> DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
> > > >>
> > > >> DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
> > > >>
> > > >> DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
> > > >>
> > > >> DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
> > > >>
> > > >> DEBUG 1: POE: PRESSURE OBSERVATION ERROR
> > > >>
> > > >> DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE VALUE
> > > >>
> > > >> DEBUG 1: PRC: PRESSURE EVENT REASON CODE
> > > >>
> > > >> DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
> > > >>
> > > >> DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
> > > >>
> > > >> DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL BASED
ON
> > BALLOON
> > > >> DFT)
> > > >>
> > > >> DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL BASED
ON
> > BALLOON
> > > >> DFT)
> > > >>
> > > >> DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR RAOB/PIBAL,
BASED
> > ON B
> > > >> DFT)
> > > >>
> > > >> DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN
(OBTAINED FROM
> > > >> SCRIPT)
> > > >>
> > > >> DEBUG 1: SQN: REPORT SEQUENCE NUMBER
> > > >>
> > > >> DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN "DHR"
WAS
> > CORRECTED
> > > >>
> > > >> DEBUG 1: RPT: REPORTED OBSERVATION TIME
> > > >>
> > > >> DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED RADIATION
CORR.
> > > >> INDICATOR
> > > >>
> > > >> DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT
ASSIMILATED)
> > > >>
> > > >> DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB)
OBSERVATION
> ERROR
> > > >>
> > > >> DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT WIND
VALUE
> > > >>
> > > >> DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT WIND
VALUE
> > > >>
> > > >> DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
REASON
> CODE
> > > >>
> > > >> DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
PROGRAM
> > CODE
> > > >>
> > > >> DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB)
(QUALITY)
> MARKER
> > > >>
> > > >> DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
EVENT
> > REASON
> > > >> CODE
> > > >>
> > > >> DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
EVENT
> PGM
> > > >> CODE
> > > >>
> > > >> DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
> (QUALITY)
> > > >> MARKER
> > > >>
> > > >> DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT
ASSIMILATED)
> > > >>
> > > >> DEBUG 1: CLAM: CLOUD AMOUNT
> > > >>
> > > >> DEBUG 1: DGOT: DEGREE OF TURBULENCE
> > > >>
> > > >> DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS MEANINGS
DEPENDING
> > ON
> > > >> TYPE)
> > > >>
> > > >> DEBUG 1: RCT: RECEIPT TIME
> > > >>
> > > >> DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK (ADDED
BY PGM
> > > >> PREPACQC)
> > > >>
> > > >> DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
> > > >>
> > > >> DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
> > > >>
> > > >> DEBUG 1: AFIC: AIRFRAME ICING
> > > >>
> > > >> DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
> > > >>
> > > >> DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
> > > >>
> > > >> DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
> > > >>
> > > >> DEBUG 1: PRWE: PRESENT WEATHER
> > > >>
> > > >> DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS
EXPECTED
> > ERROR
> > > >>
> > > >> DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON EUMETSAT
QUAL INDX
> > W/O
> > > >> FCST
> > > >>
> > > >> DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON EUMETSAT
QUAL INDX
> > W/
> > > >> FCST
> > > >>
> > > >> DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS
RECURSIVE
> > > >> FILTER FCN
> > > >>
> > > >> DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
> > > >>
> > > >> DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT
ASSIMILATED)
> > > >>
> > > >> DEBUG 1: TOCC: CLOUD COVER (TOTAL)
> > > >>
> > > >> DEBUG 1: HOVI: HORIZONTAL VISIBILITY
> > > >>
> > > >> DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
> > > >>
> > > >> DEBUG 1: MITM: MINIMUM TEMPERATURE
> > > >>
> > > >> DEBUG 1: MXTM: MAXIMUM TEMPERATURE
> > > >>
> > > >> DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
> > > >>
> > > >> DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY)
MARKER
> > > >>
> > > >> DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
> > > >>
> > > >> DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
> > > >>
> > > >> DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
> > > >>
> > > >> DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
> > > >>
> > > >> DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
> > > >>
> > > >> DEBUG 1: TOSD: TOTAL SNOW DEPTH
> > > >>
> > > >> DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC OBSERVATION)
> > > >>
> > > >> DEBUG 1: PSW2: PAST WEATHER (2)
> > > >>
> > > >> DEBUG 1: PSW1: PAST WEATHER (1)
> > > >>
> > > >> DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
> > > >>
> > > >> DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
> > > >>
> > > >> DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
> > > >>
> > > >> DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER
EQUIVALENT
> > > >>
> > > >> DEBUG 1: DOFS: DEPTH OF FRESH SNOW
> > > >>
> > > >> DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
> > > >>
> > > >> DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB - HGT
OF
> CLOUD
> > > >> BASE)
> > > >>
> > > >> DEBUG 1: PKWDSP: PEAK WIND SPEED
> > > >>
> > > >> DEBUG 1: PKWDDR: PEAK WIND DIRECTION
> > > >>
> > > >> DEBUG 1: VTVI: VERTICAL VISIBILITY
> > > >>
> > > >> DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
> > > >>
> > > >> DEBUG 1: SST1: SEA TEMPERATURE
> > > >>
> > > >> DEBUG 1: HOWW: HEIGHT OF WIND WAVES
> > > >>
> > > >> DEBUG 1: POWW: PERIOD OF WIND WAVES
> > > >>
> > > >> DEBUG 1: HOWV: HEIGHT OF WAVES
> > > >>
> > > >> DEBUG 1: POWV: PERIOD OF WAVES
> > > >>
> > > >> DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
> > > >>
> > > >> DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
> > > >>
> > > >> DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
> > > >>
> > > >> DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST 3
HOURS
> > > >>
> > > >> DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
> > > >>
> > > >> DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE
MEASUREMENT
> > > >>
> > > >> DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
> > > >>
> > > >> DEBUG 1: POSW: PERIOD OF SWELL WAVES
> > > >>
> > > >> DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
> > > >>
> > > >> DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
> > > >>
> > > >> DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON CODE
> > > >>
> > > >> DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM CODE
> > > >>
> > > >> DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
> > > >>
> > > >> DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
> > > >>
> > > >> DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE OBSERVATION
> > > >>
> > > >> DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS
ONLY)
> > > >>
> > > >> DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT REPORTS
ONLY)
> > > >>
> > > >> DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION (ASCAT
> REPORTS
> > > >> ONLY)
> > > >>
> > > >> DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT &
ASCAT
> > REPORTS
> > > >> ONLY)
> > > >>
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: John Halley Gotway
Time: Tue Sep 19 08:26:33 2017
Ben,
Great, glad you were able to make progress.
Based on running though this test case last week, the developer and I
met
on Friday to discuss ways to make this easier. We came up with a list
of
changes for pb2nc to make it more intuitive. Once those are ready,
we'll
include them in met-6.1_beta2.
I grabbed the output you created and looked in particular at the MPR
output
lines. We have a short Rscript included in MET (and on the website)
which
summarizes MPR lines. Here's what I ran:
wget
http://www.dtcenter.org/met/users/downloads/Rscripts/plot_mpr.R
Rscript plot_mpr.R point_stat_240000L_20170917_000000V_mpr.txt
This script reads the MPR lines, identifies unique combinations of
header
columns, and creates histograms, scatter plots, and q-q plots to
summarize
them. I've attached the resulting PDF file containing 2 pages.
Page 1 summarizes the VIS data while page 2 summarizes the RETOP data.
Looking at the VIS scatter plot, the observations look oddly binned
just
under 20,000 and the forecasts looked oddly binned just under 25,000.
Looking at the RETOP data, there's a clear problem. The range of the
observation data is 0 to 20,000 while the range of the forecast data
is
-5000 to about 15,000.
Based on these discrepancies, any continuous stats, like RMSE, would
be
pretty useless. You really need to know what this data means to
verify it
well.
Does a RETOP forecast of -5000 really mean 0 or is it a missing data
value
that should be skipped? What does an observation of 20,000 mean?
Should
that be skipped as well? I'll assume we really only want to compute
stats
in the range of 0 to 15,000.
There are a couple of config file options that would be useful here,
one
already exists and one is "in progress":
(1) The cnt_thresh defines filtering criteria to be used when
computing
continuous stats. The logic is that we only use MPR lines which meet
this
criteria. So for RETOP could set:
cnt_thresh = [ ge0&&le15000 ];
cnt_logic = INTERSECTION;
That would tell Point-Stat to only use matched pairs where both the
forecast and observation are between 0 and 15,000.
(2) The qc_thresh applies filtering criteria globally right when the
data
is read. Whereas the cnt_thresh only applies to CNT and SL1L2 output
line
types, the qc_thresh applies to all line types. Here's how we could
say
that any data outside the range (0, 15000) should be set to bad data:
qc_thresh = [ lt0||gt15000 ];
qc_new_val = [ -9999 ];
Any points meeting the threshold criteria will be reset to a bad data
value. However, this is a new feature that I started on last week.
So
it's not available yet.
Lastly, I'm sitting in cube number 2795 this week during my visit to
NCWCP. Feel free to drop by if you'd like to talk more about this.
John
On Mon, Sep 18, 2017 at 11:02 AM, Benjamin Blake - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82010 >
>
> Hi John,
>
> I was able to reproduce what you did using met6.1_beta1 on WCOSS
(Gyre)
> with pb2nc and point stat. I modified the point stat config file to
> produce continuous and categorical statistics for HOVI/VIS and
> CEILING/RETOP.
>
> I've placed the output on this public FTP site if you'd like to take
a
> look:
> ftp://ftp.emc.ncep.noaa.gov/mmb/bblake/met6.1_beta1/
>
> Thanks again for setting this up.
> Ben
>
> On Fri, Sep 15, 2017 at 2:01 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Ben,
> >
> > Yes, that's exactly right.
> >
> > The "old" way identifies observations by assigning them a GRIB
code.
> >
> > The "new" way identifies observations using strings. Instead of a
GRIB
> > code, we assign the observation a "var_id". That integer is an
index
> into
> > the "var_name" array in the NetCDF file which lists strings for
the
> > variables present in the file.
> >
> > In the old way, an observation of temperature would have GRIB code
11.
> >
> > In the new way, an observation of temperature might have a var_id
of 3...
> > and the "var_name" array would have the string "TMP" at index 3.
> >
> > The variable name are taken from the PREPBUFR mnemonic tables.
However,
> > you can override their use by setting up the "obs_var_map". For
example,
> > perhaps you'd like to name the observations of "HOVI" as "VIS"
instead
> and
> > observations of "CEILING" to "RETOP" instead. You'd do that by
setting:
> >
> > obs_var_map = [
> > { key = "HOVI"; val = "VIS"; },
> > { key = "CEILING"; val = "RETOP"; }
> >
> > ];
> >
> > Thanks,
> > John
> >
> > On Fri, Sep 15, 2017 at 11:41 AM Benjamin Blake - NOAA Affiliate
via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82010 >
> > >
> > > Hi John,
> > >
> > > Thanks for putting this example together. I retrieved the MPR
file off
> > of
> > > the FTP server and I will attempt to reproduce what you did on
Monday
> > using
> > > met6.1_beta1.
> > >
> > > So for running PB2NC, the "old" way you referred to is mapping
the BUFR
> > > variable name to GRIB, and the "new" way is using the MET
variable
> index
> > > from the var_name variable?
> > >
> > > Thanks,
> > > Ben
> > >
> > > On Fri, Sep 15, 2017 at 1:16 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Ugh, the file attachment was too big. So I posted it on our
> anonymous
> > > ftp
> > > > site:
> > > >
> > > > ftp ftp.rap.ucar.edu
> > > > - anonymous
> > > > - your email address
> > > > cd incoming/irap/met_help/blake_data
> > > > get point_stat_240000L_20170914_000000V_mpr.txt
> > > >
> > > > John
> > > >
> > > > On Fri, Sep 15, 2017 at 11:09 AM, John Halley Gotway <
> johnhg at ucar.edu>
> > > > wrote:
> > > >
> > > > > Ben,
> > > > >
> > > > > Sorry, that MPR file I sent was empty. Here's the real one.
> > > > >
> > > > > Thanks,
> > > > > John
> > > > >
> > > > > On Fri, Sep 15, 2017 at 11:01 AM, John Halley Gotway <
> > johnhg at ucar.edu>
> > > > > wrote:
> > > > >
> > > > >> Hi Ben,
> > > > >>
> > > > >> I tried to work through an example of using pb2nc and
point_stat
> to
> > > > >> verify visibility and ceiling. While it is *possible*
using
> > > > met-6.1_beta1,
> > > > >> it isn't very intuitive. In particular, the settings in
PB2NC are
> > > > >> confusing because the developer enabled it to be run the
"old way"
> > or
> > > > the
> > > > >> "new way". To make the pb2nc config options simpler, I
think we
> > > should
> > > > >> only support the "new way". So we'll talk about that
change
> today.
> > > > >>
> > > > >> Because of this, I think it'd be a good idea to hold off
until
> > > > >> met-6.1_beta2.
> > > > >>
> > > > >> But since I'd already written it up, here's what I did
using
> > > > >> met-6.1_beta1 to do C&V verification using PREPBUFR point
> > observations
> > > > and
> > > > >> point_stat.
> > > > >>
> > > > >> # Pull a recent NDAS PREPBUFR file and a 24-hour NAM CONUS
Nest
> > > forecast
> > > > >>
> > > > >> wget
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > > > >> am.20170914/nam.t00z.prepbufr.tm00.nr
> > > > >> wget
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > > > >> am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
> > > > >> <ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/
> > > > nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
> > > > >>
> > > > >> # Run PB2NC with the -index option to see what observations
are
> > > present.
> > > > >> # This takes a *VERY* long time to run but you'd only index
the
> > > variable
> > > > >> names once for each type of data (i.e. NDAS, GDAS, or some
variety
> > of
> > > > BUFR
> > > > >> file).
> > > > >> # I've listed the output from PB2NC at the end of this
message,
> > which
> > > > >> does include HOVI and CEILING
> > > > >>
> > > > >> met-6.1_beta1/bin/pb2nc \
> > > > >> nam.t00z.prepbufr.tm00.nr \
> > > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > > >> PB2NCConfig_candv -index
> > > > >>
> > > > >> # Run PB2NC (without the -index option) requesting HOVI and
> CEILING
> > > > using
> > > > >> the -vars command line option:
> > > > >> # -vars HOVI,CEILING
> > > > >>
> > > > >> met-6.1_beta1/bin/pb2nc \
> > > > >> nam.t00z.prepbufr.tm00.nr \
> > > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > > >> PB2NCConfig_candv -vars HOVI,CEILING
> > > > >>
> > > > >> # Run Point-Stat to compare:
> > > > >> # 1: forecast VIS to obs HOVI using message type ANYSFC
(i.e.
> > ADPSFC +
> > > > >> SFCSHP)
> > > > >> # 2: forecast RETOP to obs CEILING using message type
ANYSFC (i.e.
> > > > ADPSFC
> > > > >> + SFCSHP)
> > > > >>
> > > > >> met-6.1_beta1/bin/point_stat \
> > > > >> nam.t00z.conusnest.hiresf24.tm00.grib2 \
> > > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > > >> PointStatConfig_candv -outdir out \
> > > > >> -v 3
> > > > >>
> > > > >> I wrote out the matched pair information and saw some
interesting
> > > > >> behavior:
> > > > >>
> > > > >> 1: Model VIS has a max value of 24,100 while observed HOVI
has a
> max
> > > > >> value of 81,900. And the values look very "binned". Might
want
> to
> > do
> > > > >> categorical verification instead of continuous verification
since
> > the
> > > > data
> > > > >> doesn't look very continuous.
> > > > >>
> > > > >> 2: Model RETOP has a range of values from -5000 to 9247.
Observed
> > > > >> CEILING has a range of values from 30 to 20000. Again you
might
> > want
> > > > to do
> > > > >> categorical vx instead of continuous.
> > > > >>
> > > > >> I've attached the config files for PB2NC and Point-Stat
along with
> > the
> > > > >> matched pairs output file from Point-Stat.
> > > > >>
> > > > >> Thanks,
> > > > >> John
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
------------------------------------------------------------
> > > > >> --------------------------------------
> > > > >>
> > > > >> DEBUG 1: Default Config File:
/var/autofs/mnt/dakota_d3/proj
> > > > >> ects/MET/MET_releases/met-6.1_beta1/share/met/config/
> > > > PB2NCConfig_default
> > > > >>
> > > > >> DEBUG 1: User Config File: PB2NCConfig_candv
> > > > >>
> > > > >> DEBUG 1:
> > > > >>
> > > > >> DEBUG 1: Pre-processing Bufr File for metadata (BUFR
variable
> names)
> > > > from
> > > > >> nam.t00z.prepbufr.tm00.nr
> > > > >>
> > > > >> 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75%
80% 85%
> > 90%
> > > > 95%
> > > > >>
> > > > >>
> > > > >> DEBUG 1:
> > > > >>
> > > > >> DEBUG 1: Header variables:
> > > > >>
> > > > >> DEBUG 1: SID: STATION IDENTIFICATION
> > > > >>
> > > > >> DEBUG 1: XOB: LONGITUDE
> > > > >>
> > > > >> DEBUG 1: YOB: LATITUDE
> > > > >>
> > > > >> DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
> > > > >>
> > > > >> DEBUG 1: ELV: STATION ELEVATION
> > > > >>
> > > > >> DEBUG 1: TYP: PREPBUFR REPORT TYPE
> > > > >>
> > > > >> DEBUG 1: T29: DATA DUMP REPORT TYPE
> > > > >>
> > > > >> DEBUG 1: ITP: INSTRUMENT TYPE
> > > > >>
> > > > >> DEBUG 1:
> > > > >>
> > > > >> DEBUG 1: Observation variables:
> > > > >>
> > > > >> DEBUG 1: POB: PRESSURE OBSERVATION
> > > > >>
> > > > >> DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
> > > > >>
> > > > >> DEBUG 1: TOB: TEMPERATURE OBSERVATION
> > > > >>
> > > > >> DEBUG 1: ZOB: HEIGHT OBSERVATION
> > > > >>
> > > > >> DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
> > > > >>
> > > > >> DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
> > > > >>
> > > > >> DEBUG 1: D_DWP:
> > > > >>
> > > > >> DEBUG 1: D_WDIR:
> > > > >>
> > > > >> DEBUG 1: D_WIND:
> > > > >>
> > > > >> DEBUG 1: D_RH:
> > > > >>
> > > > >> DEBUG 1: D_MIXR:
> > > > >>
> > > > >> DEBUG 1: D_PRMSL:
> > > > >>
> > > > >> DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF
LOWEST CLOUD
> > > SEEN
> > > > >>
> > > > >> DEBUG 1: CLTP: CLOUD TYPE
> > > > >>
> > > > >> DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
> > > > >>
> > > > >> DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC
HUMIDITY
> VALUE
> > > > >>
> > > > >> DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
> > > > >>
> > > > >> DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM CODE
> > > > >>
> > > > >> DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
> > > > >>
> > > > >> DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
> > > > >>
> > > > >> DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE
VALUE
> > > > >>
> > > > >> DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
> > > > >>
> > > > >> DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
> > > > >>
> > > > >> DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
> > > > >>
> > > > >> DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION (NOT
> > > ASSIMILATED)
> > > > >>
> > > > >> DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS
(NOT
> > > > >> ASSIMILATED)
> > > > >>
> > > > >> DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
> > > > >>
> > > > >> DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
> > > > >>
> > > > >> DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
> > > > >>
> > > > >> DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
> > > > >>
> > > > >> DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
> > > > >>
> > > > >> DEBUG 1: POE: PRESSURE OBSERVATION ERROR
> > > > >>
> > > > >> DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE VALUE
> > > > >>
> > > > >> DEBUG 1: PRC: PRESSURE EVENT REASON CODE
> > > > >>
> > > > >> DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
> > > > >>
> > > > >> DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
> > > > >>
> > > > >> DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL
BASED ON
> > > BALLOON
> > > > >> DFT)
> > > > >>
> > > > >> DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL
BASED ON
> > > BALLOON
> > > > >> DFT)
> > > > >>
> > > > >> DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR
RAOB/PIBAL,
> BASED
> > > ON B
> > > > >> DFT)
> > > > >>
> > > > >> DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN
(OBTAINED
> FROM
> > > > >> SCRIPT)
> > > > >>
> > > > >> DEBUG 1: SQN: REPORT SEQUENCE NUMBER
> > > > >>
> > > > >> DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN "DHR"
WAS
> > > CORRECTED
> > > > >>
> > > > >> DEBUG 1: RPT: REPORTED OBSERVATION TIME
> > > > >>
> > > > >> DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED RADIATION
CORR.
> > > > >> INDICATOR
> > > > >>
> > > > >> DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT
> ASSIMILATED)
> > > > >>
> > > > >> DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB)
OBSERVATION
> > ERROR
> > > > >>
> > > > >> DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT
WIND VALUE
> > > > >>
> > > > >> DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT
WIND VALUE
> > > > >>
> > > > >> DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
REASON
> > CODE
> > > > >>
> > > > >> DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB) EVENT
PROGRAM
> > > CODE
> > > > >>
> > > > >> DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB)
(QUALITY)
> > MARKER
> > > > >>
> > > > >> DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
EVENT
> > > REASON
> > > > >> CODE
> > > > >>
> > > > >> DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
EVENT
> > PGM
> > > > >> CODE
> > > > >>
> > > > >> DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or SOB)
> > (QUALITY)
> > > > >> MARKER
> > > > >>
> > > > >> DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT
ASSIMILATED)
> > > > >>
> > > > >> DEBUG 1: CLAM: CLOUD AMOUNT
> > > > >>
> > > > >> DEBUG 1: DGOT: DEGREE OF TURBULENCE
> > > > >>
> > > > >> DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS MEANINGS
> DEPENDING
> > > ON
> > > > >> TYPE)
> > > > >>
> > > > >> DEBUG 1: RCT: RECEIPT TIME
> > > > >>
> > > > >> DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK
(ADDED BY
> PGM
> > > > >> PREPACQC)
> > > > >>
> > > > >> DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
> > > > >>
> > > > >> DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
> > > > >>
> > > > >> DEBUG 1: AFIC: AIRFRAME ICING
> > > > >>
> > > > >> DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
> > > > >>
> > > > >> DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
> > > > >>
> > > > >> DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
> > > > >>
> > > > >> DEBUG 1: PRWE: PRESENT WEATHER
> > > > >>
> > > > >> DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS
EXPECTED
> > > ERROR
> > > > >>
> > > > >> DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON EUMETSAT
QUAL
> INDX
> > > W/O
> > > > >> FCST
> > > > >>
> > > > >> DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON EUMETSAT
QUAL
> INDX
> > > W/
> > > > >> FCST
> > > > >>
> > > > >> DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS
RECURSIVE
> > > > >> FILTER FCN
> > > > >>
> > > > >> DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
> > > > >>
> > > > >> DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT
> ASSIMILATED)
> > > > >>
> > > > >> DEBUG 1: TOCC: CLOUD COVER (TOTAL)
> > > > >>
> > > > >> DEBUG 1: HOVI: HORIZONTAL VISIBILITY
> > > > >>
> > > > >> DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
> > > > >>
> > > > >> DEBUG 1: MITM: MINIMUM TEMPERATURE
> > > > >>
> > > > >> DEBUG 1: MXTM: MAXIMUM TEMPERATURE
> > > > >>
> > > > >> DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
> > > > >>
> > > > >> DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY)
MARKER
> > > > >>
> > > > >> DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
> > > > >>
> > > > >> DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
> > > > >>
> > > > >> DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
> > > > >>
> > > > >> DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
> > > > >>
> > > > >> DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
> > > > >>
> > > > >> DEBUG 1: TOSD: TOTAL SNOW DEPTH
> > > > >>
> > > > >> DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC OBSERVATION)
> > > > >>
> > > > >> DEBUG 1: PSW2: PAST WEATHER (2)
> > > > >>
> > > > >> DEBUG 1: PSW1: PAST WEATHER (1)
> > > > >>
> > > > >> DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
> > > > >>
> > > > >> DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
> > > > >>
> > > > >> DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
> > > > >>
> > > > >> DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER
EQUIVALENT
> > > > >>
> > > > >> DEBUG 1: DOFS: DEPTH OF FRESH SNOW
> > > > >>
> > > > >> DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
> > > > >>
> > > > >> DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB -
HGT OF
> > CLOUD
> > > > >> BASE)
> > > > >>
> > > > >> DEBUG 1: PKWDSP: PEAK WIND SPEED
> > > > >>
> > > > >> DEBUG 1: PKWDDR: PEAK WIND DIRECTION
> > > > >>
> > > > >> DEBUG 1: VTVI: VERTICAL VISIBILITY
> > > > >>
> > > > >> DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
> > > > >>
> > > > >> DEBUG 1: SST1: SEA TEMPERATURE
> > > > >>
> > > > >> DEBUG 1: HOWW: HEIGHT OF WIND WAVES
> > > > >>
> > > > >> DEBUG 1: POWW: PERIOD OF WIND WAVES
> > > > >>
> > > > >> DEBUG 1: HOWV: HEIGHT OF WAVES
> > > > >>
> > > > >> DEBUG 1: POWV: PERIOD OF WAVES
> > > > >>
> > > > >> DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
> > > > >>
> > > > >> DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
> > > > >>
> > > > >> DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
> > > > >>
> > > > >> DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST 3
HOURS
> > > > >>
> > > > >> DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
> > > > >>
> > > > >> DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE
> MEASUREMENT
> > > > >>
> > > > >> DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
> > > > >>
> > > > >> DEBUG 1: POSW: PERIOD OF SWELL WAVES
> > > > >>
> > > > >> DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
> > > > >>
> > > > >> DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
> > > > >>
> > > > >> DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON CODE
> > > > >>
> > > > >> DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM CODE
> > > > >>
> > > > >> DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
> > > > >>
> > > > >> DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
> > > > >>
> > > > >> DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE
OBSERVATION
> > > > >>
> > > > >> DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS
ONLY)
> > > > >>
> > > > >> DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT
REPORTS
> ONLY)
> > > > >>
> > > > >> DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION
(ASCAT
> > REPORTS
> > > > >> ONLY)
> > > > >>
> > > > >> DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT &
ASCAT
> > > REPORTS
> > > > >> ONLY)
> > > > >>
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Verifying visibility and cloud ceiling height
From: Benjamin Blake - NOAA Affiliate
Time: Tue Sep 19 08:55:59 2017
Hi John,
Here's something that Perry told me last week about ceiling height:
Models usually report ceiling as geopotential height, and the obs are
geometric, so you have to subtract the elevation field from the model
to
compare (at least in gridtobs).
But in this case the forecast values are from -5000 to 15000, so if we
subtract the elevation field those values would become even more
negative,
which doesn't seem right to me. Maybe I'll talk to Perry and see if
he
knows what could be happening.
Thanks for providing the config file options, those will certainly be
useful.
I actually do have a question for you (unrelated to this) so I will
stop by
shortly.
Thanks,
Ben
On Tue, Sep 19, 2017 at 10:26 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Ben,
>
> Great, glad you were able to make progress.
>
> Based on running though this test case last week, the developer and
I met
> on Friday to discuss ways to make this easier. We came up with a
list of
> changes for pb2nc to make it more intuitive. Once those are ready,
we'll
> include them in met-6.1_beta2.
>
> I grabbed the output you created and looked in particular at the MPR
output
> lines. We have a short Rscript included in MET (and on the website)
which
> summarizes MPR lines. Here's what I ran:
> wget
http://www.dtcenter.org/met/users/downloads/Rscripts/plot_mpr.R
> Rscript plot_mpr.R point_stat_240000L_20170917_000000V_mpr.txt
>
> This script reads the MPR lines, identifies unique combinations of
header
> columns, and creates histograms, scatter plots, and q-q plots to
summarize
> them. I've attached the resulting PDF file containing 2 pages.
>
> Page 1 summarizes the VIS data while page 2 summarizes the RETOP
data.
>
> Looking at the VIS scatter plot, the observations look oddly binned
just
> under 20,000 and the forecasts looked oddly binned just under
25,000.
>
> Looking at the RETOP data, there's a clear problem. The range of
the
> observation data is 0 to 20,000 while the range of the forecast data
is
> -5000 to about 15,000.
>
> Based on these discrepancies, any continuous stats, like RMSE, would
be
> pretty useless. You really need to know what this data means to
verify it
> well.
>
> Does a RETOP forecast of -5000 really mean 0 or is it a missing data
value
> that should be skipped? What does an observation of 20,000 mean?
Should
> that be skipped as well? I'll assume we really only want to compute
stats
> in the range of 0 to 15,000.
>
> There are a couple of config file options that would be useful here,
one
> already exists and one is "in progress":
>
> (1) The cnt_thresh defines filtering criteria to be used when
computing
> continuous stats. The logic is that we only use MPR lines which
meet this
> criteria. So for RETOP could set:
> cnt_thresh = [ ge0&&le15000 ];
> cnt_logic = INTERSECTION;
>
> That would tell Point-Stat to only use matched pairs where both the
> forecast and observation are between 0 and 15,000.
>
> (2) The qc_thresh applies filtering criteria globally right when the
data
> is read. Whereas the cnt_thresh only applies to CNT and SL1L2
output line
> types, the qc_thresh applies to all line types. Here's how we could
say
> that any data outside the range (0, 15000) should be set to bad
data:
> qc_thresh = [ lt0||gt15000 ];
> qc_new_val = [ -9999 ];
>
> Any points meeting the threshold criteria will be reset to a bad
data
> value. However, this is a new feature that I started on last week.
So
> it's not available yet.
>
> Lastly, I'm sitting in cube number 2795 this week during my visit to
> NCWCP. Feel free to drop by if you'd like to talk more about this.
>
> John
>
> On Mon, Sep 18, 2017 at 11:02 AM, Benjamin Blake - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82010 >
> >
> > Hi John,
> >
> > I was able to reproduce what you did using met6.1_beta1 on WCOSS
(Gyre)
> > with pb2nc and point stat. I modified the point stat config file
to
> > produce continuous and categorical statistics for HOVI/VIS and
> > CEILING/RETOP.
> >
> > I've placed the output on this public FTP site if you'd like to
take a
> > look:
> > ftp://ftp.emc.ncep.noaa.gov/mmb/bblake/met6.1_beta1/
> >
> > Thanks again for setting this up.
> > Ben
> >
> > On Fri, Sep 15, 2017 at 2:01 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Ben,
> > >
> > > Yes, that's exactly right.
> > >
> > > The "old" way identifies observations by assigning them a GRIB
code.
> > >
> > > The "new" way identifies observations using strings. Instead of
a GRIB
> > > code, we assign the observation a "var_id". That integer is an
index
> > into
> > > the "var_name" array in the NetCDF file which lists strings for
the
> > > variables present in the file.
> > >
> > > In the old way, an observation of temperature would have GRIB
code 11.
> > >
> > > In the new way, an observation of temperature might have a
var_id of
> 3...
> > > and the "var_name" array would have the string "TMP" at index 3.
> > >
> > > The variable name are taken from the PREPBUFR mnemonic tables.
> However,
> > > you can override their use by setting up the "obs_var_map". For
> example,
> > > perhaps you'd like to name the observations of "HOVI" as "VIS"
instead
> > and
> > > observations of "CEILING" to "RETOP" instead. You'd do that by
> setting:
> > >
> > > obs_var_map = [
> > > { key = "HOVI"; val = "VIS"; },
> > > { key = "CEILING"; val = "RETOP"; }
> > >
> > > ];
> > >
> > > Thanks,
> > > John
> > >
> > > On Fri, Sep 15, 2017 at 11:41 AM Benjamin Blake - NOAA Affiliate
via
> RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=82010
>
> > > >
> > > > Hi John,
> > > >
> > > > Thanks for putting this example together. I retrieved the MPR
file
> off
> > > of
> > > > the FTP server and I will attempt to reproduce what you did on
Monday
> > > using
> > > > met6.1_beta1.
> > > >
> > > > So for running PB2NC, the "old" way you referred to is mapping
the
> BUFR
> > > > variable name to GRIB, and the "new" way is using the MET
variable
> > index
> > > > from the var_name variable?
> > > >
> > > > Thanks,
> > > > Ben
> > > >
> > > > On Fri, Sep 15, 2017 at 1:16 PM, John Halley Gotway via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > > Ugh, the file attachment was too big. So I posted it on our
> > anonymous
> > > > ftp
> > > > > site:
> > > > >
> > > > > ftp ftp.rap.ucar.edu
> > > > > - anonymous
> > > > > - your email address
> > > > > cd incoming/irap/met_help/blake_data
> > > > > get point_stat_240000L_20170914_000000V_mpr.txt
> > > > >
> > > > > John
> > > > >
> > > > > On Fri, Sep 15, 2017 at 11:09 AM, John Halley Gotway <
> > johnhg at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Ben,
> > > > > >
> > > > > > Sorry, that MPR file I sent was empty. Here's the real
one.
> > > > > >
> > > > > > Thanks,
> > > > > > John
> > > > > >
> > > > > > On Fri, Sep 15, 2017 at 11:01 AM, John Halley Gotway <
> > > johnhg at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > >> Hi Ben,
> > > > > >>
> > > > > >> I tried to work through an example of using pb2nc and
point_stat
> > to
> > > > > >> verify visibility and ceiling. While it is *possible*
using
> > > > > met-6.1_beta1,
> > > > > >> it isn't very intuitive. In particular, the settings in
PB2NC
> are
> > > > > >> confusing because the developer enabled it to be run the
"old
> way"
> > > or
> > > > > the
> > > > > >> "new way". To make the pb2nc config options simpler, I
think we
> > > > should
> > > > > >> only support the "new way". So we'll talk about that
change
> > today.
> > > > > >>
> > > > > >> Because of this, I think it'd be a good idea to hold off
until
> > > > > >> met-6.1_beta2.
> > > > > >>
> > > > > >> But since I'd already written it up, here's what I did
using
> > > > > >> met-6.1_beta1 to do C&V verification using PREPBUFR point
> > > observations
> > > > > and
> > > > > >> point_stat.
> > > > > >>
> > > > > >> # Pull a recent NDAS PREPBUFR file and a 24-hour NAM
CONUS Nest
> > > > forecast
> > > > > >>
> > > > > >> wget
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > > > > >> am.20170914/nam.t00z.prepbufr.tm00.nr
> > > > > >> wget
ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/n
> > > > > >> am.20170913/nam.t00z.conusnest.hiresf24.tm00.grib2
> > > > > >> <ftp://ftpprd.ncep.noaa.gov/pub/data/nccf/com/nam/prod/
> > > > > nam.20170913/nam.t06z.conusnest.hiresf24.tm00.grib2>
> > > > > >>
> > > > > >> # Run PB2NC with the -index option to see what
observations are
> > > > present.
> > > > > >> # This takes a *VERY* long time to run but you'd only
index the
> > > > variable
> > > > > >> names once for each type of data (i.e. NDAS, GDAS, or
some
> variety
> > > of
> > > > > BUFR
> > > > > >> file).
> > > > > >> # I've listed the output from PB2NC at the end of this
message,
> > > which
> > > > > >> does include HOVI and CEILING
> > > > > >>
> > > > > >> met-6.1_beta1/bin/pb2nc \
> > > > > >> nam.t00z.prepbufr.tm00.nr \
> > > > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > > > >> PB2NCConfig_candv -index
> > > > > >>
> > > > > >> # Run PB2NC (without the -index option) requesting HOVI
and
> > CEILING
> > > > > using
> > > > > >> the -vars command line option:
> > > > > >> # -vars HOVI,CEILING
> > > > > >>
> > > > > >> met-6.1_beta1/bin/pb2nc \
> > > > > >> nam.t00z.prepbufr.tm00.nr \
> > > > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > > > >> PB2NCConfig_candv -vars HOVI,CEILING
> > > > > >>
> > > > > >> # Run Point-Stat to compare:
> > > > > >> # 1: forecast VIS to obs HOVI using message type ANYSFC
(i.e.
> > > ADPSFC +
> > > > > >> SFCSHP)
> > > > > >> # 2: forecast RETOP to obs CEILING using message type
ANYSFC
> (i.e.
> > > > > ADPSFC
> > > > > >> + SFCSHP)
> > > > > >>
> > > > > >> met-6.1_beta1/bin/point_stat \
> > > > > >> nam.t00z.conusnest.hiresf24.tm00.grib2 \
> > > > > >> nam.t00z.prepbufr.tm00_pb2nc.nc \
> > > > > >> PointStatConfig_candv -outdir out \
> > > > > >> -v 3
> > > > > >>
> > > > > >> I wrote out the matched pair information and saw some
> interesting
> > > > > >> behavior:
> > > > > >>
> > > > > >> 1: Model VIS has a max value of 24,100 while observed
HOVI has a
> > max
> > > > > >> value of 81,900. And the values look very "binned".
Might want
> > to
> > > do
> > > > > >> categorical verification instead of continuous
verification
> since
> > > the
> > > > > data
> > > > > >> doesn't look very continuous.
> > > > > >>
> > > > > >> 2: Model RETOP has a range of values from -5000 to 9247.
> Observed
> > > > > >> CEILING has a range of values from 30 to 20000. Again
you might
> > > want
> > > > > to do
> > > > > >> categorical vx instead of continuous.
> > > > > >>
> > > > > >> I've attached the config files for PB2NC and Point-Stat
along
> with
> > > the
> > > > > >> matched pairs output file from Point-Stat.
> > > > > >>
> > > > > >> Thanks,
> > > > > >> John
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
> > > > > >>
------------------------------------------------------------
> > > > > >> --------------------------------------
> > > > > >>
> > > > > >> DEBUG 1: Default Config File:
/var/autofs/mnt/dakota_d3/proj
> > > > > >> ects/MET/MET_releases/met-6.1_beta1/share/met/config/
> > > > > PB2NCConfig_default
> > > > > >>
> > > > > >> DEBUG 1: User Config File: PB2NCConfig_candv
> > > > > >>
> > > > > >> DEBUG 1:
> > > > > >>
> > > > > >> DEBUG 1: Pre-processing Bufr File for metadata (BUFR
variable
> > names)
> > > > > from
> > > > > >> nam.t00z.prepbufr.tm00.nr
> > > > > >>
> > > > > >> 5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70%
75% 80%
> 85%
> > > 90%
> > > > > 95%
> > > > > >>
> > > > > >>
> > > > > >> DEBUG 1:
> > > > > >>
> > > > > >> DEBUG 1: Header variables:
> > > > > >>
> > > > > >> DEBUG 1: SID: STATION IDENTIFICATION
> > > > > >>
> > > > > >> DEBUG 1: XOB: LONGITUDE
> > > > > >>
> > > > > >> DEBUG 1: YOB: LATITUDE
> > > > > >>
> > > > > >> DEBUG 1: DHR: OBSERVATION TIME MINUS CYCLE TIME
> > > > > >>
> > > > > >> DEBUG 1: ELV: STATION ELEVATION
> > > > > >>
> > > > > >> DEBUG 1: TYP: PREPBUFR REPORT TYPE
> > > > > >>
> > > > > >> DEBUG 1: T29: DATA DUMP REPORT TYPE
> > > > > >>
> > > > > >> DEBUG 1: ITP: INSTRUMENT TYPE
> > > > > >>
> > > > > >> DEBUG 1:
> > > > > >>
> > > > > >> DEBUG 1: Observation variables:
> > > > > >>
> > > > > >> DEBUG 1: POB: PRESSURE OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: QOB: SPECIFIC HUMIDITY OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: TOB: TEMPERATURE OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: ZOB: HEIGHT OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: UOB: U-COMPONENT WIND OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: VOB: V-COMPONENT WIND OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: D_DWP:
> > > > > >>
> > > > > >> DEBUG 1: D_WDIR:
> > > > > >>
> > > > > >> DEBUG 1: D_WIND:
> > > > > >>
> > > > > >> DEBUG 1: D_RH:
> > > > > >>
> > > > > >> DEBUG 1: D_MIXR:
> > > > > >>
> > > > > >> DEBUG 1: D_PRMSL:
> > > > > >>
> > > > > >> DEBUG 1: HBLCS: HEIGHT ABOVE SURFACE OF BASE OF
LOWEST
> CLOUD
> > > > SEEN
> > > > > >>
> > > > > >> DEBUG 1: CLTP: CLOUD TYPE
> > > > > >>
> > > > > >> DEBUG 1: QOE: RELATIVE HUMIDITY OBSERVATION ERROR
> > > > > >>
> > > > > >> DEBUG 1: QFC: FORECAST (BACKGROUND) SPECIFIC
HUMIDITY
> > VALUE
> > > > > >>
> > > > > >> DEBUG 1: QRC: SPECIFIC HUMIDITY EVENT REASON CODE
> > > > > >>
> > > > > >> DEBUG 1: QPC: SPECIFIC HUMIDITY EVENT PROGRAM
CODE
> > > > > >>
> > > > > >> DEBUG 1: QQM: SPECIFIC HUMIDITY (QUALITY) MARKER
> > > > > >>
> > > > > >> DEBUG 1: TOE: TEMPERATURE OBSERVATION ERROR
> > > > > >>
> > > > > >> DEBUG 1: TFC: FORECAST (BACKGROUND) TEMPERATURE
VALUE
> > > > > >>
> > > > > >> DEBUG 1: TRC: TEMPERATURE EVENT REASON CODE
> > > > > >>
> > > > > >> DEBUG 1: TPC: TEMPERATURE EVENT PROGRAM CODE
> > > > > >>
> > > > > >> DEBUG 1: TQM: TEMPERATURE (QUALITY) MARKER
> > > > > >>
> > > > > >> DEBUG 1: TDO: DEWPOINT TEMPERATURE OBSERVATION
(NOT
> > > > ASSIMILATED)
> > > > > >>
> > > > > >> DEBUG 1: TVO: NON-Q. CONTROLLED VIRTUAL TEMP OBS
(NOT
> > > > > >> ASSIMILATED)
> > > > > >>
> > > > > >> DEBUG 1: ZFC: FORECAST (BACKGROUND) HEIGHT VALUE
> > > > > >>
> > > > > >> DEBUG 1: ZRC: HEIGHT EVENT REASON CODE
> > > > > >>
> > > > > >> DEBUG 1: ZPC: HEIGHT EVENT PROGRAM CODE
> > > > > >>
> > > > > >> DEBUG 1: ZQM: HEIGHT (QUALITY) MARKER
> > > > > >>
> > > > > >> DEBUG 1: CAT: PREPBUFR DATA LEVEL CATEGORY
> > > > > >>
> > > > > >> DEBUG 1: POE: PRESSURE OBSERVATION ERROR
> > > > > >>
> > > > > >> DEBUG 1: PFC: FORECAST (BACKGROUND) PRESSURE
VALUE
> > > > > >>
> > > > > >> DEBUG 1: PRC: PRESSURE EVENT REASON CODE
> > > > > >>
> > > > > >> DEBUG 1: PPC: PRESSURE EVENT PROGRAM CODE
> > > > > >>
> > > > > >> DEBUG 1: PQM: PRESSURE (QUALITY) MARKER
> > > > > >>
> > > > > >> DEBUG 1: XDR: PROFILE LEVEL LON (FOR RAOB/PIBAL
BASED ON
> > > > BALLOON
> > > > > >> DFT)
> > > > > >>
> > > > > >> DEBUG 1: YDR: PROFILE LEVEL LAT (FOR RAOB/PIBAL
BASED ON
> > > > BALLOON
> > > > > >> DFT)
> > > > > >>
> > > > > >> DEBUG 1: HRDR: PROFILE LVL TIME-CYCLE (FOR
RAOB/PIBAL,
> > BASED
> > > > ON B
> > > > > >> DFT)
> > > > > >>
> > > > > >> DEBUG 1: PROCN: PROCESS NUMBER FOR THIS MPI RUN
(OBTAINED
> > FROM
> > > > > >> SCRIPT)
> > > > > >>
> > > > > >> DEBUG 1: SQN: REPORT SEQUENCE NUMBER
> > > > > >>
> > > > > >> DEBUG 1: TCOR: INDICATOR WHETHER OBS. TIME IN
"DHR" WAS
> > > > CORRECTED
> > > > > >>
> > > > > >> DEBUG 1: RPT: REPORTED OBSERVATION TIME
> > > > > >>
> > > > > >> DEBUG 1: SIRC: RAWINSONDE SOLAR & INFRARED
RADIATION
> CORR.
> > > > > >> INDICATOR
> > > > > >>
> > > > > >> DEBUG 1: FFO: WIND SPEED OBSERVATION (kts) (NOT
> > ASSIMILATED)
> > > > > >>
> > > > > >> DEBUG 1: WOE: U-, V-COMPONENT WIND (UOB/VOB)
OBSERVATION
> > > ERROR
> > > > > >>
> > > > > >> DEBUG 1: VFC: FORECAST (BACKGROUND) V-COMPONENT
WIND
> VALUE
> > > > > >>
> > > > > >> DEBUG 1: UFC: FORECAST (BACKGROUND) U-COMPONENT
WIND
> VALUE
> > > > > >>
> > > > > >> DEBUG 1: WRC: U-, V-COMPONENT WIND (UOB/VOB)
EVENT
> REASON
> > > CODE
> > > > > >>
> > > > > >> DEBUG 1: WPC: U-, V-COMPONENT WIND (UOB/VOB)
EVENT
> PROGRAM
> > > > CODE
> > > > > >>
> > > > > >> DEBUG 1: WQM: U-, V-COMPONENT WIND (UOB/VOB)
(QUALITY)
> > > MARKER
> > > > > >>
> > > > > >> DEBUG 1: DFR: WIND DIRECTION(DDO)/SPEED(FFO or
SOB)
> EVENT
> > > > REASON
> > > > > >> CODE
> > > > > >>
> > > > > >> DEBUG 1: DFP: WIND DIRECTION(DDO)/SPEED(FFO or
SOB)
> EVENT
> > > PGM
> > > > > >> CODE
> > > > > >>
> > > > > >> DEBUG 1: DFQ: WIND DIRECTION(DDO)/SPEED(FFO or
SOB)
> > > (QUALITY)
> > > > > >> MARKER
> > > > > >>
> > > > > >> DEBUG 1: DDO: WIND DIRECTION OBSERVATION (NOT
> ASSIMILATED)
> > > > > >>
> > > > > >> DEBUG 1: CLAM: CLOUD AMOUNT
> > > > > >>
> > > > > >> DEBUG 1: DGOT: DEGREE OF TURBULENCE
> > > > > >>
> > > > > >> DEBUG 1: TSB: REPORT SUBTYPE (HAS VARIOUS
MEANINGS
> > DEPENDING
> > > > ON
> > > > > >> TYPE)
> > > > > >>
> > > > > >> DEBUG 1: RCT: RECEIPT TIME
> > > > > >>
> > > > > >> DEBUG 1: NRLQMS: NRL AIRCRAFT QUALITY CNTRL MARK
(ADDED BY
> > PGM
> > > > > >> PREPACQC)
> > > > > >>
> > > > > >> DEBUG 1: HTOI: HEIGHT OF TOP OF ICING
> > > > > >>
> > > > > >> DEBUG 1: HBOI: HEIGHT OF BASE OF ICING
> > > > > >>
> > > > > >> DEBUG 1: AFIC: AIRFRAME ICING
> > > > > >>
> > > > > >> DEBUG 1: HOCB: HEIGHT OF BASE OF CLOUD
> > > > > >>
> > > > > >> DEBUG 1: HTOT: HEIGHT OF TOP OF TURBULENCE
> > > > > >>
> > > > > >> DEBUG 1: HBOT: HEIGHT OF BASE OF TURBULENCE
> > > > > >>
> > > > > >> DEBUG 1: PRWE: PRESENT WEATHER
> > > > > >>
> > > > > >> DEBUG 1: EEQF: PERCENT CONFIDENCE BASED ON NESDIS
> EXPECTED
> > > > ERROR
> > > > > >>
> > > > > >> DEBUG 1: QIFN: PERCENT CONFIDENCE BASED ON
EUMETSAT QUAL
> > INDX
> > > > W/O
> > > > > >> FCST
> > > > > >>
> > > > > >> DEBUG 1: QIFY: PERCENT CONFIDENCE BASED ON
EUMETSAT QUAL
> > INDX
> > > > W/
> > > > > >> FCST
> > > > > >>
> > > > > >> DEBUG 1: RFFL: PERCENT CONFIDENCE BASED ON NESDIS
> RECURSIVE
> > > > > >> FILTER FCN
> > > > > >>
> > > > > >> DEBUG 1: SAZA: SATELLITE ZENITH ANGLE
> > > > > >>
> > > > > >> DEBUG 1: SOB: WIND SPEED OBSERVATION (m/s) (NOT
> > ASSIMILATED)
> > > > > >>
> > > > > >> DEBUG 1: TOCC: CLOUD COVER (TOTAL)
> > > > > >>
> > > > > >> DEBUG 1: HOVI: HORIZONTAL VISIBILITY
> > > > > >>
> > > > > >> DEBUG 1: TP06: TOTAL PRECIPITATION PAST 6 HOURS
> > > > > >>
> > > > > >> DEBUG 1: MITM: MINIMUM TEMPERATURE
> > > > > >>
> > > > > >> DEBUG 1: MXTM: MAXIMUM TEMPERATURE
> > > > > >>
> > > > > >> DEBUG 1: PMIN: MEAN SEA-LEVEL PRESSURE INDICATOR
> > > > > >>
> > > > > >> DEBUG 1: PMQ: MEAN SEA-LEVEL PRESSURE (QUALITY)
MARKER
> > > > > >>
> > > > > >> DEBUG 1: PMO: MEAN SEA-LEVEL PRESSURE OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: CHPT: CHARACTERISTIC OF PRESSURE TENDENCY
> > > > > >>
> > > > > >> DEBUG 1: 3HPC: 3 HOUR PRESSURE CHANGE
> > > > > >>
> > > > > >> DEBUG 1: MXGS: MAXIMUM WIND SPEED (GUSTS)
> > > > > >>
> > > > > >> DEBUG 1: TP03: TOTAL PRECIPITATION PAST 3 HOURS
> > > > > >>
> > > > > >> DEBUG 1: TOSD: TOTAL SNOW DEPTH
> > > > > >>
> > > > > >> DEBUG 1: VSSO: VERT. SIGNIFICANCE (SFC
OBSERVATION)
> > > > > >>
> > > > > >> DEBUG 1: PSW2: PAST WEATHER (2)
> > > > > >>
> > > > > >> DEBUG 1: PSW1: PAST WEATHER (1)
> > > > > >>
> > > > > >> DEBUG 1: 24PC: 24 HOUR PRESSURE CHANGE
> > > > > >>
> > > > > >> DEBUG 1: TP24: TOTAL PRECIPITATION PAST 24 HOURS
> > > > > >>
> > > > > >> DEBUG 1: TP01: TOTAL PRECIPITATION PAST 1 HOUR
> > > > > >>
> > > > > >> DEBUG 1: TOPC: TOTAL PRECIPITATION/TOTAL WATER
EQUIVALENT
> > > > > >>
> > > > > >> DEBUG 1: DOFS: DEPTH OF FRESH SNOW
> > > > > >>
> > > > > >> DEBUG 1: ALSE: ALTIMETER SETTING OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: CEILING: CLOUD CEILING (DERIVATIVE OF HOCB -
HGT OF
> > > CLOUD
> > > > > >> BASE)
> > > > > >>
> > > > > >> DEBUG 1: PKWDSP: PEAK WIND SPEED
> > > > > >>
> > > > > >> DEBUG 1: PKWDDR: PEAK WIND DIRECTION
> > > > > >>
> > > > > >> DEBUG 1: VTVI: VERTICAL VISIBILITY
> > > > > >>
> > > > > >> DEBUG 1: SSTQM: SEA TEMPERATURE (QUALITY) MARKER
> > > > > >>
> > > > > >> DEBUG 1: SST1: SEA TEMPERATURE
> > > > > >>
> > > > > >> DEBUG 1: HOWW: HEIGHT OF WIND WAVES
> > > > > >>
> > > > > >> DEBUG 1: POWW: PERIOD OF WIND WAVES
> > > > > >>
> > > > > >> DEBUG 1: HOWV: HEIGHT OF WAVES
> > > > > >>
> > > > > >> DEBUG 1: POWV: PERIOD OF WAVES
> > > > > >>
> > > > > >> DEBUG 1: TP12: TOTAL PRECIPITATION PAST 12 HOURS
> > > > > >>
> > > > > >> DEBUG 1: RSRD: RESTRICTIONS ON REDISTRIBUTION
> > > > > >>
> > > > > >> DEBUG 1: ASMP: AVG SPD OF SHIP DURING PAST 3 HOURS
> > > > > >>
> > > > > >> DEBUG 1: TDMP: TRUE DIRECTION OF SHIP DURING PAST
3 HOURS
> > > > > >>
> > > > > >> DEBUG 1: DOSW: DIRECTION OF SWELL WAVES
> > > > > >>
> > > > > >> DEBUG 1: MSST: METHOD OF SEA SURFACE TEMPERATURE
> > MEASUREMENT
> > > > > >>
> > > > > >> DEBUG 1: HOSW: HEIGHT OF SWELL WAVES
> > > > > >>
> > > > > >> DEBUG 1: POSW: PERIOD OF SWELL WAVES
> > > > > >>
> > > > > >> DEBUG 1: XS20: 20 METER EXTRAPOLATED WIND SPEED
> > > > > >>
> > > > > >> DEBUG 1: XS10: 10 METER EXTRAPOLATED WIND SPEED
> > > > > >>
> > > > > >> DEBUG 1: CTPRC: CLOUD TOP PRESSURE EVENT REASON
CODE
> > > > > >>
> > > > > >> DEBUG 1: CTPPC: CLOUD TOP PRESSURE EVENT PROGRAM
CODE
> > > > > >>
> > > > > >> DEBUG 1: CTPQM: CLOUD TOP PRESSURE (QUALITY) MARKER
> > > > > >>
> > > > > >> DEBUG 1: CDTP: CLOUD TOP PRESSURE OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: GCDTT: GOES CLOUD TOP TEMPERATURE
OBSERVATION
> > > > > >>
> > > > > >> DEBUG 1: BSCD: BACKSCATTER DISTANCE (ASCAT REPORTS
ONLY)
> > > > > >>
> > > > > >> DEBUG 1: WVCQ: WIND VECTOR CELL QUALITY (ASCAT
REPORTS
> > ONLY)
> > > > > >>
> > > > > >> DEBUG 1: LKCS: LIKELIHOOD COMPUTED FOR SOLUTION
(ASCAT
> > > REPORTS
> > > > > >> ONLY)
> > > > > >>
> > > > > >> DEBUG 1: CTCN: CROSS TRACK CELL NUMBER (QUIKSCAT &
ASCAT
> > > > REPORTS
> > > > > >> ONLY)
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list