[Met_help] [rt.rap.ucar.edu #79969] History for How to choose a time lag in Grid Stat?
John Halley Gotway via RT
met_help at ucar.edu
Thu Apr 6 09:18:53 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear MET Help staff, I’ve built 2 NetCDF files with the time dimension size equals to 90. And I would like to evaluate precip using the Grid Stat tool. I’d like to know how to specify the exact date I want. Could you please help me?
Here is a partial dump of my OBSERVATION NetCDF file:
netcdf MERGE_20161201_20170228 {
dimensions:
time = 90 ;
lat = 313 ;
lon = 245 ;
variables:
int time(time) ;
time:units = "days since 2016-12-01 00:00:00 12:00:00" ;
time:calendar = "standard" ;
time:standard_name = "time" ;
time:long_name = "time" ;
double lat(lat) ;
lat:standard_name = "latitude" ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
lat:axis = "Y" ;
double lon(lon) ;
lon:standard_name = "longitude" ;
lon:long_name = "longitude" ;
lon:units = "degrees_east" ;
lon:axis = "X" ;
float APCP(time, lat, lon) ;
APCP:missing_value = -999.f ;
APCP:standard_name = "24-hour APCP" ;
APCP:long_name = "24-hour accumulated precipitation" ;
APCP:_FillValue = -999.f ;
// global attributes:
:Generator = "NCL NCAR Command Language" ;
:Author = "Jose Roberto Motta Garcia, PhD, DMD / CPTEC / INPE" ;
:title = "MERGE daily accummulated precip - (Rozante et al, 2010)" ;
:Period = "From 2016-12-01 00:00:00 to 2017-02-28 00:00:00" ;
:MET_version = "V5.2" ;
:Projection = "LatLon" ;
:lat_ll_deg = "-50.200000 degrees_north" ;
:lon_ll_deg = "-82.800000 degrees_east" ;
:lat_ll = "-50.200000 degrees_north" ;
:lon_ll = "-82.800000 degrees_east" ;
:delta_lat_deg = "0.200000 degrees" ;
:delta_lon_deg = "0.200000 degrees" ;
:delta_lat = "0.200000 degrees" ;
:delta_lon = "0.200000 degrees" ;
:Nlat = "245 grid_points" ;
:Nlon = "313 grid_points" ;
And here is a partial dump of my FORECAST NetCDF file, time has size 1 because it speeds up the file generation and hence the testing procedures, but it will have 90, as the observation file.
netcdf Eta5_2016120100_2016120100_36hs_pcp_combine {
dimensions:
time = 1 ;
lat = 1320 ;
lon = 1162 ;
variables:
int time(time) ;
time:units = "days since 2016-12-01 00:00:00" ;
time:calendar = "standard" ;
time:standard_name = "time" ;
time:long_name = "time" ;
float lat(lat) ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
float lon(lon) ;
lon:long_name = "longitude" ;
lon:units = "degrees_east" ;
lon:standard_name = "longitude" ;
float APCP(time, lat, lon) ;
APCP:missing_value = -9999.f ;
APCP:Projection = "LatLon" ;
APCP:units = "kg/m^2" ;
APCP:standard_name = "24-hour APCP" ;
APCP:long_name = "24-hour accumulated precipitation" ;
APCP:_FillValue = -9999.f ;
// global attributes:
:Generator = "MET::pcp_combine" ;
:Author = "Jose Roberto Motta Garcia, PhD, DMD / CPTEC / INPE" ;
:title = "Eta 5km 24-hs accummulated APCP for 36hs forecast" ;
:Period = "From 2016-12-01 00:00:00 to 2016-12-01 00:00:00" ;
:Projection = "LatLon" ;
:MET_version = "V5.2" ;
:lat_ll_deg = "-51.000000 degrees_north" ;
:lat_ll = "-51.000000 degrees_north" ;
:lon_ll_deg = "-84.100000 degrees_east" ;
:lon_ll = "-84.100000 degrees_east" ;
:delta_lat_deg = "0.050000 degrees" ;
:delta_lon_deg = "0.050000 degrees" ;
:delta_lat = "0.050000 degrees" ;
:delta_lon = "0.050000 degrees" ;
:Nlat = "1162 grid_points" ;
:Nlon = "1320 grid_points" ;
Attached is the Grid Stat config file I’m adjusting to run.
Thank you very much
JR Garcia
--
=================================
Jose Roberto Motta Garcia, PhD
www.cptec.inpe.br <http://www.cptec.inpe.br/>
www.inpe.br <http://www.inpe.br/>
Tel.: (55) 12 3186-7966
----------------------------------------------------------
***** Save natural resources *****
=================================
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: How to choose a time lag in Grid Stat?
From: John Halley Gotway
Time: Tue Mar 28 16:58:24 2017
JR Garcia,
When processing NetCDF files, you specify the level information to
tell MET
which 2D slice of data to use. There is currently no way to
explicitly
define which time slice you'd like other than selecting the time
index.
Let's use plot_data_plane as an example:
met-5.2/bin/plot_data_plane \
MERGE_20161201_20170228.nc \
obs.ps \
'name="APCP"; level="(5,*,*)";'
Since these indices are 0-based, this will select the 6-th time slice
of
your APCP data and plot it.
MET *should* be smart enough to correctly lookup the time value
corresponding to the 6-th time dimension and write that to output
files
(i.e. in the FCST_VALID_BEG column of Grid-Stat output). But I'd
suggest
testing that to verify that it's actually working as expected.
Thanks,
John Halley Gotway
On Fri, Mar 24, 2017 at 12:55 PM, Garcia, J.R.M. via RT
<met_help at ucar.edu>
wrote:
>
> Fri Mar 24 12:55:44 2017: Request 79969 was acted upon.
> Transaction: Ticket created by garcia.cptec at gmail.com
> Queue: met_help
> Subject: How to choose a time lag in Grid Stat?
> Owner: Nobody
> Requestors: garcia.cptec at gmail.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79969 >
>
>
> Dear MET Help staff, I’ve built 2 NetCDF files with the time
dimension
> size equals to 90. And I would like to evaluate precip using the
Grid Stat
> tool. I’d like to know how to specify the exact date I want. Could
you
> please help me?
>
> Here is a partial dump of my OBSERVATION NetCDF file:
>
> netcdf MERGE_20161201_20170228 {
> dimensions:
> time = 90 ;
> lat = 313 ;
> lon = 245 ;
> variables:
> int time(time) ;
> time:units = "days since 2016-12-01 00:00:00
12:00:00" ;
> time:calendar = "standard" ;
> time:standard_name = "time" ;
> time:long_name = "time" ;
> double lat(lat) ;
> lat:standard_name = "latitude" ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> lat:axis = "Y" ;
> double lon(lon) ;
> lon:standard_name = "longitude" ;
> lon:long_name = "longitude" ;
> lon:units = "degrees_east" ;
> lon:axis = "X" ;
> float APCP(time, lat, lon) ;
> APCP:missing_value = -999.f ;
> APCP:standard_name = "24-hour APCP" ;
> APCP:long_name = "24-hour accumulated precipitation"
;
> APCP:_FillValue = -999.f ;
>
> // global attributes:
> :Generator = "NCL NCAR Command Language" ;
> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC /
> INPE" ;
> :title = "MERGE daily accummulated precip - (Rozante
et
> al, 2010)" ;
> :Period = "From 2016-12-01 00:00:00 to 2017-02-28
> 00:00:00" ;
> :MET_version = "V5.2" ;
> :Projection = "LatLon" ;
> :lat_ll_deg = "-50.200000 degrees_north" ;
> :lon_ll_deg = "-82.800000 degrees_east" ;
> :lat_ll = "-50.200000 degrees_north" ;
> :lon_ll = "-82.800000 degrees_east" ;
> :delta_lat_deg = "0.200000 degrees" ;
> :delta_lon_deg = "0.200000 degrees" ;
> :delta_lat = "0.200000 degrees" ;
> :delta_lon = "0.200000 degrees" ;
> :Nlat = "245 grid_points" ;
> :Nlon = "313 grid_points" ;
>
>
> And here is a partial dump of my FORECAST NetCDF file, time has size
1
> because it speeds up the file generation and hence the testing
procedures,
> but it will have 90, as the observation file.
>
> netcdf Eta5_2016120100_2016120100_36hs_pcp_combine {
> dimensions:
> time = 1 ;
> lat = 1320 ;
> lon = 1162 ;
> variables:
> int time(time) ;
> time:units = "days since 2016-12-01 00:00:00" ;
> time:calendar = "standard" ;
> time:standard_name = "time" ;
> time:long_name = "time" ;
> float lat(lat) ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> lat:standard_name = "latitude" ;
> float lon(lon) ;
> lon:long_name = "longitude" ;
> lon:units = "degrees_east" ;
> lon:standard_name = "longitude" ;
> float APCP(time, lat, lon) ;
> APCP:missing_value = -9999.f ;
> APCP:Projection = "LatLon" ;
> APCP:units = "kg/m^2" ;
> APCP:standard_name = "24-hour APCP" ;
> APCP:long_name = "24-hour accumulated precipitation"
;
> APCP:_FillValue = -9999.f ;
>
> // global attributes:
> :Generator = "MET::pcp_combine" ;
> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC /
> INPE" ;
> :title = "Eta 5km 24-hs accummulated APCP for 36hs
> forecast" ;
> :Period = "From 2016-12-01 00:00:00 to 2016-12-01
> 00:00:00" ;
> :Projection = "LatLon" ;
> :MET_version = "V5.2" ;
> :lat_ll_deg = "-51.000000 degrees_north" ;
> :lat_ll = "-51.000000 degrees_north" ;
> :lon_ll_deg = "-84.100000 degrees_east" ;
> :lon_ll = "-84.100000 degrees_east" ;
> :delta_lat_deg = "0.050000 degrees" ;
> :delta_lon_deg = "0.050000 degrees" ;
> :delta_lat = "0.050000 degrees" ;
> :delta_lon = "0.050000 degrees" ;
> :Nlat = "1162 grid_points" ;
> :Nlon = "1320 grid_points" ;
>
> Attached is the Grid Stat config file I’m adjusting to run.
>
> Thank you very much
>
>
> JR Garcia
>
>
>
> --
> =================================
> Jose Roberto Motta Garcia, PhD
>
> www.cptec.inpe.br <http://www.cptec.inpe.br/>
> www.inpe.br <http://www.inpe.br/>
> Tel.: (55) 12 3186-7966
> ----------------------------------------------------------
> ***** Save natural resources *****
> =================================
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #79969] How to choose a time lag in Grid Stat?
From: Garcia, J.R.M.
Time: Wed Mar 29 11:31:09 2017
Ok, John, thank you very much again.
I'll try.
JR Garcia
=======================================================
Jose Roberto Motta Garcia, PhD
DMD - Modelling and Development Division
CPTEC - Center for Weather Forecast and Climate Studies
INPE - Brazilian National Institute for Space Research
Tel.: +55 (12) 3208-7966
-------------------------------------------------------
SAVE NATURAL RESOURCES!
=======================================================
On 28/03/2017 19:58, John Halley Gotway via RT wrote:
> JR Garcia,
>
> When processing NetCDF files, you specify the level information to
tell MET
> which 2D slice of data to use. There is currently no way to
explicitly
> define which time slice you'd like other than selecting the time
index.
>
> Let's use plot_data_plane as an example:
>
> met-5.2/bin/plot_data_plane \
> MERGE_20161201_20170228.nc \
> obs.ps \
> 'name="APCP"; level="(5,*,*)";'
>
> Since these indices are 0-based, this will select the 6-th time
slice of
> your APCP data and plot it.
>
> MET *should* be smart enough to correctly lookup the time value
> corresponding to the 6-th time dimension and write that to output
files
> (i.e. in the FCST_VALID_BEG column of Grid-Stat output). But I'd
suggest
> testing that to verify that it's actually working as expected.
>
> Thanks,
> John Halley Gotway
>
> On Fri, Mar 24, 2017 at 12:55 PM, Garcia, J.R.M. via RT
<met_help at ucar.edu>
> wrote:
>
>> Fri Mar 24 12:55:44 2017: Request 79969 was acted upon.
>> Transaction: Ticket created by garcia.cptec at gmail.com
>> Queue: met_help
>> Subject: How to choose a time lag in Grid Stat?
>> Owner: Nobody
>> Requestors: garcia.cptec at gmail.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79969 >
>>
>>
>> Dear MET Help staff, I’ve built 2 NetCDF files with the time
dimension
>> size equals to 90. And I would like to evaluate precip using the
Grid Stat
>> tool. I’d like to know how to specify the exact date I want. Could
you
>> please help me?
>>
>> Here is a partial dump of my OBSERVATION NetCDF file:
>>
>> netcdf MERGE_20161201_20170228 {
>> dimensions:
>> time = 90 ;
>> lat = 313 ;
>> lon = 245 ;
>> variables:
>> int time(time) ;
>> time:units = "days since 2016-12-01 00:00:00
12:00:00" ;
>> time:calendar = "standard" ;
>> time:standard_name = "time" ;
>> time:long_name = "time" ;
>> double lat(lat) ;
>> lat:standard_name = "latitude" ;
>> lat:long_name = "latitude" ;
>> lat:units = "degrees_north" ;
>> lat:axis = "Y" ;
>> double lon(lon) ;
>> lon:standard_name = "longitude" ;
>> lon:long_name = "longitude" ;
>> lon:units = "degrees_east" ;
>> lon:axis = "X" ;
>> float APCP(time, lat, lon) ;
>> APCP:missing_value = -999.f ;
>> APCP:standard_name = "24-hour APCP" ;
>> APCP:long_name = "24-hour accumulated
precipitation" ;
>> APCP:_FillValue = -999.f ;
>>
>> // global attributes:
>> :Generator = "NCL NCAR Command Language" ;
>> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC /
>> INPE" ;
>> :title = "MERGE daily accummulated precip -
(Rozante et
>> al, 2010)" ;
>> :Period = "From 2016-12-01 00:00:00 to 2017-02-28
>> 00:00:00" ;
>> :MET_version = "V5.2" ;
>> :Projection = "LatLon" ;
>> :lat_ll_deg = "-50.200000 degrees_north" ;
>> :lon_ll_deg = "-82.800000 degrees_east" ;
>> :lat_ll = "-50.200000 degrees_north" ;
>> :lon_ll = "-82.800000 degrees_east" ;
>> :delta_lat_deg = "0.200000 degrees" ;
>> :delta_lon_deg = "0.200000 degrees" ;
>> :delta_lat = "0.200000 degrees" ;
>> :delta_lon = "0.200000 degrees" ;
>> :Nlat = "245 grid_points" ;
>> :Nlon = "313 grid_points" ;
>>
>>
>> And here is a partial dump of my FORECAST NetCDF file, time has
size 1
>> because it speeds up the file generation and hence the testing
procedures,
>> but it will have 90, as the observation file.
>>
>> netcdf Eta5_2016120100_2016120100_36hs_pcp_combine {
>> dimensions:
>> time = 1 ;
>> lat = 1320 ;
>> lon = 1162 ;
>> variables:
>> int time(time) ;
>> time:units = "days since 2016-12-01 00:00:00" ;
>> time:calendar = "standard" ;
>> time:standard_name = "time" ;
>> time:long_name = "time" ;
>> float lat(lat) ;
>> lat:long_name = "latitude" ;
>> lat:units = "degrees_north" ;
>> lat:standard_name = "latitude" ;
>> float lon(lon) ;
>> lon:long_name = "longitude" ;
>> lon:units = "degrees_east" ;
>> lon:standard_name = "longitude" ;
>> float APCP(time, lat, lon) ;
>> APCP:missing_value = -9999.f ;
>> APCP:Projection = "LatLon" ;
>> APCP:units = "kg/m^2" ;
>> APCP:standard_name = "24-hour APCP" ;
>> APCP:long_name = "24-hour accumulated
precipitation" ;
>> APCP:_FillValue = -9999.f ;
>>
>> // global attributes:
>> :Generator = "MET::pcp_combine" ;
>> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC /
>> INPE" ;
>> :title = "Eta 5km 24-hs accummulated APCP for 36hs
>> forecast" ;
>> :Period = "From 2016-12-01 00:00:00 to 2016-12-01
>> 00:00:00" ;
>> :Projection = "LatLon" ;
>> :MET_version = "V5.2" ;
>> :lat_ll_deg = "-51.000000 degrees_north" ;
>> :lat_ll = "-51.000000 degrees_north" ;
>> :lon_ll_deg = "-84.100000 degrees_east" ;
>> :lon_ll = "-84.100000 degrees_east" ;
>> :delta_lat_deg = "0.050000 degrees" ;
>> :delta_lon_deg = "0.050000 degrees" ;
>> :delta_lat = "0.050000 degrees" ;
>> :delta_lon = "0.050000 degrees" ;
>> :Nlat = "1162 grid_points" ;
>> :Nlon = "1320 grid_points" ;
>>
>> Attached is the Grid Stat config file I’m adjusting to run.
>>
>> Thank you very much
>>
>>
>> JR Garcia
>>
>>
>>
>> --
>> =================================
>> Jose Roberto Motta Garcia, PhD
>>
>> www.cptec.inpe.br <http://www.cptec.inpe.br/>
>> www.inpe.br <http://www.inpe.br/>
>> Tel.: (55) 12 3186-7966
>> ----------------------------------------------------------
>> ***** Save natural resources *****
>> =================================
>>
>>
>>
------------------------------------------------
Subject: How to choose a time lag in Grid Stat?
From: Garcia, J.R.M.
Time: Wed Mar 29 11:52:43 2017
John, the command line I'm trying is
grid_stat FCT.nc OBS.nc GridStat.cfg 'name="APCP"; level="(0,*,*)";'
- Both FCT and OBS have size 90 for the time dimension and both have
APCP variable indexed on (time, lat, lon), as ncdump output is showing
at the end of this email.
And I get an output like if I have issued a wrong syntax:
*** Model Evaluation Tools (METV5.2) ***
Usage: grid_stat
fcst_file
obs_file
config_file
[-outdir path]
[-log file]
[-v level]
where "fcst_file" is a gridded forecast file containing the
field(s) to be verified (required).
"obs_file" is a gridded observation file containing the
verifying field(s) (required).
"config_file" is a GridStatConfig file containing the desired
configuration settings (required).
"-outdir path" overrides the default output directory (.)
(optional).
"-log file" outputs log messages to the specified file
(optional).
"-v level" overrides the default level of logging (2)
(optional).
Could you help me, please? The syntax for grid_stat says nothing about
the last parameter ('name="APCP"; level="(0,*,*)";').
Thanks
JR Garcia
=======================================================
Jose Roberto Motta Garcia, PhD
DMD - Modelling and Development Division
CPTEC - Center for Weather Forecast and Climate Studies
INPE - Brazilian National Institute for Space Research
Tel.: +55 (12) 3208-7966
-------------------------------------------------------
SAVE NATURAL RESOURCES!
=======================================================
On 28/03/2017 19:58, John Halley Gotway via RT wrote:
> JR Garcia,
>
> When processing NetCDF files, you specify the level information to
tell MET
> which 2D slice of data to use. There is currently no way to
explicitly
> define which time slice you'd like other than selecting the time
index.
>
> Let's use plot_data_plane as an example:
>
> met-5.2/bin/plot_data_plane \
> MERGE_20161201_20170228.nc \
> obs.ps \
> 'name="APCP"; level="(5,*,*)";'
>
> Since these indices are 0-based, this will select the 6-th time
slice of
> your APCP data and plot it.
>
> MET *should* be smart enough to correctly lookup the time value
> corresponding to the 6-th time dimension and write that to output
files
> (i.e. in the FCST_VALID_BEG column of Grid-Stat output). But I'd
suggest
> testing that to verify that it's actually working as expected.
>
> Thanks,
> John Halley Gotway
>
> On Fri, Mar 24, 2017 at 12:55 PM, Garcia, J.R.M. via RT
<met_help at ucar.edu>
> wrote:
>
>> Fri Mar 24 12:55:44 2017: Request 79969 was acted upon.
>> Transaction: Ticket created by garcia.cptec at gmail.com
>> Queue: met_help
>> Subject: How to choose a time lag in Grid Stat?
>> Owner: Nobody
>> Requestors: garcia.cptec at gmail.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79969 >
>>
>>
>> Dear MET Help staff, I’ve built 2 NetCDF files with the time
dimension
>> size equals to 90. And I would like to evaluate precip using the
Grid Stat
>> tool. I’d like to know how to specify the exact date I want. Could
you
>> please help me?
>>
>> Here is a partial dump of my OBSERVATION NetCDF file:
>>
>> netcdf MERGE_20161201_20170228 {
>> dimensions:
>> time = 90 ;
>> lat = 313 ;
>> lon = 245 ;
>> variables:
>> int time(time) ;
>> time:units = "days since 2016-12-01 00:00:00
12:00:00" ;
>> time:calendar = "standard" ;
>> time:standard_name = "time" ;
>> time:long_name = "time" ;
>> double lat(lat) ;
>> lat:standard_name = "latitude" ;
>> lat:long_name = "latitude" ;
>> lat:units = "degrees_north" ;
>> lat:axis = "Y" ;
>> double lon(lon) ;
>> lon:standard_name = "longitude" ;
>> lon:long_name = "longitude" ;
>> lon:units = "degrees_east" ;
>> lon:axis = "X" ;
>> float APCP(time, lat, lon) ;
>> APCP:missing_value = -999.f ;
>> APCP:standard_name = "24-hour APCP" ;
>> APCP:long_name = "24-hour accumulated
precipitation" ;
>> APCP:_FillValue = -999.f ;
>>
>> // global attributes:
>> :Generator = "NCL NCAR Command Language" ;
>> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC /
>> INPE" ;
>> :title = "MERGE daily accummulated precip -
(Rozante et
>> al, 2010)" ;
>> :Period = "From 2016-12-01 00:00:00 to 2017-02-28
>> 00:00:00" ;
>> :MET_version = "V5.2" ;
>> :Projection = "LatLon" ;
>> :lat_ll_deg = "-50.200000 degrees_north" ;
>> :lon_ll_deg = "-82.800000 degrees_east" ;
>> :lat_ll = "-50.200000 degrees_north" ;
>> :lon_ll = "-82.800000 degrees_east" ;
>> :delta_lat_deg = "0.200000 degrees" ;
>> :delta_lon_deg = "0.200000 degrees" ;
>> :delta_lat = "0.200000 degrees" ;
>> :delta_lon = "0.200000 degrees" ;
>> :Nlat = "245 grid_points" ;
>> :Nlon = "313 grid_points" ;
>>
>>
>> And here is a partial dump of my FORECAST NetCDF file, time has
size 1
>> because it speeds up the file generation and hence the testing
procedures,
>> but it will have 90, as the observation file.
>>
>> netcdf Eta5_2016120100_2016120100_36hs_pcp_combine {
>> dimensions:
>> time = 1 ;
>> lat = 1320 ;
>> lon = 1162 ;
>> variables:
>> int time(time) ;
>> time:units = "days since 2016-12-01 00:00:00" ;
>> time:calendar = "standard" ;
>> time:standard_name = "time" ;
>> time:long_name = "time" ;
>> float lat(lat) ;
>> lat:long_name = "latitude" ;
>> lat:units = "degrees_north" ;
>> lat:standard_name = "latitude" ;
>> float lon(lon) ;
>> lon:long_name = "longitude" ;
>> lon:units = "degrees_east" ;
>> lon:standard_name = "longitude" ;
>> float APCP(time, lat, lon) ;
>> APCP:missing_value = -9999.f ;
>> APCP:Projection = "LatLon" ;
>> APCP:units = "kg/m^2" ;
>> APCP:standard_name = "24-hour APCP" ;
>> APCP:long_name = "24-hour accumulated
precipitation" ;
>> APCP:_FillValue = -9999.f ;
>>
>> // global attributes:
>> :Generator = "MET::pcp_combine" ;
>> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC /
>> INPE" ;
>> :title = "Eta 5km 24-hs accummulated APCP for 36hs
>> forecast" ;
>> :Period = "From 2016-12-01 00:00:00 to 2016-12-01
>> 00:00:00" ;
>> :Projection = "LatLon" ;
>> :MET_version = "V5.2" ;
>> :lat_ll_deg = "-51.000000 degrees_north" ;
>> :lat_ll = "-51.000000 degrees_north" ;
>> :lon_ll_deg = "-84.100000 degrees_east" ;
>> :lon_ll = "-84.100000 degrees_east" ;
>> :delta_lat_deg = "0.050000 degrees" ;
>> :delta_lon_deg = "0.050000 degrees" ;
>> :delta_lat = "0.050000 degrees" ;
>> :delta_lon = "0.050000 degrees" ;
>> :Nlat = "1162 grid_points" ;
>> :Nlon = "1320 grid_points" ;
>>
>> Attached is the Grid Stat config file I’m adjusting to run.
>>
>> Thank you very much
>>
>>
>> JR Garcia
>>
>>
>>
>> --
>> =================================
>> Jose Roberto Motta Garcia, PhD
>>
>> www.cptec.inpe.br <http://www.cptec.inpe.br/>
>> www.inpe.br <http://www.inpe.br/>
>> Tel.: (55) 12 3186-7966
>> ----------------------------------------------------------
>> ***** Save natural resources *****
>> =================================
>>
>>
>>
------------------------------------------------
Subject: How to choose a time lag in Grid Stat?
From: John Halley Gotway
Time: Thu Mar 30 13:11:27 2017
JR Garcia,
The Grid-Stat tool in MET takes as input a configuration file
(GridStat.cfg).
But you're trying to pass it a configuration string ('name="APCP";
level="(0,*,*)";') which causes a problem when parsing the command
line.
Some MET tools like plot_data_plane and regrid_data_plane do support
to use
of configuration strings as command line arguments, but Grid-Stat is
not
one of them.
Instead, your config strings should be included in the Grid-Stat
configuration file. And the MET User's Guide includes details about
those
config file options.
So you Grid-Stat command line just need to be:
grid_stat FCT.nc OBS.nc GridStat.cfg
Hope that helps clarify.
Thanks,
John
On Wed, Mar 29, 2017 at 11:52 AM, Garcia, J.R.M. via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79969 >
>
> John, the command line I'm trying is
>
> grid_stat FCT.nc OBS.nc GridStat.cfg 'name="APCP"; level="(0,*,*)";'
>
> - Both FCT and OBS have size 90 for the time dimension and both have
> APCP variable indexed on (time, lat, lon), as ncdump output is
showing
> at the end of this email.
>
> And I get an output like if I have issued a wrong syntax:
>
> *** Model Evaluation Tools (METV5.2) ***
>
> Usage: grid_stat
> fcst_file
> obs_file
> config_file
> [-outdir path]
> [-log file]
> [-v level]
>
> where "fcst_file" is a gridded forecast file containing the
> field(s) to be verified (required).
> "obs_file" is a gridded observation file containing the
> verifying field(s) (required).
> "config_file" is a GridStatConfig file containing the
desired
> configuration settings (required).
> "-outdir path" overrides the default output directory (.)
> (optional).
> "-log file" outputs log messages to the specified file
(optional).
> "-v level" overrides the default level of logging (2)
(optional).
>
> Could you help me, please? The syntax for grid_stat says nothing
about
> the last parameter ('name="APCP"; level="(0,*,*)";').
>
> Thanks
>
> JR Garcia
>
> =======================================================
> Jose Roberto Motta Garcia, PhD
>
> DMD - Modelling and Development Division
> CPTEC - Center for Weather Forecast and Climate Studies
> INPE - Brazilian National Institute for Space Research
> Tel.: +55 (12) 3208-7966
> -------------------------------------------------------
> SAVE NATURAL RESOURCES!
> =======================================================
>
> On 28/03/2017 19:58, John Halley Gotway via RT wrote:
> > JR Garcia,
> >
> > When processing NetCDF files, you specify the level information to
tell
> MET
> > which 2D slice of data to use. There is currently no way to
explicitly
> > define which time slice you'd like other than selecting the time
index.
> >
> > Let's use plot_data_plane as an example:
> >
> > met-5.2/bin/plot_data_plane \
> > MERGE_20161201_20170228.nc \
> > obs.ps \
> > 'name="APCP"; level="(5,*,*)";'
> >
> > Since these indices are 0-based, this will select the 6-th time
slice of
> > your APCP data and plot it.
> >
> > MET *should* be smart enough to correctly lookup the time value
> > corresponding to the 6-th time dimension and write that to output
files
> > (i.e. in the FCST_VALID_BEG column of Grid-Stat output). But I'd
suggest
> > testing that to verify that it's actually working as expected.
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Fri, Mar 24, 2017 at 12:55 PM, Garcia, J.R.M. via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >> Fri Mar 24 12:55:44 2017: Request 79969 was acted upon.
> >> Transaction: Ticket created by garcia.cptec at gmail.com
> >> Queue: met_help
> >> Subject: How to choose a time lag in Grid Stat?
> >> Owner: Nobody
> >> Requestors: garcia.cptec at gmail.com
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=79969
> >
> >>
> >>
> >> Dear MET Help staff, I’ve built 2 NetCDF files with the time
dimension
> >> size equals to 90. And I would like to evaluate precip using the
Grid
> Stat
> >> tool. I’d like to know how to specify the exact date I want.
Could you
> >> please help me?
> >>
> >> Here is a partial dump of my OBSERVATION NetCDF file:
> >>
> >> netcdf MERGE_20161201_20170228 {
> >> dimensions:
> >> time = 90 ;
> >> lat = 313 ;
> >> lon = 245 ;
> >> variables:
> >> int time(time) ;
> >> time:units = "days since 2016-12-01 00:00:00
12:00:00"
> ;
> >> time:calendar = "standard" ;
> >> time:standard_name = "time" ;
> >> time:long_name = "time" ;
> >> double lat(lat) ;
> >> lat:standard_name = "latitude" ;
> >> lat:long_name = "latitude" ;
> >> lat:units = "degrees_north" ;
> >> lat:axis = "Y" ;
> >> double lon(lon) ;
> >> lon:standard_name = "longitude" ;
> >> lon:long_name = "longitude" ;
> >> lon:units = "degrees_east" ;
> >> lon:axis = "X" ;
> >> float APCP(time, lat, lon) ;
> >> APCP:missing_value = -999.f ;
> >> APCP:standard_name = "24-hour APCP" ;
> >> APCP:long_name = "24-hour accumulated
precipitation" ;
> >> APCP:_FillValue = -999.f ;
> >>
> >> // global attributes:
> >> :Generator = "NCL NCAR Command Language" ;
> >> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC
> /
> >> INPE" ;
> >> :title = "MERGE daily accummulated precip -
(Rozante et
> >> al, 2010)" ;
> >> :Period = "From 2016-12-01 00:00:00 to 2017-02-
28
> >> 00:00:00" ;
> >> :MET_version = "V5.2" ;
> >> :Projection = "LatLon" ;
> >> :lat_ll_deg = "-50.200000 degrees_north" ;
> >> :lon_ll_deg = "-82.800000 degrees_east" ;
> >> :lat_ll = "-50.200000 degrees_north" ;
> >> :lon_ll = "-82.800000 degrees_east" ;
> >> :delta_lat_deg = "0.200000 degrees" ;
> >> :delta_lon_deg = "0.200000 degrees" ;
> >> :delta_lat = "0.200000 degrees" ;
> >> :delta_lon = "0.200000 degrees" ;
> >> :Nlat = "245 grid_points" ;
> >> :Nlon = "313 grid_points" ;
> >>
> >>
> >> And here is a partial dump of my FORECAST NetCDF file, time has
size 1
> >> because it speeds up the file generation and hence the testing
> procedures,
> >> but it will have 90, as the observation file.
> >>
> >> netcdf Eta5_2016120100_2016120100_36hs_pcp_combine {
> >> dimensions:
> >> time = 1 ;
> >> lat = 1320 ;
> >> lon = 1162 ;
> >> variables:
> >> int time(time) ;
> >> time:units = "days since 2016-12-01 00:00:00" ;
> >> time:calendar = "standard" ;
> >> time:standard_name = "time" ;
> >> time:long_name = "time" ;
> >> float lat(lat) ;
> >> lat:long_name = "latitude" ;
> >> lat:units = "degrees_north" ;
> >> lat:standard_name = "latitude" ;
> >> float lon(lon) ;
> >> lon:long_name = "longitude" ;
> >> lon:units = "degrees_east" ;
> >> lon:standard_name = "longitude" ;
> >> float APCP(time, lat, lon) ;
> >> APCP:missing_value = -9999.f ;
> >> APCP:Projection = "LatLon" ;
> >> APCP:units = "kg/m^2" ;
> >> APCP:standard_name = "24-hour APCP" ;
> >> APCP:long_name = "24-hour accumulated
precipitation" ;
> >> APCP:_FillValue = -9999.f ;
> >>
> >> // global attributes:
> >> :Generator = "MET::pcp_combine" ;
> >> :Author = "Jose Roberto Motta Garcia, PhD, DMD /
CPTEC
> /
> >> INPE" ;
> >> :title = "Eta 5km 24-hs accummulated APCP for
36hs
> >> forecast" ;
> >> :Period = "From 2016-12-01 00:00:00 to 2016-12-
01
> >> 00:00:00" ;
> >> :Projection = "LatLon" ;
> >> :MET_version = "V5.2" ;
> >> :lat_ll_deg = "-51.000000 degrees_north" ;
> >> :lat_ll = "-51.000000 degrees_north" ;
> >> :lon_ll_deg = "-84.100000 degrees_east" ;
> >> :lon_ll = "-84.100000 degrees_east" ;
> >> :delta_lat_deg = "0.050000 degrees" ;
> >> :delta_lon_deg = "0.050000 degrees" ;
> >> :delta_lat = "0.050000 degrees" ;
> >> :delta_lon = "0.050000 degrees" ;
> >> :Nlat = "1162 grid_points" ;
> >> :Nlon = "1320 grid_points" ;
> >>
> >> Attached is the Grid Stat config file I’m adjusting to run.
> >>
> >> Thank you very much
> >>
> >>
> >> JR Garcia
> >>
> >>
> >>
> >> --
> >> =================================
> >> Jose Roberto Motta Garcia, PhD
> >>
> >> www.cptec.inpe.br <http://www.cptec.inpe.br/>
> >> www.inpe.br <http://www.inpe.br/>
> >> Tel.: (55) 12 3186-7966
> >> ----------------------------------------------------------
> >> ***** Save natural resources *****
> >> =================================
> >>
> >>
> >>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list