[Met_help] [rt.rap.ucar.edu #95981] History for missing fields in stat files

John Halley Gotway via RT met_help at ucar.edu
Wed Jul 22 16:19:19 MDT 2020


----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Hi,

Currently, I'm setting up verification for the meteorological files from my
CMAQ runs.  I had intended on using the following variables in this way:



























*BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925, P850, P700, P500,
P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME = RHBOTH_VAR2_LEVELS
= Z2, P1000, P925, P850, P700, P500, P400, P300, P250BOTH_VAR3_NAME =
DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME = UGRDBOTH_VAR4_LEVELS = Z10, P1000,
P925, P850, P700, P500, P400, P300, P250, P200, P150, P100,
P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000, P925, P850, P700,
P500, P400, P300, P250, P200, P150, P100, P50BOTH_VAR6_NAME =
PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME = WINDBOTH_VAR7_LEVELS =
Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS = Z0FCST_VAR8_OPTIONS = cnt_thresh
= [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000, >3000,
>4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS = Z0-100000OBS_VAR8_OPTIONS =
cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH = >500, >1000,
>1500, >2000, >3000, >4000FCST_VAR9_NAME = HPBLFCST_VAR9_LEVELS =
Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS = desc = "TKE";*

The ones that are highlighted blue are the ones being stored.  Note that
CAPE has Z0 and Z0-100000; I had changed that from L0 when L0 didn't work.
However, in both instances CAPE wasn't not stored in the point stat files.
I also found that no fields were stored on pressure levels, which I
attribute to the fact that the data is being stored on hybrid levels rather
than standard pressure levels.  However, aside from the pressure level
issue, 2-meter dewpoint, CAPE, and sea-level pressure are also not being
stored.  I get messages like this, for example:














*DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
process_fcst_climo_files() -> no fields matching VGRD/P50 found in file:
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
MetGrib2DataFile::data_plane_array() -> No matching records found for
'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
--------------------------------------------------------------------------------DEBUG
2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
process_fcst_climo_files() -> no fields matching PRMSL/Z0 found in file:
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*

I can reason with why fields at pressure levels are not being stored as
well as CAPE, but I can't reason with why 2-meter dewpoint and sea-level
pressure is not being stored.  Moreover, since CAPE is a derived field, can
I not use the output available to derive it during the point stat step?  Or
is that just done for observations during the PB2NC step?  If I can't
derive fields during the point stat step, then I guess that would explain
why all the fields that I intended to store did not store.  I'm okay with
that, although dewpoint and CAPE would be of interest.  However, I would
need a way to supplant pressure levels with hybrid levels if possible.



-- 
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717


----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: missing fields in stat files
From: John Halley Gotway
Time: Wed Jul 22 14:15:12 2020

Ed,

I logged onto wcoss and took a look at:
 /gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00

Using wgrib2 to inventory the file I see:
(1) No record of PRMSL present.
(2) No record of CAPE present.
(3) No record of DPT present.

Of the 910 records in that file, 842 are on hybrid levels, 40 are at
the
surface, and the rest are soil moisture below ground or other misc
heights
(like tropopause, entire atmosphere, and so on). The only ones are 2
meters
are:

800:55227406:d=2020071806:TMP:2 m above ground:26 hour fcst:
801:55361052:d=2020071806:SPFH:2 m above ground:26 hour fcst:
802:55480631:d=2020071806:RH:2 m above ground:26 hour fcst:

The derivation of cape is only done in pb2nc, not for gridded data.

Not much we can do on the MET side of things here. I'd recommend that
this
data be post-processed to pressure levels rather than remaining on the
model's native vertical coordinate.

Thanks,
John Halley Gotway

On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:

>
> Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> Transaction: Ticket created by edward.strobach at noaa.gov
>        Queue: met_help
>      Subject: missing fields in stat files
>        Owner: Nobody
>   Requestors: edward.strobach at noaa.gov
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
>
>
> Hi,
>
> Currently, I'm setting up verification for the meteorological files
from my
> CMAQ runs.  I had intended on using the following variables in this
way:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925, P850, P700,
P500,
> P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
RHBOTH_VAR2_LEVELS
> = Z2, P1000, P925, P850, P700, P500, P400, P300, P250BOTH_VAR3_NAME
=
> DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME = UGRDBOTH_VAR4_LEVELS = Z10,
P1000,
> P925, P850, P700, P500, P400, P300, P250, P200, P150, P100,
> P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000, P925, P850,
P700,
> P500, P400, P300, P250, P200, P150, P100, P50BOTH_VAR6_NAME =
> PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME = WINDBOTH_VAR7_LEVELS =
> Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS = Z0FCST_VAR8_OPTIONS =
cnt_thresh
> = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000, >3000,
> >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS = Z0-100000OBS_VAR8_OPTIONS
=
> cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH = >500,
>1000,
> >1500, >2000, >3000, >4000FCST_VAR9_NAME = HPBLFCST_VAR9_LEVELS =
> Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS = desc =
"TKE";*
>
> The ones that are highlighted blue are the ones being stored.  Note
that
> CAPE has Z0 and Z0-100000; I had changed that from L0 when L0 didn't
work.
> However, in both instances CAPE wasn't not stored in the point stat
files.
> I also found that no fields were stored on pressure levels, which I
> attribute to the fact that the data is being stored on hybrid levels
rather
> than standard pressure levels.  However, aside from the pressure
level
> issue, 2-meter dewpoint, CAPE, and sea-level pressure are also not
being
> stored.  I get messages like this, for example:
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> process_fcst_climo_files() -> no fields matching VGRD/P50 found in
file:
>
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> MetGrib2DataFile::data_plane_array() -> No matching records found
for
> 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
>
>
--------------------------------------------------------------------------------DEBUG
> 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> process_fcst_climo_files() -> no fields matching PRMSL/Z0 found in
file:
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
>
> I can reason with why fields at pressure levels are not being stored
as
> well as CAPE, but I can't reason with why 2-meter dewpoint and sea-
level
> pressure is not being stored.  Moreover, since CAPE is a derived
field, can
> I not use the output available to derive it during the point stat
step?  Or
> is that just done for observations during the PB2NC step?  If I
can't
> derive fields during the point stat step, then I guess that would
explain
> why all the fields that I intended to store did not store.  I'm okay
with
> that, although dewpoint and CAPE would be of interest.  However, I
would
> need a way to supplant pressure levels with hybrid levels if
possible.
>
>
>
> --
> Edward Strobach
> EMC/NCEP/NWS/
> IMSG Contractor
> Cubicle#: 2029
> 301-683-3717
>
>

------------------------------------------------
Subject: missing fields in stat files
From: Edward Strobach - NOAA Affiliate
Time: Wed Jul 22 14:17:56 2020

That's what I thought.  THanks

On Wed, Jul 22, 2020 at 4:15 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:

> Ed,
>
> I logged onto wcoss and took a look at:
>  /gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00
>
> Using wgrib2 to inventory the file I see:
> (1) No record of PRMSL present.
> (2) No record of CAPE present.
> (3) No record of DPT present.
>
> Of the 910 records in that file, 842 are on hybrid levels, 40 are at
the
> surface, and the rest are soil moisture below ground or other misc
heights
> (like tropopause, entire atmosphere, and so on). The only ones are 2
meters
> are:
>
> 800:55227406:d=2020071806:TMP:2 m above ground:26 hour fcst:
> 801:55361052:d=2020071806:SPFH:2 m above ground:26 hour fcst:
> 802:55480631:d=2020071806:RH:2 m above ground:26 hour fcst:
>
> The derivation of cape is only done in pb2nc, not for gridded data.
>
> Not much we can do on the MET side of things here. I'd recommend
that this
> data be post-processed to pressure levels rather than remaining on
the
> model's native vertical coordinate.
>
> Thanks,
> John Halley Gotway
>
> On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> > Transaction: Ticket created by edward.strobach at noaa.gov
> >        Queue: met_help
> >      Subject: missing fields in stat files
> >        Owner: Nobody
> >   Requestors: edward.strobach at noaa.gov
> >       Status: new
> >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
> >
> >
> > Hi,
> >
> > Currently, I'm setting up verification for the meteorological
files from
> my
> > CMAQ runs.  I had intended on using the following variables in
this way:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925, P850,
P700,
> P500,
> > P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
> RHBOTH_VAR2_LEVELS
> > = Z2, P1000, P925, P850, P700, P500, P400, P300,
P250BOTH_VAR3_NAME =
> > DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME = UGRDBOTH_VAR4_LEVELS =
Z10,
> P1000,
> > P925, P850, P700, P500, P400, P300, P250, P200, P150, P100,
> > P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000, P925, P850,
P700,
> > P500, P400, P300, P250, P200, P150, P100, P50BOTH_VAR6_NAME =
> > PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME = WINDBOTH_VAR7_LEVELS =
> > Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS = Z0FCST_VAR8_OPTIONS =
> cnt_thresh
> > = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000, >3000,
> > >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS = Z0-
100000OBS_VAR8_OPTIONS =
> > cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH = >500,
>1000,
> > >1500, >2000, >3000, >4000FCST_VAR9_NAME = HPBLFCST_VAR9_LEVELS =
> > Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS = desc =
> "TKE";*
> >
> > The ones that are highlighted blue are the ones being stored.
Note that
> > CAPE has Z0 and Z0-100000; I had changed that from L0 when L0
didn't
> work.
> > However, in both instances CAPE wasn't not stored in the point
stat
> files.
> > I also found that no fields were stored on pressure levels, which
I
> > attribute to the fact that the data is being stored on hybrid
levels
> rather
> > than standard pressure levels.  However, aside from the pressure
level
> > issue, 2-meter dewpoint, CAPE, and sea-level pressure are also not
being
> > stored.  I get messages like this, for example:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> > process_fcst_climo_files() -> no fields matching VGRD/P50 found in
file:
> >
> >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> > MetGrib2DataFile::data_plane_array() -> No matching records found
for
> > 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
> >
> >
>
--------------------------------------------------------------------------------DEBUG
> > 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> > process_fcst_climo_files() -> no fields matching PRMSL/Z0 found in
file:
> >
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
> >
> > I can reason with why fields at pressure levels are not being
stored as
> > well as CAPE, but I can't reason with why 2-meter dewpoint and
sea-level
> > pressure is not being stored.  Moreover, since CAPE is a derived
field,
> can
> > I not use the output available to derive it during the point stat
step?
> Or
> > is that just done for observations during the PB2NC step?  If I
can't
> > derive fields during the point stat step, then I guess that would
explain
> > why all the fields that I intended to store did not store.  I'm
okay with
> > that, although dewpoint and CAPE would be of interest.  However, I
would
> > need a way to supplant pressure levels with hybrid levels if
possible.
> >
> >
> >
> > --
> > Edward Strobach
> > EMC/NCEP/NWS/
> > IMSG Contractor
> > Cubicle#: 2029
> > 301-683-3717
> >
> >
>
>

--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: missing fields in stat files
From: John Halley Gotway
Time: Wed Jul 22 15:18:12 2020

Ed,

Before resolving this ticket, I want to clarify one minor point. You
can
configure Point-Stat to have some control over which point obs levels
are
used. Below I've listed 3 examples:

(1) Require an exact match... only use observations exactly at 500mb:
fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
obs = fcst;

(2) Match any point obs close to 500 mb to the forecast at that level:
fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
obs = { field = [ { name = "TMP"; level = "P475-525"; } ]; }

(3) Suppose you have TMP at P400, P500, and P600, use point obs
between 450
and 500 and vertically interpolate the forecast values to the pressure
level of the observation.
fcst = { field = [ { name = "TMP"; level = "P400-600"; } ]; }
obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }

Since you have hybrid levels, none of these really apply. But let's
say
that it was meaningful to match hybrid level 10 to observations
between
P450 and 550 (which I'm sure it's not!). You could do so like this:
fcst = { field = [ { name = "TMP"; level = "L10"; } ]; }
obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }

Just wanted to clarify.

Thanks,
John

On Wed, Jul 22, 2020 at 2:18 PM Edward Strobach - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
>
> That's what I thought.  THanks
>
> On Wed, Jul 22, 2020 at 4:15 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Ed,
> >
> > I logged onto wcoss and took a look at:
> >  /gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00
> >
> > Using wgrib2 to inventory the file I see:
> > (1) No record of PRMSL present.
> > (2) No record of CAPE present.
> > (3) No record of DPT present.
> >
> > Of the 910 records in that file, 842 are on hybrid levels, 40 are
at the
> > surface, and the rest are soil moisture below ground or other misc
> heights
> > (like tropopause, entire atmosphere, and so on). The only ones are
2
> meters
> > are:
> >
> > 800:55227406:d=2020071806:TMP:2 m above ground:26 hour fcst:
> > 801:55361052:d=2020071806:SPFH:2 m above ground:26 hour fcst:
> > 802:55480631:d=2020071806:RH:2 m above ground:26 hour fcst:
> >
> > The derivation of cape is only done in pb2nc, not for gridded
data.
> >
> > Not much we can do on the MET side of things here. I'd recommend
that
> this
> > data be post-processed to pressure levels rather than remaining on
the
> > model's native vertical coordinate.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA Affiliate
via RT
> <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> > > Transaction: Ticket created by edward.strobach at noaa.gov
> > >        Queue: met_help
> > >      Subject: missing fields in stat files
> > >        Owner: Nobody
> > >   Requestors: edward.strobach at noaa.gov
> > >       Status: new
> > >  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981
> >
> > >
> > >
> > > Hi,
> > >
> > > Currently, I'm setting up verification for the meteorological
files
> from
> > my
> > > CMAQ runs.  I had intended on using the following variables in
this
> way:
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925, P850,
P700,
> > P500,
> > > P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
> > RHBOTH_VAR2_LEVELS
> > > = Z2, P1000, P925, P850, P700, P500, P400, P300,
P250BOTH_VAR3_NAME =
> > > DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME = UGRDBOTH_VAR4_LEVELS =
Z10,
> > P1000,
> > > P925, P850, P700, P500, P400, P300, P250, P200, P150, P100,
> > > P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000, P925,
P850,
> P700,
> > > P500, P400, P300, P250, P200, P150, P100, P50BOTH_VAR6_NAME =
> > > PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME = WINDBOTH_VAR7_LEVELS
=
> > > Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS = Z0FCST_VAR8_OPTIONS =
> > cnt_thresh
> > > = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000, >3000,
> > > >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS = Z0-
100000OBS_VAR8_OPTIONS =
> > > cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH = >500,
>1000,
> > > >1500, >2000, >3000, >4000FCST_VAR9_NAME = HPBLFCST_VAR9_LEVELS
=
> > > Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS = desc
=
> > "TKE";*
> > >
> > > The ones that are highlighted blue are the ones being stored.
Note
> that
> > > CAPE has Z0 and Z0-100000; I had changed that from L0 when L0
didn't
> > work.
> > > However, in both instances CAPE wasn't not stored in the point
stat
> > files.
> > > I also found that no fields were stored on pressure levels,
which I
> > > attribute to the fact that the data is being stored on hybrid
levels
> > rather
> > > than standard pressure levels.  However, aside from the pressure
level
> > > issue, 2-meter dewpoint, CAPE, and sea-level pressure are also
not
> being
> > > stored.  I get messages like this, for example:
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> > > process_fcst_climo_files() -> no fields matching VGRD/P50 found
in
> file:
> > >
> > >
> >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> > > MetGrib2DataFile::data_plane_array() -> No matching records
found for
> > > 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
> > >
> > >
> >
>
--------------------------------------------------------------------------------DEBUG
> > > 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> > > process_fcst_climo_files() -> no fields matching PRMSL/Z0 found
in
> file:
> > >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
> > >
> > > I can reason with why fields at pressure levels are not being
stored as
> > > well as CAPE, but I can't reason with why 2-meter dewpoint and
> sea-level
> > > pressure is not being stored.  Moreover, since CAPE is a derived
field,
> > can
> > > I not use the output available to derive it during the point
stat step?
> > Or
> > > is that just done for observations during the PB2NC step?  If I
can't
> > > derive fields during the point stat step, then I guess that
would
> explain
> > > why all the fields that I intended to store did not store.  I'm
okay
> with
> > > that, although dewpoint and CAPE would be of interest.  However,
I
> would
> > > need a way to supplant pressure levels with hybrid levels if
possible.
> > >
> > >
> > >
> > > --
> > > Edward Strobach
> > > EMC/NCEP/NWS/
> > > IMSG Contractor
> > > Cubicle#: 2029
> > > 301-683-3717
> > >
> > >
> >
> >
>
> --
> Edward Strobach
> EMC/NCEP/NWS/
> IMSG Contractor
> Cubicle#: 2029
> 301-683-3717
>
>

------------------------------------------------
Subject: missing fields in stat files
From: Edward Strobach - NOAA Affiliate
Time: Wed Jul 22 15:25:15 2020

I think I know what you're saying here.  I can give that a test I
suppose.
I'll first have to identify what L10 (or LXX) is, and see what the
average
pressure of that level is, and construct a range of pressure that
would
encompass that level.  Is that what you mean?  This looks like
something I
would have to modify in my PointStatConfig_cam file.  I would then
define
something like this L1, L2, L3, ..., L30,..
instead of P1000, P950,..., P150, etc..
inside my Point_Stat_cam.conf


On Wed, Jul 22, 2020 at 5:18 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:

> Ed,
>
> Before resolving this ticket, I want to clarify one minor point. You
can
> configure Point-Stat to have some control over which point obs
levels are
> used. Below I've listed 3 examples:
>
> (1) Require an exact match... only use observations exactly at
500mb:
> fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> obs = fcst;
>
> (2) Match any point obs close to 500 mb to the forecast at that
level:
> fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> obs = { field = [ { name = "TMP"; level = "P475-525"; } ]; }
>
> (3) Suppose you have TMP at P400, P500, and P600, use point obs
between 450
> and 500 and vertically interpolate the forecast values to the
pressure
> level of the observation.
> fcst = { field = [ { name = "TMP"; level = "P400-600"; } ]; }
> obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
>
> Since you have hybrid levels, none of these really apply. But let's
say
> that it was meaningful to match hybrid level 10 to observations
between
> P450 and 550 (which I'm sure it's not!). You could do so like this:
> fcst = { field = [ { name = "TMP"; level = "L10"; } ]; }
> obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
>
> Just wanted to clarify.
>
> Thanks,
> John
>
> On Wed, Jul 22, 2020 at 2:18 PM Edward Strobach - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
> >
> > That's what I thought.  THanks
> >
> > On Wed, Jul 22, 2020 at 4:15 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Ed,
> > >
> > > I logged onto wcoss and took a look at:
> > >  /gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00
> > >
> > > Using wgrib2 to inventory the file I see:
> > > (1) No record of PRMSL present.
> > > (2) No record of CAPE present.
> > > (3) No record of DPT present.
> > >
> > > Of the 910 records in that file, 842 are on hybrid levels, 40
are at
> the
> > > surface, and the rest are soil moisture below ground or other
misc
> > heights
> > > (like tropopause, entire atmosphere, and so on). The only ones
are 2
> > meters
> > > are:
> > >
> > > 800:55227406:d=2020071806:TMP:2 m above ground:26 hour fcst:
> > > 801:55361052:d=2020071806:SPFH:2 m above ground:26 hour fcst:
> > > 802:55480631:d=2020071806:RH:2 m above ground:26 hour fcst:
> > >
> > > The derivation of cape is only done in pb2nc, not for gridded
data.
> > >
> > > Not much we can do on the MET side of things here. I'd recommend
that
> > this
> > > data be post-processed to pressure levels rather than remaining
on the
> > > model's native vertical coordinate.
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA
Affiliate via
> RT
> > <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > >        Queue: met_help
> > > >      Subject: missing fields in stat files
> > > >        Owner: Nobody
> > > >   Requestors: edward.strobach at noaa.gov
> > > >       Status: new
> > > >  Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > Currently, I'm setting up verification for the meteorological
files
> > from
> > > my
> > > > CMAQ runs.  I had intended on using the following variables in
this
> > way:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925, P850,
P700,
> > > P500,
> > > > P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
> > > RHBOTH_VAR2_LEVELS
> > > > = Z2, P1000, P925, P850, P700, P500, P400, P300,
P250BOTH_VAR3_NAME =
> > > > DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME = UGRDBOTH_VAR4_LEVELS
= Z10,
> > > P1000,
> > > > P925, P850, P700, P500, P400, P300, P250, P200, P150, P100,
> > > > P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000, P925,
P850,
> > P700,
> > > > P500, P400, P300, P250, P200, P150, P100, P50BOTH_VAR6_NAME =
> > > > PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME =
WINDBOTH_VAR7_LEVELS =
> > > > Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS = Z0FCST_VAR8_OPTIONS
=
> > > cnt_thresh
> > > > = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000, >3000,
> > > > >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS = Z0-
100000OBS_VAR8_OPTIONS
> =
> > > > cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH = >500,
>1000,
> > > > >1500, >2000, >3000, >4000FCST_VAR9_NAME =
HPBLFCST_VAR9_LEVELS =
> > > > Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS =
desc =
> > > "TKE";*
> > > >
> > > > The ones that are highlighted blue are the ones being stored.
Note
> > that
> > > > CAPE has Z0 and Z0-100000; I had changed that from L0 when L0
didn't
> > > work.
> > > > However, in both instances CAPE wasn't not stored in the point
stat
> > > files.
> > > > I also found that no fields were stored on pressure levels,
which I
> > > > attribute to the fact that the data is being stored on hybrid
levels
> > > rather
> > > > than standard pressure levels.  However, aside from the
pressure
> level
> > > > issue, 2-meter dewpoint, CAPE, and sea-level pressure are also
not
> > being
> > > > stored.  I get messages like this, for example:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> > > > process_fcst_climo_files() -> no fields matching VGRD/P50
found in
> > file:
> > > >
> > > >
> > >
> >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> > > > MetGrib2DataFile::data_plane_array() -> No matching records
found for
> > > > 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
> > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------DEBUG
> > > > 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> > > > process_fcst_climo_files() -> no fields matching PRMSL/Z0
found in
> > file:
> > > >
> >
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
> > > >
> > > > I can reason with why fields at pressure levels are not being
stored
> as
> > > > well as CAPE, but I can't reason with why 2-meter dewpoint and
> > sea-level
> > > > pressure is not being stored.  Moreover, since CAPE is a
derived
> field,
> > > can
> > > > I not use the output available to derive it during the point
stat
> step?
> > > Or
> > > > is that just done for observations during the PB2NC step?  If
I can't
> > > > derive fields during the point stat step, then I guess that
would
> > explain
> > > > why all the fields that I intended to store did not store.
I'm okay
> > with
> > > > that, although dewpoint and CAPE would be of interest.
However, I
> > would
> > > > need a way to supplant pressure levels with hybrid levels if
> possible.
> > > >
> > > >
> > > >
> > > > --
> > > > Edward Strobach
> > > > EMC/NCEP/NWS/
> > > > IMSG Contractor
> > > > Cubicle#: 2029
> > > > 301-683-3717
> > > >
> > > >
> > >
> > >
> >
> > --
> > Edward Strobach
> > EMC/NCEP/NWS/
> > IMSG Contractor
> > Cubicle#: 2029
> > 301-683-3717
> >
> >
>
>

--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: missing fields in stat files
From: John Halley Gotway
Time: Wed Jul 22 15:47:57 2020

Yes, but I wouldn't actually recommend running that way since there's
no
consistent mapping from hybrid levels to pressure levels. I just
wanted to
tell you about those options when running point_stat.

John

On Wed, Jul 22, 2020 at 3:25 PM Edward Strobach - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
>
> I think I know what you're saying here.  I can give that a test I
suppose.
> I'll first have to identify what L10 (or LXX) is, and see what the
average
> pressure of that level is, and construct a range of pressure that
would
> encompass that level.  Is that what you mean?  This looks like
something I
> would have to modify in my PointStatConfig_cam file.  I would then
define
> something like this L1, L2, L3, ..., L30,..
> instead of P1000, P950,..., P150, etc..
> inside my Point_Stat_cam.conf
>
>
> On Wed, Jul 22, 2020 at 5:18 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Ed,
> >
> > Before resolving this ticket, I want to clarify one minor point.
You can
> > configure Point-Stat to have some control over which point obs
levels are
> > used. Below I've listed 3 examples:
> >
> > (1) Require an exact match... only use observations exactly at
500mb:
> > fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> > obs = fcst;
> >
> > (2) Match any point obs close to 500 mb to the forecast at that
level:
> > fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> > obs = { field = [ { name = "TMP"; level = "P475-525"; } ]; }
> >
> > (3) Suppose you have TMP at P400, P500, and P600, use point obs
between
> 450
> > and 500 and vertically interpolate the forecast values to the
pressure
> > level of the observation.
> > fcst = { field = [ { name = "TMP"; level = "P400-600"; } ]; }
> > obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
> >
> > Since you have hybrid levels, none of these really apply. But
let's say
> > that it was meaningful to match hybrid level 10 to observations
between
> > P450 and 550 (which I'm sure it's not!). You could do so like
this:
> > fcst = { field = [ { name = "TMP"; level = "L10"; } ]; }
> > obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
> >
> > Just wanted to clarify.
> >
> > Thanks,
> > John
> >
> > On Wed, Jul 22, 2020 at 2:18 PM Edward Strobach - NOAA Affiliate
via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
> > >
> > > That's what I thought.  THanks
> > >
> > > On Wed, Jul 22, 2020 at 4:15 PM John Halley Gotway via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Ed,
> > > >
> > > > I logged onto wcoss and took a look at:
> > > >
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00
> > > >
> > > > Using wgrib2 to inventory the file I see:
> > > > (1) No record of PRMSL present.
> > > > (2) No record of CAPE present.
> > > > (3) No record of DPT present.
> > > >
> > > > Of the 910 records in that file, 842 are on hybrid levels, 40
are at
> > the
> > > > surface, and the rest are soil moisture below ground or other
misc
> > > heights
> > > > (like tropopause, entire atmosphere, and so on). The only ones
are 2
> > > meters
> > > > are:
> > > >
> > > > 800:55227406:d=2020071806:TMP:2 m above ground:26 hour fcst:
> > > > 801:55361052:d=2020071806:SPFH:2 m above ground:26 hour fcst:
> > > > 802:55480631:d=2020071806:RH:2 m above ground:26 hour fcst:
> > > >
> > > > The derivation of cape is only done in pb2nc, not for gridded
data.
> > > >
> > > > Not much we can do on the MET side of things here. I'd
recommend that
> > > this
> > > > data be post-processed to pressure levels rather than
remaining on
> the
> > > > model's native vertical coordinate.
> > > >
> > > > Thanks,
> > > > John Halley Gotway
> > > >
> > > > On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA
Affiliate via
> > RT
> > > <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > >        Queue: met_help
> > > > >      Subject: missing fields in stat files
> > > > >        Owner: Nobody
> > > > >   Requestors: edward.strobach at noaa.gov
> > > > >       Status: new
> > > > >  Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981
> > > >
> > > > >
> > > > >
> > > > > Hi,
> > > > >
> > > > > Currently, I'm setting up verification for the
meteorological files
> > > from
> > > > my
> > > > > CMAQ runs.  I had intended on using the following variables
in this
> > > way:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925,
P850,
> P700,
> > > > P500,
> > > > > P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
> > > > RHBOTH_VAR2_LEVELS
> > > > > = Z2, P1000, P925, P850, P700, P500, P400, P300,
> P250BOTH_VAR3_NAME =
> > > > > DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME =
UGRDBOTH_VAR4_LEVELS =
> Z10,
> > > > P1000,
> > > > > P925, P850, P700, P500, P400, P300, P250, P200, P150, P100,
> > > > > P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000, P925,
P850,
> > > P700,
> > > > > P500, P400, P300, P250, P200, P150, P100, P50BOTH_VAR6_NAME
=
> > > > > PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME =
WINDBOTH_VAR7_LEVELS =
> > > > > Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS =
Z0FCST_VAR8_OPTIONS =
> > > > cnt_thresh
> > > > > = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000,
>3000,
> > > > > >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS =
> Z0-100000OBS_VAR8_OPTIONS
> > =
> > > > > cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH =
>500,
> >1000,
> > > > > >1500, >2000, >3000, >4000FCST_VAR9_NAME =
HPBLFCST_VAR9_LEVELS =
> > > > > Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS =
desc =
> > > > "TKE";*
> > > > >
> > > > > The ones that are highlighted blue are the ones being
stored.  Note
> > > that
> > > > > CAPE has Z0 and Z0-100000; I had changed that from L0 when
L0
> didn't
> > > > work.
> > > > > However, in both instances CAPE wasn't not stored in the
point stat
> > > > files.
> > > > > I also found that no fields were stored on pressure levels,
which I
> > > > > attribute to the fact that the data is being stored on
hybrid
> levels
> > > > rather
> > > > > than standard pressure levels.  However, aside from the
pressure
> > level
> > > > > issue, 2-meter dewpoint, CAPE, and sea-level pressure are
also not
> > > being
> > > > > stored.  I get messages like this, for example:
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> > > > > process_fcst_climo_files() -> no fields matching VGRD/P50
found in
> > > file:
> > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> > > > > MetGrib2DataFile::data_plane_array() -> No matching records
found
> for
> > > > > 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
> > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------DEBUG
> > > > > 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> > > > > process_fcst_climo_files() -> no fields matching PRMSL/Z0
found in
> > > file:
> > > > >
> > >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
> > > > >
> > > > > I can reason with why fields at pressure levels are not
being
> stored
> > as
> > > > > well as CAPE, but I can't reason with why 2-meter dewpoint
and
> > > sea-level
> > > > > pressure is not being stored.  Moreover, since CAPE is a
derived
> > field,
> > > > can
> > > > > I not use the output available to derive it during the point
stat
> > step?
> > > > Or
> > > > > is that just done for observations during the PB2NC step?
If I
> can't
> > > > > derive fields during the point stat step, then I guess that
would
> > > explain
> > > > > why all the fields that I intended to store did not store.
I'm
> okay
> > > with
> > > > > that, although dewpoint and CAPE would be of interest.
However, I
> > > would
> > > > > need a way to supplant pressure levels with hybrid levels if
> > possible.
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Edward Strobach
> > > > > EMC/NCEP/NWS/
> > > > > IMSG Contractor
> > > > > Cubicle#: 2029
> > > > > 301-683-3717
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > --
> > > Edward Strobach
> > > EMC/NCEP/NWS/
> > > IMSG Contractor
> > > Cubicle#: 2029
> > > 301-683-3717
> > >
> > >
> >
> >
>
> --
> Edward Strobach
> EMC/NCEP/NWS/
> IMSG Contractor
> Cubicle#: 2029
> 301-683-3717
>
>

------------------------------------------------
Subject: missing fields in stat files
From: Edward Strobach - NOAA Affiliate
Time: Wed Jul 22 15:53:31 2020

I understand.  What about using your approach along with interpolating
to
the exact level. I know met can interpolate.  Still will be
problematic for
fields with large second derivatives though, even if interpolation to
standard levels was possible

On Wed, Jul 22, 2020 at 5:48 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:

> Yes, but I wouldn't actually recommend running that way since
there's no
> consistent mapping from hybrid levels to pressure levels. I just
wanted to
> tell you about those options when running point_stat.
>
> John
>
> On Wed, Jul 22, 2020 at 3:25 PM Edward Strobach - NOAA Affiliate via
RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
> >
> > I think I know what you're saying here.  I can give that a test I
> suppose.
> > I'll first have to identify what L10 (or LXX) is, and see what the
> average
> > pressure of that level is, and construct a range of pressure that
would
> > encompass that level.  Is that what you mean?  This looks like
something
> I
> > would have to modify in my PointStatConfig_cam file.  I would then
define
> > something like this L1, L2, L3, ..., L30,..
> > instead of P1000, P950,..., P150, etc..
> > inside my Point_Stat_cam.conf
> >
> >
> > On Wed, Jul 22, 2020 at 5:18 PM John Halley Gotway via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Ed,
> > >
> > > Before resolving this ticket, I want to clarify one minor point.
You
> can
> > > configure Point-Stat to have some control over which point obs
levels
> are
> > > used. Below I've listed 3 examples:
> > >
> > > (1) Require an exact match... only use observations exactly at
500mb:
> > > fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> > > obs = fcst;
> > >
> > > (2) Match any point obs close to 500 mb to the forecast at that
level:
> > > fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> > > obs = { field = [ { name = "TMP"; level = "P475-525"; } ]; }
> > >
> > > (3) Suppose you have TMP at P400, P500, and P600, use point obs
between
> > 450
> > > and 500 and vertically interpolate the forecast values to the
pressure
> > > level of the observation.
> > > fcst = { field = [ { name = "TMP"; level = "P400-600"; } ]; }
> > > obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
> > >
> > > Since you have hybrid levels, none of these really apply. But
let's say
> > > that it was meaningful to match hybrid level 10 to observations
between
> > > P450 and 550 (which I'm sure it's not!). You could do so like
this:
> > > fcst = { field = [ { name = "TMP"; level = "L10"; } ]; }
> > > obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
> > >
> > > Just wanted to clarify.
> > >
> > > Thanks,
> > > John
> > >
> > > On Wed, Jul 22, 2020 at 2:18 PM Edward Strobach - NOAA Affiliate
via
> RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981
>
> > > >
> > > > That's what I thought.  THanks
> > > >
> > > > On Wed, Jul 22, 2020 at 4:15 PM John Halley Gotway via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Ed,
> > > > >
> > > > > I logged onto wcoss and took a look at:
> > > > >
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00
> > > > >
> > > > > Using wgrib2 to inventory the file I see:
> > > > > (1) No record of PRMSL present.
> > > > > (2) No record of CAPE present.
> > > > > (3) No record of DPT present.
> > > > >
> > > > > Of the 910 records in that file, 842 are on hybrid levels,
40 are
> at
> > > the
> > > > > surface, and the rest are soil moisture below ground or
other misc
> > > > heights
> > > > > (like tropopause, entire atmosphere, and so on). The only
ones are
> 2
> > > > meters
> > > > > are:
> > > > >
> > > > > 800:55227406:d=2020071806:TMP:2 m above ground:26 hour fcst:
> > > > > 801:55361052:d=2020071806:SPFH:2 m above ground:26 hour
fcst:
> > > > > 802:55480631:d=2020071806:RH:2 m above ground:26 hour fcst:
> > > > >
> > > > > The derivation of cape is only done in pb2nc, not for
gridded data.
> > > > >
> > > > > Not much we can do on the MET side of things here. I'd
recommend
> that
> > > > this
> > > > > data be post-processed to pressure levels rather than
remaining on
> > the
> > > > > model's native vertical coordinate.
> > > > >
> > > > > Thanks,
> > > > > John Halley Gotway
> > > > >
> > > > > On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA
Affiliate
> via
> > > RT
> > > > <
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> > > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > > >        Queue: met_help
> > > > > >      Subject: missing fields in stat files
> > > > > >        Owner: Nobody
> > > > > >   Requestors: edward.strobach at noaa.gov
> > > > > >       Status: new
> > > > > >  Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981
> > > > >
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Currently, I'm setting up verification for the
meteorological
> files
> > > > from
> > > > > my
> > > > > > CMAQ runs.  I had intended on using the following
variables in
> this
> > > > way:
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925,
P850,
> > P700,
> > > > > P500,
> > > > > > P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
> > > > > RHBOTH_VAR2_LEVELS
> > > > > > = Z2, P1000, P925, P850, P700, P500, P400, P300,
> > P250BOTH_VAR3_NAME =
> > > > > > DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME =
UGRDBOTH_VAR4_LEVELS =
> > Z10,
> > > > > P1000,
> > > > > > P925, P850, P700, P500, P400, P300, P250, P200, P150,
P100,
> > > > > > P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000,
P925,
> P850,
> > > > P700,
> > > > > > P500, P400, P300, P250, P200, P150, P100,
P50BOTH_VAR6_NAME =
> > > > > > PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME =
WINDBOTH_VAR7_LEVELS =
> > > > > > Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS =
Z0FCST_VAR8_OPTIONS =
> > > > > cnt_thresh
> > > > > > = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000,
>3000,
> > > > > > >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS =
> > Z0-100000OBS_VAR8_OPTIONS
> > > =
> > > > > > cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH =
>500,
> > >1000,
> > > > > > >1500, >2000, >3000, >4000FCST_VAR9_NAME =
HPBLFCST_VAR9_LEVELS =
> > > > > > Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS = L0OBS_VAR9_OPTIONS
= desc
> =
> > > > > "TKE";*
> > > > > >
> > > > > > The ones that are highlighted blue are the ones being
stored.
> Note
> > > > that
> > > > > > CAPE has Z0 and Z0-100000; I had changed that from L0 when
L0
> > didn't
> > > > > work.
> > > > > > However, in both instances CAPE wasn't not stored in the
point
> stat
> > > > > files.
> > > > > > I also found that no fields were stored on pressure
levels,
> which I
> > > > > > attribute to the fact that the data is being stored on
hybrid
> > levels
> > > > > rather
> > > > > > than standard pressure levels.  However, aside from the
pressure
> > > level
> > > > > > issue, 2-meter dewpoint, CAPE, and sea-level pressure are
also
> not
> > > > being
> > > > > > stored.  I get messages like this, for example:
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> > > > > > process_fcst_climo_files() -> no fields matching VGRD/P50
found
> in
> > > > file:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> > > > > > MetGrib2DataFile::data_plane_array() -> No matching
records found
> > for
> > > > > > 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------DEBUG
> > > > > > 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> > > > > > process_fcst_climo_files() -> no fields matching PRMSL/Z0
found
> in
> > > > file:
> > > > > >
> > > >
> >
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
> > > > > >
> > > > > > I can reason with why fields at pressure levels are not
being
> > stored
> > > as
> > > > > > well as CAPE, but I can't reason with why 2-meter dewpoint
and
> > > > sea-level
> > > > > > pressure is not being stored.  Moreover, since CAPE is a
derived
> > > field,
> > > > > can
> > > > > > I not use the output available to derive it during the
point stat
> > > step?
> > > > > Or
> > > > > > is that just done for observations during the PB2NC step?
If I
> > can't
> > > > > > derive fields during the point stat step, then I guess
that would
> > > > explain
> > > > > > why all the fields that I intended to store did not store.
I'm
> > okay
> > > > with
> > > > > > that, although dewpoint and CAPE would be of interest.
However,
> I
> > > > would
> > > > > > need a way to supplant pressure levels with hybrid levels
if
> > > possible.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Edward Strobach
> > > > > > EMC/NCEP/NWS/
> > > > > > IMSG Contractor
> > > > > > Cubicle#: 2029
> > > > > > 301-683-3717
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > Edward Strobach
> > > > EMC/NCEP/NWS/
> > > > IMSG Contractor
> > > > Cubicle#: 2029
> > > > 301-683-3717
> > > >
> > > >
> > >
> > >
> >
> > --
> > Edward Strobach
> > EMC/NCEP/NWS/
> > IMSG Contractor
> > Cubicle#: 2029
> > 301-683-3717
> >
> >
>
>

--
Edward Strobach
EMC/NCEP/NWS/
IMSG Contractor
Cubicle#: 2029
301-683-3717

------------------------------------------------
Subject: missing fields in stat files
From: John Halley Gotway
Time: Wed Jul 22 16:09:22 2020

MET doesn't include any logic to handle a model's native vertical
coordinate. So we have no way of knowing how to interpolate
observation
pressure levels to model hybrid coordinates or vice-versa. This is the
main
reason why running UPP to post-process model output to pressure levels
is
required prior to verifying against point observations.

I'll go ahead and resolve this ticket.

Thanks,
John



On Wed, Jul 22, 2020 at 3:54 PM Edward Strobach - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
>
> I understand.  What about using your approach along with
interpolating to
> the exact level. I know met can interpolate.  Still will be
problematic for
> fields with large second derivatives though, even if interpolation
to
> standard levels was possible
>
> On Wed, Jul 22, 2020 at 5:48 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Yes, but I wouldn't actually recommend running that way since
there's no
> > consistent mapping from hybrid levels to pressure levels. I just
wanted
> to
> > tell you about those options when running point_stat.
> >
> > John
> >
> > On Wed, Jul 22, 2020 at 3:25 PM Edward Strobach - NOAA Affiliate
via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
> > >
> > > I think I know what you're saying here.  I can give that a test
I
> > suppose.
> > > I'll first have to identify what L10 (or LXX) is, and see what
the
> > average
> > > pressure of that level is, and construct a range of pressure
that would
> > > encompass that level.  Is that what you mean?  This looks like
> something
> > I
> > > would have to modify in my PointStatConfig_cam file.  I would
then
> define
> > > something like this L1, L2, L3, ..., L30,..
> > > instead of P1000, P950,..., P150, etc..
> > > inside my Point_Stat_cam.conf
> > >
> > >
> > > On Wed, Jul 22, 2020 at 5:18 PM John Halley Gotway via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Ed,
> > > >
> > > > Before resolving this ticket, I want to clarify one minor
point. You
> > can
> > > > configure Point-Stat to have some control over which point obs
levels
> > are
> > > > used. Below I've listed 3 examples:
> > > >
> > > > (1) Require an exact match... only use observations exactly at
500mb:
> > > > fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> > > > obs = fcst;
> > > >
> > > > (2) Match any point obs close to 500 mb to the forecast at
that
> level:
> > > > fcst = { field = [ { name = "TMP"; level = "P500"; } ]; }
> > > > obs = { field = [ { name = "TMP"; level = "P475-525"; } ]; }
> > > >
> > > > (3) Suppose you have TMP at P400, P500, and P600, use point
obs
> between
> > > 450
> > > > and 500 and vertically interpolate the forecast values to the
> pressure
> > > > level of the observation.
> > > > fcst = { field = [ { name = "TMP"; level = "P400-600"; } ]; }
> > > > obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
> > > >
> > > > Since you have hybrid levels, none of these really apply. But
let's
> say
> > > > that it was meaningful to match hybrid level 10 to
observations
> between
> > > > P450 and 550 (which I'm sure it's not!). You could do so like
this:
> > > > fcst = { field = [ { name = "TMP"; level = "L10"; } ]; }
> > > > obs = { field = [ { name = "TMP"; level = "P450-550"; } ]; }
> > > >
> > > > Just wanted to clarify.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > > On Wed, Jul 22, 2020 at 2:18 PM Edward Strobach - NOAA
Affiliate via
> > RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981 >
> > > > >
> > > > > That's what I thought.  THanks
> > > > >
> > > > > On Wed, Jul 22, 2020 at 4:15 PM John Halley Gotway via RT <
> > > > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Ed,
> > > > > >
> > > > > > I logged onto wcoss and took a look at:
> > > > > >
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00
> > > > > >
> > > > > > Using wgrib2 to inventory the file I see:
> > > > > > (1) No record of PRMSL present.
> > > > > > (2) No record of CAPE present.
> > > > > > (3) No record of DPT present.
> > > > > >
> > > > > > Of the 910 records in that file, 842 are on hybrid levels,
40 are
> > at
> > > > the
> > > > > > surface, and the rest are soil moisture below ground or
other
> misc
> > > > > heights
> > > > > > (like tropopause, entire atmosphere, and so on). The only
ones
> are
> > 2
> > > > > meters
> > > > > > are:
> > > > > >
> > > > > > 800:55227406:d=2020071806:TMP:2 m above ground:26 hour
fcst:
> > > > > > 801:55361052:d=2020071806:SPFH:2 m above ground:26 hour
fcst:
> > > > > > 802:55480631:d=2020071806:RH:2 m above ground:26 hour
fcst:
> > > > > >
> > > > > > The derivation of cape is only done in pb2nc, not for
gridded
> data.
> > > > > >
> > > > > > Not much we can do on the MET side of things here. I'd
recommend
> > that
> > > > > this
> > > > > > data be post-processed to pressure levels rather than
remaining
> on
> > > the
> > > > > > model's native vertical coordinate.
> > > > > >
> > > > > > Thanks,
> > > > > > John Halley Gotway
> > > > > >
> > > > > > On Wed, Jul 22, 2020 at 10:56 AM Edward Strobach - NOAA
Affiliate
> > via
> > > > RT
> > > > > <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > > >
> > > > > > > Wed Jul 22 10:56:56 2020: Request 95981 was acted upon.
> > > > > > > Transaction: Ticket created by edward.strobach at noaa.gov
> > > > > > >        Queue: met_help
> > > > > > >      Subject: missing fields in stat files
> > > > > > >        Owner: Nobody
> > > > > > >   Requestors: edward.strobach at noaa.gov
> > > > > > >       Status: new
> > > > > > >  Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=95981
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Currently, I'm setting up verification for the
meteorological
> > files
> > > > > from
> > > > > > my
> > > > > > > CMAQ runs.  I had intended on using the following
variables in
> > this
> > > > > way:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > *BOTH_VAR1_NAME = TMPBOTH_VAR1_LEVELS = Z2, P1000, P925,
P850,
> > > P700,
> > > > > > P500,
> > > > > > > P400, P300, P250, P200, P150, P100, P50BOTH_VAR2_NAME =
> > > > > > RHBOTH_VAR2_LEVELS
> > > > > > > = Z2, P1000, P925, P850, P700, P500, P400, P300,
> > > P250BOTH_VAR3_NAME =
> > > > > > > DPTBOTH_VAR3_LEVELS = Z2BOTH_VAR4_NAME =
UGRDBOTH_VAR4_LEVELS =
> > > Z10,
> > > > > > P1000,
> > > > > > > P925, P850, P700, P500, P400, P300, P250, P200, P150,
P100,
> > > > > > > P50BOTH_VAR5_NAME = VGRDBOTH_VAR5_LEVELS = Z10, P1000,
P925,
> > P850,
> > > > > P700,
> > > > > > > P500, P400, P300, P250, P200, P150, P100,
P50BOTH_VAR6_NAME =
> > > > > > > PRMSLBOTH_VAR6_LEVELS = L0BOTH_VAR7_NAME =
> WINDBOTH_VAR7_LEVELS =
> > > > > > > Z10FCST_VAR8_NAME = CAPEFCST_VAR8_LEVELS =
Z0FCST_VAR8_OPTIONS
> =
> > > > > > cnt_thresh
> > > > > > > = [ >0 ];FCST_VAR8_THRESH = >500, >1000, >1500, >2000,
>3000,
> > > > > > > >4000OBS_VAR8_NAME = CAPEOBS_VAR8_LEVELS =
> > > Z0-100000OBS_VAR8_OPTIONS
> > > > =
> > > > > > > cnt_thresh = [ >0 ]; cnt_logic = UNION;OBS_VAR8_THRESH =
>500,
> > > >1000,
> > > > > > > >1500, >2000, >3000, >4000FCST_VAR9_NAME =
> HPBLFCST_VAR9_LEVELS =
> > > > > > > Z0OBS_VAR9_NAME = PBLOBS_VAR9_LEVELS =
L0OBS_VAR9_OPTIONS =
> desc
> > =
> > > > > > "TKE";*
> > > > > > >
> > > > > > > The ones that are highlighted blue are the ones being
stored.
> > Note
> > > > > that
> > > > > > > CAPE has Z0 and Z0-100000; I had changed that from L0
when L0
> > > didn't
> > > > > > work.
> > > > > > > However, in both instances CAPE wasn't not stored in the
point
> > stat
> > > > > > files.
> > > > > > > I also found that no fields were stored on pressure
levels,
> > which I
> > > > > > > attribute to the fact that the data is being stored on
hybrid
> > > levels
> > > > > > rather
> > > > > > > than standard pressure levels.  However, aside from the
> pressure
> > > > level
> > > > > > > issue, 2-meter dewpoint, CAPE, and sea-level pressure
are also
> > not
> > > > > being
> > > > > > > stored.  I get messages like this, for example:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > *DEBUG 2: Reading data for VGRD/P50.WARNING:WARNING:
> > > > > > > process_fcst_climo_files() -> no fields matching
VGRD/P50 found
> > in
> > > > > file:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:WARNING:WARNING:
> > > > > > > MetGrib2DataFile::data_plane_array() -> No matching
records
> found
> > > for
> > > > > > > 'PRMSL/Z0'WARNING:DEBUG 2:DEBUG 2:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--------------------------------------------------------------------------------DEBUG
> > > > > > > 2:DEBUG 2: Reading data for PRMSL/Z0.WARNING:WARNING:
> > > > > > > process_fcst_climo_files() -> no fields matching
PRMSL/Z0 found
> > in
> > > > > file:
> > > > > > >
> > > > >
> > >
>
/gpfs/hps/nco/ops/com/aqm/prod/aqm.20200718/aqm.t06z.nmm26.tm00WARNING:*
> > > > > > >
> > > > > > > I can reason with why fields at pressure levels are not
being
> > > stored
> > > > as
> > > > > > > well as CAPE, but I can't reason with why 2-meter
dewpoint and
> > > > > sea-level
> > > > > > > pressure is not being stored.  Moreover, since CAPE is a
> derived
> > > > field,
> > > > > > can
> > > > > > > I not use the output available to derive it during the
point
> stat
> > > > step?
> > > > > > Or
> > > > > > > is that just done for observations during the PB2NC
step?  If I
> > > can't
> > > > > > > derive fields during the point stat step, then I guess
that
> would
> > > > > explain
> > > > > > > why all the fields that I intended to store did not
store.  I'm
> > > okay
> > > > > with
> > > > > > > that, although dewpoint and CAPE would be of interest.
> However,
> > I
> > > > > would
> > > > > > > need a way to supplant pressure levels with hybrid
levels if
> > > > possible.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Edward Strobach
> > > > > > > EMC/NCEP/NWS/
> > > > > > > IMSG Contractor
> > > > > > > Cubicle#: 2029
> > > > > > > 301-683-3717
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Edward Strobach
> > > > > EMC/NCEP/NWS/
> > > > > IMSG Contractor
> > > > > Cubicle#: 2029
> > > > > 301-683-3717
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > --
> > > Edward Strobach
> > > EMC/NCEP/NWS/
> > > IMSG Contractor
> > > Cubicle#: 2029
> > > 301-683-3717
> > >
> > >
> >
> >
>
> --
> Edward Strobach
> EMC/NCEP/NWS/
> IMSG Contractor
> Cubicle#: 2029
> 301-683-3717
>
>

------------------------------------------------


More information about the Met_help mailing list