[Met_help] [rt.rap.ucar.edu #90137] History for Ascii2NC
John Halley Gotway via RT
met_help at ucar.edu
Fri May 24 10:50:54 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I am trying to convert some HDF5 point observations. I have two HDF5 file
per date, one for radiosondes and another for surface obs. From your
ASCII2NC documentation, I see the following:
"
The input ASCII MET point observation format contains one observation per
line. Each input observation line should consist of the following 11 columns
of data:
1. Message_Type
2. Station_ID
3. Valid_Time in YYYYMMDD_HHMMSS format
4. Lat in degrees North
5. Lon in degrees East
6. Elevation in meters above sea level
7. Grib_Code as the integer GRIB code value or variable name
corresponding to this observation type
8. Level as the pressure level in hPa or accumulation interval in hours
9. Height in meters above sea level or above ground level
10. QC_String corresponding to the quality control value
11. Observation_Value in the units prescribed for the grib code
In order to use ASCII2NC, it is the user's responsibility to get their ASCII
point observations into this format
"
I am a bit confused on #6-9. What is the difference between elevation,
level and height and how do I define these when I start to write the ascii
file for the surface obs? Also I am using
https://apps.ecmwf.int/codes/grib/param-db to find the Grib Codes. Is the
column entitled "Parameter ID" what MET uses to determine the variable?
Thanks,
Justin
Justin Tsu
Marine Meteorology Division
Data Assimilation/Mesoscale Modeling
Building 704 Room 212
Naval Research Laboratory, Code 7531
7 Grace Hopper Avenue
Monterey, CA 93943-5502
Ph. (831) 656-4111
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Ascii2NC
From: Howard Soh
Time: Wed May 08 18:25:18 2019
Column 1 to 6 are header information about a station or an equipment.
And column 7 to 11 are observation data.
column 6: the elevation of the station or the equipment (lat/lon/elv)
column 8: the pressure level associated with observation data
column 9: the height associated with observation data
column 8 and/or column 9 are the vertical information of the
observation data.
Cheers,
Howard
On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> Hi,
>
>
>
> I am trying to convert some HDF5 point observations. I have two
HDF5 file
> per date, one for radiosondes and another for surface obs. From
your
> ASCII2NC documentation, I see the following:
>
> "
>
> The input ASCII MET point observation format contains one
observation per
> line. Each input observation line should consist of the following 11
columns
> of data:
>
> 1. Message_Type
>
> 2. Station_ID
>
> 3. Valid_Time in YYYYMMDD_HHMMSS format
>
> 4. Lat in degrees North
>
> 5. Lon in degrees East
>
> 6. Elevation in meters above sea level
>
> 7. Grib_Code as the integer GRIB code value or variable name
> corresponding to this observation type
>
> 8. Level as the pressure level in hPa or accumulation interval
in hours
>
> 9. Height in meters above sea level or above ground level
>
> 10. QC_String corresponding to the quality control value
>
> 11. Observation_Value in the units prescribed for the grib code
>
> In order to use ASCII2NC, it is the user's responsibility to get
their ASCII
> point observations into this format
>
> "
>
> I am a bit confused on #6-9. What is the difference between
elevation,
> level and height and how do I define these when I start to write the
ascii
> file for the surface obs? Also I am using
> https://apps.ecmwf.int/codes/grib/param-db to find the Grib Codes.
Is the
> column entitled "Parameter ID" what MET uses to determine the
variable?
>
>
>
> Thanks,
>
> Justin
>
>
>
>
>
> Justin Tsu
>
> Marine Meteorology Division
>
> Data Assimilation/Mesoscale Modeling
>
> Building 704 Room 212
>
> Naval Research Laboratory, Code 7531
>
> 7 Grace Hopper Avenue
>
> Monterey, CA 93943-5502
>
>
>
> Ph. (831) 656-4111
>
>
>
------------------------------------------------
Subject: Ascii2NC
From: Tsu, Mr. Justin
Time: Wed May 08 18:31:26 2019
Thank you for clarifying column 6, 8, and 9. How do I define these
same
columns for surface observations? Would I just set these to surface
level (0
meter and 1013 hpa)? Also from my initial email:
I am using https://apps.ecmwf.int/codes/grib/param-db to find the Grib
Codes.
Is the column entitled "Parameter ID" what MET uses to determine the
variable?
Thanks,
Justin
-----Original Message-----
From: Howard Soh via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, May 8, 2019 5:25 PM
To: Tsu, Mr. Justin
Subject: [rt.rap.ucar.edu #90137] Ascii2NC
Column 1 to 6 are header information about a station or an equipment.
And
column 7 to 11 are observation data.
column 6: the elevation of the station or the equipment (lat/lon/elv)
column 8: the pressure level associated with observation data
column 9: the height associated with observation data
column 8 and/or column 9 are the vertical information of the
observation data.
Cheers,
Howard
On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> Hi,
>
>
>
> I am trying to convert some HDF5 point observations. I have two
HDF5 file
> per date, one for radiosondes and another for surface obs. From
your
> ASCII2NC documentation, I see the following:
>
> "
>
> The input ASCII MET point observation format contains one
observation per
> line. Each input observation line should consist of the following 11
columns
> of data:
>
> 1. Message_Type
>
> 2. Station_ID
>
> 3. Valid_Time in YYYYMMDD_HHMMSS format
>
> 4. Lat in degrees North
>
> 5. Lon in degrees East
>
> 6. Elevation in meters above sea level
>
> 7. Grib_Code as the integer GRIB code value or variable name
> corresponding to this observation type
>
> 8. Level as the pressure level in hPa or accumulation interval
in hours
>
> 9. Height in meters above sea level or above ground level
>
> 10. QC_String corresponding to the quality control value
>
> 11. Observation_Value in the units prescribed for the grib code
>
> In order to use ASCII2NC, it is the user's responsibility to get
their ASCII
> point observations into this format
>
> "
>
> I am a bit confused on #6-9. What is the difference between
elevation,
> level and height and how do I define these when I start to write the
ascii
> file for the surface obs? Also I am using
> https://apps.ecmwf.int/codes/grib/param-db to find the Grib Codes.
Is the
> column entitled "Parameter ID" what MET uses to determine the
variable?
>
>
>
> Thanks,
>
> Justin
>
>
>
>
>
> Justin Tsu
>
> Marine Meteorology Division
>
> Data Assimilation/Mesoscale Modeling
>
> Building 704 Room 212
>
> Naval Research Laboratory, Code 7531
>
> 7 Grace Hopper Avenue
>
> Monterey, CA 93943-5502
>
>
>
> Ph. (831) 656-4111
>
>
>
------------------------------------------------
Subject: Ascii2NC
From: Howard Soh
Time: Wed May 08 19:23:01 2019
The grib_code, variable id or variable name are associated with other
MET tools. There are some common grib codes but other grib codes could
have different names depending on the grib table. MET tool supports
variable names as alternative. The other MET tools can be configured
with variable names instead of the grib code.
It depends on how you use the ascii2nc output with other tools. The
height of the surface data is not the same. For example, 2m
temperature and 10m wind data. If you put the height 0 for 10m wind
data, other tools read it as 0m wind data. One consideration is the
characteristics of the pairing data. For example, the pairing gridded
data has pressure levels as vertical coordinate, column 8 data will be
more useful than column 9.
Cheers,
Howard
On Wed May 08 18:31:26 2019, justin.tsu at nrlmry.navy.mil wrote:
> Thank you for clarifying column 6, 8, and 9. How do I define these
> same
> columns for surface observations? Would I just set these to surface
> level (0
> meter and 1013 hpa)? Also from my initial email:
> I am using https://apps.ecmwf.int/codes/grib/param-db to find the
Grib
> Codes.
> Is the column entitled "Parameter ID" what MET uses to determine the
> variable?
>
> Thanks,
> Justin
> -----Original Message-----
> From: Howard Soh via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, May 8, 2019 5:25 PM
> To: Tsu, Mr. Justin
> Subject: [rt.rap.ucar.edu #90137] Ascii2NC
>
> Column 1 to 6 are header information about a station or an
equipment.
> And
> column 7 to 11 are observation data.
>
> column 6: the elevation of the station or the equipment
(lat/lon/elv)
> column 8: the pressure level associated with observation data
> column 9: the height associated with observation data
>
> column 8 and/or column 9 are the vertical information of the
> observation data.
>
>
> Cheers,
> Howard
>
> On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> > Hi,
> >
> >
> >
> > I am trying to convert some HDF5 point observations. I have two
HDF5
> > file
> > per date, one for radiosondes and another for surface obs. From
your
> > ASCII2NC documentation, I see the following:
> >
> > "
> >
> > The input ASCII MET point observation format contains one
observation
> > per
> > line. Each input observation line should consist of the following
11
> > columns
> > of data:
> >
> > 1. Message_Type
> >
> > 2. Station_ID
> >
> > 3. Valid_Time in YYYYMMDD_HHMMSS format
> >
> > 4. Lat in degrees North
> >
> > 5. Lon in degrees East
> >
> > 6. Elevation in meters above sea level
> >
> > 7. Grib_Code as the integer GRIB code value or variable name
> > corresponding to this observation type
> >
> > 8. Level as the pressure level in hPa or accumulation
interval
> > in hours
> >
> > 9. Height in meters above sea level or above ground level
> >
> > 10. QC_String corresponding to the quality control value
> >
> > 11. Observation_Value in the units prescribed for the grib code
> >
> > In order to use ASCII2NC, it is the user's responsibility to get
> > their ASCII
> > point observations into this format
> >
> > "
> >
> > I am a bit confused on #6-9. What is the difference between
> > elevation,
> > level and height and how do I define these when I start to write
the
> > ascii
> > file for the surface obs? Also I am using
> > https://apps.ecmwf.int/codes/grib/param-db to find the Grib Codes.
Is
> > the
> > column entitled "Parameter ID" what MET uses to determine the
> > variable?
> >
> >
> >
> > Thanks,
> >
> > Justin
> >
> >
> >
> >
> >
> > Justin Tsu
> >
> > Marine Meteorology Division
> >
> > Data Assimilation/Mesoscale Modeling
> >
> > Building 704 Room 212
> >
> > Naval Research Laboratory, Code 7531
> >
> > 7 Grace Hopper Avenue
> >
> > Monterey, CA 93943-5502
> >
> >
> >
> > Ph. (831) 656-4111
> >
> >
> >
------------------------------------------------
Subject: Ascii2NC
From: Tsu, Mr. Justin
Time: Thu May 09 11:10:31 2019
Thanks Howard,
Do you have a reference for how MET defines variable names? I am aware
that
NRL probably defines variable names differently than other
meteorological
communities do.
Justin
-----Original Message-----
From: Howard Soh via RT [mailto:met_help at ucar.edu]
Sent: Wednesday, May 8, 2019 6:23 PM
To: Tsu, Mr. Justin
Subject: [rt.rap.ucar.edu #90137] Ascii2NC
The grib_code, variable id or variable name are associated with other
MET
tools. There are some common grib codes but other grib codes could
have
different names depending on the grib table. MET tool supports
variable names
as alternative. The other MET tools can be configured with variable
names
instead of the grib code.
It depends on how you use the ascii2nc output with other tools. The
height of
the surface data is not the same. For example, 2m temperature and 10m
wind
data. If you put the height 0 for 10m wind data, other tools read it
as 0m
wind data. One consideration is the characteristics of the pairing
data. For
example, the pairing gridded data has pressure levels as vertical
coordinate,
column 8 data will be more useful than column 9.
Cheers,
Howard
On Wed May 08 18:31:26 2019, justin.tsu at nrlmry.navy.mil wrote:
> Thank you for clarifying column 6, 8, and 9. How do I define these
> same
> columns for surface observations? Would I just set these to surface
> level (0
> meter and 1013 hpa)? Also from my initial email:
> I am using https://apps.ecmwf.int/codes/grib/param-db to find the
Grib
> Codes.
> Is the column entitled "Parameter ID" what MET uses to determine the
> variable?
>
> Thanks,
> Justin
> -----Original Message-----
> From: Howard Soh via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, May 8, 2019 5:25 PM
> To: Tsu, Mr. Justin
> Subject: [rt.rap.ucar.edu #90137] Ascii2NC
>
> Column 1 to 6 are header information about a station or an
equipment.
> And
> column 7 to 11 are observation data.
>
> column 6: the elevation of the station or the equipment
(lat/lon/elv)
> column 8: the pressure level associated with observation data
> column 9: the height associated with observation data
>
> column 8 and/or column 9 are the vertical information of the
> observation data.
>
>
> Cheers,
> Howard
>
> On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> > Hi,
> >
> >
> >
> > I am trying to convert some HDF5 point observations. I have two
HDF5
> > file
> > per date, one for radiosondes and another for surface obs. From
your
> > ASCII2NC documentation, I see the following:
> >
> > "
> >
> > The input ASCII MET point observation format contains one
observation
> > per
> > line. Each input observation line should consist of the following
11
> > columns
> > of data:
> >
> > 1. Message_Type
> >
> > 2. Station_ID
> >
> > 3. Valid_Time in YYYYMMDD_HHMMSS format
> >
> > 4. Lat in degrees North
> >
> > 5. Lon in degrees East
> >
> > 6. Elevation in meters above sea level
> >
> > 7. Grib_Code as the integer GRIB code value or variable name
> > corresponding to this observation type
> >
> > 8. Level as the pressure level in hPa or accumulation
interval
> > in hours
> >
> > 9. Height in meters above sea level or above ground level
> >
> > 10. QC_String corresponding to the quality control value
> >
> > 11. Observation_Value in the units prescribed for the grib code
> >
> > In order to use ASCII2NC, it is the user's responsibility to get
> > their ASCII
> > point observations into this format
> >
> > "
> >
> > I am a bit confused on #6-9. What is the difference between
> > elevation,
> > level and height and how do I define these when I start to write
the
> > ascii
> > file for the surface obs? Also I am using
> > https://apps.ecmwf.int/codes/grib/param-db to find the Grib Codes.
Is
> > the
> > column entitled "Parameter ID" what MET uses to determine the
> > variable?
> >
> >
> >
> > Thanks,
> >
> > Justin
> >
> >
> >
> >
> >
> > Justin Tsu
> >
> > Marine Meteorology Division
> >
> > Data Assimilation/Mesoscale Modeling
> >
> > Building 704 Room 212
> >
> > Naval Research Laboratory, Code 7531
> >
> > 7 Grace Hopper Avenue
> >
> > Monterey, CA 93943-5502
> >
> >
> >
> > Ph. (831) 656-4111
> >
> >
> >
------------------------------------------------
Subject: Ascii2NC
From: John Halley Gotway
Time: Thu May 09 13:00:15 2019
Justin and George,
Just wanted to chime in on this ticket. Justin, you're welcome to
name the
observation variables however you'd like. MET does not enforce any
standards other than requiring that variable name contain no embedded
whitespace.
Let's say you have some forecast data named ABC, and you want to
compare
that to observations named XYZ. You can just set up the MET config
file to
account for that:
*fcst = {*
* field = [ { name = "ABC"; level = "P500";' } ];*
*}*
*obs = {*
* field = [ { name = "XYZ"; level = "P500"; } ];*
*}*
If both your forecast and observation use the same name, it just makes
the
config file slightly easier since you can use the following short-
hand:
*obs = fcst;*
But handling different naming conventions is done in the MET config
files. Hope
this helps.
Thanks,
John
On Thu, May 9, 2019 at 11:10 AM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90137 >
>
> Thanks Howard,
>
> Do you have a reference for how MET defines variable names? I am
aware
> that
> NRL probably defines variable names differently than other
meteorological
> communities do.
>
> Justin
>
> -----Original Message-----
> From: Howard Soh via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, May 8, 2019 6:23 PM
> To: Tsu, Mr. Justin
> Subject: [rt.rap.ucar.edu #90137] Ascii2NC
>
> The grib_code, variable id or variable name are associated with
other MET
> tools. There are some common grib codes but other grib codes could
have
> different names depending on the grib table. MET tool supports
variable
> names
> as alternative. The other MET tools can be configured with variable
names
> instead of the grib code.
>
> It depends on how you use the ascii2nc output with other tools. The
height
> of
> the surface data is not the same. For example, 2m temperature and
10m wind
> data. If you put the height 0 for 10m wind data, other tools read it
as 0m
> wind data. One consideration is the characteristics of the pairing
data.
> For
> example, the pairing gridded data has pressure levels as vertical
> coordinate,
> column 8 data will be more useful than column 9.
>
> Cheers,
> Howard
>
> On Wed May 08 18:31:26 2019, justin.tsu at nrlmry.navy.mil wrote:
> > Thank you for clarifying column 6, 8, and 9. How do I define
these
> > same
> > columns for surface observations? Would I just set these to
surface
> > level (0
> > meter and 1013 hpa)? Also from my initial email:
> > I am using https://apps.ecmwf.int/codes/grib/param-db to find the
Grib
> > Codes.
> > Is the column entitled "Parameter ID" what MET uses to determine
the
> > variable?
> >
> > Thanks,
> > Justin
> > -----Original Message-----
> > From: Howard Soh via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, May 8, 2019 5:25 PM
> > To: Tsu, Mr. Justin
> > Subject: [rt.rap.ucar.edu #90137] Ascii2NC
> >
> > Column 1 to 6 are header information about a station or an
equipment.
> > And
> > column 7 to 11 are observation data.
> >
> > column 6: the elevation of the station or the equipment
(lat/lon/elv)
> > column 8: the pressure level associated with observation data
> > column 9: the height associated with observation data
> >
> > column 8 and/or column 9 are the vertical information of the
> > observation data.
> >
> >
> > Cheers,
> > Howard
> >
> > On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> > > Hi,
> > >
> > >
> > >
> > > I am trying to convert some HDF5 point observations. I have two
HDF5
> > > file
> > > per date, one for radiosondes and another for surface obs. From
your
> > > ASCII2NC documentation, I see the following:
> > >
> > > "
> > >
> > > The input ASCII MET point observation format contains one
observation
> > > per
> > > line. Each input observation line should consist of the
following 11
> > > columns
> > > of data:
> > >
> > > 1. Message_Type
> > >
> > > 2. Station_ID
> > >
> > > 3. Valid_Time in YYYYMMDD_HHMMSS format
> > >
> > > 4. Lat in degrees North
> > >
> > > 5. Lon in degrees East
> > >
> > > 6. Elevation in meters above sea level
> > >
> > > 7. Grib_Code as the integer GRIB code value or variable
name
> > > corresponding to this observation type
> > >
> > > 8. Level as the pressure level in hPa or accumulation
interval
> > > in hours
> > >
> > > 9. Height in meters above sea level or above ground level
> > >
> > > 10. QC_String corresponding to the quality control value
> > >
> > > 11. Observation_Value in the units prescribed for the grib
code
> > >
> > > In order to use ASCII2NC, it is the user's responsibility to get
> > > their ASCII
> > > point observations into this format
> > >
> > > "
> > >
> > > I am a bit confused on #6-9. What is the difference between
> > > elevation,
> > > level and height and how do I define these when I start to write
the
> > > ascii
> > > file for the surface obs? Also I am using
> > > https://apps.ecmwf.int/codes/grib/param-db to find the Grib
Codes. Is
> > > the
> > > column entitled "Parameter ID" what MET uses to determine the
> > > variable?
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Justin
> > >
> > >
> > >
> > >
> > >
> > > Justin Tsu
> > >
> > > Marine Meteorology Division
> > >
> > > Data Assimilation/Mesoscale Modeling
> > >
> > > Building 704 Room 212
> > >
> > > Naval Research Laboratory, Code 7531
> > >
> > > 7 Grace Hopper Avenue
> > >
> > > Monterey, CA 93943-5502
> > >
> > >
> > >
> > > Ph. (831) 656-4111
> > >
> > >
> > >
>
>
>
>
>
------------------------------------------------
Subject: Ascii2NC
From: Tsu, Mr. Justin
Time: Mon May 13 16:52:25 2019
Thanks John,
Ive got my forecast field in the form of a grib file entitled
GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
This is the U Component of wind at 1000 mb. My ob file is in a netcdf
file
created using ascii2nc. I named wind speed obs "ws" in the ascii file
that I
ran the ascii2nc tool on ( I am aware that I am trying to compare Wind
speed
and u component of wind, but I just want to see if I can get
point_stat
working).
How should I arrange my fcst and obs arrays? Here is what I have so
far:
52 fcst = {
53 field = [
54 {
55 name = "U";
56 level = "P1000";
57 file_type = GRIB2;
58 cat_thresh = [ >80.0 ];
59 }
60 ];
61
62 }
63
64 obs = {
65 field = [
66 {
67 file_type = NETCDF_NCCF;
68 name = "UGRD";
69 level = ["P1000"];
70 }
71 ];
72 }
Running the command as follows gives me this error:
[tsu at maury2 00_POINT_STAT_WORK]$ point_stat
GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
NAF_sfc_2019042612.nc config.rc -v 1
DEBUG 1: Default Config File:
/software/depot/met/met-
8.0_bugfix/share/met/config/PointStatConfig_default
DEBUG 1: User Config File: config.rc
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=1726142812
DEBUG 1: Forecast File:
GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
DEBUG 1: Observation File: NAF_sfc_2019042612.nc
WARNING:
WARNING: process_fcst_climo_files() -> no fields matching U/P1000
found in
file:
GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
WARNING:
ERROR :
ERROR : process_fcst_climo_files() -> no requested forecast data
found!
Exiting...
ERROR :
Justin
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, May 9, 2019 12:00 PM
To: Tsu, Mr. Justin
Subject: Re: [rt.rap.ucar.edu #90137] Ascii2NC
Justin and George,
Just wanted to chime in on this ticket. Justin, you're welcome to
name the
observation variables however you'd like. MET does not enforce any
standards other than requiring that variable name contain no embedded
whitespace.
Let's say you have some forecast data named ABC, and you want to
compare
that to observations named XYZ. You can just set up the MET config
file to
account for that:
*fcst = {*
* field = [ { name = "ABC"; level = "P500";' } ];*
*}*
*obs = {*
* field = [ { name = "XYZ"; level = "P500"; } ];*
*}*
If both your forecast and observation use the same name, it just makes
the
config file slightly easier since you can use the following short-
hand:
*obs = fcst;*
But handling different naming conventions is done in the MET config
files. Hope
this helps.
Thanks,
John
On Thu, May 9, 2019 at 11:10 AM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90137 >
>
> Thanks Howard,
>
> Do you have a reference for how MET defines variable names? I am
aware
> that
> NRL probably defines variable names differently than other
meteorological
> communities do.
>
> Justin
>
> -----Original Message-----
> From: Howard Soh via RT [mailto:met_help at ucar.edu]
> Sent: Wednesday, May 8, 2019 6:23 PM
> To: Tsu, Mr. Justin
> Subject: [rt.rap.ucar.edu #90137] Ascii2NC
>
> The grib_code, variable id or variable name are associated with
other MET
> tools. There are some common grib codes but other grib codes could
have
> different names depending on the grib table. MET tool supports
variable
> names
> as alternative. The other MET tools can be configured with variable
names
> instead of the grib code.
>
> It depends on how you use the ascii2nc output with other tools. The
height
> of
> the surface data is not the same. For example, 2m temperature and
10m wind
> data. If you put the height 0 for 10m wind data, other tools read it
as 0m
> wind data. One consideration is the characteristics of the pairing
data.
> For
> example, the pairing gridded data has pressure levels as vertical
> coordinate,
> column 8 data will be more useful than column 9.
>
> Cheers,
> Howard
>
> On Wed May 08 18:31:26 2019, justin.tsu at nrlmry.navy.mil wrote:
> > Thank you for clarifying column 6, 8, and 9. How do I define
these
> > same
> > columns for surface observations? Would I just set these to
surface
> > level (0
> > meter and 1013 hpa)? Also from my initial email:
> > I am using https://apps.ecmwf.int/codes/grib/param-db to find the
Grib
> > Codes.
> > Is the column entitled "Parameter ID" what MET uses to determine
the
> > variable?
> >
> > Thanks,
> > Justin
> > -----Original Message-----
> > From: Howard Soh via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, May 8, 2019 5:25 PM
> > To: Tsu, Mr. Justin
> > Subject: [rt.rap.ucar.edu #90137] Ascii2NC
> >
> > Column 1 to 6 are header information about a station or an
equipment.
> > And
> > column 7 to 11 are observation data.
> >
> > column 6: the elevation of the station or the equipment
(lat/lon/elv)
> > column 8: the pressure level associated with observation data
> > column 9: the height associated with observation data
> >
> > column 8 and/or column 9 are the vertical information of the
> > observation data.
> >
> >
> > Cheers,
> > Howard
> >
> > On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> > > Hi,
> > >
> > >
> > >
> > > I am trying to convert some HDF5 point observations. I have two
HDF5
> > > file
> > > per date, one for radiosondes and another for surface obs. From
your
> > > ASCII2NC documentation, I see the following:
> > >
> > > "
> > >
> > > The input ASCII MET point observation format contains one
observation
> > > per
> > > line. Each input observation line should consist of the
following 11
> > > columns
> > > of data:
> > >
> > > 1. Message_Type
> > >
> > > 2. Station_ID
> > >
> > > 3. Valid_Time in YYYYMMDD_HHMMSS format
> > >
> > > 4. Lat in degrees North
> > >
> > > 5. Lon in degrees East
> > >
> > > 6. Elevation in meters above sea level
> > >
> > > 7. Grib_Code as the integer GRIB code value or variable
name
> > > corresponding to this observation type
> > >
> > > 8. Level as the pressure level in hPa or accumulation
interval
> > > in hours
> > >
> > > 9. Height in meters above sea level or above ground level
> > >
> > > 10. QC_String corresponding to the quality control value
> > >
> > > 11. Observation_Value in the units prescribed for the grib
code
> > >
> > > In order to use ASCII2NC, it is the user's responsibility to get
> > > their ASCII
> > > point observations into this format
> > >
> > > "
> > >
> > > I am a bit confused on #6-9. What is the difference between
> > > elevation,
> > > level and height and how do I define these when I start to write
the
> > > ascii
> > > file for the surface obs? Also I am using
> > > https://apps.ecmwf.int/codes/grib/param-db to find the Grib
Codes. Is
> > > the
> > > column entitled "Parameter ID" what MET uses to determine the
> > > variable?
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Justin
> > >
> > >
> > >
> > >
> > >
> > > Justin Tsu
> > >
> > > Marine Meteorology Division
> > >
> > > Data Assimilation/Mesoscale Modeling
> > >
> > > Building 704 Room 212
> > >
> > > Naval Research Laboratory, Code 7531
> > >
> > > 7 Grace Hopper Avenue
> > >
> > > Monterey, CA 93943-5502
> > >
> > >
> > >
> > > Ph. (831) 656-4111
> > >
> > >
> > >
>
>
>
>
>
------------------------------------------------
Subject: Ascii2NC
From: John Halley Gotway
Time: Fri May 24 10:43:58 2019
Hi Justin,
I'm just following up on old met-help tickets. I'm guessing that this
is
no longer an issue since I believe we addressed it on another ticket.
But
I wanted to double-check with you before closing it.
Thanks,
John
On Mon, May 13, 2019 at 4:52 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90137 >
>
> Thanks John,
>
> Ive got my forecast field in the form of a grib file entitled
>
>
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
>
> This is the U Component of wind at 1000 mb. My ob file is in a
netcdf
> file
> created using ascii2nc. I named wind speed obs "ws" in the ascii
file
> that I
> ran the ascii2nc tool on ( I am aware that I am trying to compare
Wind
> speed
> and u component of wind, but I just want to see if I can get
point_stat
> working).
>
> How should I arrange my fcst and obs arrays? Here is what I have
so far:
>
> 52 fcst = {
> 53 field = [
> 54 {
> 55 name = "U";
> 56 level = "P1000";
> 57 file_type = GRIB2;
> 58 cat_thresh = [ >80.0 ];
> 59 }
> 60 ];
> 61
> 62 }
> 63
> 64 obs = {
> 65 field = [
> 66 {
> 67 file_type = NETCDF_NCCF;
> 68 name = "UGRD";
> 69 level = ["P1000"];
> 70 }
> 71 ];
> 72 }
>
> Running the command as follows gives me this error:
>
> [tsu at maury2 00_POINT_STAT_WORK]$ point_stat
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
>
> NAF_sfc_2019042612.nc config.rc -v 1
> DEBUG 1: Default Config File:
> /software/depot/met/met-
8.0_bugfix/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File: config.rc
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1726142812
> DEBUG 1: Forecast File:
>
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
> DEBUG 1: Observation File: NAF_sfc_2019042612.nc
> WARNING:
> WARNING: process_fcst_climo_files() -> no fields matching U/P1000
found in
> file:
>
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
> WARNING:
> ERROR :
> ERROR : process_fcst_climo_files() -> no requested forecast data
found!
> Exiting...
> ERROR :
>
> Justin
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, May 9, 2019 12:00 PM
> To: Tsu, Mr. Justin
> Subject: Re: [rt.rap.ucar.edu #90137] Ascii2NC
>
> Justin and George,
>
> Just wanted to chime in on this ticket. Justin, you're welcome to
name the
> observation variables however you'd like. MET does not enforce any
> standards other than requiring that variable name contain no
embedded
> whitespace.
>
> Let's say you have some forecast data named ABC, and you want to
compare
> that to observations named XYZ. You can just set up the MET config
file to
> account for that:
>
> *fcst = {*
> * field = [ { name = "ABC"; level = "P500";' } ];*
> *}*
> *obs = {*
> * field = [ { name = "XYZ"; level = "P500"; } ];*
> *}*
>
> If both your forecast and observation use the same name, it just
makes the
> config file slightly easier since you can use the following short-
hand:
>
> *obs = fcst;*
>
> But handling different naming conventions is done in the MET config
> files. Hope
> this helps.
>
> Thanks,
> John
>
> On Thu, May 9, 2019 at 11:10 AM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90137 >
> >
> > Thanks Howard,
> >
> > Do you have a reference for how MET defines variable names? I am
aware
> > that
> > NRL probably defines variable names differently than other
meteorological
> > communities do.
> >
> > Justin
> >
> > -----Original Message-----
> > From: Howard Soh via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, May 8, 2019 6:23 PM
> > To: Tsu, Mr. Justin
> > Subject: [rt.rap.ucar.edu #90137] Ascii2NC
> >
> > The grib_code, variable id or variable name are associated with
other MET
> > tools. There are some common grib codes but other grib codes could
have
> > different names depending on the grib table. MET tool supports
variable
> > names
> > as alternative. The other MET tools can be configured with
variable names
> > instead of the grib code.
> >
> > It depends on how you use the ascii2nc output with other tools.
The
> height
> > of
> > the surface data is not the same. For example, 2m temperature and
10m
> wind
> > data. If you put the height 0 for 10m wind data, other tools read
it as
> 0m
> > wind data. One consideration is the characteristics of the pairing
data.
> > For
> > example, the pairing gridded data has pressure levels as vertical
> > coordinate,
> > column 8 data will be more useful than column 9.
> >
> > Cheers,
> > Howard
> >
> > On Wed May 08 18:31:26 2019, justin.tsu at nrlmry.navy.mil wrote:
> > > Thank you for clarifying column 6, 8, and 9. How do I define
these
> > > same
> > > columns for surface observations? Would I just set these to
surface
> > > level (0
> > > meter and 1013 hpa)? Also from my initial email:
> > > I am using https://apps.ecmwf.int/codes/grib/param-db to find
the Grib
> > > Codes.
> > > Is the column entitled "Parameter ID" what MET uses to determine
the
> > > variable?
> > >
> > > Thanks,
> > > Justin
> > > -----Original Message-----
> > > From: Howard Soh via RT [mailto:met_help at ucar.edu]
> > > Sent: Wednesday, May 8, 2019 5:25 PM
> > > To: Tsu, Mr. Justin
> > > Subject: [rt.rap.ucar.edu #90137] Ascii2NC
> > >
> > > Column 1 to 6 are header information about a station or an
equipment.
> > > And
> > > column 7 to 11 are observation data.
> > >
> > > column 6: the elevation of the station or the equipment
(lat/lon/elv)
> > > column 8: the pressure level associated with observation data
> > > column 9: the height associated with observation data
> > >
> > > column 8 and/or column 9 are the vertical information of the
> > > observation data.
> > >
> > >
> > > Cheers,
> > > Howard
> > >
> > > On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> > > > Hi,
> > > >
> > > >
> > > >
> > > > I am trying to convert some HDF5 point observations. I have
two HDF5
> > > > file
> > > > per date, one for radiosondes and another for surface obs.
>From your
> > > > ASCII2NC documentation, I see the following:
> > > >
> > > > "
> > > >
> > > > The input ASCII MET point observation format contains one
observation
> > > > per
> > > > line. Each input observation line should consist of the
following 11
> > > > columns
> > > > of data:
> > > >
> > > > 1. Message_Type
> > > >
> > > > 2. Station_ID
> > > >
> > > > 3. Valid_Time in YYYYMMDD_HHMMSS format
> > > >
> > > > 4. Lat in degrees North
> > > >
> > > > 5. Lon in degrees East
> > > >
> > > > 6. Elevation in meters above sea level
> > > >
> > > > 7. Grib_Code as the integer GRIB code value or variable
name
> > > > corresponding to this observation type
> > > >
> > > > 8. Level as the pressure level in hPa or accumulation
interval
> > > > in hours
> > > >
> > > > 9. Height in meters above sea level or above ground level
> > > >
> > > > 10. QC_String corresponding to the quality control value
> > > >
> > > > 11. Observation_Value in the units prescribed for the grib
code
> > > >
> > > > In order to use ASCII2NC, it is the user's responsibility to
get
> > > > their ASCII
> > > > point observations into this format
> > > >
> > > > "
> > > >
> > > > I am a bit confused on #6-9. What is the difference between
> > > > elevation,
> > > > level and height and how do I define these when I start to
write the
> > > > ascii
> > > > file for the surface obs? Also I am using
> > > > https://apps.ecmwf.int/codes/grib/param-db to find the Grib
Codes.
> Is
> > > > the
> > > > column entitled "Parameter ID" what MET uses to determine the
> > > > variable?
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Justin
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Justin Tsu
> > > >
> > > > Marine Meteorology Division
> > > >
> > > > Data Assimilation/Mesoscale Modeling
> > > >
> > > > Building 704 Room 212
> > > >
> > > > Naval Research Laboratory, Code 7531
> > > >
> > > > 7 Grace Hopper Avenue
> > > >
> > > > Monterey, CA 93943-5502
> > > >
> > > >
> > > >
> > > > Ph. (831) 656-4111
> > > >
> > > >
> > > >
> >
> >
> >
> >
> >
>
>
>
------------------------------------------------
Subject: Ascii2NC
From: Tsu, Mr. Justin
Time: Fri May 24 10:46:12 2019
Hi John,
Yes, I thought I sent an email thank you for solving the issue. Sorry
if you didn’t get it, but the problem has been solved thanks to your
tremendous help. I appreciate your patience in walking me through
everything.
Thanks,
Justin
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, May 24, 2019 9:44 AM
To: Tsu, Mr. Justin
Subject: Re: [rt.rap.ucar.edu #90137] Ascii2NC
Hi Justin,
I'm just following up on old met-help tickets. I'm guessing that this
is
no longer an issue since I believe we addressed it on another ticket.
But
I wanted to double-check with you before closing it.
Thanks,
John
On Mon, May 13, 2019 at 4:52 PM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90137 >
>
> Thanks John,
>
> Ive got my forecast field in the form of a grib file entitled
>
>
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
>
> This is the U Component of wind at 1000 mb. My ob file is in a
netcdf
> file
> created using ascii2nc. I named wind speed obs "ws" in the ascii
file
> that I
> ran the ascii2nc tool on ( I am aware that I am trying to compare
Wind
> speed
> and u component of wind, but I just want to see if I can get
point_stat
> working).
>
> How should I arrange my fcst and obs arrays? Here is what I have
so far:
>
> 52 fcst = {
> 53 field = [
> 54 {
> 55 name = "U";
> 56 level = "P1000";
> 57 file_type = GRIB2;
> 58 cat_thresh = [ >80.0 ];
> 59 }
> 60 ];
> 61
> 62 }
> 63
> 64 obs = {
> 65 field = [
> 66 {
> 67 file_type = NETCDF_NCCF;
> 68 name = "UGRD";
> 69 level = ["P1000"];
> 70 }
> 71 ];
> 72 }
>
> Running the command as follows gives me this error:
>
> [tsu at maury2 00_POINT_STAT_WORK]$ point_stat
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
>
> NAF_sfc_2019042612.nc config.rc -v 1
> DEBUG 1: Default Config File:
> /software/depot/met/met-
8.0_bugfix/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File: config.rc
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1726142812
> DEBUG 1: Forecast File:
>
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
> DEBUG 1: Observation File: NAF_sfc_2019042612.nc
> WARNING:
> WARNING: process_fcst_climo_files() -> no fields matching U/P1000
found in
> file:
>
> GRIB_UCMP/US058GMET-GR1dyn.COAMPS-CENCOOS_CENCOOS-n2-
c1_02700F0NL2019042612_0100_010000-000000wnd_ucmp
> WARNING:
> ERROR :
> ERROR : process_fcst_climo_files() -> no requested forecast data
found!
> Exiting...
> ERROR :
>
> Justin
>
> -----Original Message-----
> From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
> Sent: Thursday, May 9, 2019 12:00 PM
> To: Tsu, Mr. Justin
> Subject: Re: [rt.rap.ucar.edu #90137] Ascii2NC
>
> Justin and George,
>
> Just wanted to chime in on this ticket. Justin, you're welcome to
name the
> observation variables however you'd like. MET does not enforce any
> standards other than requiring that variable name contain no
embedded
> whitespace.
>
> Let's say you have some forecast data named ABC, and you want to
compare
> that to observations named XYZ. You can just set up the MET config
file to
> account for that:
>
> *fcst = {*
> * field = [ { name = "ABC"; level = "P500";' } ];*
> *}*
> *obs = {*
> * field = [ { name = "XYZ"; level = "P500"; } ];*
> *}*
>
> If both your forecast and observation use the same name, it just
makes the
> config file slightly easier since you can use the following short-
hand:
>
> *obs = fcst;*
>
> But handling different naming conventions is done in the MET config
> files. Hope
> this helps.
>
> Thanks,
> John
>
> On Thu, May 9, 2019 at 11:10 AM Tsu, Mr. Justin via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90137 >
> >
> > Thanks Howard,
> >
> > Do you have a reference for how MET defines variable names? I am
aware
> > that
> > NRL probably defines variable names differently than other
meteorological
> > communities do.
> >
> > Justin
> >
> > -----Original Message-----
> > From: Howard Soh via RT [mailto:met_help at ucar.edu]
> > Sent: Wednesday, May 8, 2019 6:23 PM
> > To: Tsu, Mr. Justin
> > Subject: [rt.rap.ucar.edu #90137] Ascii2NC
> >
> > The grib_code, variable id or variable name are associated with
other MET
> > tools. There are some common grib codes but other grib codes could
have
> > different names depending on the grib table. MET tool supports
variable
> > names
> > as alternative. The other MET tools can be configured with
variable names
> > instead of the grib code.
> >
> > It depends on how you use the ascii2nc output with other tools.
The
> height
> > of
> > the surface data is not the same. For example, 2m temperature and
10m
> wind
> > data. If you put the height 0 for 10m wind data, other tools read
it as
> 0m
> > wind data. One consideration is the characteristics of the pairing
data.
> > For
> > example, the pairing gridded data has pressure levels as vertical
> > coordinate,
> > column 8 data will be more useful than column 9.
> >
> > Cheers,
> > Howard
> >
> > On Wed May 08 18:31:26 2019, justin.tsu at nrlmry.navy.mil wrote:
> > > Thank you for clarifying column 6, 8, and 9. How do I define
these
> > > same
> > > columns for surface observations? Would I just set these to
surface
> > > level (0
> > > meter and 1013 hpa)? Also from my initial email:
> > > I am using https://apps.ecmwf.int/codes/grib/param-db to find
the Grib
> > > Codes.
> > > Is the column entitled "Parameter ID" what MET uses to determine
the
> > > variable?
> > >
> > > Thanks,
> > > Justin
> > > -----Original Message-----
> > > From: Howard Soh via RT [mailto:met_help at ucar.edu]
> > > Sent: Wednesday, May 8, 2019 5:25 PM
> > > To: Tsu, Mr. Justin
> > > Subject: [rt.rap.ucar.edu #90137] Ascii2NC
> > >
> > > Column 1 to 6 are header information about a station or an
equipment.
> > > And
> > > column 7 to 11 are observation data.
> > >
> > > column 6: the elevation of the station or the equipment
(lat/lon/elv)
> > > column 8: the pressure level associated with observation data
> > > column 9: the height associated with observation data
> > >
> > > column 8 and/or column 9 are the vertical information of the
> > > observation data.
> > >
> > >
> > > Cheers,
> > > Howard
> > >
> > > On Wed May 08 17:12:45 2019, justin.tsu at nrlmry.navy.mil wrote:
> > > > Hi,
> > > >
> > > >
> > > >
> > > > I am trying to convert some HDF5 point observations. I have
two HDF5
> > > > file
> > > > per date, one for radiosondes and another for surface obs.
>From your
> > > > ASCII2NC documentation, I see the following:
> > > >
> > > > "
> > > >
> > > > The input ASCII MET point observation format contains one
observation
> > > > per
> > > > line. Each input observation line should consist of the
following 11
> > > > columns
> > > > of data:
> > > >
> > > > 1. Message_Type
> > > >
> > > > 2. Station_ID
> > > >
> > > > 3. Valid_Time in YYYYMMDD_HHMMSS format
> > > >
> > > > 4. Lat in degrees North
> > > >
> > > > 5. Lon in degrees East
> > > >
> > > > 6. Elevation in meters above sea level
> > > >
> > > > 7. Grib_Code as the integer GRIB code value or variable
name
> > > > corresponding to this observation type
> > > >
> > > > 8. Level as the pressure level in hPa or accumulation
interval
> > > > in hours
> > > >
> > > > 9. Height in meters above sea level or above ground level
> > > >
> > > > 10. QC_String corresponding to the quality control value
> > > >
> > > > 11. Observation_Value in the units prescribed for the grib
code
> > > >
> > > > In order to use ASCII2NC, it is the user's responsibility to
get
> > > > their ASCII
> > > > point observations into this format
> > > >
> > > > "
> > > >
> > > > I am a bit confused on #6-9. What is the difference between
> > > > elevation,
> > > > level and height and how do I define these when I start to
write the
> > > > ascii
> > > > file for the surface obs? Also I am using
> > > > https://apps.ecmwf.int/codes/grib/param-db to find the Grib
Codes.
> Is
> > > > the
> > > > column entitled "Parameter ID" what MET uses to determine the
> > > > variable?
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Justin
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Justin Tsu
> > > >
> > > > Marine Meteorology Division
> > > >
> > > > Data Assimilation/Mesoscale Modeling
> > > >
> > > > Building 704 Room 212
> > > >
> > > > Naval Research Laboratory, Code 7531
> > > >
> > > > 7 Grace Hopper Avenue
> > > >
> > > > Monterey, CA 93943-5502
> > > >
> > > >
> > > >
> > > > Ph. (831) 656-4111
> > > >
> > > >
> > > >
> >
> >
> >
> >
> >
>
>
>
------------------------------------------------
More information about the Met_help
mailing list