[Met_help] [rt.rap.ucar.edu #97213] History for level in tc_rmw configuration file
John Halley Gotway via RT
met_help at ucar.edu
Mon Oct 26 17:10:20 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I use the same level definition indicated in
https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
field = [
{
name = "PRMSL";
level = ["L0"];
},
{
name = "TMP";
level = ["P500"];
},
{
name = "UGRD";
level = ["P500"];
},
{
name = "VGRD";
level = ["P500"];
}
];
Then I run:
tc_rmw -data invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
invest09l.2019091212.trak.hafs.atcfun
ix.all -config TCRMWConfig -out Humber.nc
I got :
DEBUG 1: Config File Default:
/apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
DEBUG 1: Config File User: TCRMWConfig
DEBUG 2: Found 4 variable/level fields requested in the configuration file.
DEBUG 2: Processing 1 track data file(s).
DEBUG 1: Reading track file: invest09l.2019091212.trak.hafs.atcfunix.all
WARNING:
WARNING: process_track_files() -> multiple tracks found (2)! Using the
first one. Adjust the configuration file filtering options to select a
single track.
WARNING:
DEBUG 2: Writing 45 track lines.
DEBUG 2: Processing 1 track consisting of 43 points.
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> No matching record found for
'PRMSL/L0'
WARNING:
ERROR :
ERROR : get_series_entry() -> Could not find data for PRMSL/L0 in file:
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
ERROR :
Here is a snapshot of the data inventory of the grib2 data using wgrib2:
1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
2:6210615:d=2019091212:REFC:entire atmosphere (considered as a single
layer):36 hour fcst:
3:9010808:d=2019091212:GUST:surface:36 hour fcst:
4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
My question is how should I define "level" for PRMSL and UGRD? Here is my
working directory on orion:
/work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
Thanks,
Man
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: level in tc_rmw configuration file
From: John Halley Gotway
Time: Mon Oct 26 09:45:55 2020
Hi Man,
I see you have a question about setting the level config option for
the MET
tools. Unfortunately, I'm not able to access Orion. Can you please tar
up
your sample data and post it to our anonymous ftp site following these
instructions?
http://www.dtcenter.org/community-code/model-evaluation-tools-met/met-
help-desk#ftp
Or, if it's easier, copy it to cheyenne, hera, jet, or one of the DTC
project machines at NCAR.
Thanks,
John
On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
> Transaction: Ticket created by man.zhang at noaa.gov
> Queue: met_help
> Subject: level in tc_rmw configuration file
> Owner: Nobody
> Requestors: man.zhang at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>
>
> Hello,
>
> I use the same level definition indicated in
> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
>
> field = [
>
> {
>
> name = "PRMSL";
>
> level = ["L0"];
>
> },
>
> {
>
> name = "TMP";
>
> level = ["P500"];
>
> },
>
> {
>
> name = "UGRD";
>
> level = ["P500"];
>
> },
>
> {
>
> name = "VGRD";
>
> level = ["P500"];
>
> }
>
> ];
> Then I run:
>
> tc_rmw -data invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
-deck
> invest09l.2019091212.trak.hafs.atcfun
>
> ix.all -config TCRMWConfig -out Humber.nc
>
> I got :
>
> DEBUG 1: Config File Default:
> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
>
> DEBUG 1: Config File User: TCRMWConfig
>
> DEBUG 2: Found 4 variable/level fields requested in the
configuration file.
>
> DEBUG 2: Processing 1 track data file(s).
>
> DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
>
> WARNING:
>
> WARNING: process_track_files() -> multiple tracks found (2)! Using
the
> first one. Adjust the configuration file filtering options to select
a
> single track.
>
> WARNING:
>
> DEBUG 2: Writing 45 track lines.
>
> DEBUG 2: Processing 1 track consisting of 43 points.
>
> WARNING:
>
> WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
> 'PRMSL/L0'
>
> WARNING:
>
> ERROR :
>
> ERROR : get_series_entry() -> Could not find data for PRMSL/L0 in
file:
> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>
> ERROR :
>
>
> Here is a snapshot of the data inventory of the grib2 data using
wgrib2:
>
> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
>
> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
> layer):36 hour fcst:
>
> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
>
> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
>
> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
>
> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
>
> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
>
> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
>
> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
>
> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
>
> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
>
> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
>
> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
>
> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
>
> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
>
> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
>
> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
>
> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
>
> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
>
> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
>
> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
>
> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
>
> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
>
> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
>
> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
>
> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
>
> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
>
> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
>
> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
>
> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
>
> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
>
> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
>
> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
>
> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
>
> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
>
> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
>
> My question is how should I define "level" for PRMSL and UGRD? Here
is my
> working directory on orion:
>
> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
>
>
> Thanks,
>
> Man
>
>
------------------------------------------------
Subject: level in tc_rmw configuration file
From: Man Zhang - NOAA Affiliate
Time: Mon Oct 26 10:14:46 2020
John,
I moved the directory to Hera:
/scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
I typed
*plot_data_plane invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
It can generate the plot as expected.
However, as you can see, I define
{
name = "UGRD";
level = ["P500"];
},
in TCRMWConfig, and type
[Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig -out
Humberto.nc
DEBUG 1: Config File Default:
/contrib/met/9.1/share/met/config/TCRMWConfig_default
DEBUG 1: Config File User: TCRMWConfig
DEBUG 2: Found 2 variable/level fields requested in the configuration
file.
DEBUG 2: Processing 1 track data file(s).
DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
WARNING:
WARNING: process_track_files() -> multiple tracks found (2)! Using the
first one. Adjust the configuration file filtering options to select a
single track.
WARNING:
DEBUG 2: Writing 45 track lines.
DEBUG 2: Processing 1 track consisting of 43 points.
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
'UGRD/P500'
WARNING:
ERROR :
ERROR : get_series_entry() -> Could not find data for UGRD/P500 in
file:
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
ERROR :
My question is how should I define the level and field name in
TCRMWConfig
file.
Thanks,
Man
On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Hi Man,
>
> I see you have a question about setting the level config option for
the MET
> tools. Unfortunately, I'm not able to access Orion. Can you please
tar up
> your sample data and post it to our anonymous ftp site following
these
> instructions?
>
>
> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>
> Or, if it's easier, copy it to cheyenne, hera, jet, or one of the
DTC
> project machines at NCAR.
>
> Thanks,
> John
>
> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
> > Transaction: Ticket created by man.zhang at noaa.gov
> > Queue: met_help
> > Subject: level in tc_rmw configuration file
> > Owner: Nobody
> > Requestors: man.zhang at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
> >
> >
> > Hello,
> >
> > I use the same level definition indicated in
> > https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
> >
> > field = [
> >
> > {
> >
> > name = "PRMSL";
> >
> > level = ["L0"];
> >
> > },
> >
> > {
> >
> > name = "TMP";
> >
> > level = ["P500"];
> >
> > },
> >
> > {
> >
> > name = "UGRD";
> >
> > level = ["P500"];
> >
> > },
> >
> > {
> >
> > name = "VGRD";
> >
> > level = ["P500"];
> >
> > }
> >
> > ];
> > Then I run:
> >
> > tc_rmw -data invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
-deck
> > invest09l.2019091212.trak.hafs.atcfun
> >
> > ix.all -config TCRMWConfig -out Humber.nc
> >
> > I got :
> >
> > DEBUG 1: Config File Default:
> > /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
> >
> > DEBUG 1: Config File User: TCRMWConfig
> >
> > DEBUG 2: Found 4 variable/level fields requested in the
configuration
> file.
> >
> > DEBUG 2: Processing 1 track data file(s).
> >
> > DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
> >
> > WARNING:
> >
> > WARNING: process_track_files() -> multiple tracks found (2)! Using
the
> > first one. Adjust the configuration file filtering options to
select a
> > single track.
> >
> > WARNING:
> >
> > DEBUG 2: Writing 45 track lines.
> >
> > DEBUG 2: Processing 1 track consisting of 43 points.
> >
> > WARNING:
> >
> > WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
> > 'PRMSL/L0'
> >
> > WARNING:
> >
> > ERROR :
> >
> > ERROR : get_series_entry() -> Could not find data for PRMSL/L0 in
file:
> > invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> >
> > ERROR :
> >
> >
> > Here is a snapshot of the data inventory of the grib2 data using
wgrib2:
> >
> > 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
> >
> > 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
> > layer):36 hour fcst:
> >
> > 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
> >
> > 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
> >
> > 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
> >
> > 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
> >
> > 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
> >
> > 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
> >
> > 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
> >
> > 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
> >
> > 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
> >
> > 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
> >
> > 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
> >
> > 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
> >
> > 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
> >
> > 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
> >
> > 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
> >
> > 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
> >
> > 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
> >
> > 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
> >
> > 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
> >
> > 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
> >
> > 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
> >
> > 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
> >
> > 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
> >
> > 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
> >
> > 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
> >
> > 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
> >
> > 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
> >
> > 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
> >
> > 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
> >
> > 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
> >
> > 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
> >
> > 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
> >
> > 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
> >
> > 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
> >
> > My question is how should I define "level" for PRMSL and UGRD?
Here is my
> > working directory on orion:
> >
> > /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
> >
> >
> > Thanks,
> >
> > Man
> >
> >
>
>
------------------------------------------------
Subject: level in tc_rmw configuration file
From: John Halley Gotway
Time: Mon Oct 26 15:58:18 2020
Man,
Looks like there's permission problems with this data on Hera:
[John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
/scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
[John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
total 2.2G
drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
-rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
Can you please open up the permissions?
Sorry it's taken so long. I had to reset my master password on Hera
and
that takes a few hours to complete.
John
On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>
> John,
> I moved the directory to Hera:
>
> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>
>
> I typed
>
> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
>
> It can generate the plot as expected.
>
>
> However, as you can see, I define
>
> {
>
> name = "UGRD";
>
> level = ["P500"];
>
> },
>
> in TCRMWConfig, and type
>
>
> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig -out
> Humberto.nc
>
> DEBUG 1: Config File Default:
> /contrib/met/9.1/share/met/config/TCRMWConfig_default
>
> DEBUG 1: Config File User: TCRMWConfig
>
> DEBUG 2: Found 2 variable/level fields requested in the
configuration file.
>
> DEBUG 2: Processing 1 track data file(s).
>
> DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
>
> WARNING:
>
> WARNING: process_track_files() -> multiple tracks found (2)! Using
the
> first one. Adjust the configuration file filtering options to select
a
> single track.
>
> WARNING:
>
> DEBUG 2: Writing 45 track lines.
>
> DEBUG 2: Processing 1 track consisting of 43 points.
>
> WARNING:
>
> WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
> 'UGRD/P500'
>
> WARNING:
>
> ERROR :
>
> ERROR : get_series_entry() -> Could not find data for UGRD/P500 in
file:
> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>
> ERROR :
>
> My question is how should I define the level and field name in
TCRMWConfig
> file.
>
> Thanks,
> Man
>
>
> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Man,
> >
> > I see you have a question about setting the level config option
for the
> MET
> > tools. Unfortunately, I'm not able to access Orion. Can you please
tar up
> > your sample data and post it to our anonymous ftp site following
these
> > instructions?
> >
> >
> >
> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
> >
> > Or, if it's easier, copy it to cheyenne, hera, jet, or one of the
DTC
> > project machines at NCAR.
> >
> > Thanks,
> > John
> >
> > On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via RT
<
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
> > > Transaction: Ticket created by man.zhang at noaa.gov
> > > Queue: met_help
> > > Subject: level in tc_rmw configuration file
> > > Owner: Nobody
> > > Requestors: man.zhang at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
> >
> > >
> > >
> > > Hello,
> > >
> > > I use the same level definition indicated in
> > > https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
> > >
> > > field = [
> > >
> > > {
> > >
> > > name = "PRMSL";
> > >
> > > level = ["L0"];
> > >
> > > },
> > >
> > > {
> > >
> > > name = "TMP";
> > >
> > > level = ["P500"];
> > >
> > > },
> > >
> > > {
> > >
> > > name = "UGRD";
> > >
> > > level = ["P500"];
> > >
> > > },
> > >
> > > {
> > >
> > > name = "VGRD";
> > >
> > > level = ["P500"];
> > >
> > > }
> > >
> > > ];
> > > Then I run:
> > >
> > > tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
> > > invest09l.2019091212.trak.hafs.atcfun
> > >
> > > ix.all -config TCRMWConfig -out Humber.nc
> > >
> > > I got :
> > >
> > > DEBUG 1: Config File Default:
> > > /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
> > >
> > > DEBUG 1: Config File User: TCRMWConfig
> > >
> > > DEBUG 2: Found 4 variable/level fields requested in the
configuration
> > file.
> > >
> > > DEBUG 2: Processing 1 track data file(s).
> > >
> > > DEBUG 1: Reading track file:
> invest09l.2019091212.trak.hafs.atcfunix.all
> > >
> > > WARNING:
> > >
> > > WARNING: process_track_files() -> multiple tracks found (2)!
Using the
> > > first one. Adjust the configuration file filtering options to
select a
> > > single track.
> > >
> > > WARNING:
> > >
> > > DEBUG 2: Writing 45 track lines.
> > >
> > > DEBUG 2: Processing 1 track consisting of 43 points.
> > >
> > > WARNING:
> > >
> > > WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
> > > 'PRMSL/L0'
> > >
> > > WARNING:
> > >
> > > ERROR :
> > >
> > > ERROR : get_series_entry() -> Could not find data for PRMSL/L0
in
> file:
> > > invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> > >
> > > ERROR :
> > >
> > >
> > > Here is a snapshot of the data inventory of the grib2 data using
> wgrib2:
> > >
> > > 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
> > >
> > > 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
> > > layer):36 hour fcst:
> > >
> > > 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
> > >
> > > 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
> > >
> > > 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
> > >
> > > 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
> > >
> > > 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
> > >
> > > 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
> > >
> > > 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
> > >
> > > 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
> > >
> > > 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
> > >
> > > 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
> > >
> > > 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
> > >
> > > 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
> > >
> > > 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
> > >
> > > 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
> > >
> > > 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
> > >
> > > 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
> > >
> > > 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
> > >
> > > 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
> > >
> > > 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
> > >
> > > 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
> > >
> > > 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
> > >
> > > 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
> > >
> > > 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
> > >
> > > 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
> > >
> > > 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
> > >
> > > 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
> > >
> > > 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
> > >
> > > 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
> > >
> > > 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
> > >
> > > 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
> > >
> > > 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
> > >
> > > 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
> > >
> > > 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
> > >
> > > 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
> > >
> > > My question is how should I define "level" for PRMSL and UGRD?
Here is
> my
> > > working directory on orion:
> > >
> > > /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
> > >
> > >
> > > Thanks,
> > >
> > > Man
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #97213] level in tc_rmw configuration file
From: Man Zhang - NOAA Affiliate
Time: Mon Oct 26 16:00:39 2020
Please try again. -M
> On Oct 26, 2020, at 3:58 PM, John Halley Gotway via RT
<met_help at ucar.edu> wrote:
>
> Man,
>
> Looks like there's permission problems with this data on Hera:
>
> [John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
> [John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
> total 2.2G
> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
> drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
> drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
>
> Can you please open up the permissions?
>
> Sorry it's taken so long. I had to reset my master password on Hera
and
> that takes a few hours to complete.
>
> John
>
> On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>
>> John,
>> I moved the directory to Hera:
>>
>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>>
>>
>> I typed
>>
>> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
>>
>> It can generate the plot as expected.
>>
>>
>> However, as you can see, I define
>>
>> {
>>
>> name = "UGRD";
>>
>> level = ["P500"];
>>
>> },
>>
>> in TCRMWConfig, and type
>>
>>
>> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
>> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig
-out
>> Humberto.nc
>>
>> DEBUG 1: Config File Default:
>> /contrib/met/9.1/share/met/config/TCRMWConfig_default
>>
>> DEBUG 1: Config File User: TCRMWConfig
>>
>> DEBUG 2: Found 2 variable/level fields requested in the
configuration file.
>>
>> DEBUG 2: Processing 1 track data file(s).
>>
>> DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
>>
>> WARNING:
>>
>> WARNING: process_track_files() -> multiple tracks found (2)! Using
the
>> first one. Adjust the configuration file filtering options to
select a
>> single track.
>>
>> WARNING:
>>
>> DEBUG 2: Writing 45 track lines.
>>
>> DEBUG 2: Processing 1 track consisting of 43 points.
>>
>> WARNING:
>>
>> WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
>> 'UGRD/P500'
>>
>> WARNING:
>>
>> ERROR :
>>
>> ERROR : get_series_entry() -> Could not find data for UGRD/P500 in
file:
>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>
>> ERROR :
>>
>> My question is how should I define the level and field name in
TCRMWConfig
>> file.
>>
>> Thanks,
>> Man
>>
>>
>> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
>> met_help at ucar.edu>
>> wrote:
>>
>>> Hi Man,
>>>
>>> I see you have a question about setting the level config option
for the
>> MET
>>> tools. Unfortunately, I'm not able to access Orion. Can you please
tar up
>>> your sample data and post it to our anonymous ftp site following
these
>>> instructions?
>>>
>>>
>>>
>> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>>>
>>> Or, if it's easier, copy it to cheyenne, hera, jet, or one of the
DTC
>>> project machines at NCAR.
>>>
>>> Thanks,
>>> John
>>>
>>> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via RT
<
>>> met_help at ucar.edu> wrote:
>>>
>>>>
>>>> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
>>>> Transaction: Ticket created by man.zhang at noaa.gov
>>>> Queue: met_help
>>>> Subject: level in tc_rmw configuration file
>>>> Owner: Nobody
>>>> Requestors: man.zhang at noaa.gov
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
>>>
>>>>
>>>>
>>>> Hello,
>>>>
>>>> I use the same level definition indicated in
>>>> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
>>>>
>>>> field = [
>>>>
>>>> {
>>>>
>>>> name = "PRMSL";
>>>>
>>>> level = ["L0"];
>>>>
>>>> },
>>>>
>>>> {
>>>>
>>>> name = "TMP";
>>>>
>>>> level = ["P500"];
>>>>
>>>> },
>>>>
>>>> {
>>>>
>>>> name = "UGRD";
>>>>
>>>> level = ["P500"];
>>>>
>>>> },
>>>>
>>>> {
>>>>
>>>> name = "VGRD";
>>>>
>>>> level = ["P500"];
>>>>
>>>> }
>>>>
>>>> ];
>>>> Then I run:
>>>>
>>>> tc_rmw -data invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
-deck
>>>> invest09l.2019091212.trak.hafs.atcfun
>>>>
>>>> ix.all -config TCRMWConfig -out Humber.nc
>>>>
>>>> I got :
>>>>
>>>> DEBUG 1: Config File Default:
>>>> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
>>>>
>>>> DEBUG 1: Config File User: TCRMWConfig
>>>>
>>>> DEBUG 2: Found 4 variable/level fields requested in the
configuration
>>> file.
>>>>
>>>> DEBUG 2: Processing 1 track data file(s).
>>>>
>>>> DEBUG 1: Reading track file:
>> invest09l.2019091212.trak.hafs.atcfunix.all
>>>>
>>>> WARNING:
>>>>
>>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
>>>> first one. Adjust the configuration file filtering options to
select a
>>>> single track.
>>>>
>>>> WARNING:
>>>>
>>>> DEBUG 2: Writing 45 track lines.
>>>>
>>>> DEBUG 2: Processing 1 track consisting of 43 points.
>>>>
>>>> WARNING:
>>>>
>>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
>>>> 'PRMSL/L0'
>>>>
>>>> WARNING:
>>>>
>>>> ERROR :
>>>>
>>>> ERROR : get_series_entry() -> Could not find data for PRMSL/L0
in
>> file:
>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>>
>>>> ERROR :
>>>>
>>>>
>>>> Here is a snapshot of the data inventory of the grib2 data using
>> wgrib2:
>>>>
>>>> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
>>>>
>>>> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
>>>> layer):36 hour fcst:
>>>>
>>>> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
>>>>
>>>> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
>>>>
>>>> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
>>>>
>>>> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
>>>>
>>>> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
>>>>
>>>> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
>>>>
>>>> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
>>>>
>>>> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
>>>>
>>>> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
>>>>
>>>> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
>>>>
>>>> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
>>>>
>>>> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
>>>>
>>>> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
>>>>
>>>> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
>>>>
>>>> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
>>>>
>>>> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
>>>>
>>>> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
>>>>
>>>> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
>>>>
>>>> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
>>>>
>>>> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
>>>>
>>>> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
>>>>
>>>> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
>>>>
>>>> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
>>>>
>>>> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
>>>>
>>>> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
>>>>
>>>> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
>>>>
>>>> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
>>>>
>>>> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
>>>>
>>>> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
>>>>
>>>> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
>>>>
>>>> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
>>>>
>>>> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
>>>>
>>>> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
>>>>
>>>> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
>>>>
>>>> My question is how should I define "level" for PRMSL and UGRD?
Here is
>> my
>>>> working directory on orion:
>>>>
>>>> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Man
>>>>
>>>>
>>>
>>>
>>
>>
>
------------------------------------------------
Subject: level in tc_rmw configuration file
From: John Halley Gotway
Time: Mon Oct 26 16:04:38 2020
Man,
Looks like you need to chmod them recursively:
[John.H.Gotway at hfe08 _MET_TC]$ ls -lah
/scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
total 2.2G
drwxr-sr-x 2 Man.Zhang gmtb 4.0K Oct 26 16:09 .
drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
-rw-r----- 1 Man.Zhang gmtb 41K Oct 24 03:36 grb2.log
-rw-r----- 1 Man.Zhang gmtb 349K Oct 24 22:17 Humber.nc
-rw-r----- 1 Man.Zhang gmtb 349K Oct 24 03:12 Humberto.log
-rw-r----- 1 Man.Zhang gmtb 348K Oct 26 16:10 Humberto.nc
-rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:47
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
-rw-r----- 1 Man.Zhang gmtb 23K Oct 24 02:20
invest09l.2019091212.trak.hafs.atcfunix.all
-rw-r----- 1 Man.Zhang gmtb 324 Oct 26 16:02 README.zhang
-rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:40 TCRMWConfig
-rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 02:24 TCRMWConfig_default
-rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:54 TCRMWConfig_nc
-rw-r----- 1 Man.Zhang gmtb 766K Oct 26 16:04 tmp.ps
John
On Mon, Oct 26, 2020 at 4:01 PM Man Zhang - NOAA Affiliate via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>
> Please try again. -M
> > On Oct 26, 2020, at 3:58 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
> >
> > Man,
> >
> > Looks like there's permission problems with this data on Hera:
> >
> > [John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
> > /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
> > [John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
> > total 2.2G
> > drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
> > drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
> > drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
> > -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
> >
> > Can you please open up the permissions?
> >
> > Sorry it's taken so long. I had to reset my master password on
Hera and
> > that takes a few hours to complete.
> >
> > John
> >
> > On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via RT
<
> > met_help at ucar.edu> wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
> >>
> >> John,
> >> I moved the directory to Hera:
> >>
> >> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
> >>
> >>
> >> I typed
> >>
> >> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> >> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
> >>
> >> It can generate the plot as expected.
> >>
> >>
> >> However, as you can see, I define
> >>
> >> {
> >>
> >> name = "UGRD";
> >>
> >> level = ["P500"];
> >>
> >> },
> >>
> >> in TCRMWConfig, and type
> >>
> >>
> >> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
> >> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
> >> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig
-out
> >> Humberto.nc
> >>
> >> DEBUG 1: Config File Default:
> >> /contrib/met/9.1/share/met/config/TCRMWConfig_default
> >>
> >> DEBUG 1: Config File User: TCRMWConfig
> >>
> >> DEBUG 2: Found 2 variable/level fields requested in the
configuration
> file.
> >>
> >> DEBUG 2: Processing 1 track data file(s).
> >>
> >> DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
> >>
> >> WARNING:
> >>
> >> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
> >> first one. Adjust the configuration file filtering options to
select a
> >> single track.
> >>
> >> WARNING:
> >>
> >> DEBUG 2: Writing 45 track lines.
> >>
> >> DEBUG 2: Processing 1 track consisting of 43 points.
> >>
> >> WARNING:
> >>
> >> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
> >> 'UGRD/P500'
> >>
> >> WARNING:
> >>
> >> ERROR :
> >>
> >> ERROR : get_series_entry() -> Could not find data for UGRD/P500
in
> file:
> >> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> >>
> >> ERROR :
> >>
> >> My question is how should I define the level and field name in
> TCRMWConfig
> >> file.
> >>
> >> Thanks,
> >> Man
> >>
> >>
> >> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
> >> met_help at ucar.edu>
> >> wrote:
> >>
> >>> Hi Man,
> >>>
> >>> I see you have a question about setting the level config option
for the
> >> MET
> >>> tools. Unfortunately, I'm not able to access Orion. Can you
please tar
> up
> >>> your sample data and post it to our anonymous ftp site following
these
> >>> instructions?
> >>>
> >>>
> >>>
> >>
> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
> >>>
> >>> Or, if it's easier, copy it to cheyenne, hera, jet, or one of
the DTC
> >>> project machines at NCAR.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via
RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>>
> >>>> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
> >>>> Transaction: Ticket created by man.zhang at noaa.gov
> >>>> Queue: met_help
> >>>> Subject: level in tc_rmw configuration file
> >>>> Owner: Nobody
> >>>> Requestors: man.zhang at noaa.gov
> >>>> Status: new
> >>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
> >>>
> >>>>
> >>>>
> >>>> Hello,
> >>>>
> >>>> I use the same level definition indicated in
> >>>> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
> >>>>
> >>>> field = [
> >>>>
> >>>> {
> >>>>
> >>>> name = "PRMSL";
> >>>>
> >>>> level = ["L0"];
> >>>>
> >>>> },
> >>>>
> >>>> {
> >>>>
> >>>> name = "TMP";
> >>>>
> >>>> level = ["P500"];
> >>>>
> >>>> },
> >>>>
> >>>> {
> >>>>
> >>>> name = "UGRD";
> >>>>
> >>>> level = ["P500"];
> >>>>
> >>>> },
> >>>>
> >>>> {
> >>>>
> >>>> name = "VGRD";
> >>>>
> >>>> level = ["P500"];
> >>>>
> >>>> }
> >>>>
> >>>> ];
> >>>> Then I run:
> >>>>
> >>>> tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> -deck
> >>>> invest09l.2019091212.trak.hafs.atcfun
> >>>>
> >>>> ix.all -config TCRMWConfig -out Humber.nc
> >>>>
> >>>> I got :
> >>>>
> >>>> DEBUG 1: Config File Default:
> >>>> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
> >>>>
> >>>> DEBUG 1: Config File User: TCRMWConfig
> >>>>
> >>>> DEBUG 2: Found 4 variable/level fields requested in the
configuration
> >>> file.
> >>>>
> >>>> DEBUG 2: Processing 1 track data file(s).
> >>>>
> >>>> DEBUG 1: Reading track file:
> >> invest09l.2019091212.trak.hafs.atcfunix.all
> >>>>
> >>>> WARNING:
> >>>>
> >>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
> >>>> first one. Adjust the configuration file filtering options to
select a
> >>>> single track.
> >>>>
> >>>> WARNING:
> >>>>
> >>>> DEBUG 2: Writing 45 track lines.
> >>>>
> >>>> DEBUG 2: Processing 1 track consisting of 43 points.
> >>>>
> >>>> WARNING:
> >>>>
> >>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
> for
> >>>> 'PRMSL/L0'
> >>>>
> >>>> WARNING:
> >>>>
> >>>> ERROR :
> >>>>
> >>>> ERROR : get_series_entry() -> Could not find data for PRMSL/L0
in
> >> file:
> >>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> >>>>
> >>>> ERROR :
> >>>>
> >>>>
> >>>> Here is a snapshot of the data inventory of the grib2 data
using
> >> wgrib2:
> >>>>
> >>>> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
> >>>>
> >>>> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
> >>>> layer):36 hour fcst:
> >>>>
> >>>> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
> >>>>
> >>>> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
> >>>>
> >>>> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
> >>>>
> >>>> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
> >>>>
> >>>> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
> >>>>
> >>>> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
> >>>>
> >>>> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
> >>>>
> >>>> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
> >>>>
> >>>> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
> >>>>
> >>>> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
> >>>>
> >>>> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
> >>>>
> >>>> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
> >>>>
> >>>> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
> >>>>
> >>>> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
> >>>>
> >>>> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
> >>>>
> >>>> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
> >>>>
> >>>> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
> >>>>
> >>>> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
> >>>>
> >>>> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
> >>>>
> >>>> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
> >>>>
> >>>> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
> >>>>
> >>>> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
> >>>>
> >>>> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
> >>>>
> >>>> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
> >>>>
> >>>> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
> >>>>
> >>>> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
> >>>>
> >>>> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
> >>>>
> >>>> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
> >>>>
> >>>> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
> >>>>
> >>>> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
> >>>>
> >>>> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
> >>>>
> >>>> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
> >>>>
> >>>> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
> >>>>
> >>>> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
> >>>>
> >>>> My question is how should I define "level" for PRMSL and UGRD?
Here is
> >> my
> >>>> working directory on orion:
> >>>>
> >>>> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Man
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #97213] level in tc_rmw configuration file
From: Man Zhang - NOAA Affiliate
Time: Mon Oct 26 16:06:46 2020
sorry about that. should be ok now
> On Oct 26, 2020, at 4:04 PM, John Halley Gotway via RT
<met_help at ucar.edu> wrote:
>
> Man,
>
> Looks like you need to chmod them recursively:
>
> [John.H.Gotway at hfe08 _MET_TC]$ ls -lah
> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
> total 2.2G
> drwxr-sr-x 2 Man.Zhang gmtb 4.0K Oct 26 16:09 .
> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
> -rw-r----- 1 Man.Zhang gmtb 41K Oct 24 03:36 grb2.log
> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 22:17 Humber.nc
> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 03:12 Humberto.log
> -rw-r----- 1 Man.Zhang gmtb 348K Oct 26 16:10 Humberto.nc
> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:47
> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> -rw-r----- 1 Man.Zhang gmtb 23K Oct 24 02:20
> invest09l.2019091212.trak.hafs.atcfunix.all
> -rw-r----- 1 Man.Zhang gmtb 324 Oct 26 16:02 README.zhang
> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:40 TCRMWConfig
> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 02:24 TCRMWConfig_default
> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:54 TCRMWConfig_nc
> -rw-r----- 1 Man.Zhang gmtb 766K Oct 26 16:04 tmp.ps
>
> John
>
> On Mon, Oct 26, 2020 at 4:01 PM Man Zhang - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>
>> Please try again. -M
>>> On Oct 26, 2020, at 3:58 PM, John Halley Gotway via RT <
>> met_help at ucar.edu> wrote:
>>>
>>> Man,
>>>
>>> Looks like there's permission problems with this data on Hera:
>>>
>>> [John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
>>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
>>> [John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
>>> total 2.2G
>>> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
>>> drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
>>> drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
>>> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
>>>
>>> Can you please open up the permissions?
>>>
>>> Sorry it's taken so long. I had to reset my master password on
Hera and
>>> that takes a few hours to complete.
>>>
>>> John
>>>
>>> On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via RT
<
>>> met_help at ucar.edu> wrote:
>>>
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>>>
>>>> John,
>>>> I moved the directory to Hera:
>>>>
>>>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>>>>
>>>>
>>>> I typed
>>>>
>>>> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
>>>>
>>>> It can generate the plot as expected.
>>>>
>>>>
>>>> However, as you can see, I define
>>>>
>>>> {
>>>>
>>>> name = "UGRD";
>>>>
>>>> level = ["P500"];
>>>>
>>>> },
>>>>
>>>> in TCRMWConfig, and type
>>>>
>>>>
>>>> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
>>>> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig
-out
>>>> Humberto.nc
>>>>
>>>> DEBUG 1: Config File Default:
>>>> /contrib/met/9.1/share/met/config/TCRMWConfig_default
>>>>
>>>> DEBUG 1: Config File User: TCRMWConfig
>>>>
>>>> DEBUG 2: Found 2 variable/level fields requested in the
configuration
>> file.
>>>>
>>>> DEBUG 2: Processing 1 track data file(s).
>>>>
>>>> DEBUG 1: Reading track file:
invest09l.2019091212.trak.hafs.atcfunix.all
>>>>
>>>> WARNING:
>>>>
>>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
>>>> first one. Adjust the configuration file filtering options to
select a
>>>> single track.
>>>>
>>>> WARNING:
>>>>
>>>> DEBUG 2: Writing 45 track lines.
>>>>
>>>> DEBUG 2: Processing 1 track consisting of 43 points.
>>>>
>>>> WARNING:
>>>>
>>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
>>>> 'UGRD/P500'
>>>>
>>>> WARNING:
>>>>
>>>> ERROR :
>>>>
>>>> ERROR : get_series_entry() -> Could not find data for UGRD/P500
in
>> file:
>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>>
>>>> ERROR :
>>>>
>>>> My question is how should I define the level and field name in
>> TCRMWConfig
>>>> file.
>>>>
>>>> Thanks,
>>>> Man
>>>>
>>>>
>>>> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
>>>> met_help at ucar.edu>
>>>> wrote:
>>>>
>>>>> Hi Man,
>>>>>
>>>>> I see you have a question about setting the level config option
for the
>>>> MET
>>>>> tools. Unfortunately, I'm not able to access Orion. Can you
please tar
>> up
>>>>> your sample data and post it to our anonymous ftp site following
these
>>>>> instructions?
>>>>>
>>>>>
>>>>>
>>>>
>> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>>>>>
>>>>> Or, if it's easier, copy it to cheyenne, hera, jet, or one of
the DTC
>>>>> project machines at NCAR.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via
RT <
>>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>>>
>>>>>> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
>>>>>> Transaction: Ticket created by man.zhang at noaa.gov
>>>>>> Queue: met_help
>>>>>> Subject: level in tc_rmw configuration file
>>>>>> Owner: Nobody
>>>>>> Requestors: man.zhang at noaa.gov
>>>>>> Status: new
>>>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
>>>>>
>>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I use the same level definition indicated in
>>>>>> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
>>>>>>
>>>>>> field = [
>>>>>>
>>>>>> {
>>>>>>
>>>>>> name = "PRMSL";
>>>>>>
>>>>>> level = ["L0"];
>>>>>>
>>>>>> },
>>>>>>
>>>>>> {
>>>>>>
>>>>>> name = "TMP";
>>>>>>
>>>>>> level = ["P500"];
>>>>>>
>>>>>> },
>>>>>>
>>>>>> {
>>>>>>
>>>>>> name = "UGRD";
>>>>>>
>>>>>> level = ["P500"];
>>>>>>
>>>>>> },
>>>>>>
>>>>>> {
>>>>>>
>>>>>> name = "VGRD";
>>>>>>
>>>>>> level = ["P500"];
>>>>>>
>>>>>> }
>>>>>>
>>>>>> ];
>>>>>> Then I run:
>>>>>>
>>>>>> tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> -deck
>>>>>> invest09l.2019091212.trak.hafs.atcfun
>>>>>>
>>>>>> ix.all -config TCRMWConfig -out Humber.nc
>>>>>>
>>>>>> I got :
>>>>>>
>>>>>> DEBUG 1: Config File Default:
>>>>>> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
>>>>>>
>>>>>> DEBUG 1: Config File User: TCRMWConfig
>>>>>>
>>>>>> DEBUG 2: Found 4 variable/level fields requested in the
configuration
>>>>> file.
>>>>>>
>>>>>> DEBUG 2: Processing 1 track data file(s).
>>>>>>
>>>>>> DEBUG 1: Reading track file:
>>>> invest09l.2019091212.trak.hafs.atcfunix.all
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
>>>>>> first one. Adjust the configuration file filtering options to
select a
>>>>>> single track.
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> DEBUG 2: Writing 45 track lines.
>>>>>>
>>>>>> DEBUG 2: Processing 1 track consisting of 43 points.
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
>> for
>>>>>> 'PRMSL/L0'
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> ERROR :
>>>>>>
>>>>>> ERROR : get_series_entry() -> Could not find data for PRMSL/L0
in
>>>> file:
>>>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>>>>
>>>>>> ERROR :
>>>>>>
>>>>>>
>>>>>> Here is a snapshot of the data inventory of the grib2 data
using
>>>> wgrib2:
>>>>>>
>>>>>> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
>>>>>>
>>>>>> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
>>>>>> layer):36 hour fcst:
>>>>>>
>>>>>> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
>>>>>>
>>>>>> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
>>>>>>
>>>>>> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
>>>>>>
>>>>>> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
>>>>>>
>>>>>> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
>>>>>>
>>>>>> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
>>>>>>
>>>>>> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
>>>>>>
>>>>>> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
>>>>>>
>>>>>> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
>>>>>>
>>>>>> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
>>>>>>
>>>>>> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
>>>>>>
>>>>>> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
>>>>>>
>>>>>> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
>>>>>>
>>>>>> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
>>>>>>
>>>>>> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
>>>>>>
>>>>>> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
>>>>>>
>>>>>> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
>>>>>>
>>>>>> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
>>>>>>
>>>>>> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
>>>>>>
>>>>>> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
>>>>>>
>>>>>> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
>>>>>>
>>>>>> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
>>>>>>
>>>>>> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
>>>>>>
>>>>>> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
>>>>>>
>>>>>> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
>>>>>>
>>>>>> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
>>>>>>
>>>>>> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
>>>>>>
>>>>>> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
>>>>>>
>>>>>> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
>>>>>>
>>>>>> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
>>>>>>
>>>>>> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
>>>>>>
>>>>>> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
>>>>>>
>>>>>> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
>>>>>>
>>>>>> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
>>>>>>
>>>>>> My question is how should I define "level" for PRMSL and UGRD?
Here is
>>>> my
>>>>>> working directory on orion:
>>>>>>
>>>>>> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Man
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>>
>>
>
------------------------------------------------
Subject: level in tc_rmw configuration file
From: John Halley Gotway
Time: Mon Oct 26 16:37:49 2020
Man,
OK, great, I'm able to read those files now.
I see that you're able to run plot_data_plane to read/plot the
UGRD/P500
field. But when you run tc_rmw, it can't find a matching UGRD/P500
field.
So tc_rmw is designed to...
(1) Read a single input hurricane track.
(2) Process each point of that track by looking for matching gridded
data
FOR THE VALID time of each track point.
The most likely explanation for the behavior you're seeing is a
mismatch in
time between the track point and the gridded data you're passing to
the
tool. And this is a relatively new tool, so it's very possible that
the log
messages should be improved to point you in the right direction.
I'm testing directly on hera in:
/scratch1/BMC/dtc/John.H.Gotway/MET/MET_Help/zhang_data_20201026
Loading the existing met-9.1 code:
*module use -a /contrib/anaconda/modulefilesmodule load
intel/18.0.5.274module load anaconda/latestmodule use -a
/contrib/met/modulefiles/module load met/9.1*
Confirmed that plot_data_plane works as you described and it does:
*plot_data_plane
_MET_TC/invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
UGRD_P500.ps
'name="UGRD"; level="P500";'*
Replicating the tc_rmw behavior you saw:
*tc_rmw -data
_MET_TC/invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
-deck _MET_TC/invest09l.2019091212.trak.hafs.atcfunix.all -config
TCRMWConfig*
(1) Let's start with this warning:
*WARNING: process_track_files() -> multiple tracks found (2)! Using
the
first one. Adjust the configuration file filtering options to select a
single track.*
Looking in the track file, I see lines for storm number 09 and 95, but
the
track lines look to be duplicates. I resolved this warning by picking
a
single one in the TCRMW config file like this:
* cyclone_number = "09";*
(2) And the next warning:
*WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
'UGRD/P500'*
Running at verbosity level 3 (-v 3), I see track points with valid
times of
20190912_12, 20190912_15, 20190912_18, and so on. But you're only
providing
gridded data for forecast hour 36.
If you only want to process this single point, you need to subset the
track
down by setting:
* lead = [ "36" ];*
And with these 2 changes, tc_rmw now runs on this data.
I can see how we should improve the warning/error messages to give the
user
more information about the times for which data cannot be found.
Hope that helps.
John
On Mon, Oct 26, 2020 at 4:04 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Man,
>
> Looks like you need to chmod them recursively:
>
> [John.H.Gotway at hfe08 _MET_TC]$ ls -lah
> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
> total 2.2G
> drwxr-sr-x 2 Man.Zhang gmtb 4.0K Oct 26 16:09 .
> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
> -rw-r----- 1 Man.Zhang gmtb 41K Oct 24 03:36 grb2.log
> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 22:17 Humber.nc
> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 03:12 Humberto.log
> -rw-r----- 1 Man.Zhang gmtb 348K Oct 26 16:10 Humberto.nc
> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:47
> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> -rw-r----- 1 Man.Zhang gmtb 23K Oct 24 02:20
> invest09l.2019091212.trak.hafs.atcfunix.all
> -rw-r----- 1 Man.Zhang gmtb 324 Oct 26 16:02 README.zhang
> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:40 TCRMWConfig
> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 02:24 TCRMWConfig_default
> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:54 TCRMWConfig_nc
> -rw-r----- 1 Man.Zhang gmtb 766K Oct 26 16:04 tmp.ps
>
> John
>
> On Mon, Oct 26, 2020 at 4:01 PM Man Zhang - NOAA Affiliate via RT <
> met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>
>> Please try again. -M
>> > On Oct 26, 2020, at 3:58 PM, John Halley Gotway via RT <
>> met_help at ucar.edu> wrote:
>> >
>> > Man,
>> >
>> > Looks like there's permission problems with this data on Hera:
>> >
>> > [John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
>> > /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
>> > [John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
>> > total 2.2G
>> > drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
>> > drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
>> > drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
>> > -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
>> >
>> > Can you please open up the permissions?
>> >
>> > Sorry it's taken so long. I had to reset my master password on
Hera and
>> > that takes a few hours to complete.
>> >
>> > John
>> >
>> > On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via
RT <
>> > met_help at ucar.edu> wrote:
>> >
>> >>
>> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>> >>
>> >> John,
>> >> I moved the directory to Hera:
>> >>
>> >> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>> >>
>> >>
>> >> I typed
>> >>
>> >> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> >> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
>> >>
>> >> It can generate the plot as expected.
>> >>
>> >>
>> >> However, as you can see, I define
>> >>
>> >> {
>> >>
>> >> name = "UGRD";
>> >>
>> >> level = ["P500"];
>> >>
>> >> },
>> >>
>> >> in TCRMWConfig, and type
>> >>
>> >>
>> >> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
>> >> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
>> >> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig
-out
>> >> Humberto.nc
>> >>
>> >> DEBUG 1: Config File Default:
>> >> /contrib/met/9.1/share/met/config/TCRMWConfig_default
>> >>
>> >> DEBUG 1: Config File User: TCRMWConfig
>> >>
>> >> DEBUG 2: Found 2 variable/level fields requested in the
configuration
>> file.
>> >>
>> >> DEBUG 2: Processing 1 track data file(s).
>> >>
>> >> DEBUG 1: Reading track file:
>> invest09l.2019091212.trak.hafs.atcfunix.all
>> >>
>> >> WARNING:
>> >>
>> >> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
>> >> first one. Adjust the configuration file filtering options to
select a
>> >> single track.
>> >>
>> >> WARNING:
>> >>
>> >> DEBUG 2: Writing 45 track lines.
>> >>
>> >> DEBUG 2: Processing 1 track consisting of 43 points.
>> >>
>> >> WARNING:
>> >>
>> >> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
>> >> 'UGRD/P500'
>> >>
>> >> WARNING:
>> >>
>> >> ERROR :
>> >>
>> >> ERROR : get_series_entry() -> Could not find data for UGRD/P500
in
>> file:
>> >> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> >>
>> >> ERROR :
>> >>
>> >> My question is how should I define the level and field name in
>> TCRMWConfig
>> >> file.
>> >>
>> >> Thanks,
>> >> Man
>> >>
>> >>
>> >> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
>> >> met_help at ucar.edu>
>> >> wrote:
>> >>
>> >>> Hi Man,
>> >>>
>> >>> I see you have a question about setting the level config option
for
>> the
>> >> MET
>> >>> tools. Unfortunately, I'm not able to access Orion. Can you
please
>> tar up
>> >>> your sample data and post it to our anonymous ftp site
following these
>> >>> instructions?
>> >>>
>> >>>
>> >>>
>> >>
>> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>> >>>
>> >>> Or, if it's easier, copy it to cheyenne, hera, jet, or one of
the DTC
>> >>> project machines at NCAR.
>> >>>
>> >>> Thanks,
>> >>> John
>> >>>
>> >>> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via
RT <
>> >>> met_help at ucar.edu> wrote:
>> >>>
>> >>>>
>> >>>> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
>> >>>> Transaction: Ticket created by man.zhang at noaa.gov
>> >>>> Queue: met_help
>> >>>> Subject: level in tc_rmw configuration file
>> >>>> Owner: Nobody
>> >>>> Requestors: man.zhang at noaa.gov
>> >>>> Status: new
>> >>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
>> >>>
>> >>>>
>> >>>>
>> >>>> Hello,
>> >>>>
>> >>>> I use the same level definition indicated in
>> >>>> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
>> >>>>
>> >>>> field = [
>> >>>>
>> >>>> {
>> >>>>
>> >>>> name = "PRMSL";
>> >>>>
>> >>>> level = ["L0"];
>> >>>>
>> >>>> },
>> >>>>
>> >>>> {
>> >>>>
>> >>>> name = "TMP";
>> >>>>
>> >>>> level = ["P500"];
>> >>>>
>> >>>> },
>> >>>>
>> >>>> {
>> >>>>
>> >>>> name = "UGRD";
>> >>>>
>> >>>> level = ["P500"];
>> >>>>
>> >>>> },
>> >>>>
>> >>>> {
>> >>>>
>> >>>> name = "VGRD";
>> >>>>
>> >>>> level = ["P500"];
>> >>>>
>> >>>> }
>> >>>>
>> >>>> ];
>> >>>> Then I run:
>> >>>>
>> >>>> tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> -deck
>> >>>> invest09l.2019091212.trak.hafs.atcfun
>> >>>>
>> >>>> ix.all -config TCRMWConfig -out Humber.nc
>> >>>>
>> >>>> I got :
>> >>>>
>> >>>> DEBUG 1: Config File Default:
>> >>>> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
>> >>>>
>> >>>> DEBUG 1: Config File User: TCRMWConfig
>> >>>>
>> >>>> DEBUG 2: Found 4 variable/level fields requested in the
configuration
>> >>> file.
>> >>>>
>> >>>> DEBUG 2: Processing 1 track data file(s).
>> >>>>
>> >>>> DEBUG 1: Reading track file:
>> >> invest09l.2019091212.trak.hafs.atcfunix.all
>> >>>>
>> >>>> WARNING:
>> >>>>
>> >>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using
>> the
>> >>>> first one. Adjust the configuration file filtering options to
select
>> a
>> >>>> single track.
>> >>>>
>> >>>> WARNING:
>> >>>>
>> >>>> DEBUG 2: Writing 45 track lines.
>> >>>>
>> >>>> DEBUG 2: Processing 1 track consisting of 43 points.
>> >>>>
>> >>>> WARNING:
>> >>>>
>> >>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
>> for
>> >>>> 'PRMSL/L0'
>> >>>>
>> >>>> WARNING:
>> >>>>
>> >>>> ERROR :
>> >>>>
>> >>>> ERROR : get_series_entry() -> Could not find data for
PRMSL/L0 in
>> >> file:
>> >>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> >>>>
>> >>>> ERROR :
>> >>>>
>> >>>>
>> >>>> Here is a snapshot of the data inventory of the grib2 data
using
>> >> wgrib2:
>> >>>>
>> >>>> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
>> >>>>
>> >>>> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as a
single
>> >>>> layer):36 hour fcst:
>> >>>>
>> >>>> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
>> >>>>
>> >>>> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
>> >>>>
>> >>>> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
>> >>>>
>> >>>> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
>> >>>>
>> >>>> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
>> >>>>
>> >>>> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
>> >>>>
>> >>>> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
>> >>>>
>> >>>> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
>> >>>>
>> >>>> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
>> >>>>
>> >>>> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
>> >>>>
>> >>>> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
>> >>>>
>> >>>> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
>> >>>>
>> >>>> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
>> >>>>
>> >>>> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
>> >>>>
>> >>>> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
>> >>>>
>> >>>> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
>> >>>>
>> >>>> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
>> >>>>
>> >>>> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
>> >>>>
>> >>>> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
>> >>>>
>> >>>> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
>> >>>>
>> >>>> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
>> >>>>
>> >>>> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
>> >>>>
>> >>>> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
>> >>>>
>> >>>> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
>> >>>>
>> >>>> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
>> >>>>
>> >>>> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
>> >>>>
>> >>>> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
>> >>>>
>> >>>> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
>> >>>>
>> >>>> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
>> >>>>
>> >>>> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
>> >>>>
>> >>>> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
>> >>>>
>> >>>> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
>> >>>>
>> >>>> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
>> >>>>
>> >>>> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
>> >>>>
>> >>>> My question is how should I define "level" for PRMSL and UGRD?
Here
>> is
>> >> my
>> >>>> working directory on orion:
>> >>>>
>> >>>> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
>> >>>>
>> >>>>
>> >>>> Thanks,
>> >>>>
>> >>>> Man
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>>
>>
>>
>>
------------------------------------------------
Subject: level in tc_rmw configuration file
From: John Halley Gotway
Time: Mon Oct 26 16:43:18 2020
Man,
Ah, I realize that there are some helpful log messages at verbosity
level
3. Whenever a MET tool fails and you don't know why, it's always a
good
idea to rerun at higher verbosity and look for additional log
messages.
The default logging level of 2 can be changed using the "-v" command
line
option. For example, "-v 3" produces:
DEBUG 2: Processing 1 track consisting of 43 points.
DEBUG 3: [1 of 43] Processing track point valid at 20190912_120000
with
center (lat, lon) = (23.2, -74.6).
DEBUG 3: Processing series entry 1: UGRD/P500
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
'UGRD/P500'
WARNING:
So this prints the valid time and location of each track point being
processed.
Thanks,
John
On Mon, Oct 26, 2020 at 4:37 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
> Man,
>
> OK, great, I'm able to read those files now.
>
> I see that you're able to run plot_data_plane to read/plot the
UGRD/P500
> field. But when you run tc_rmw, it can't find a matching UGRD/P500
field.
>
> So tc_rmw is designed to...
> (1) Read a single input hurricane track.
> (2) Process each point of that track by looking for matching gridded
data
> FOR THE VALID time of each track point.
>
> The most likely explanation for the behavior you're seeing is a
mismatch
> in time between the track point and the gridded data you're passing
to the
> tool. And this is a relatively new tool, so it's very possible that
the log
> messages should be improved to point you in the right direction.
>
> I'm testing directly on hera in:
> /scratch1/BMC/dtc/John.H.Gotway/MET/MET_Help/zhang_data_20201026
>
> Loading the existing met-9.1 code:
>
>
>
>
> *module use -a /contrib/anaconda/modulefilesmodule load
> intel/18.0.5.274module load anaconda/latestmodule use -a
> /contrib/met/modulefiles/module load met/9.1*
>
> Confirmed that plot_data_plane works as you described and it does:
> *plot_data_plane
> _MET_TC/invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
UGRD_P500.ps
> 'name="UGRD"; level="P500";'*
>
> Replicating the tc_rmw behavior you saw:
> *tc_rmw -data
_MET_TC/invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
> -deck _MET_TC/invest09l.2019091212.trak.hafs.atcfunix.all -config
> TCRMWConfig*
>
> (1) Let's start with this warning:
> *WARNING: process_track_files() -> multiple tracks found (2)! Using
the
> first one. Adjust the configuration file filtering options to select
a
> single track.*
> Looking in the track file, I see lines for storm number 09 and 95,
but the
> track lines look to be duplicates. I resolved this warning by
picking a
> single one in the TCRMW config file like this:
> * cyclone_number = "09";*
>
> (2) And the next warning:
> *WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
> 'UGRD/P500'*
> Running at verbosity level 3 (-v 3), I see track points with valid
times
> of 20190912_12, 20190912_15, 20190912_18, and so on. But you're only
> providing gridded data for forecast hour 36.
> If you only want to process this single point, you need to subset
the
> track down by setting:
> * lead = [ "36" ];*
>
> And with these 2 changes, tc_rmw now runs on this data.
>
> I can see how we should improve the warning/error messages to give
the
> user more information about the times for which data cannot be
found.
>
> Hope that helps.
>
> John
>
> On Mon, Oct 26, 2020 at 4:04 PM John Halley Gotway <johnhg at ucar.edu>
> wrote:
>
>> Man,
>>
>> Looks like you need to chmod them recursively:
>>
>> [John.H.Gotway at hfe08 _MET_TC]$ ls -lah
>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>> total 2.2G
>> drwxr-sr-x 2 Man.Zhang gmtb 4.0K Oct 26 16:09 .
>> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
>> -rw-r----- 1 Man.Zhang gmtb 41K Oct 24 03:36 grb2.log
>> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 22:17 Humber.nc
>> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 03:12 Humberto.log
>> -rw-r----- 1 Man.Zhang gmtb 348K Oct 26 16:10 Humberto.nc
>> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:47
>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> -rw-r----- 1 Man.Zhang gmtb 23K Oct 24 02:20
>> invest09l.2019091212.trak.hafs.atcfunix.all
>> -rw-r----- 1 Man.Zhang gmtb 324 Oct 26 16:02 README.zhang
>> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:40 TCRMWConfig
>> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 02:24 TCRMWConfig_default
>> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:54 TCRMWConfig_nc
>> -rw-r----- 1 Man.Zhang gmtb 766K Oct 26 16:04 tmp.ps
>>
>> John
>>
>> On Mon, Oct 26, 2020 at 4:01 PM Man Zhang - NOAA Affiliate via RT <
>> met_help at ucar.edu> wrote:
>>
>>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>>
>>> Please try again. -M
>>> > On Oct 26, 2020, at 3:58 PM, John Halley Gotway via RT <
>>> met_help at ucar.edu> wrote:
>>> >
>>> > Man,
>>> >
>>> > Looks like there's permission problems with this data on Hera:
>>> >
>>> > [John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
>>> > /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
>>> > [John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
>>> > total 2.2G
>>> > drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
>>> > drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
>>> > drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
>>> > -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
>>> >
>>> > Can you please open up the permissions?
>>> >
>>> > Sorry it's taken so long. I had to reset my master password on
Hera and
>>> > that takes a few hours to complete.
>>> >
>>> > John
>>> >
>>> > On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via
RT <
>>> > met_help at ucar.edu> wrote:
>>> >
>>> >>
>>> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>> >>
>>> >> John,
>>> >> I moved the directory to Hera:
>>> >>
>>> >> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>>> >>
>>> >>
>>> >> I typed
>>> >>
>>> >> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>> >> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
>>> >>
>>> >> It can generate the plot as expected.
>>> >>
>>> >>
>>> >> However, as you can see, I define
>>> >>
>>> >> {
>>> >>
>>> >> name = "UGRD";
>>> >>
>>> >> level = ["P500"];
>>> >>
>>> >> },
>>> >>
>>> >> in TCRMWConfig, and type
>>> >>
>>> >>
>>> >> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
>>> >> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
>>> >> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig
-out
>>> >> Humberto.nc
>>> >>
>>> >> DEBUG 1: Config File Default:
>>> >> /contrib/met/9.1/share/met/config/TCRMWConfig_default
>>> >>
>>> >> DEBUG 1: Config File User: TCRMWConfig
>>> >>
>>> >> DEBUG 2: Found 2 variable/level fields requested in the
configuration
>>> file.
>>> >>
>>> >> DEBUG 2: Processing 1 track data file(s).
>>> >>
>>> >> DEBUG 1: Reading track file:
>>> invest09l.2019091212.trak.hafs.atcfunix.all
>>> >>
>>> >> WARNING:
>>> >>
>>> >> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
>>> >> first one. Adjust the configuration file filtering options to
select a
>>> >> single track.
>>> >>
>>> >> WARNING:
>>> >>
>>> >> DEBUG 2: Writing 45 track lines.
>>> >>
>>> >> DEBUG 2: Processing 1 track consisting of 43 points.
>>> >>
>>> >> WARNING:
>>> >>
>>> >> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
>>> for
>>> >> 'UGRD/P500'
>>> >>
>>> >> WARNING:
>>> >>
>>> >> ERROR :
>>> >>
>>> >> ERROR : get_series_entry() -> Could not find data for
UGRD/P500 in
>>> file:
>>> >> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>> >>
>>> >> ERROR :
>>> >>
>>> >> My question is how should I define the level and field name in
>>> TCRMWConfig
>>> >> file.
>>> >>
>>> >> Thanks,
>>> >> Man
>>> >>
>>> >>
>>> >> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
>>> >> met_help at ucar.edu>
>>> >> wrote:
>>> >>
>>> >>> Hi Man,
>>> >>>
>>> >>> I see you have a question about setting the level config
option for
>>> the
>>> >> MET
>>> >>> tools. Unfortunately, I'm not able to access Orion. Can you
please
>>> tar up
>>> >>> your sample data and post it to our anonymous ftp site
following
>>> these
>>> >>> instructions?
>>> >>>
>>> >>>
>>> >>>
>>> >>
>>> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>>> >>>
>>> >>> Or, if it's easier, copy it to cheyenne, hera, jet, or one of
the DTC
>>> >>> project machines at NCAR.
>>> >>>
>>> >>> Thanks,
>>> >>> John
>>> >>>
>>> >>> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via
RT <
>>> >>> met_help at ucar.edu> wrote:
>>> >>>
>>> >>>>
>>> >>>> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
>>> >>>> Transaction: Ticket created by man.zhang at noaa.gov
>>> >>>> Queue: met_help
>>> >>>> Subject: level in tc_rmw configuration file
>>> >>>> Owner: Nobody
>>> >>>> Requestors: man.zhang at noaa.gov
>>> >>>> Status: new
>>> >>>> Ticket <URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
>>> >>>
>>> >>>>
>>> >>>>
>>> >>>> Hello,
>>> >>>>
>>> >>>> I use the same level definition indicated in
>>> >>>> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
>>> >>>>
>>> >>>> field = [
>>> >>>>
>>> >>>> {
>>> >>>>
>>> >>>> name = "PRMSL";
>>> >>>>
>>> >>>> level = ["L0"];
>>> >>>>
>>> >>>> },
>>> >>>>
>>> >>>> {
>>> >>>>
>>> >>>> name = "TMP";
>>> >>>>
>>> >>>> level = ["P500"];
>>> >>>>
>>> >>>> },
>>> >>>>
>>> >>>> {
>>> >>>>
>>> >>>> name = "UGRD";
>>> >>>>
>>> >>>> level = ["P500"];
>>> >>>>
>>> >>>> },
>>> >>>>
>>> >>>> {
>>> >>>>
>>> >>>> name = "VGRD";
>>> >>>>
>>> >>>> level = ["P500"];
>>> >>>>
>>> >>>> }
>>> >>>>
>>> >>>> ];
>>> >>>> Then I run:
>>> >>>>
>>> >>>> tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>> -deck
>>> >>>> invest09l.2019091212.trak.hafs.atcfun
>>> >>>>
>>> >>>> ix.all -config TCRMWConfig -out Humber.nc
>>> >>>>
>>> >>>> I got :
>>> >>>>
>>> >>>> DEBUG 1: Config File Default:
>>> >>>> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
>>> >>>>
>>> >>>> DEBUG 1: Config File User: TCRMWConfig
>>> >>>>
>>> >>>> DEBUG 2: Found 4 variable/level fields requested in the
>>> configuration
>>> >>> file.
>>> >>>>
>>> >>>> DEBUG 2: Processing 1 track data file(s).
>>> >>>>
>>> >>>> DEBUG 1: Reading track file:
>>> >> invest09l.2019091212.trak.hafs.atcfunix.all
>>> >>>>
>>> >>>> WARNING:
>>> >>>>
>>> >>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using
>>> the
>>> >>>> first one. Adjust the configuration file filtering options to
>>> select a
>>> >>>> single track.
>>> >>>>
>>> >>>> WARNING:
>>> >>>>
>>> >>>> DEBUG 2: Writing 45 track lines.
>>> >>>>
>>> >>>> DEBUG 2: Processing 1 track consisting of 43 points.
>>> >>>>
>>> >>>> WARNING:
>>> >>>>
>>> >>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
>>> for
>>> >>>> 'PRMSL/L0'
>>> >>>>
>>> >>>> WARNING:
>>> >>>>
>>> >>>> ERROR :
>>> >>>>
>>> >>>> ERROR : get_series_entry() -> Could not find data for
PRMSL/L0 in
>>> >> file:
>>> >>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>> >>>>
>>> >>>> ERROR :
>>> >>>>
>>> >>>>
>>> >>>> Here is a snapshot of the data inventory of the grib2 data
using
>>> >> wgrib2:
>>> >>>>
>>> >>>> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
>>> >>>>
>>> >>>> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as
a
>>> single
>>> >>>> layer):36 hour fcst:
>>> >>>>
>>> >>>> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
>>> >>>>
>>> >>>> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
>>> >>>>
>>> >>>> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
>>> >>>>
>>> >>>> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
>>> >>>>
>>> >>>> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
>>> >>>>
>>> >>>> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
>>> >>>>
>>> >>>> My question is how should I define "level" for PRMSL and
UGRD? Here
>>> is
>>> >> my
>>> >>>> working directory on orion:
>>> >>>>
>>> >>>> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
>>> >>>>
>>> >>>>
>>> >>>> Thanks,
>>> >>>>
>>> >>>> Man
>>> >>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >
>>>
>>>
>>>
>>>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #97213] level in tc_rmw configuration file
From: Man Zhang - NOAA Affiliate
Time: Mon Oct 26 17:05:09 2020
Mystery solved!
Thanks for providing a handy TC analysis tool!
Man
> On Oct 26, 2020, at 4:43 PM, John Halley Gotway via RT
<met_help at ucar.edu> wrote:
>
> Man,
>
> Ah, I realize that there are some helpful log messages at verbosity
level
> 3. Whenever a MET tool fails and you don't know why, it's always a
good
> idea to rerun at higher verbosity and look for additional log
messages.
> The default logging level of 2 can be changed using the "-v" command
line
> option. For example, "-v 3" produces:
>
> DEBUG 2: Processing 1 track consisting of 43 points.
> DEBUG 3: [1 of 43] Processing track point valid at 20190912_120000
with
> center (lat, lon) = (23.2, -74.6).
> DEBUG 3: Processing series entry 1: UGRD/P500
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() -> No matching record found
for
> 'UGRD/P500'
> WARNING:
>
> So this prints the valid time and location of each track point being
> processed.
>
> Thanks,
> John
>
> On Mon, Oct 26, 2020 at 4:37 PM John Halley Gotway <johnhg at ucar.edu>
wrote:
>
>> Man,
>>
>> OK, great, I'm able to read those files now.
>>
>> I see that you're able to run plot_data_plane to read/plot the
UGRD/P500
>> field. But when you run tc_rmw, it can't find a matching UGRD/P500
field.
>>
>> So tc_rmw is designed to...
>> (1) Read a single input hurricane track.
>> (2) Process each point of that track by looking for matching
gridded data
>> FOR THE VALID time of each track point.
>>
>> The most likely explanation for the behavior you're seeing is a
mismatch
>> in time between the track point and the gridded data you're passing
to the
>> tool. And this is a relatively new tool, so it's very possible that
the log
>> messages should be improved to point you in the right direction.
>>
>> I'm testing directly on hera in:
>> /scratch1/BMC/dtc/John.H.Gotway/MET/MET_Help/zhang_data_20201026
>>
>> Loading the existing met-9.1 code:
>>
>>
>>
>>
>> *module use -a /contrib/anaconda/modulefilesmodule load
>> intel/18.0.5.274module load anaconda/latestmodule use -a
>> /contrib/met/modulefiles/module load met/9.1*
>>
>> Confirmed that plot_data_plane works as you described and it does:
>> *plot_data_plane
>> _MET_TC/invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
UGRD_P500.ps
>> 'name="UGRD"; level="P500";'*
>>
>> Replicating the tc_rmw behavior you saw:
>> *tc_rmw -data
_MET_TC/invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>> -deck _MET_TC/invest09l.2019091212.trak.hafs.atcfunix.all -config
>> TCRMWConfig*
>>
>> (1) Let's start with this warning:
>> *WARNING: process_track_files() -> multiple tracks found (2)! Using
the
>> first one. Adjust the configuration file filtering options to
select a
>> single track.*
>> Looking in the track file, I see lines for storm number 09 and 95,
but the
>> track lines look to be duplicates. I resolved this warning by
picking a
>> single one in the TCRMW config file like this:
>> * cyclone_number = "09";*
>>
>> (2) And the next warning:
>> *WARNING: MetGrib2DataFile::data_plane() -> No matching record
found for
>> 'UGRD/P500'*
>> Running at verbosity level 3 (-v 3), I see track points with valid
times
>> of 20190912_12, 20190912_15, 20190912_18, and so on. But you're
only
>> providing gridded data for forecast hour 36.
>> If you only want to process this single point, you need to subset
the
>> track down by setting:
>> * lead = [ "36" ];*
>>
>> And with these 2 changes, tc_rmw now runs on this data.
>>
>> I can see how we should improve the warning/error messages to give
the
>> user more information about the times for which data cannot be
found.
>>
>> Hope that helps.
>>
>> John
>>
>> On Mon, Oct 26, 2020 at 4:04 PM John Halley Gotway
<johnhg at ucar.edu>
>> wrote:
>>
>>> Man,
>>>
>>> Looks like you need to chmod them recursively:
>>>
>>> [John.H.Gotway at hfe08 _MET_TC]$ ls -lah
>>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>>> total 2.2G
>>> drwxr-sr-x 2 Man.Zhang gmtb 4.0K Oct 26 16:09 .
>>> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
>>> -rw-r----- 1 Man.Zhang gmtb 41K Oct 24 03:36 grb2.log
>>> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 22:17 Humber.nc
>>> -rw-r----- 1 Man.Zhang gmtb 349K Oct 24 03:12 Humberto.log
>>> -rw-r----- 1 Man.Zhang gmtb 348K Oct 26 16:10 Humberto.nc
>>> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:47
>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>> -rw-r----- 1 Man.Zhang gmtb 23K Oct 24 02:20
>>> invest09l.2019091212.trak.hafs.atcfunix.all
>>> -rw-r----- 1 Man.Zhang gmtb 324 Oct 26 16:02 README.zhang
>>> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:40 TCRMWConfig
>>> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 02:24 TCRMWConfig_default
>>> -rw-r----- 1 Man.Zhang gmtb 1.7K Oct 24 22:54 TCRMWConfig_nc
>>> -rw-r----- 1 Man.Zhang gmtb 766K Oct 26 16:04 tmp.ps
>>>
>>> John
>>>
>>> On Mon, Oct 26, 2020 at 4:01 PM Man Zhang - NOAA Affiliate via RT
<
>>> met_help at ucar.edu> wrote:
>>>
>>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>>>
>>>> Please try again. -M
>>>>> On Oct 26, 2020, at 3:58 PM, John Halley Gotway via RT <
>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>> Man,
>>>>>
>>>>> Looks like there's permission problems with this data on Hera:
>>>>>
>>>>> [John.H.Gotway at hfe08 _MET_tc_rmw]$ pwd
>>>>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw
>>>>> [John.H.Gotway at hfe08 _MET_tc_rmw]$ ls -lah
>>>>> total 2.2G
>>>>> drwxr-sr-x 3 Man.Zhang gmtb 4.0K Oct 26 15:59 .
>>>>> drwxr-sr-x 45 Man.Zhang gmtb 4.0K Oct 26 15:59 ..
>>>>> drwxr-s--- 2 Man.Zhang gmtb 4.0K Oct 26 16:09 _MET_TC
>>>>> -rw-r----- 1 Man.Zhang gmtb 2.2G Oct 26 15:56 TC_RMW.tar
>>>>>
>>>>> Can you please open up the permissions?
>>>>>
>>>>> Sorry it's taken so long. I had to reset my master password on
Hera and
>>>>> that takes a few hours to complete.
>>>>>
>>>>> John
>>>>>
>>>>> On Mon, Oct 26, 2020 at 10:15 AM Man Zhang - NOAA Affiliate via
RT <
>>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213 >
>>>>>>
>>>>>> John,
>>>>>> I moved the directory to Hera:
>>>>>>
>>>>>> /scratch1/BMC/gmtb/Man.Zhang/_MET_tc_rmw/_MET_TC
>>>>>>
>>>>>>
>>>>>> I typed
>>>>>>
>>>>>> *plot_data_plane
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>>>> tmp.ps <http://tmp.ps> 'name="UGRD"; level="P500";'*
>>>>>>
>>>>>> It can generate the plot as expected.
>>>>>>
>>>>>>
>>>>>> However, as you can see, I define
>>>>>>
>>>>>> {
>>>>>>
>>>>>> name = "UGRD";
>>>>>>
>>>>>> level = ["P500"];
>>>>>>
>>>>>> },
>>>>>>
>>>>>> in TCRMWConfig, and type
>>>>>>
>>>>>>
>>>>>> [Man.Zhang at hfe02 _MET_TC]$ tc_rmw -data
>>>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2 -deck
>>>>>> invest09l.2019091212.trak.hafs.atcfunix.all -config TCRMWConfig
-out
>>>>>> Humberto.nc
>>>>>>
>>>>>> DEBUG 1: Config File Default:
>>>>>> /contrib/met/9.1/share/met/config/TCRMWConfig_default
>>>>>>
>>>>>> DEBUG 1: Config File User: TCRMWConfig
>>>>>>
>>>>>> DEBUG 2: Found 2 variable/level fields requested in the
configuration
>>>> file.
>>>>>>
>>>>>> DEBUG 2: Processing 1 track data file(s).
>>>>>>
>>>>>> DEBUG 1: Reading track file:
>>>> invest09l.2019091212.trak.hafs.atcfunix.all
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using the
>>>>>> first one. Adjust the configuration file filtering options to
select a
>>>>>> single track.
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> DEBUG 2: Writing 45 track lines.
>>>>>>
>>>>>> DEBUG 2: Processing 1 track consisting of 43 points.
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
>>>> for
>>>>>> 'UGRD/P500'
>>>>>>
>>>>>> WARNING:
>>>>>>
>>>>>> ERROR :
>>>>>>
>>>>>> ERROR : get_series_entry() -> Could not find data for
UGRD/P500 in
>>>> file:
>>>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>>>>
>>>>>> ERROR :
>>>>>>
>>>>>> My question is how should I define the level and field name in
>>>> TCRMWConfig
>>>>>> file.
>>>>>>
>>>>>> Thanks,
>>>>>> Man
>>>>>>
>>>>>>
>>>>>> On Mon, Oct 26, 2020 at 9:46 AM John Halley Gotway via RT <
>>>>>> met_help at ucar.edu>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Man,
>>>>>>>
>>>>>>> I see you have a question about setting the level config
option for
>>>> the
>>>>>> MET
>>>>>>> tools. Unfortunately, I'm not able to access Orion. Can you
please
>>>> tar up
>>>>>>> your sample data and post it to our anonymous ftp site
following
>>>> these
>>>>>>> instructions?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>> http://www.dtcenter.org/community-code/model-evaluation-tools-
met/met-help-desk#ftp
>>>>>>>
>>>>>>> Or, if it's easier, copy it to cheyenne, hera, jet, or one of
the DTC
>>>>>>> project machines at NCAR.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>> On Fri, Oct 23, 2020 at 9:55 PM Man Zhang - NOAA Affiliate via
RT <
>>>>>>> met_help at ucar.edu> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> Fri Oct 23 21:55:00 2020: Request 97213 was acted upon.
>>>>>>>> Transaction: Ticket created by man.zhang at noaa.gov
>>>>>>>> Queue: met_help
>>>>>>>> Subject: level in tc_rmw configuration file
>>>>>>>> Owner: Nobody
>>>>>>>> Requestors: man.zhang at noaa.gov
>>>>>>>> Status: new
>>>>>>>> Ticket <URL:
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=97213
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I use the same level definition indicated in
>>>>>>>> https://dtcenter.github.io/MET/latest/Users_Guide/tc-rmw.html
>>>>>>>>
>>>>>>>> field = [
>>>>>>>>
>>>>>>>> {
>>>>>>>>
>>>>>>>> name = "PRMSL";
>>>>>>>>
>>>>>>>> level = ["L0"];
>>>>>>>>
>>>>>>>> },
>>>>>>>>
>>>>>>>> {
>>>>>>>>
>>>>>>>> name = "TMP";
>>>>>>>>
>>>>>>>> level = ["P500"];
>>>>>>>>
>>>>>>>> },
>>>>>>>>
>>>>>>>> {
>>>>>>>>
>>>>>>>> name = "UGRD";
>>>>>>>>
>>>>>>>> level = ["P500"];
>>>>>>>>
>>>>>>>> },
>>>>>>>>
>>>>>>>> {
>>>>>>>>
>>>>>>>> name = "VGRD";
>>>>>>>>
>>>>>>>> level = ["P500"];
>>>>>>>>
>>>>>>>> }
>>>>>>>>
>>>>>>>> ];
>>>>>>>> Then I run:
>>>>>>>>
>>>>>>>> tc_rmw -data
invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>> -deck
>>>>>>>> invest09l.2019091212.trak.hafs.atcfun
>>>>>>>>
>>>>>>>> ix.all -config TCRMWConfig -out Humber.nc
>>>>>>>>
>>>>>>>> I got :
>>>>>>>>
>>>>>>>> DEBUG 1: Config File Default:
>>>>>>>> /apps/contrib/MET/9.1/share/met/config/TCRMWConfig_default
>>>>>>>>
>>>>>>>> DEBUG 1: Config File User: TCRMWConfig
>>>>>>>>
>>>>>>>> DEBUG 2: Found 4 variable/level fields requested in the
>>>> configuration
>>>>>>> file.
>>>>>>>>
>>>>>>>> DEBUG 2: Processing 1 track data file(s).
>>>>>>>>
>>>>>>>> DEBUG 1: Reading track file:
>>>>>> invest09l.2019091212.trak.hafs.atcfunix.all
>>>>>>>>
>>>>>>>> WARNING:
>>>>>>>>
>>>>>>>> WARNING: process_track_files() -> multiple tracks found (2)!
Using
>>>> the
>>>>>>>> first one. Adjust the configuration file filtering options to
>>>> select a
>>>>>>>> single track.
>>>>>>>>
>>>>>>>> WARNING:
>>>>>>>>
>>>>>>>> DEBUG 2: Writing 45 track lines.
>>>>>>>>
>>>>>>>> DEBUG 2: Processing 1 track consisting of 43 points.
>>>>>>>>
>>>>>>>> WARNING:
>>>>>>>>
>>>>>>>> WARNING: MetGrib2DataFile::data_plane() -> No matching record
found
>>>> for
>>>>>>>> 'PRMSL/L0'
>>>>>>>>
>>>>>>>> WARNING:
>>>>>>>>
>>>>>>>> ERROR :
>>>>>>>>
>>>>>>>> ERROR : get_series_entry() -> Could not find data for
PRMSL/L0 in
>>>>>> file:
>>>>>>>> invest09l.2019091212.hafsprs.synoptic.0p03.f036.grb2
>>>>>>>>
>>>>>>>> ERROR :
>>>>>>>>
>>>>>>>>
>>>>>>>> Here is a snapshot of the data inventory of the grib2 data
using
>>>>>> wgrib2:
>>>>>>>>
>>>>>>>> 1:0:d=2019091212:PRMSL:mean sea level:36 hour fcst:
>>>>>>>>
>>>>>>>> 2:6210615:d=2019091212:REFC:entire atmosphere (considered as
a
>>>> single
>>>>>>>> layer):36 hour fcst:
>>>>>>>>
>>>>>>>> 3:9010808:d=2019091212:GUST:surface:36 hour fcst:
>>>>>>>>
>>>>>>>> 4:12639832:d=2019091212:HGT:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 5:18014232:d=2019091212:TMP:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 6:20636342:d=2019091212:RH:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 7:22178191:d=2019091212:SPFH:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 8:26172867:d=2019091212:VVEL:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 9:32567349:d=2019091212:DZDT:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 10:35363237:d=2019091212:UGRD:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 11:39240443:d=2019091212:VGRD:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 12:42913833:d=2019091212:ABSV:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 13:46958726:d=2019091212:TKE:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 14:46958905:d=2019091212:CLMR:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 15:47834800:d=2019091212:ICMR:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 16:48710695:d=2019091212:RWMR:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 17:50888282:d=2019091212:SNMR:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 18:53727261:d=2019091212:REFD:2 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 19:53858625:d=2019091212:HGT:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 20:59282005:d=2019091212:TMP:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 21:61969946:d=2019091212:RH:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 22:63938944:d=2019091212:SPFH:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 23:68113688:d=2019091212:VVEL:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 24:75059398:d=2019091212:DZDT:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 25:77928184:d=2019091212:UGRD:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 26:82331881:d=2019091212:VGRD:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 27:86244994:d=2019091212:ABSV:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 28:90270813:d=2019091212:TKE:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 29:90270992:d=2019091212:CLMR:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 30:91146887:d=2019091212:ICMR:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 31:92022782:d=2019091212:RWMR:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 32:93750263:d=2019091212:SNMR:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 33:95805597:d=2019091212:REFD:5 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 34:95928062:d=2019091212:HGT:7 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 35:101431227:d=2019091212:TMP:7 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> 36:104042177:d=2019091212:RH:7 mb:36 hour fcst:
>>>>>>>>
>>>>>>>> My question is how should I define "level" for PRMSL and
UGRD? Here
>>>> is
>>>>>> my
>>>>>>>> working directory on orion:
>>>>>>>>
>>>>>>>> /work/noaa/hwrf/manzhang/_Humberto_2019091212/_MET_TC
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Man
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>
------------------------------------------------
More information about the Met_help
mailing list