[Met_help] [rt.rap.ucar.edu #80169] History for can't set corner for variable "APCP" error
John Halley Gotway via RT
met_help at ucar.edu
Fri Apr 21 09:49:56 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi John, I converted all obs and fct NetCDF files to the NetCDF 3
Classic version and issued the same command, could you please help me
interpret this error? What does "corner" refer to?
Thanks
> grid_stat Eta40ens_00_036hs.nc MERGE_20161201_20170228_Eta40Grid.nc
GridStat.cfg -v 4
DEBUG 1: Default Config File:
/stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/GridStatConfig_default
DEBUG 1: User Config File: GridStat.cfg
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -50.2
DEBUG 4: lon_ll = 83
DEBUG 4: delta_lat = 0.4
DEBUG 4: delta_lon = 0.4
DEBUG 4: Nlat = 157
DEBUG 4: Nlon = 144
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Latitude/Longitude Grid Data:
DEBUG 4: lat_ll = -50.2
DEBUG 4: lon_ll = 82.8
DEBUG 4: delta_lat = 0.2
DEBUG 4: delta_lon = 0.2
DEBUG 4: Nlat = 144
DEBUG 4: Nlon = 157
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_NcMet".
DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_NcMet".
WARNING:
WARNING: parse_conf_interp() -> For neareast neighbor interpolation
method, resetting method from "UW_MEAN" to "NEAREST" since the
interpolation width is 1.
WARNING:
DEBUG 3: Use the forecast grid.
DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157 lat_ll:
-50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=1639511128
DEBUG 1: Forecast File:
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_00_036hs.nc
DEBUG 1: Observation File:
/stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_20161201_20170228_Eta40Grid.nc
DEBUG 3: Reading forecast data for APCP(0,0,*,*).
DEBUG 3: Reading observation data for APCP(0,*,*).
ERROR :
ERROR : MetNcFile::data(NcVar *, const LongArray &) const -> can't set
corner for variable "APCP"
ERROR :
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 10/04/2017 16:51, John Halley Gotway via RT wrote:
> JR Garcia,
>
> Thanks for sending the sample data file. This is definitely a NetCDF4 file
> using the enhanced data model. MET version 5.2 is not able to read NetCDF4
> files. The recent release of MET (version 6.0) has been enhanced to do so.
>
> I tried a few things:
>
> (1) Convert your forecast file from NetCDF4 to 3 using the nccopy command.
> That results in the following error:
>
>> nccopy -3 FCT.nc FCT_nc3.nc
> NetCDF: Not a valid data type or _FillValue type mismatch
> Location: file nccopy.c; line 788
>
> (2) View your file using ncview. It brings up the display but all the
> values are 0:
>
>> ncview FCT.nc
> (3) Run MET version 6.0 plot_data_plane to plot that file telling it to
> interpret it at a MET NetCDF file. That results in the following error:
>
>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
> level="(0,0,*,*)"; file_type=NETCDF_MET;'
> terminate called after throwing an instance of 'netCDF::exceptions::NcChar'
> what(): NcChar: Attempt to convert between text & numbers
> file: ncAtt.cpp line:104
> Abort
>
> (4) Lastly, I ran (3) above through the debugger and found that it is
> indeed all those "string" types that are causing the problem. I used the
> ncatted utility to change those data types from "string" to "character".
> After doing that and telling MET to interpret it as a CF-compliant NetCDF
> file, I was at least able to plot it. The plot looks bad but at least it
> works. Here are the very long commands I ran:
>
> # Run ncatted to switch types from strings to characters
> ncatted FCT.nc \
> -a FileOrigins,global,o,c,"File example.nc generated 20170409_140422 UTC on
> host eslogin03 by the MET pcp_combine tool" \
> -a MET_version,global,o,c,"V5.2" \
> -a MET_tool,global,o,c,"pcp_combine" \
> -a RunCommand,global,o,c,"Addition: 1 files." \
> -a Projection,global,o,c,"LatLon" \
> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> -a delta_lat,global,o,c,"0.400000 degrees" \
> -a delta_lon,global,o,c,"0.400000 degrees" \
> -a Nlat,global,o,c,"157 grid_points" \
> -a Nlon,global,o,c,"144 grid_points" \
> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> -a institution,global,o,c,"DMD / CPTEC / INPE" \
> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> -a source,global,o,c,"Eta40ens regional weather forecasting model" \
> -a title,global,o,c,"24-hr accummulated precipitation" \
> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
> -a increment,time,o,c,"24 hours in seconds" \
> -a calendar,time,o,c,"standard" \
> -a long_name,time,o,c,"Forecast target time" \
> -a units,member,o,c,"Values from 0 to #_of_members-1" \
> -a long_name,member,o,c,"Members of the ensemble model Eta40ens" \
> -a long_name,lat,o,c,"latitude" \
> -a units,lat,o,c,"degrees_north" \
> -a standard_name,lat,o,c,"latitude" \
> -a long_name,lon,o,c,"longitude" \
> -a units,lon,o,c,"degrees_east" \
> -a standard_name,lon,o,c,"longitude" \
> -a Projection,APCP,o,c,"LatLon" \
> -a units,APCP,o,c,"kg/m^2" \
> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated precipitation" \
> -o FCT_edit.nc
>
> # Run plot_data_plane version 6.0 to plot the file
> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps 'name="APCP";
> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>
>
> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
>>
>> Hi John,
>>
>> I’ve created garcia_data and put the files in your incoming ftp site.
>> Thank you for your help.
>>
>> About those repeated strings that I suppose you are referring to *._deg
>> strings, I’had to create them because one of MET tools complained about the
>> lack of them, and I think it was grid_stat itself. To generate them I took
>> the pcp_combine output as a template but when running the grid_stat command
>> it showed this message to me.
>>
>> Thank you again.
>>
>> 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 *****
>> =================================
>>
>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>> JR Garcia,
>>>
>>> I see that you're having trouble reading this dataset, and I certainly
>>> agree, that error message isn't very helpful. I looked at the ncdump
>>> output you sent and don't see anything obviously wrong. However, I
>> haven't
>>> seen all those repeated "string" values in ncdump output before. Perhaps
>>> there's a netcdf version issue going on.
>>>
>>> If possible, the easiest way for me to debug would be for you to post a
>>> sample file to our anonymous ftp site following these instructions:
>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>> Also please indicate the version of MET that you're using.
>>>
>>> If I can replicate the behavior here, it should be pretty easy to
>> determine
>>> the problem.
>>>
>>> Thanks,
>>> John
>>>
>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via RT <
>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>
>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>> Transaction: Ticket created by roberto.garcia at inpe.br <mailto:
>> roberto.garcia at inpe.br>
>>>> Queue: met_help
>>>> Subject: FileType_None error in GridStat tool
>>>> Owner: Nobody
>>>> Requestors: roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>
>>>> Status: new
>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 <
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>
>>>> Dear John, that met-help ticket which manipulated 90 time slices has
>>>> increased to 101 time slices. Attached are headers of the ncdump command
>>>> for both FSCT.nc and OBS.nc.
>>>>
>>>> I'm running the following command:
>>>>
>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>
>>>> And the entries for the forecast and observation fields is configured
>>>> inside GridStat.cfg are:
>>>>
>>>> // Forecast fields to be verified ==============================
>>>> fcst = {
>>>> field = [
>>>> {
>>>> name = "APCP";
>>>> level = "(0,0,*,*)"; // 24-hour accumulation
>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ] // ORIGINAL
>>>> }
>>>> ];
>>>> }
>>>> // Observation fields to be verified ==============================
>>>> obs = {
>>>> field = [
>>>> {
>>>> name = "APCP";
>>>> level = "(0,*,*)"; // 24-hour accumulation
>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ] // ORIGINAL
>>>> }
>>>> ];
>>>> }
>>>>
>>>> I'm getting the following error:
>>>>
>>>> DEBUG 1: Default Config File:
>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>> GridStatConfig_default
>>>> DEBUG 1: User Config File: GridStat.cfg
>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
>>>> Met2dDataFile object of type "FileType_None".
>>>> ERROR :
>>>> ERROR : Trouble reading forecast file
>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>> Eta40ens_00_036hs.nc"
>>>> ERROR :
>>>>
>>>> The message is not clear but I suppose MET was not able to find out the
>>>> FCST file type. Could you help me, please?
>>>>
>>>> Best regards.
>>>>
>>>> --
>>>> 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!
>>>> =======================================================
>>>>
>>>>
>>>>
>>
>>
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: John Halley Gotway
Time: Mon Apr 17 10:26:49 2017
JR Garcia,
Can you please post a sample one of your converted files to our ftp
site
following these instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
I'll take a look at let you know what I find.
Thanks,
John
On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
met_help at ucar.edu> wrote:
>
> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
> Transaction: Ticket created by roberto.garcia at inpe.br
> Queue: met_help
> Subject: can't set corner for variable "APCP" error
> Owner: Nobody
> Requestors: roberto.garcia at inpe.br
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>
>
> Hi John, I converted all obs and fct NetCDF files to the NetCDF 3
> Classic version and issued the same command, could you please help
me
> interpret this error? What does "corner" refer to?
>
> Thanks
>
>
> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40Grid.nc
> GridStat.cfg -v 4
>
> DEBUG 1: Default Config File:
> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> GridStatConfig_default
> DEBUG 1: User Config File: GridStat.cfg
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -50.2
> DEBUG 4: lon_ll = 83
> DEBUG 4: delta_lat = 0.4
> DEBUG 4: delta_lon = 0.4
> DEBUG 4: Nlat = 157
> DEBUG 4: Nlon = 144
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Latitude/Longitude Grid Data:
> DEBUG 4: lat_ll = -50.2
> DEBUG 4: lon_ll = 82.8
> DEBUG 4: delta_lat = 0.2
> DEBUG 4: delta_lon = 0.2
> DEBUG 4: Nlat = 144
> DEBUG 4: Nlon = 157
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_NcMet".
> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> type "FileType_NcMet".
> WARNING:
> WARNING: parse_conf_interp() -> For neareast neighbor interpolation
> method, resetting method from "UW_MEAN" to "NEAREST" since the
> interpolation width is 1.
> WARNING:
> DEBUG 3: Use the forecast grid.
> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1639511128
> DEBUG 1: Forecast File:
>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_00_036hs.nc
> DEBUG 1: Observation File:
> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
> 20161201_20170228_Eta40Grid.nc
> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
> DEBUG 3: Reading observation data for APCP(0,*,*).
> ERROR :
> ERROR : MetNcFile::data(NcVar *, const LongArray &) const -> can't
set
> corner for variable "APCP"
> ERROR :
>
>
>
> 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 10/04/2017 16:51, John Halley Gotway via RT wrote:
> > JR Garcia,
> >
> > Thanks for sending the sample data file. This is definitely a
NetCDF4
> file
> > using the enhanced data model. MET version 5.2 is not able to
read
> NetCDF4
> > files. The recent release of MET (version 6.0) has been enhanced
to do
> so.
> >
> > I tried a few things:
> >
> > (1) Convert your forecast file from NetCDF4 to 3 using the nccopy
> command.
> > That results in the following error:
> >
> >> nccopy -3 FCT.nc FCT_nc3.nc
> > NetCDF: Not a valid data type or _FillValue type mismatch
> > Location: file nccopy.c; line 788
> >
> > (2) View your file using ncview. It brings up the display but all
the
> > values are 0:
> >
> >> ncview FCT.nc
> > (3) Run MET version 6.0 plot_data_plane to plot that file telling
it to
> > interpret it at a MET NetCDF file. That results in the following
error:
> >
> >> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
> > level="(0,0,*,*)"; file_type=NETCDF_MET;'
> > terminate called after throwing an instance of
> 'netCDF::exceptions::NcChar'
> > what(): NcChar: Attempt to convert between text & numbers
> > file: ncAtt.cpp line:104
> > Abort
> >
> > (4) Lastly, I ran (3) above through the debugger and found that it
is
> > indeed all those "string" types that are causing the problem. I
used the
> > ncatted utility to change those data types from "string" to
"character".
> > After doing that and telling MET to interpret it as a CF-compliant
NetCDF
> > file, I was at least able to plot it. The plot looks bad but at
least it
> > works. Here are the very long commands I ran:
> >
> > # Run ncatted to switch types from strings to characters
> > ncatted FCT.nc \
> > -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
> UTC on
> > host eslogin03 by the MET pcp_combine tool" \
> > -a MET_version,global,o,c,"V5.2" \
> > -a MET_tool,global,o,c,"pcp_combine" \
> > -a RunCommand,global,o,c,"Addition: 1 files." \
> > -a Projection,global,o,c,"LatLon" \
> > -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> > -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> > -a delta_lat,global,o,c,"0.400000 degrees" \
> > -a delta_lon,global,o,c,"0.400000 degrees" \
> > -a Nlat,global,o,c,"157 grid_points" \
> > -a Nlon,global,o,c,"144 grid_points" \
> > -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> > -a institution,global,o,c,"DMD / CPTEC / INPE" \
> > -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> > -a source,global,o,c,"Eta40ens regional weather forecasting model"
\
> > -a title,global,o,c,"24-hr accummulated precipitation" \
> > -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
> > -a increment,time,o,c,"24 hours in seconds" \
> > -a calendar,time,o,c,"standard" \
> > -a long_name,time,o,c,"Forecast target time" \
> > -a units,member,o,c,"Values from 0 to #_of_members-1" \
> > -a long_name,member,o,c,"Members of the ensemble model Eta40ens" \
> > -a long_name,lat,o,c,"latitude" \
> > -a units,lat,o,c,"degrees_north" \
> > -a standard_name,lat,o,c,"latitude" \
> > -a long_name,lon,o,c,"longitude" \
> > -a units,lon,o,c,"degrees_east" \
> > -a standard_name,lon,o,c,"longitude" \
> > -a Projection,APCP,o,c,"LatLon" \
> > -a units,APCP,o,c,"kg/m^2" \
> > -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated precipitation"
\
> > -o FCT_edit.nc
> >
> > # Run plot_data_plane version 6.0 to plot the file
> > met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps 'name="APCP";
> > level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
> >
> >
> > On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
> >>
> >> Hi John,
> >>
> >> I’ve created garcia_data and put the files in your incoming ftp
site.
> >> Thank you for your help.
> >>
> >> About those repeated strings that I suppose you are referring to
*._deg
> >> strings, I’had to create them because one of MET tools complained
about
> the
> >> lack of them, and I think it was grid_stat itself. To generate
them I
> took
> >> the pcp_combine output as a template but when running the
grid_stat
> command
> >> it showed this message to me.
> >>
> >> Thank you again.
> >>
> >> 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 *****
> >> =================================
> >>
> >>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
> >> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>> JR Garcia,
> >>>
> >>> I see that you're having trouble reading this dataset, and I
certainly
> >>> agree, that error message isn't very helpful. I looked at the
ncdump
> >>> output you sent and don't see anything obviously wrong. However,
I
> >> haven't
> >>> seen all those repeated "string" values in ncdump output before.
> Perhaps
> >>> there's a netcdf version issue going on.
> >>>
> >>> If possible, the easiest way for me to debug would be for you to
post a
> >>> sample file to our anonymous ftp site following these
instructions:
> >>> http://www.dtcenter.org/met/users/support/met_help.php#ftp <
> >> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
> >>> Also please indicate the version of MET that you're using.
> >>>
> >>> If I can replicate the behavior here, it should be pretty easy
to
> >> determine
> >>> the problem.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via RT <
> >>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>
> >>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
> >>>> Transaction: Ticket created by roberto.garcia at inpe.br <mailto:
> >> roberto.garcia at inpe.br>
> >>>> Queue: met_help
> >>>> Subject: FileType_None error in GridStat tool
> >>>> Owner: Nobody
> >>>> Requestors: roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br>
> >>>> Status: new
> >>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
> <
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
> >>>>
> >>>> Dear John, that met-help ticket which manipulated 90 time
slices has
> >>>> increased to 101 time slices. Attached are headers of the
ncdump
> command
> >>>> for both FSCT.nc and OBS.nc.
> >>>>
> >>>> I'm running the following command:
> >>>>
> >>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
> >>>>
> >>>> And the entries for the forecast and observation fields is
configured
> >>>> inside GridStat.cfg are:
> >>>>
> >>>> // Forecast fields to be verified
==============================
> >>>> fcst = {
> >>>> field = [
> >>>> {
> >>>> name = "APCP";
> >>>> level = "(0,0,*,*)"; // 24-hour
accumulation
> >>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ]
//
> ORIGINAL
> >>>> }
> >>>> ];
> >>>> }
> >>>> // Observation fields to be verified
==============================
> >>>> obs = {
> >>>> field = [
> >>>> {
> >>>> name = "APCP";
> >>>> level = "(0,*,*)"; // 24-hour accumulation
> >>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ]
//
> ORIGINAL
> >>>> }
> >>>> ];
> >>>> }
> >>>>
> >>>> I'm getting the following error:
> >>>>
> >>>> DEBUG 1: Default Config File:
> >>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >>>> GridStatConfig_default
> >>>> DEBUG 1: User Config File: GridStat.cfg
> >>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> >>>> Met2dDataFile object of type "FileType_None".
> >>>> ERROR :
> >>>> ERROR : Trouble reading forecast file
> >>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
> >> Eta40ens_00_036hs.nc"
> >>>> ERROR :
> >>>>
> >>>> The message is not clear but I suppose MET was not able to find
out
> the
> >>>> FCST file type. Could you help me, please?
> >>>>
> >>>> Best regards.
> >>>>
> >>>> --
> >>>> 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!
> >>>> =======================================================
> >>>>
> >>>>
> >>>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #80169] can't set corner for variable "APCP" error
From: Roberto Garcia (INPE)
Time: Mon Apr 17 11:18:34 2017
Data are there!
Thanks John.
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 17/04/2017 13:26, John Halley Gotway via RT wrote:
> JR Garcia,
>
> Can you please post a sample one of your converted files to our ftp
site
> following these instructions:
>
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> I'll take a look at let you know what I find.
>
> Thanks,
> John
>
> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
> met_help at ucar.edu> wrote:
>
>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>> Transaction: Ticket created by roberto.garcia at inpe.br
>> Queue: met_help
>> Subject: can't set corner for variable "APCP" error
>> Owner: Nobody
>> Requestors: roberto.garcia at inpe.br
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>>
>>
>> Hi John, I converted all obs and fct NetCDF files to the NetCDF 3
>> Classic version and issued the same command, could you please help
me
>> interpret this error? What does "corner" refer to?
>>
>> Thanks
>>
>>
>> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40Grid.nc
>> GridStat.cfg -v 4
>>
>> DEBUG 1: Default Config File:
>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>> GridStatConfig_default
>> DEBUG 1: User Config File: GridStat.cfg
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_NcMet".
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll = -50.2
>> DEBUG 4: lon_ll = 83
>> DEBUG 4: delta_lat = 0.4
>> DEBUG 4: delta_lon = 0.4
>> DEBUG 4: Nlat = 157
>> DEBUG 4: Nlon = 144
>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>> Met2dDataFile object of type "FileType_NcMet".
>> DEBUG 4: Latitude/Longitude Grid Data:
>> DEBUG 4: lat_ll = -50.2
>> DEBUG 4: lon_ll = 82.8
>> DEBUG 4: delta_lat = 0.2
>> DEBUG 4: delta_lon = 0.2
>> DEBUG 4: Nlat = 144
>> DEBUG 4: Nlon = 157
>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
>> type "FileType_NcMet".
>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
>> type "FileType_NcMet".
>> WARNING:
>> WARNING: parse_conf_interp() -> For neareast neighbor interpolation
>> method, resetting method from "UW_MEAN" to "NEAREST" since the
>> interpolation width is 1.
>> WARNING:
>> DEBUG 3: Use the forecast grid.
>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>> GSL_RNG_TYPE=mt19937
>> GSL_RNG_SEED=1639511128
>> DEBUG 1: Forecast File:
>>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_00_036hs.nc
>> DEBUG 1: Observation File:
>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>> 20161201_20170228_Eta40Grid.nc
>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>> DEBUG 3: Reading observation data for APCP(0,*,*).
>> ERROR :
>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't set
>> corner for variable "APCP"
>> ERROR :
>>
>>
>>
>> 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 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>> JR Garcia,
>>>
>>> Thanks for sending the sample data file. This is definitely a
NetCDF4
>> file
>>> using the enhanced data model. MET version 5.2 is not able to
read
>> NetCDF4
>>> files. The recent release of MET (version 6.0) has been enhanced
to do
>> so.
>>> I tried a few things:
>>>
>>> (1) Convert your forecast file from NetCDF4 to 3 using the nccopy
>> command.
>>> That results in the following error:
>>>
>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>> NetCDF: Not a valid data type or _FillValue type mismatch
>>> Location: file nccopy.c; line 788
>>>
>>> (2) View your file using ncview. It brings up the display but all
the
>>> values are 0:
>>>
>>>> ncview FCT.nc
>>> (3) Run MET version 6.0 plot_data_plane to plot that file telling
it to
>>> interpret it at a MET NetCDF file. That results in the following
error:
>>>
>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>> terminate called after throwing an instance of
>> 'netCDF::exceptions::NcChar'
>>> what(): NcChar: Attempt to convert between text & numbers
>>> file: ncAtt.cpp line:104
>>> Abort
>>>
>>> (4) Lastly, I ran (3) above through the debugger and found that it
is
>>> indeed all those "string" types that are causing the problem. I
used the
>>> ncatted utility to change those data types from "string" to
"character".
>>> After doing that and telling MET to interpret it as a CF-compliant
NetCDF
>>> file, I was at least able to plot it. The plot looks bad but at
least it
>>> works. Here are the very long commands I ran:
>>>
>>> # Run ncatted to switch types from strings to characters
>>> ncatted FCT.nc \
>>> -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
>> UTC on
>>> host eslogin03 by the MET pcp_combine tool" \
>>> -a MET_version,global,o,c,"V5.2" \
>>> -a MET_tool,global,o,c,"pcp_combine" \
>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>> -a Projection,global,o,c,"LatLon" \
>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>> -a Nlat,global,o,c,"157 grid_points" \
>>> -a Nlon,global,o,c,"144 grid_points" \
>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>> -a source,global,o,c,"Eta40ens regional weather forecasting model"
\
>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
>>> -a increment,time,o,c,"24 hours in seconds" \
>>> -a calendar,time,o,c,"standard" \
>>> -a long_name,time,o,c,"Forecast target time" \
>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>> -a long_name,member,o,c,"Members of the ensemble model Eta40ens" \
>>> -a long_name,lat,o,c,"latitude" \
>>> -a units,lat,o,c,"degrees_north" \
>>> -a standard_name,lat,o,c,"latitude" \
>>> -a long_name,lon,o,c,"longitude" \
>>> -a units,lon,o,c,"degrees_east" \
>>> -a standard_name,lon,o,c,"longitude" \
>>> -a Projection,APCP,o,c,"LatLon" \
>>> -a units,APCP,o,c,"kg/m^2" \
>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated precipitation"
\
>>> -o FCT_edit.nc
>>>
>>> # Run plot_data_plane version 6.0 to plot the file
>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps 'name="APCP";
>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>
>>>
>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
>>>>
>>>> Hi John,
>>>>
>>>> I’ve created garcia_data and put the files in your incoming ftp
site.
>>>> Thank you for your help.
>>>>
>>>> About those repeated strings that I suppose you are referring to
*._deg
>>>> strings, I’had to create them because one of MET tools complained
about
>> the
>>>> lack of them, and I think it was grid_stat itself. To generate
them I
>> took
>>>> the pcp_combine output as a template but when running the
grid_stat
>> command
>>>> it showed this message to me.
>>>>
>>>> Thank you again.
>>>>
>>>> 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 *****
>>>> =================================
>>>>
>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>> JR Garcia,
>>>>>
>>>>> I see that you're having trouble reading this dataset, and I
certainly
>>>>> agree, that error message isn't very helpful. I looked at the
ncdump
>>>>> output you sent and don't see anything obviously wrong. However,
I
>>>> haven't
>>>>> seen all those repeated "string" values in ncdump output before.
>> Perhaps
>>>>> there's a netcdf version issue going on.
>>>>>
>>>>> If possible, the easiest way for me to debug would be for you to
post a
>>>>> sample file to our anonymous ftp site following these
instructions:
>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>>>> Also please indicate the version of MET that you're using.
>>>>>
>>>>> If I can replicate the behavior here, it should be pretty easy
to
>>>> determine
>>>>> the problem.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via RT <
>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>
>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br <mailto:
>>>> roberto.garcia at inpe.br>
>>>>>> Queue: met_help
>>>>>> Subject: FileType_None error in GridStat tool
>>>>>> Owner: Nobody
>>>>>> Requestors: roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br>
>>>>>> Status: new
>>>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
>> <
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices has
>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
>> command
>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>
>>>>>> I'm running the following command:
>>>>>>
>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>
>>>>>> And the entries for the forecast and observation fields is
configured
>>>>>> inside GridStat.cfg are:
>>>>>>
>>>>>> // Forecast fields to be verified
==============================
>>>>>> fcst = {
>>>>>> field = [
>>>>>> {
>>>>>> name = "APCP";
>>>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
>>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ]
//
>> ORIGINAL
>>>>>> }
>>>>>> ];
>>>>>> }
>>>>>> // Observation fields to be verified
==============================
>>>>>> obs = {
>>>>>> field = [
>>>>>> {
>>>>>> name = "APCP";
>>>>>> level = "(0,*,*)"; // 24-hour
accumulation
>>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ]
//
>> ORIGINAL
>>>>>> }
>>>>>> ];
>>>>>> }
>>>>>>
>>>>>> I'm getting the following error:
>>>>>>
>>>>>> DEBUG 1: Default Config File:
>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>> GridStatConfig_default
>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>> ERROR :
>>>>>> ERROR : Trouble reading forecast file
>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>> Eta40ens_00_036hs.nc"
>>>>>> ERROR :
>>>>>>
>>>>>> The message is not clear but I suppose MET was not able to find
out
>> the
>>>>>> FCST file type. Could you help me, please?
>>>>>>
>>>>>> Best regards.
>>>>>>
>>>>>> --
>>>>>> 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!
>>>>>> =======================================================
>>>>>>
>>>>>>
>>>>>>
>>>>
>>
>>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: John Halley Gotway
Time: Mon Apr 17 12:07:50 2017
JR Garcia,
You have the Nlat and Nlon global attributes set wrong in the
MERGE_20161201_20170228.nc file:
:Nlat = "245 grid_points" ;
:Nlon = "313 grid_points" ;
Those numbers don't match the lat/lon dimensions:
dimensions:
time = 90 ;
lat = 313 ;
lon = 245 ;
I ran the following command to switch them:
ncatted -a Nlat,global,o,c,"313 grid_points" \
-a Nlon,global,o,c,"245 grid_points" \
MERGE_20161201_20170228.nc \
-o MERGE_20161201_20170228_PATCH.nc
After switching that, MET version 5.2 processes them fine.
Also, testing this out using version 6.0 revealed a little bug we
introduced when switching from NetCDF3 to NetCDF4. I'll post a bugfix
for
this as soon as one is available.
In order to run this data through version 6.0, you'll need that
bugfix.
Thanks,
John
On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>
> Data are there!
>
> Thanks John.
>
> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
> > JR Garcia,
> >
> > Can you please post a sample one of your converted files to our
ftp site
> > following these instructions:
> >
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > I'll take a look at let you know what I find.
> >
> > Thanks,
> > John
> >
> > On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
> >> Transaction: Ticket created by roberto.garcia at inpe.br
> >> Queue: met_help
> >> Subject: can't set corner for variable "APCP" error
> >> Owner: Nobody
> >> Requestors: roberto.garcia at inpe.br
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
> >
> >>
> >>
> >> Hi John, I converted all obs and fct NetCDF files to the NetCDF 3
> >> Classic version and issued the same command, could you please
help me
> >> interpret this error? What does "corner" refer to?
> >>
> >> Thanks
> >>
> >>
> >> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40Grid.nc
> >> GridStat.cfg -v 4
> >>
> >> DEBUG 1: Default Config File:
> >> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >> GridStatConfig_default
> >> DEBUG 1: User Config File: GridStat.cfg
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >> Met2dDataFile object of type "FileType_NcMet".
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll = -50.2
> >> DEBUG 4: lon_ll = 83
> >> DEBUG 4: delta_lat = 0.4
> >> DEBUG 4: delta_lon = 0.4
> >> DEBUG 4: Nlat = 157
> >> DEBUG 4: Nlon = 144
> >> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >> Met2dDataFile object of type "FileType_NcMet".
> >> DEBUG 4: Latitude/Longitude Grid Data:
> >> DEBUG 4: lat_ll = -50.2
> >> DEBUG 4: lon_ll = 82.8
> >> DEBUG 4: delta_lat = 0.2
> >> DEBUG 4: delta_lon = 0.2
> >> DEBUG 4: Nlat = 144
> >> DEBUG 4: Nlon = 157
> >> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> >> type "FileType_NcMet".
> >> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
> >> type "FileType_NcMet".
> >> WARNING:
> >> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
> >> method, resetting method from "UW_MEAN" to "NEAREST" since the
> >> interpolation width is 1.
> >> WARNING:
> >> DEBUG 3: Use the forecast grid.
> >> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
> >> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
> >> GSL_RNG_TYPE=mt19937
> >> GSL_RNG_SEED=1639511128
> >> DEBUG 1: Forecast File:
> >>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_00_036hs.nc
> >> DEBUG 1: Observation File:
> >> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
> >> 20161201_20170228_Eta40Grid.nc
> >> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
> >> DEBUG 3: Reading observation data for APCP(0,*,*).
> >> ERROR :
> >> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't set
> >> corner for variable "APCP"
> >> ERROR :
> >>
> >>
> >>
> >> 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 10/04/2017 16:51, John Halley Gotway via RT wrote:
> >>> JR Garcia,
> >>>
> >>> Thanks for sending the sample data file. This is definitely a
NetCDF4
> >> file
> >>> using the enhanced data model. MET version 5.2 is not able to
read
> >> NetCDF4
> >>> files. The recent release of MET (version 6.0) has been
enhanced to do
> >> so.
> >>> I tried a few things:
> >>>
> >>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
> >> command.
> >>> That results in the following error:
> >>>
> >>>> nccopy -3 FCT.nc FCT_nc3.nc
> >>> NetCDF: Not a valid data type or _FillValue type mismatch
> >>> Location: file nccopy.c; line 788
> >>>
> >>> (2) View your file using ncview. It brings up the display but
all the
> >>> values are 0:
> >>>
> >>>> ncview FCT.nc
> >>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling it to
> >>> interpret it at a MET NetCDF file. That results in the
following
> error:
> >>>
> >>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
> >>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
> >>> terminate called after throwing an instance of
> >> 'netCDF::exceptions::NcChar'
> >>> what(): NcChar: Attempt to convert between text & numbers
> >>> file: ncAtt.cpp line:104
> >>> Abort
> >>>
> >>> (4) Lastly, I ran (3) above through the debugger and found that
it is
> >>> indeed all those "string" types that are causing the problem. I
used
> the
> >>> ncatted utility to change those data types from "string" to
> "character".
> >>> After doing that and telling MET to interpret it as a CF-
compliant
> NetCDF
> >>> file, I was at least able to plot it. The plot looks bad but at
least
> it
> >>> works. Here are the very long commands I ran:
> >>>
> >>> # Run ncatted to switch types from strings to characters
> >>> ncatted FCT.nc \
> >>> -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
> >> UTC on
> >>> host eslogin03 by the MET pcp_combine tool" \
> >>> -a MET_version,global,o,c,"V5.2" \
> >>> -a MET_tool,global,o,c,"pcp_combine" \
> >>> -a RunCommand,global,o,c,"Addition: 1 files." \
> >>> -a Projection,global,o,c,"LatLon" \
> >>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> >>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> >>> -a delta_lat,global,o,c,"0.400000 degrees" \
> >>> -a delta_lon,global,o,c,"0.400000 degrees" \
> >>> -a Nlat,global,o,c,"157 grid_points" \
> >>> -a Nlon,global,o,c,"144 grid_points" \
> >>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> >>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
> >>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> >>> -a source,global,o,c,"Eta40ens regional weather forecasting
model" \
> >>> -a title,global,o,c,"24-hr accummulated precipitation" \
> >>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
> >>> -a increment,time,o,c,"24 hours in seconds" \
> >>> -a calendar,time,o,c,"standard" \
> >>> -a long_name,time,o,c,"Forecast target time" \
> >>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
> >>> -a long_name,member,o,c,"Members of the ensemble model Eta40ens"
\
> >>> -a long_name,lat,o,c,"latitude" \
> >>> -a units,lat,o,c,"degrees_north" \
> >>> -a standard_name,lat,o,c,"latitude" \
> >>> -a long_name,lon,o,c,"longitude" \
> >>> -a units,lon,o,c,"degrees_east" \
> >>> -a standard_name,lon,o,c,"longitude" \
> >>> -a Projection,APCP,o,c,"LatLon" \
> >>> -a units,APCP,o,c,"kg/m^2" \
> >>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation" \
> >>> -o FCT_edit.nc
> >>>
> >>> # Run plot_data_plane version 6.0 to plot the file
> >>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
> >>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
> >>>
> >>>
> >>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
> >>>>
> >>>> Hi John,
> >>>>
> >>>> I’ve created garcia_data and put the files in your incoming ftp
site.
> >>>> Thank you for your help.
> >>>>
> >>>> About those repeated strings that I suppose you are referring
to
> *._deg
> >>>> strings, I’had to create them because one of MET tools
complained
> about
> >> the
> >>>> lack of them, and I think it was grid_stat itself. To generate
them I
> >> took
> >>>> the pcp_combine output as a template but when running the
grid_stat
> >> command
> >>>> it showed this message to me.
> >>>>
> >>>> Thank you again.
> >>>>
> >>>> 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 *****
> >>>> =================================
> >>>>
> >>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
> >>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>> JR Garcia,
> >>>>>
> >>>>> I see that you're having trouble reading this dataset, and I
> certainly
> >>>>> agree, that error message isn't very helpful. I looked at the
ncdump
> >>>>> output you sent and don't see anything obviously wrong.
However, I
> >>>> haven't
> >>>>> seen all those repeated "string" values in ncdump output
before.
> >> Perhaps
> >>>>> there's a netcdf version issue going on.
> >>>>>
> >>>>> If possible, the easiest way for me to debug would be for you
to
> post a
> >>>>> sample file to our anonymous ftp site following these
instructions:
> >>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<
> >>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
> >>>>> Also please indicate the version of MET that you're using.
> >>>>>
> >>>>> If I can replicate the behavior here, it should be pretty easy
to
> >>>> determine
> >>>>> the problem.
> >>>>>
> >>>>> Thanks,
> >>>>> John
> >>>>>
> >>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via RT
<
> >>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>
> >>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
> >>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
> >>>> roberto.garcia at inpe.br>
> >>>>>> Queue: met_help
> >>>>>> Subject: FileType_None error in GridStat tool
> >>>>>> Owner: Nobody
> >>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> roberto.garcia at inpe.br>
> >>>>>> Status: new
> >>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=80092
> >> <
> >>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
> >>>>>> Dear John, that met-help ticket which manipulated 90 time
slices has
> >>>>>> increased to 101 time slices. Attached are headers of the
ncdump
> >> command
> >>>>>> for both FSCT.nc and OBS.nc.
> >>>>>>
> >>>>>> I'm running the following command:
> >>>>>>
> >>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
> >>>>>>
> >>>>>> And the entries for the forecast and observation fields is
> configured
> >>>>>> inside GridStat.cfg are:
> >>>>>>
> >>>>>> // Forecast fields to be verified
==============================
> >>>>>> fcst = {
> >>>>>> field = [
> >>>>>> {
> >>>>>> name = "APCP";
> >>>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
> >>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ]
//
> >> ORIGINAL
> >>>>>> }
> >>>>>> ];
> >>>>>> }
> >>>>>> // Observation fields to be verified
==============================
> >>>>>> obs = {
> >>>>>> field = [
> >>>>>> {
> >>>>>> name = "APCP";
> >>>>>> level = "(0,*,*)"; // 24-hour
accumulation
> >>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0 ]
//
> >> ORIGINAL
> >>>>>> }
> >>>>>> ];
> >>>>>> }
> >>>>>>
> >>>>>> I'm getting the following error:
> >>>>>>
> >>>>>> DEBUG 1: Default Config File:
> >>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >>>>>> GridStatConfig_default
> >>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> >>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>> ERROR :
> >>>>>> ERROR : Trouble reading forecast file
> >>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
> >>>> Eta40ens_00_036hs.nc"
> >>>>>> ERROR :
> >>>>>>
> >>>>>> The message is not clear but I suppose MET was not able to
find out
> >> the
> >>>>>> FCST file type. Could you help me, please?
> >>>>>>
> >>>>>> Best regards.
> >>>>>>
> >>>>>> --
> >>>>>> 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!
> >>>>>> =======================================================
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #80169] can't set corner for variable "APCP" error
From: Roberto Garcia (INPE)
Time: Mon Apr 17 12:43:16 2017
Ok John, I inverted the variable names while creating the NetCDF.
It worked!
Thank you very much.
PS: I'm still using v5.2
Best Regards,
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 17/04/2017 15:07, John Halley Gotway via RT wrote:
> JR Garcia,
>
> You have the Nlat and Nlon global attributes set wrong in the
> MERGE_20161201_20170228.nc file:
> :Nlat = "245 grid_points" ;
> :Nlon = "313 grid_points" ;
>
> Those numbers don't match the lat/lon dimensions:
> dimensions:
> time = 90 ;
> lat = 313 ;
> lon = 245 ;
>
> I ran the following command to switch them:
>
> ncatted -a Nlat,global,o,c,"313 grid_points" \
> -a Nlon,global,o,c,"245 grid_points" \
> MERGE_20161201_20170228.nc \
> -o MERGE_20161201_20170228_PATCH.nc
>
> After switching that, MET version 5.2 processes them fine.
>
> Also, testing this out using version 6.0 revealed a little bug we
> introduced when switching from NetCDF3 to NetCDF4. I'll post a
bugfix for
> this as soon as one is available.
>
> In order to run this data through version 6.0, you'll need that
bugfix.
>
> Thanks,
> John
>
>
> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
> met_help at ucar.edu> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>>
>> Data are there!
>>
>> Thanks John.
>>
>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
>>> JR Garcia,
>>>
>>> Can you please post a sample one of your converted files to our
ftp site
>>> following these instructions:
>>>
>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>
>>> I'll take a look at let you know what I find.
>>>
>>> Thanks,
>>> John
>>>
>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>>>> Transaction: Ticket created by roberto.garcia at inpe.br
>>>> Queue: met_help
>>>> Subject: can't set corner for variable "APCP" error
>>>> Owner: Nobody
>>>> Requestors: roberto.garcia at inpe.br
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
>>>>
>>>> Hi John, I converted all obs and fct NetCDF files to the NetCDF 3
>>>> Classic version and issued the same command, could you please
help me
>>>> interpret this error? What does "corner" refer to?
>>>>
>>>> Thanks
>>>>
>>>>
>>>> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40Grid.nc
>>>> GridStat.cfg -v 4
>>>>
>>>> DEBUG 1: Default Config File:
>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>> GridStatConfig_default
>>>> DEBUG 1: User Config File: GridStat.cfg
>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>>> Met2dDataFile object of type "FileType_NcMet".
>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>> DEBUG 4: lat_ll = -50.2
>>>> DEBUG 4: lon_ll = 83
>>>> DEBUG 4: delta_lat = 0.4
>>>> DEBUG 4: delta_lon = 0.4
>>>> DEBUG 4: Nlat = 157
>>>> DEBUG 4: Nlon = 144
>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>>> Met2dDataFile object of type "FileType_NcMet".
>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>> DEBUG 4: lat_ll = -50.2
>>>> DEBUG 4: lon_ll = 82.8
>>>> DEBUG 4: delta_lat = 0.2
>>>> DEBUG 4: delta_lon = 0.2
>>>> DEBUG 4: Nlat = 144
>>>> DEBUG 4: Nlon = 157
>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
>>>> type "FileType_NcMet".
>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
>>>> type "FileType_NcMet".
>>>> WARNING:
>>>> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
>>>> method, resetting method from "UW_MEAN" to "NEAREST" since the
>>>> interpolation width is 1.
>>>> WARNING:
>>>> DEBUG 3: Use the forecast grid.
>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>>>> GSL_RNG_TYPE=mt19937
>>>> GSL_RNG_SEED=1639511128
>>>> DEBUG 1: Forecast File:
>>>>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_00_036hs.nc
>>>> DEBUG 1: Observation File:
>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>>>> 20161201_20170228_Eta40Grid.nc
>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
>>>> ERROR :
>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't set
>>>> corner for variable "APCP"
>>>> ERROR :
>>>>
>>>>
>>>>
>>>> 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 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>>>> JR Garcia,
>>>>>
>>>>> Thanks for sending the sample data file. This is definitely a
NetCDF4
>>>> file
>>>>> using the enhanced data model. MET version 5.2 is not able to
read
>>>> NetCDF4
>>>>> files. The recent release of MET (version 6.0) has been
enhanced to do
>>>> so.
>>>>> I tried a few things:
>>>>>
>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
>>>> command.
>>>>> That results in the following error:
>>>>>
>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
>>>>> Location: file nccopy.c; line 788
>>>>>
>>>>> (2) View your file using ncview. It brings up the display but
all the
>>>>> values are 0:
>>>>>
>>>>>> ncview FCT.nc
>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling it to
>>>>> interpret it at a MET NetCDF file. That results in the
following
>> error:
>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>>>> terminate called after throwing an instance of
>>>> 'netCDF::exceptions::NcChar'
>>>>> what(): NcChar: Attempt to convert between text & numbers
>>>>> file: ncAtt.cpp line:104
>>>>> Abort
>>>>>
>>>>> (4) Lastly, I ran (3) above through the debugger and found that
it is
>>>>> indeed all those "string" types that are causing the problem. I
used
>> the
>>>>> ncatted utility to change those data types from "string" to
>> "character".
>>>>> After doing that and telling MET to interpret it as a CF-
compliant
>> NetCDF
>>>>> file, I was at least able to plot it. The plot looks bad but at
least
>> it
>>>>> works. Here are the very long commands I ran:
>>>>>
>>>>> # Run ncatted to switch types from strings to characters
>>>>> ncatted FCT.nc \
>>>>> -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
>>>> UTC on
>>>>> host eslogin03 by the MET pcp_combine tool" \
>>>>> -a MET_version,global,o,c,"V5.2" \
>>>>> -a MET_tool,global,o,c,"pcp_combine" \
>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>>>> -a Projection,global,o,c,"LatLon" \
>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>>>> -a Nlat,global,o,c,"157 grid_points" \
>>>>> -a Nlon,global,o,c,"144 grid_points" \
>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>>>> -a source,global,o,c,"Eta40ens regional weather forecasting
model" \
>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
>>>>> -a increment,time,o,c,"24 hours in seconds" \
>>>>> -a calendar,time,o,c,"standard" \
>>>>> -a long_name,time,o,c,"Forecast target time" \
>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>>>> -a long_name,member,o,c,"Members of the ensemble model Eta40ens"
\
>>>>> -a long_name,lat,o,c,"latitude" \
>>>>> -a units,lat,o,c,"degrees_north" \
>>>>> -a standard_name,lat,o,c,"latitude" \
>>>>> -a long_name,lon,o,c,"longitude" \
>>>>> -a units,lon,o,c,"degrees_east" \
>>>>> -a standard_name,lon,o,c,"longitude" \
>>>>> -a Projection,APCP,o,c,"LatLon" \
>>>>> -a units,APCP,o,c,"kg/m^2" \
>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation" \
>>>>> -o FCT_edit.nc
>>>>>
>>>>> # Run plot_data_plane version 6.0 to plot the file
>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>>>
>>>>>
>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
>>>>>>
>>>>>> Hi John,
>>>>>>
>>>>>> I’ve created garcia_data and put the files in your incoming ftp
site.
>>>>>> Thank you for your help.
>>>>>>
>>>>>> About those repeated strings that I suppose you are referring
to
>> *._deg
>>>>>> strings, I’had to create them because one of MET tools
complained
>> about
>>>> the
>>>>>> lack of them, and I think it was grid_stat itself. To generate
them I
>>>> took
>>>>>> the pcp_combine output as a template but when running the
grid_stat
>>>> command
>>>>>> it showed this message to me.
>>>>>>
>>>>>> Thank you again.
>>>>>>
>>>>>> 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 *****
>>>>>> =================================
>>>>>>
>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>> JR Garcia,
>>>>>>>
>>>>>>> I see that you're having trouble reading this dataset, and I
>> certainly
>>>>>>> agree, that error message isn't very helpful. I looked at the
ncdump
>>>>>>> output you sent and don't see anything obviously wrong.
However, I
>>>>>> haven't
>>>>>>> seen all those repeated "string" values in ncdump output
before.
>>>> Perhaps
>>>>>>> there's a netcdf version issue going on.
>>>>>>>
>>>>>>> If possible, the easiest way for me to debug would be for you
to
>> post a
>>>>>>> sample file to our anonymous ftp site following these
instructions:
>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>>>>>> Also please indicate the version of MET that you're using.
>>>>>>>
>>>>>>> If I can replicate the behavior here, it should be pretty easy
to
>>>>>> determine
>>>>>>> the problem.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via RT
<
>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>
>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
>>>>>> roberto.garcia at inpe.br>
>>>>>>>> Queue: met_help
>>>>>>>> Subject: FileType_None error in GridStat tool
>>>>>>>> Owner: Nobody
>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
>> roberto.garcia at inpe.br>
>>>>>>>> Status: new
>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
>> Ticket/Display.html?id=80092
>>>> <
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices has
>>>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
>>>> command
>>>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>>>
>>>>>>>> I'm running the following command:
>>>>>>>>
>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>>>
>>>>>>>> And the entries for the forecast and observation fields is
>> configured
>>>>>>>> inside GridStat.cfg are:
>>>>>>>>
>>>>>>>> // Forecast fields to be verified
==============================
>>>>>>>> fcst = {
>>>>>>>> field = [
>>>>>>>> {
>>>>>>>> name = "APCP";
>>>>>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
>>>>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0
] //
>>>> ORIGINAL
>>>>>>>> }
>>>>>>>> ];
>>>>>>>> }
>>>>>>>> // Observation fields to be verified
==============================
>>>>>>>> obs = {
>>>>>>>> field = [
>>>>>>>> {
>>>>>>>> name = "APCP";
>>>>>>>> level = "(0,*,*)"; // 24-hour
accumulation
>>>>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0
] //
>>>> ORIGINAL
>>>>>>>> }
>>>>>>>> ];
>>>>>>>> }
>>>>>>>>
>>>>>>>> I'm getting the following error:
>>>>>>>>
>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>>>> GridStatConfig_default
>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>> new
>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>> ERROR :
>>>>>>>> ERROR : Trouble reading forecast file
>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>>>> Eta40ens_00_036hs.nc"
>>>>>>>> ERROR :
>>>>>>>>
>>>>>>>> The message is not clear but I suppose MET was not able to
find out
>>>> the
>>>>>>>> FCST file type. Could you help me, please?
>>>>>>>>
>>>>>>>> Best regards.
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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!
>>>>>>>> =======================================================
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>
>>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: Roberto Garcia (INPE)
Time: Mon Apr 17 13:56:13 2017
Dear John, can you clarify why the output files were generated to
1970010 000000 valid time and 000000 lead time?
As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
Below is the partial print of the forecasting NetCDF. Shouldn't MET
calculate the correct time according to the time slice I specified in
the config file *level = "(0,0,*,*)"* and its unit *"hours since"*?
What
I'm doing wrong?
variables:
int time(time) ;
time:units = "hours since 1970-01-01 00:00:00 UTC" ;
time:calendar = "standard" ;
time:long_name = "Forecast target time" ;
time = 411036, 411060, 411084, 411108, 411132, 411156, 411180,
411204,
411228, 411252, 411276, 411300, 411324, 411348, 411372, 411396,
411420,
411444, 411468, 411492, 411516, 411540, 411564, 411588, 411612,
411636,
Another questions regarding the config file, please. At the highest
level of grid_stat config file there is a group of entries:
cat_thresh = [ NA ];
cnt_thresh = [ NA ];
cnt_logic = UNION;
wind_thresh = [ NA ];
wind_logic = UNION;
1) Do them control the behavior of the verification in a general
aspect?
Concerning cat_thresh specifically, what happens if I set some
thresholds at it and also inside the fcst and/o obs entries?
2) Why there is cat_thresh entry for both fcst and obs entries?
Wouldn't
a general cat_thresh entry be enough? Does the use of different
cat_thresh values for obs and fcst make sense?
Thank you
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 17/04/2017 15:07, John Halley Gotway via RT wrote:
> JR Garcia,
>
> You have the Nlat and Nlon global attributes set wrong in the
> MERGE_20161201_20170228.nc file:
> :Nlat = "245 grid_points" ;
> :Nlon = "313 grid_points" ;
>
> Those numbers don't match the lat/lon dimensions:
> dimensions:
> time = 90 ;
> lat = 313 ;
> lon = 245 ;
>
> I ran the following command to switch them:
>
> ncatted -a Nlat,global,o,c,"313 grid_points" \
> -a Nlon,global,o,c,"245 grid_points" \
> MERGE_20161201_20170228.nc \
> -o MERGE_20161201_20170228_PATCH.nc
>
> After switching that, MET version 5.2 processes them fine.
>
> Also, testing this out using version 6.0 revealed a little bug we
> introduced when switching from NetCDF3 to NetCDF4. I'll post a
bugfix for
> this as soon as one is available.
>
> In order to run this data through version 6.0, you'll need that
bugfix.
>
> Thanks,
> John
>
>
> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
> met_help at ucar.edu> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>>
>> Data are there!
>>
>> Thanks John.
>>
>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
>>> JR Garcia,
>>>
>>> Can you please post a sample one of your converted files to our
ftp site
>>> following these instructions:
>>>
>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>
>>> I'll take a look at let you know what I find.
>>>
>>> Thanks,
>>> John
>>>
>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>>>> Transaction: Ticket created by roberto.garcia at inpe.br
>>>> Queue: met_help
>>>> Subject: can't set corner for variable "APCP" error
>>>> Owner: Nobody
>>>> Requestors: roberto.garcia at inpe.br
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
>>>>
>>>> Hi John, I converted all obs and fct NetCDF files to the NetCDF 3
>>>> Classic version and issued the same command, could you please
help me
>>>> interpret this error? What does "corner" refer to?
>>>>
>>>> Thanks
>>>>
>>>>
>>>> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40Grid.nc
>>>> GridStat.cfg -v 4
>>>>
>>>> DEBUG 1: Default Config File:
>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>> GridStatConfig_default
>>>> DEBUG 1: User Config File: GridStat.cfg
>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>>> Met2dDataFile object of type "FileType_NcMet".
>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>> DEBUG 4: lat_ll = -50.2
>>>> DEBUG 4: lon_ll = 83
>>>> DEBUG 4: delta_lat = 0.4
>>>> DEBUG 4: delta_lon = 0.4
>>>> DEBUG 4: Nlat = 157
>>>> DEBUG 4: Nlon = 144
>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>>> Met2dDataFile object of type "FileType_NcMet".
>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>> DEBUG 4: lat_ll = -50.2
>>>> DEBUG 4: lon_ll = 82.8
>>>> DEBUG 4: delta_lat = 0.2
>>>> DEBUG 4: delta_lon = 0.2
>>>> DEBUG 4: Nlat = 144
>>>> DEBUG 4: Nlon = 157
>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
>>>> type "FileType_NcMet".
>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object of
>>>> type "FileType_NcMet".
>>>> WARNING:
>>>> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
>>>> method, resetting method from "UW_MEAN" to "NEAREST" since the
>>>> interpolation width is 1.
>>>> WARNING:
>>>> DEBUG 3: Use the forecast grid.
>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>>>> GSL_RNG_TYPE=mt19937
>>>> GSL_RNG_SEED=1639511128
>>>> DEBUG 1: Forecast File:
>>>>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_00_036hs.nc
>>>> DEBUG 1: Observation File:
>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>>>> 20161201_20170228_Eta40Grid.nc
>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
>>>> ERROR :
>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't set
>>>> corner for variable "APCP"
>>>> ERROR :
>>>>
>>>>
>>>>
>>>> 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 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>>>> JR Garcia,
>>>>>
>>>>> Thanks for sending the sample data file. This is definitely a
NetCDF4
>>>> file
>>>>> using the enhanced data model. MET version 5.2 is not able to
read
>>>> NetCDF4
>>>>> files. The recent release of MET (version 6.0) has been
enhanced to do
>>>> so.
>>>>> I tried a few things:
>>>>>
>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
>>>> command.
>>>>> That results in the following error:
>>>>>
>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
>>>>> Location: file nccopy.c; line 788
>>>>>
>>>>> (2) View your file using ncview. It brings up the display but
all the
>>>>> values are 0:
>>>>>
>>>>>> ncview FCT.nc
>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling it to
>>>>> interpret it at a MET NetCDF file. That results in the
following
>> error:
>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>>>> terminate called after throwing an instance of
>>>> 'netCDF::exceptions::NcChar'
>>>>> what(): NcChar: Attempt to convert between text & numbers
>>>>> file: ncAtt.cpp line:104
>>>>> Abort
>>>>>
>>>>> (4) Lastly, I ran (3) above through the debugger and found that
it is
>>>>> indeed all those "string" types that are causing the problem. I
used
>> the
>>>>> ncatted utility to change those data types from "string" to
>> "character".
>>>>> After doing that and telling MET to interpret it as a CF-
compliant
>> NetCDF
>>>>> file, I was at least able to plot it. The plot looks bad but at
least
>> it
>>>>> works. Here are the very long commands I ran:
>>>>>
>>>>> # Run ncatted to switch types from strings to characters
>>>>> ncatted FCT.nc \
>>>>> -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
>>>> UTC on
>>>>> host eslogin03 by the MET pcp_combine tool" \
>>>>> -a MET_version,global,o,c,"V5.2" \
>>>>> -a MET_tool,global,o,c,"pcp_combine" \
>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>>>> -a Projection,global,o,c,"LatLon" \
>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>>>> -a Nlat,global,o,c,"157 grid_points" \
>>>>> -a Nlon,global,o,c,"144 grid_points" \
>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>>>> -a source,global,o,c,"Eta40ens regional weather forecasting
model" \
>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
>>>>> -a increment,time,o,c,"24 hours in seconds" \
>>>>> -a calendar,time,o,c,"standard" \
>>>>> -a long_name,time,o,c,"Forecast target time" \
>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>>>> -a long_name,member,o,c,"Members of the ensemble model Eta40ens"
\
>>>>> -a long_name,lat,o,c,"latitude" \
>>>>> -a units,lat,o,c,"degrees_north" \
>>>>> -a standard_name,lat,o,c,"latitude" \
>>>>> -a long_name,lon,o,c,"longitude" \
>>>>> -a units,lon,o,c,"degrees_east" \
>>>>> -a standard_name,lon,o,c,"longitude" \
>>>>> -a Projection,APCP,o,c,"LatLon" \
>>>>> -a units,APCP,o,c,"kg/m^2" \
>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation" \
>>>>> -o FCT_edit.nc
>>>>>
>>>>> # Run plot_data_plane version 6.0 to plot the file
>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>>>
>>>>>
>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
>>>>>>
>>>>>> Hi John,
>>>>>>
>>>>>> I’ve created garcia_data and put the files in your incoming ftp
site.
>>>>>> Thank you for your help.
>>>>>>
>>>>>> About those repeated strings that I suppose you are referring
to
>> *._deg
>>>>>> strings, I’had to create them because one of MET tools
complained
>> about
>>>> the
>>>>>> lack of them, and I think it was grid_stat itself. To generate
them I
>>>> took
>>>>>> the pcp_combine output as a template but when running the
grid_stat
>>>> command
>>>>>> it showed this message to me.
>>>>>>
>>>>>> Thank you again.
>>>>>>
>>>>>> 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 *****
>>>>>> =================================
>>>>>>
>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>> JR Garcia,
>>>>>>>
>>>>>>> I see that you're having trouble reading this dataset, and I
>> certainly
>>>>>>> agree, that error message isn't very helpful. I looked at the
ncdump
>>>>>>> output you sent and don't see anything obviously wrong.
However, I
>>>>>> haven't
>>>>>>> seen all those repeated "string" values in ncdump output
before.
>>>> Perhaps
>>>>>>> there's a netcdf version issue going on.
>>>>>>>
>>>>>>> If possible, the easiest way for me to debug would be for you
to
>> post a
>>>>>>> sample file to our anonymous ftp site following these
instructions:
>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>>>>>> Also please indicate the version of MET that you're using.
>>>>>>>
>>>>>>> If I can replicate the behavior here, it should be pretty easy
to
>>>>>> determine
>>>>>>> the problem.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via RT
<
>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>
>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
>>>>>> roberto.garcia at inpe.br>
>>>>>>>> Queue: met_help
>>>>>>>> Subject: FileType_None error in GridStat tool
>>>>>>>> Owner: Nobody
>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
>> roberto.garcia at inpe.br>
>>>>>>>> Status: new
>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
>> Ticket/Display.html?id=80092
>>>> <
>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices has
>>>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
>>>> command
>>>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>>>
>>>>>>>> I'm running the following command:
>>>>>>>>
>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>>>
>>>>>>>> And the entries for the forecast and observation fields is
>> configured
>>>>>>>> inside GridStat.cfg are:
>>>>>>>>
>>>>>>>> // Forecast fields to be verified
==============================
>>>>>>>> fcst = {
>>>>>>>> field = [
>>>>>>>> {
>>>>>>>> name = "APCP";
>>>>>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
>>>>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0
] //
>>>> ORIGINAL
>>>>>>>> }
>>>>>>>> ];
>>>>>>>> }
>>>>>>>> // Observation fields to be verified
==============================
>>>>>>>> obs = {
>>>>>>>> field = [
>>>>>>>> {
>>>>>>>> name = "APCP";
>>>>>>>> level = "(0,*,*)"; // 24-hour
accumulation
>>>>>>>> cat_thresh = [ NA ]; // [ >1.0, >=5.0
] //
>>>> ORIGINAL
>>>>>>>> }
>>>>>>>> ];
>>>>>>>> }
>>>>>>>>
>>>>>>>> I'm getting the following error:
>>>>>>>>
>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>>>> GridStatConfig_default
>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>> new
>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>> ERROR :
>>>>>>>> ERROR : Trouble reading forecast file
>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>>>> Eta40ens_00_036hs.nc"
>>>>>>>> ERROR :
>>>>>>>>
>>>>>>>> The message is not clear but I suppose MET was not able to
find out
>>>> the
>>>>>>>> FCST file type. Could you help me, please?
>>>>>>>>
>>>>>>>> Best regards.
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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!
>>>>>>>> =======================================================
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>
>>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: John Halley Gotway
Time: Mon Apr 17 14:48:20 2017
JR Garcia,
Yes, you can set the "cat_thresh" separately for each entry in the
"fcst.field" and "obs.field" arrays.
Usually people run Grid-Stat to compare the same type of data from
both the
forecast and observation datasets but there is no reason why you have
to.
For example, you have the flexibility to compare forecast temperature
to
observed precipitation. That probably won't yield very meaningful
results,
but if you did that, you'd probably want to specify different
thresholds
for each field.
But you're right, you can just specify "cat_thresh" once outside the
"fcst"
and "obs" settings and that one setting will be applied to both. See
example below.
Next... MET supports 3 different flavors of NetCDF, and the timing
information is stored differently in them. Please just try telling
MET to
interpret your data following the CF-conventions using: file_type =
NETCDF_NCCF; Since we want it apply to both the "fcst" and "obs", I
just
defined it once at the top-level context of the config file. And I've
also
included that in the Grid-Stat config example listed below.
Thanks,
John
cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
file_type = NETCDF_NCCF;
// Forecast fields to be verified ==============================
fcst = {
field = [
{
name = "APCP";
level = "(0,0,*,*)"; // 24-hour accumulation
}
];
}
// Observation fields to be verified ==============================
obs = {
field = [
{
name = "APCP";
level = "(0,*,*)"; // 24-hour accumulation
}
];
}
As for the issue with the timestamps,
On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>
> Dear John, can you clarify why the output files were generated to
> 1970010 000000 valid time and 000000 lead time?
>
> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
>
> Below is the partial print of the forecasting NetCDF. Shouldn't MET
> calculate the correct time according to the time slice I specified
in
> the config file *level = "(0,0,*,*)"* and its unit *"hours since"*?
What
> I'm doing wrong?
>
> variables:
> int time(time) ;
> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
> time:calendar = "standard" ;
> time:long_name = "Forecast target time" ;
>
> time = 411036, 411060, 411084, 411108, 411132, 411156, 411180,
411204,
> 411228, 411252, 411276, 411300, 411324, 411348, 411372, 411396,
> 411420,
> 411444, 411468, 411492, 411516, 411540, 411564, 411588, 411612,
> 411636,
>
>
> Another questions regarding the config file, please. At the highest
> level of grid_stat config file there is a group of entries:
>
> cat_thresh = [ NA ];
> cnt_thresh = [ NA ];
> cnt_logic = UNION;
> wind_thresh = [ NA ];
> wind_logic = UNION;
>
> 1) Do them control the behavior of the verification in a general
aspect?
> Concerning cat_thresh specifically, what happens if I set some
> thresholds at it and also inside the fcst and/o obs entries?
>
> 2) Why there is cat_thresh entry for both fcst and obs entries?
Wouldn't
> a general cat_thresh entry be enough? Does the use of different
> cat_thresh values for obs and fcst make sense?
>
> Thank you
>
>
> 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 17/04/2017 15:07, John Halley Gotway via RT wrote:
> > JR Garcia,
> >
> > You have the Nlat and Nlon global attributes set wrong in the
> > MERGE_20161201_20170228.nc file:
> > :Nlat = "245 grid_points" ;
> > :Nlon = "313 grid_points" ;
> >
> > Those numbers don't match the lat/lon dimensions:
> > dimensions:
> > time = 90 ;
> > lat = 313 ;
> > lon = 245 ;
> >
> > I ran the following command to switch them:
> >
> > ncatted -a Nlat,global,o,c,"313 grid_points" \
> > -a Nlon,global,o,c,"245 grid_points" \
> > MERGE_20161201_20170228.nc \
> > -o MERGE_20161201_20170228_PATCH.nc
> >
> > After switching that, MET version 5.2 processes them fine.
> >
> > Also, testing this out using version 6.0 revealed a little bug we
> > introduced when switching from NetCDF3 to NetCDF4. I'll post a
bugfix
> for
> > this as soon as one is available.
> >
> > In order to run this data through version 6.0, you'll need that
bugfix.
> >
> > Thanks,
> > John
> >
> >
> > On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
> > met_help at ucar.edu> wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
> >>
> >> Data are there!
> >>
> >> Thanks John.
> >>
> >> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
> >>> JR Garcia,
> >>>
> >>> Can you please post a sample one of your converted files to our
ftp
> site
> >>> following these instructions:
> >>>
> >>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>
> >>> I'll take a look at let you know what I find.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
> >>>> Transaction: Ticket created by roberto.garcia at inpe.br
> >>>> Queue: met_help
> >>>> Subject: can't set corner for variable "APCP" error
> >>>> Owner: Nobody
> >>>> Requestors: roberto.garcia at inpe.br
> >>>> Status: new
> >>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> ket/Display.html?id=80169
> >>>>
> >>>> Hi John, I converted all obs and fct NetCDF files to the NetCDF
3
> >>>> Classic version and issued the same command, could you please
help me
> >>>> interpret this error? What does "corner" refer to?
> >>>>
> >>>> Thanks
> >>>>
> >>>>
> >>>> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
> rid.nc
> >>>> GridStat.cfg -v 4
> >>>>
> >>>> DEBUG 1: Default Config File:
> >>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >>>> GridStatConfig_default
> >>>> DEBUG 1: User Config File: GridStat.cfg
> >>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> >>>> Met2dDataFile object of type "FileType_NcMet".
> >>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>> DEBUG 4: lat_ll = -50.2
> >>>> DEBUG 4: lon_ll = 83
> >>>> DEBUG 4: delta_lat = 0.4
> >>>> DEBUG 4: delta_lon = 0.4
> >>>> DEBUG 4: Nlat = 157
> >>>> DEBUG 4: Nlon = 144
> >>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> >>>> Met2dDataFile object of type "FileType_NcMet".
> >>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>> DEBUG 4: lat_ll = -50.2
> >>>> DEBUG 4: lon_ll = 82.8
> >>>> DEBUG 4: delta_lat = 0.2
> >>>> DEBUG 4: delta_lon = 0.2
> >>>> DEBUG 4: Nlat = 144
> >>>> DEBUG 4: Nlon = 157
> >>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of
> >>>> type "FileType_NcMet".
> >>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
> of
> >>>> type "FileType_NcMet".
> >>>> WARNING:
> >>>> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
> >>>> method, resetting method from "UW_MEAN" to "NEAREST" since the
> >>>> interpolation width is 1.
> >>>> WARNING:
> >>>> DEBUG 3: Use the forecast grid.
> >>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
> >>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
> >>>> GSL_RNG_TYPE=mt19937
> >>>> GSL_RNG_SEED=1639511128
> >>>> DEBUG 1: Forecast File:
> >>>> /stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
> 00_036hs.nc
> >>>> DEBUG 1: Observation File:
> >>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
> >>>> 20161201_20170228_Eta40Grid.nc
> >>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
> >>>> DEBUG 3: Reading observation data for APCP(0,*,*).
> >>>> ERROR :
> >>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't
> set
> >>>> corner for variable "APCP"
> >>>> ERROR :
> >>>>
> >>>>
> >>>>
> >>>> 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 <+55%2012%203208-7966>
> >>>> -------------------------------------------------------
> >>>> SAVE NATURAL RESOURCES!
> >>>> =======================================================
> >>>>
> >>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
> >>>>> JR Garcia,
> >>>>>
> >>>>> Thanks for sending the sample data file. This is definitely a
> NetCDF4
> >>>> file
> >>>>> using the enhanced data model. MET version 5.2 is not able to
read
> >>>> NetCDF4
> >>>>> files. The recent release of MET (version 6.0) has been
enhanced to
> do
> >>>> so.
> >>>>> I tried a few things:
> Until the NCO sys admins can get it installed in a more general
area, this
> MET installation is available for use. We will be rolling out some
patches
> shortly, at which point I will update this installation.
> >>>>>
> >>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
> >>>> command.
> >>>>> That results in the following error:
> >>>>>
> >>>>>> nccopy -3 FCT.nc FCT_nc3.nc
> >>>>> NetCDF: Not a valid data type or _FillValue type mismatch
> >>>>> Location: file nccopy.c; line 788
> >>>>>
> >>>>> (2) View your file using ncview. It brings up the display but
all
> the
> >>>>> values are 0:
> >>>>>
> >>>>>> ncview FCT.nc
> >>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling it
> to
> >>>>> interpret it at a MET NetCDF file. That results in the
following
> >> error:
> >>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
> >>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
> >>>>> terminate called after throwing an instance of
> >>>> 'netCDF::exceptions::NcChar'
> >>>>> what(): NcChar: Attempt to convert between text &
numbers
> >>>>> file: ncAtt.cpp line:104
> >>>>> Abort
> >>>>>
> >>>>> (4) Lastly, I ran (3) above through the debugger and found
that it is
> >>>>> indeed all those "string" types that are causing the problem.
I used
> >> the
> >>>>> ncatted utility to change those data types from "string" to
> >> "character".
> >>>>> After doing that and telling MET to interpret it as a CF-
compliant
> >> NetCDF
> >>>>> file, I was at least able to plot it. The plot looks bad but
at
> least
> >> it
> >>>>> works. Here are the very long commands I ran:
> >>>>>
> >>>>> # Run ncatted to switch types from strings to characters
> >>>>> ncatted FCT.nc \
> >>>>> -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
> >>>> UTC on
> >>>>> host eslogin03 by the MET pcp_combine tool" \
> >>>>> -a MET_version,global,o,c,"V5.2" \
> >>>>> -a MET_tool,global,o,c,"pcp_combine" \
> >>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
> >>>>> -a Projection,global,o,c,"LatLon" \
> >>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> >>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> >>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
> >>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
> >>>>> -a Nlat,global,o,c,"157 grid_points" \
> >>>>> -a Nlon,global,o,c,"144 grid_points" \
> >>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> >>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
> >>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> >>>>> -a source,global,o,c,"Eta40ens regional weather forecasting
model" \
> >>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
> >>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
> >>>>> -a increment,time,o,c,"24 hours in seconds" \
> >>>>> -a calendar,time,o,c,"standard" \
> >>>>> -a long_name,time,o,c,"Forecast target time" \
> >>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
> >>>>> -a long_name,member,o,c,"Members of the ensemble model
Eta40ens" \
> >>>>> -a long_name,lat,o,c,"latitude" \
> >>>>> -a units,lat,o,c,"degrees_north" \
> >>>>> -a standard_name,lat,o,c,"latitude" \
> >>>>> -a long_name,lon,o,c,"longitude" \
> >>>>> -a units,lon,o,c,"degrees_east" \
> >>>>> -a standard_name,lon,o,c,"longitude" \
> >>>>> -a Projection,APCP,o,c,"LatLon" \
> >>>>> -a units,APCP,o,c,"kg/m^2" \
> >>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation" \
> >>>>> -o FCT_edit.nc
> >>>>>
> >>>>> # Run plot_data_plane version 6.0 to plot the file
> >>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
> >>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
> >>>>>
> >>>>>
> >>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
>
> >>>>>>
> >>>>>> Hi John,
> >>>>>>
> >>>>>> I’ve created garcia_data and put the files in your incoming
ftp
> site.
> >>>>>> Thank you for your help.
> >>>>>>
> >>>>>> About those repeated strings that I suppose you are referring
to
> >> *._deg
> >>>>>> strings, I’had to create them because one of MET tools
complained
> >> about
> >>>> the
> >>>>>> lack of them, and I think it was grid_stat itself. To
generate them
> I
> >>>> took
> >>>>>> the pcp_combine output as a template but when running the
grid_stat
> >>>> command
> >>>>>> it showed this message to me.
> >>>>>>
> >>>>>> Thank you again.
> >>>>>>
> >>>>>> 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 *****
> >>>>>> =================================
> >>>>>>
> >>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
> >>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>> JR Garcia,
> >>>>>>>
> >>>>>>> I see that you're having trouble reading this dataset, and I
> >> certainly
> >>>>>>> agree, that error message isn't very helpful. I looked at
the
> ncdump
> >>>>>>> output you sent and don't see anything obviously wrong.
However, I
> >>>>>> haven't
> >>>>>>> seen all those repeated "string" values in ncdump output
before.
> >>>> Perhaps
> >>>>>>> there's a netcdf version issue going on.
> >>>>>>>
> >>>>>>> If possible, the easiest way for me to debug would be for
you to
> >> post a
> >>>>>>> sample file to our anonymous ftp site following these
instructions:
> >>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
> >>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
> >>>>>>> Also please indicate the version of MET that you're using.
> >>>>>>>
> >>>>>>> If I can replicate the behavior here, it should be pretty
easy to
> >>>>>> determine
> >>>>>>> the problem.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> John
> >>>>>>>
> >>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via
RT <
> >>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>>
> >>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
> >>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
> >>>>>> roberto.garcia at inpe.br>
> >>>>>>>> Queue: met_help
> >>>>>>>> Subject: FileType_None error in GridStat tool
> >>>>>>>> Owner: Nobody
> >>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> >> roberto.garcia at inpe.br>
> >>>>>>>> Status: new
> >>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
> >> Ticket/Display.html?id=80092
> >>>> <
> >>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
> >>>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices
> has
> >>>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
> >>>> command
> >>>>>>>> for both FSCT.nc and OBS.nc.
> >>>>>>>>
> >>>>>>>> I'm running the following command:
> >>>>>>>>
> >>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
> >>>>>>>>
> >>>>>>>> And the entries for the forecast and observation fields is
> >> configured
> >>>>>>>> inside GridStat.cfg are:
> >>>>>>>>
> >>>>>>>> // Forecast fields to be verified
==============================
> >>>>>>>> fcst = {
> >>>>>>>> field = [
> >>>>>>>> {
> >>>>>>>> name = "APCP";
> >>>>>>>> level = "(0,0,*,*)"; // 24-hour
> accumulation
> >>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0 ] //
> >>>> ORIGINAL
> >>>>>>>> }
> >>>>>>>> ];
> >>>>>>>> }
> >>>>>>>> // Observation fields to be verified
> ==============================
> >>>>>>>> obs = {
> >>>>>>>> field = [
> >>>>>>>> {
> >>>>>>>> name = "APCP";
> >>>>>>>> level = "(0,*,*)"; // 24-hour
accumulation
> >>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0 ] //
> >>>> ORIGINAL
> >>>>>>>> }
> >>>>>>>> ];
> >>>>>>>> }
> >>>>>>>>
> >>>>>>>> I'm getting the following error:
> >>>>>>>>
> >>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >>>>>>>> GridStatConfig_default
> >>>>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>>>> DEBUG 4: Me
> Until the NCO sys admins can get it installed in a more general
area, this
> MET installation is available for use. We will be rolling out some
patches
> shortly, at which point I will update this installation.
> t2dDataFileFactory::new_met_2d_data_file() -> created
> >> new
> >>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>> ERROR :
> >>>>>>>> ERROR : Trouble reading forecast file
> >>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
> >>>>>> Eta40ens_00_036hs.nc"
> >>>>>>>> ERROR :
> >>>>>>>>
> >>>>>>>> The message is not clear but I suppose MET was not able to
find
> out
> >>>> the
> >>>>>>>> FCST file type. Could you help me, please?
> >>>>>>>>
> >>>>>>>> Best regards.
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> 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 <+55%2012%203208-7966>
> >>>>>>>> -------------------------------------------------------
> >>>>>>>> SAVE NATURAL RESOURCES!
> >>>>>>>> =======================================================
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #80169] can't set corner for variable "APCP" error
From: Roberto Garcia (INPE)
Time: Mon Apr 17 15:11:07 2017
Ok, John. Thanks again. It worked! I think we are getting there!
Now, I'm wondering what element can change the Lead Time in the file
name. Can it be changed using grid_stat or it is a standard name
format
that serves all MET tools and some of them can change it?
grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
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 17/04/2017 17:48, John Halley Gotway via RT wrote:
> JR Garcia,
>
> Yes, you can set the "cat_thresh" separately for each entry in the
> "fcst.field" and "obs.field" arrays.
>
> Usually people run Grid-Stat to compare the same type of data from
both the
> forecast and observation datasets but there is no reason why you
have to.
> For example, you have the flexibility to compare forecast
temperature to
> observed precipitation. That probably won't yield very meaningful
results,
> but if you did that, you'd probably want to specify different
thresholds
> for each field.
>
> But you're right, you can just specify "cat_thresh" once outside the
"fcst"
> and "obs" settings and that one setting will be applied to both.
See
> example below.
>
> Next... MET supports 3 different flavors of NetCDF, and the timing
> information is stored differently in them. Please just try telling
MET to
> interpret your data following the CF-conventions using: file_type =
> NETCDF_NCCF; Since we want it apply to both the "fcst" and "obs",
I just
> defined it once at the top-level context of the config file. And
I've also
> included that in the Grid-Stat config example listed below.
>
> Thanks,
> John
>
> cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
> file_type = NETCDF_NCCF;
>
> // Forecast fields to be verified ==============================
> fcst = {
> field = [
> {
> name = "APCP";
> level = "(0,0,*,*)"; // 24-hour accumulation
> }
> ];
> }
> // Observation fields to be verified ==============================
> obs = {
> field = [
> {
> name = "APCP";
> level = "(0,*,*)"; // 24-hour accumulation
> }
> ];
> }
>
> As for the issue with the timestamps,
>
>
>
>
> On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT <
> met_help at ucar.edu> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>>
>> Dear John, can you clarify why the output files were generated to
>> 1970010 000000 valid time and 000000 lead time?
>>
>> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
>>
>> Below is the partial print of the forecasting NetCDF. Shouldn't MET
>> calculate the correct time according to the time slice I specified
in
>> the config file *level = "(0,0,*,*)"* and its unit *"hours since"*?
What
>> I'm doing wrong?
>>
>> variables:
>> int time(time) ;
>> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
>> time:calendar = "standard" ;
>> time:long_name = "Forecast target time" ;
>>
>> time = 411036, 411060, 411084, 411108, 411132, 411156, 411180,
411204,
>> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
411396,
>> 411420,
>> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
411612,
>> 411636,
>>
>>
>> Another questions regarding the config file, please. At the highest
>> level of grid_stat config file there is a group of entries:
>>
>> cat_thresh = [ NA ];
>> cnt_thresh = [ NA ];
>> cnt_logic = UNION;
>> wind_thresh = [ NA ];
>> wind_logic = UNION;
>>
>> 1) Do them control the behavior of the verification in a general
aspect?
>> Concerning cat_thresh specifically, what happens if I set some
>> thresholds at it and also inside the fcst and/o obs entries?
>>
>> 2) Why there is cat_thresh entry for both fcst and obs entries?
Wouldn't
>> a general cat_thresh entry be enough? Does the use of different
>> cat_thresh values for obs and fcst make sense?
>>
>> Thank you
>>
>>
>> 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 17/04/2017 15:07, John Halley Gotway via RT wrote:
>>> JR Garcia,
>>>
>>> You have the Nlat and Nlon global attributes set wrong in the
>>> MERGE_20161201_20170228.nc file:
>>> :Nlat = "245 grid_points" ;
>>> :Nlon = "313 grid_points" ;
>>>
>>> Those numbers don't match the lat/lon dimensions:
>>> dimensions:
>>> time = 90 ;
>>> lat = 313 ;
>>> lon = 245 ;
>>>
>>> I ran the following command to switch them:
>>>
>>> ncatted -a Nlat,global,o,c,"313 grid_points" \
>>> -a Nlon,global,o,c,"245 grid_points" \
>>> MERGE_20161201_20170228.nc \
>>> -o MERGE_20161201_20170228_PATCH.nc
>>>
>>> After switching that, MET version 5.2 processes them fine.
>>>
>>> Also, testing this out using version 6.0 revealed a little bug we
>>> introduced when switching from NetCDF3 to NetCDF4. I'll post a
bugfix
>> for
>>> this as soon as one is available.
>>>
>>> In order to run this data through version 6.0, you'll need that
bugfix.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
>>> met_help at ucar.edu> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>>>>
>>>> Data are there!
>>>>
>>>> Thanks John.
>>>>
>>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
>>>>> JR Garcia,
>>>>>
>>>>> Can you please post a sample one of your converted files to our
ftp
>> site
>>>>> following these instructions:
>>>>>
>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>
>>>>> I'll take a look at let you know what I find.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT <
>>>>> met_help at ucar.edu> wrote:
>>>>>
>>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
>>>>>> Queue: met_help
>>>>>> Subject: can't set corner for variable "APCP" error
>>>>>> Owner: Nobody
>>>>>> Requestors: roberto.garcia at inpe.br
>>>>>> Status: new
>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
>> ket/Display.html?id=80169
>>>>>> Hi John, I converted all obs and fct NetCDF files to the NetCDF
3
>>>>>> Classic version and issued the same command, could you please
help me
>>>>>> interpret this error? What does "corner" refer to?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>>
>>>>>> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
>> rid.nc
>>>>>> GridStat.cfg -v 4
>>>>>>
>>>>>> DEBUG 1: Default Config File:
>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>> GridStatConfig_default
>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>> DEBUG 4: lon_ll = 83
>>>>>> DEBUG 4: delta_lat = 0.4
>>>>>> DEBUG 4: delta_lon = 0.4
>>>>>> DEBUG 4: Nlat = 157
>>>>>> DEBUG 4: Nlon = 144
>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>> DEBUG 4: lon_ll = 82.8
>>>>>> DEBUG 4: delta_lat = 0.2
>>>>>> DEBUG 4: delta_lon = 0.2
>>>>>> DEBUG 4: Nlat = 144
>>>>>> DEBUG 4: Nlon = 157
>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
>> of
>>>>>> type "FileType_NcMet".
>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo
object
>> of
>>>>>> type "FileType_NcMet".
>>>>>> WARNING:
>>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
>>>>>> method, resetting method from "UW_MEAN" to "NEAREST" since the
>>>>>> interpolation width is 1.
>>>>>> WARNING:
>>>>>> DEBUG 3: Use the forecast grid.
>>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
lat_ll:
>>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>>>>>> GSL_RNG_TYPE=mt19937
>>>>>> GSL_RNG_SEED=1639511128
>>>>>> DEBUG 1: Forecast File:
>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
>> 00_036hs.nc
>>>>>> DEBUG 1: Observation File:
>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>>>>>> 20161201_20170228_Eta40Grid.nc
>>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
>>>>>> ERROR :
>>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't
>> set
>>>>>> corner for variable "APCP"
>>>>>> ERROR :
>>>>>>
>>>>>>
>>>>>>
>>>>>> 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 <+55%2012%203208-7966>
>>>>>> -------------------------------------------------------
>>>>>> SAVE NATURAL RESOURCES!
>>>>>> =======================================================
>>>>>>
>>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>>>>>> JR Garcia,
>>>>>>>
>>>>>>> Thanks for sending the sample data file. This is definitely a
>> NetCDF4
>>>>>> file
>>>>>>> using the enhanced data model. MET version 5.2 is not able to
read
>>>>>> NetCDF4
>>>>>>> files. The recent release of MET (version 6.0) has been
enhanced to
>> do
>>>>>> so.
>>>>>>> I tried a few things:
>> Until the NCO sys admins can get it installed in a more general
area, this
>> MET installation is available for use. We will be rolling out some
patches
>> shortly, at which point I will update this installation.
>>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
>>>>>> command.
>>>>>>> That results in the following error:
>>>>>>>
>>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
>>>>>>> Location: file nccopy.c; line 788
>>>>>>>
>>>>>>> (2) View your file using ncview. It brings up the display but
all
>> the
>>>>>>> values are 0:
>>>>>>>
>>>>>>>> ncview FCT.nc
>>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling it
>> to
>>>>>>> interpret it at a MET NetCDF file. That results in the
following
>>>> error:
>>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps 'name="APCP";
>>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>>>>>> terminate called after throwing an instance of
>>>>>> 'netCDF::exceptions::NcChar'
>>>>>>> what(): NcChar: Attempt to convert between text &
numbers
>>>>>>> file: ncAtt.cpp line:104
>>>>>>> Abort
>>>>>>>
>>>>>>> (4) Lastly, I ran (3) above through the debugger and found
that it is
>>>>>>> indeed all those "string" types that are causing the problem.
I used
>>>> the
>>>>>>> ncatted utility to change those data types from "string" to
>>>> "character".
>>>>>>> After doing that and telling MET to interpret it as a CF-
compliant
>>>> NetCDF
>>>>>>> file, I was at least able to plot it. The plot looks bad but
at
>> least
>>>> it
>>>>>>> works. Here are the very long commands I ran:
>>>>>>>
>>>>>>> # Run ncatted to switch types from strings to characters
>>>>>>> ncatted FCT.nc \
>>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
20170409_140422
>>>>>> UTC on
>>>>>>> host eslogin03 by the MET pcp_combine tool" \
>>>>>>> -a MET_version,global,o,c,"V5.2" \
>>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
>>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>>>>>> -a Projection,global,o,c,"LatLon" \
>>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>>>>>> -a Nlat,global,o,c,"157 grid_points" \
>>>>>>> -a Nlon,global,o,c,"144 grid_points" \
>>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>>>>>> -a source,global,o,c,"Eta40ens regional weather forecasting
model" \
>>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
>>>>>>> -a increment,time,o,c,"24 hours in seconds" \
>>>>>>> -a calendar,time,o,c,"standard" \
>>>>>>> -a long_name,time,o,c,"Forecast target time" \
>>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>>>>>> -a long_name,member,o,c,"Members of the ensemble model
Eta40ens" \
>>>>>>> -a long_name,lat,o,c,"latitude" \
>>>>>>> -a units,lat,o,c,"degrees_north" \
>>>>>>> -a standard_name,lat,o,c,"latitude" \
>>>>>>> -a long_name,lon,o,c,"longitude" \
>>>>>>> -a units,lon,o,c,"degrees_east" \
>>>>>>> -a standard_name,lon,o,c,"longitude" \
>>>>>>> -a Projection,APCP,o,c,"LatLon" \
>>>>>>> -a units,APCP,o,c,"kg/m^2" \
>>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation" \
>>>>>>> -o FCT_edit.nc
>>>>>>>
>>>>>>> # Run plot_data_plane version 6.0 to plot the file
>>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
>>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>>>>>
>>>>>>>
>>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
>
>>>>>>>>
>>>>>>>> Hi John,
>>>>>>>>
>>>>>>>> I’ve created garcia_data and put the files in your incoming
ftp
>> site.
>>>>>>>> Thank you for your help.
>>>>>>>>
>>>>>>>> About those repeated strings that I suppose you are referring
to
>>>> *._deg
>>>>>>>> strings, I’had to create them because one of MET tools
complained
>>>> about
>>>>>> the
>>>>>>>> lack of them, and I think it was grid_stat itself. To
generate them
>> I
>>>>>> took
>>>>>>>> the pcp_combine output as a template but when running the
grid_stat
>>>>>> command
>>>>>>>> it showed this message to me.
>>>>>>>>
>>>>>>>> Thank you again.
>>>>>>>>
>>>>>>>> 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 *****
>>>>>>>> =================================
>>>>>>>>
>>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>>> JR Garcia,
>>>>>>>>>
>>>>>>>>> I see that you're having trouble reading this dataset, and I
>>>> certainly
>>>>>>>>> agree, that error message isn't very helpful. I looked at
the
>> ncdump
>>>>>>>>> output you sent and don't see anything obviously wrong.
However, I
>>>>>>>> haven't
>>>>>>>>> seen all those repeated "string" values in ncdump output
before.
>>>>>> Perhaps
>>>>>>>>> there's a netcdf version issue going on.
>>>>>>>>>
>>>>>>>>> If possible, the easiest way for me to debug would be for
you to
>>>> post a
>>>>>>>>> sample file to our anonymous ftp site following these
instructions:
>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>>>>>>>> Also please indicate the version of MET that you're using.
>>>>>>>>>
>>>>>>>>> If I can replicate the behavior here, it should be pretty
easy to
>>>>>>>> determine
>>>>>>>>> the problem.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via
RT <
>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>>>
>>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
>>>>>>>> roberto.garcia at inpe.br>
>>>>>>>>>> Queue: met_help
>>>>>>>>>> Subject: FileType_None error in GridStat tool
>>>>>>>>>> Owner: Nobody
>>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
>>>> roberto.garcia at inpe.br>
>>>>>>>>>> Status: new
>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
>>>> Ticket/Display.html?id=80092
>>>>>> <
>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices
>> has
>>>>>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
>>>>>> command
>>>>>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>>>>>
>>>>>>>>>> I'm running the following command:
>>>>>>>>>>
>>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>>>>>
>>>>>>>>>> And the entries for the forecast and observation fields is
>>>> configured
>>>>>>>>>> inside GridStat.cfg are:
>>>>>>>>>>
>>>>>>>>>> // Forecast fields to be verified
==============================
>>>>>>>>>> fcst = {
>>>>>>>>>> field = [
>>>>>>>>>> {
>>>>>>>>>> name = "APCP";
>>>>>>>>>> level = "(0,0,*,*)"; // 24-hour
>> accumulation
>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0 ] //
>>>>>> ORIGINAL
>>>>>>>>>> }
>>>>>>>>>> ];
>>>>>>>>>> }
>>>>>>>>>> // Observation fields to be verified
>> ==============================
>>>>>>>>>> obs = {
>>>>>>>>>> field = [
>>>>>>>>>> {
>>>>>>>>>> name = "APCP";
>>>>>>>>>> level = "(0,*,*)"; // 24-hour
accumulation
>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0 ] //
>>>>>> ORIGINAL
>>>>>>>>>> }
>>>>>>>>>> ];
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> I'm getting the following error:
>>>>>>>>>>
>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>>>>>> GridStatConfig_default
>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>>>> DEBUG 4: Me
>> Until the NCO sys admins can get it installed in a more general
area, this
>> MET installation is available for use. We will be rolling out some
patches
>> shortly, at which point I will update this installation.
>> t2dDataFileFactory::new_met_2d_data_file() -> created
>>>> new
>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>> ERROR :
>>>>>>>>>> ERROR : Trouble reading forecast file
>>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>>>>>> Eta40ens_00_036hs.nc"
>>>>>>>>>> ERROR :
>>>>>>>>>>
>>>>>>>>>> The message is not clear but I suppose MET was not able to
find
>> out
>>>>>> the
>>>>>>>>>> FCST file type. Could you help me, please?
>>>>>>>>>>
>>>>>>>>>> Best regards.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>>>> =======================================================
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>
>>
>>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: John Halley Gotway
Time: Mon Apr 17 15:26:46 2017
JR Garcia,
In the CF-convention, the "time" value specifies the valid time. And
there
is a convention for specifying the model initialization time. MET
computes
the "lead_time" as the valid time minus the initialization time.
Add a variable named "forecast_reference_time" that looks like this:
double forecast_reference_time
;
forecast_reference_time:long_name = "reference time"
;
forecast_reference_time:units = "seconds since 1970-1-
1" ;
Thanks,
John
On Mon, Apr 17, 2017 at 3:11 PM, Roberto Garcia (INPE) via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>
> Ok, John. Thanks again. It worked! I think we are getting there!
>
> Now, I'm wondering what element can change the Lead Time in the file
> name. Can it be changed using grid_stat or it is a standard name
format
> that serves all MET tools and some of them can change it?
>
> grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
>
> 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 17/04/2017 17:48, John Halley Gotway via RT wrote:
> > JR Garcia,
> >
> > Yes, you can set the "cat_thresh" separately for each entry in the
> > "fcst.field" and "obs.field" arrays.
> >
> > Usually people run Grid-Stat to compare the same type of data from
both
> the
> > forecast and observation datasets but there is no reason why you
have to.
> > For example, you have the flexibility to compare forecast
temperature to
> > observed precipitation. That probably won't yield very meaningful
> results,
> > but if you did that, you'd probably want to specify different
thresholds
> > for each field.
> >
> > But you're right, you can just specify "cat_thresh" once outside
the
> "fcst"
> > and "obs" settings and that one setting will be applied to both.
See
> > example below.
> >
> > Next... MET supports 3 different flavors of NetCDF, and the timing
> > information is stored differently in them. Please just try
telling MET
> to
> > interpret your data following the CF-conventions using: file_type
=
> > NETCDF_NCCF; Since we want it apply to both the "fcst" and
"obs", I
> just
> > defined it once at the top-level context of the config file. And
I've
> also
> > included that in the Grid-Stat config example listed below.
> >
> > Thanks,
> > John
> >
> > cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
> > file_type = NETCDF_NCCF;
> >
> > // Forecast fields to be verified ==============================
> > fcst = {
> > field = [
> > {
> > name = "APCP";
> > level = "(0,0,*,*)"; // 24-hour accumulation
> > }
> > ];
> > }
> > // Observation fields to be verified
==============================
> > obs = {
> > field = [
> > {
> > name = "APCP";
> > level = "(0,*,*)"; // 24-hour accumulation
> > }
> > ];
> > }
> >
> > As for the issue with the timestamps,
> >
> >
> >
> >
> > On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT <
> > met_help at ucar.edu> wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
> >>
> >> Dear John, can you clarify why the output files were generated to
> >> 1970010 000000 valid time and 000000 lead time?
> >>
> >> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
> >>
> >> Below is the partial print of the forecasting NetCDF. Shouldn't
MET
> >> calculate the correct time according to the time slice I
specified in
> >> the config file *level = "(0,0,*,*)"* and its unit *"hours
since"*? What
> >> I'm doing wrong?
> >>
> >> variables:
> >> int time(time) ;
> >> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
> >> time:calendar = "standard" ;
> >> time:long_name = "Forecast target time" ;
> >>
> >> time = 411036, 411060, 411084, 411108, 411132, 411156, 411180,
> 411204,
> >> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
411396,
> >> 411420,
> >> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
411612,
> >> 411636,
> >>
> >>
> >> Another questions regarding the config file, please. At the
highest
> >> level of grid_stat config file there is a group of entries:
> >>
> >> cat_thresh = [ NA ];
> >> cnt_thresh = [ NA ];
> >> cnt_logic = UNION;
> >> wind_thresh = [ NA ];
> >> wind_logic = UNION;
> >>
> >> 1) Do them control the behavior of the verification in a general
aspect?
> >> Concerning cat_thresh specifically, what happens if I set some
> >> thresholds at it and also inside the fcst and/o obs entries?
> >>
> >> 2) Why there is cat_thresh entry for both fcst and obs entries?
Wouldn't
> >> a general cat_thresh entry be enough? Does the use of different
> >> cat_thresh values for obs and fcst make sense?
> >>
> >> Thank you
> >>
> >>
> >> 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 <+55%2012%203208-7966>
> >> -------------------------------------------------------
> >> SAVE NATURAL RESOURCES!
> >> =======================================================
> >>
> >> On 17/04/2017 15:07, John Halley Gotway via RT wrote:
> >>> JR Garcia,
> >>>
> >>> You have the Nlat and Nlon global attributes set wrong in the
> >>> MERGE_20161201_20170228.nc file:
> >>> :Nlat = "245 grid_points" ;
> >>> :Nlon = "313 grid_points" ;
> >>>
> >>> Those numbers don't match the lat/lon dimensions:
> >>> dimensions:
> >>> time = 90 ;
> >>> lat = 313 ;
> >>> lon = 245 ;
> >>>
> >>> I ran the following command to switch them:
> >>>
> >>> ncatted -a Nlat,global,o,c,"313 grid_points" \
> >>> -a Nlon,global,o,c,"245 grid_points" \
> >>> MERGE_20161201_20170228.nc \
> >>> -o MERGE_20161201_20170228_PATCH.nc
> >>>
> >>> After switching that, MET version 5.2 processes them fine.
> >>>
> >>> Also, testing this out using version 6.0 revealed a little bug
we
> >>> introduced when switching from NetCDF3 to NetCDF4. I'll post a
bugfix
> >> for
> >>> this as soon as one is available.
> >>>
> >>> In order to run this data through version 6.0, you'll need that
bugfix.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>>
> >>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
> >>> met_help at ucar.edu> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
> >>>>
> >>>> Data are there!
> >>>>
> >>>> Thanks John.
> >>>>
> >>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
> >>>>> JR Garcia,
> >>>>>
> >>>>> Can you please post a sample one of your converted files to
our ftp
> >> site
> >>>>> following these instructions:
> >>>>>
> >>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>
> >>>>> I'll take a look at let you know what I find.
> >>>>>
> >>>>> Thanks,
> >>>>> John
> >>>>>
> >>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT
<
> >>>>> met_help at ucar.edu> wrote:
> >>>>>
> >>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
> >>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
> >>>>>> Queue: met_help
> >>>>>> Subject: can't set corner for variable "APCP" error
> >>>>>> Owner: Nobody
> >>>>>> Requestors: roberto.garcia at inpe.br
> >>>>>> Status: new
> >>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
> >> ket/Display.html?id=80169
> >>>>>> Hi John, I converted all obs and fct NetCDF files to the
NetCDF 3
> >>>>>> Classic version and issued the same command, could you please
help
> me
> >>>>>> interpret this error? What does "corner" refer to?
> >>>>>>
> >>>>>> Thanks
> >>>>>>
> >>>>>>
> >>>>>> > grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
> >> rid.nc
> >>>>>> GridStat.cfg -v 4
> >>>>>>
> >>>>>> DEBUG 1: Default Config File:
> >>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >>>>>> GridStatConfig_default
> >>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> >>>>>> Met2dDataFile object of type "FileType_NcMet".
> >>>>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>>>> DEBUG 4: lat_ll = -50.2
> >>>>>> DEBUG 4: lon_ll = 83
> >>>>>> DEBUG 4: delta_lat = 0.4
> >>>>>> DEBUG 4: delta_lon = 0.4
> >>>>>> DEBUG 4: Nlat = 157
> >>>>>> DEBUG 4: Nlon = 144
> >>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> >>>>>> Met2dDataFile object of type "FileType_NcMet".
> >>>>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>>>> DEBUG 4: lat_ll = -50.2
> >>>>>> DEBUG 4: lon_ll = 82.8
> >>>>>> DEBUG 4: delta_lat = 0.2
> >>>>>> DEBUG 4: delta_lon = 0.2
> >>>>>> DEBUG 4: Nlat = 144
> >>>>>> DEBUG 4: Nlon = 157
> >>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
> object
> >> of
> >>>>>> type "FileType_NcMet".
> >>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
> object
> >> of
> >>>>>> type "FileType_NcMet".
> >>>>>> WARNING:
> >>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
> >>>>>> method, resetting method from "UW_MEAN" to "NEAREST" since
the
> >>>>>> interpolation width is 1.
> >>>>>> WARNING:
> >>>>>> DEBUG 3: Use the forecast grid.
> >>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
> lat_ll:
> >>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
> >>>>>> GSL_RNG_TYPE=mt19937
> >>>>>> GSL_RNG_SEED=1639511128
> >>>>>> DEBUG 1: Forecast File:
> >>>>>> /stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
> >> 00_036hs.nc
> >>>>>> DEBUG 1: Observation File:
> >>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
> >>>>>> 20161201_20170228_Eta40Grid.nc
> >>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
> >>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
> >>>>>> ERROR :
> >>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't
> >> set
> >>>>>> corner for variable "APCP"
> >>>>>> ERROR :
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> 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 <+55%2012%203208-7966>
> >>>>>> -------------------------------------------------------
> >>>>>> SAVE NATURAL RESOURCES!
> >>>>>> =======================================================
> >>>>>>
> >>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
> >>>>>>> JR Garcia,
> >>>>>>>
> >>>>>>> Thanks for sending the sample data file. This is definitely
a
> >> NetCDF4
> >>>>>> file
> >>>>>>> using the enhanced data model. MET version 5.2 is not able
to read
> >>>>>> NetCDF4
> >>>>>>> files. The recent release of MET (version 6.0) has been
enhanced
> to
> >> do
> >>>>>> so.
> >>>>>>> I tried a few things:
> >> Until the NCO sys admins can get it installed in a more general
area,
> this
> >> MET installation is available for use. We will be rolling out
some
> patches
> >> shortly, at which point I will update this installation.
> >>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
> >>>>>> command.
> >>>>>>> That results in the following error:
> >>>>>>>
> >>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
> >>>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
> >>>>>>> Location: file nccopy.c; line 788
> >>>>>>>
> >>>>>>> (2) View your file using ncview. It brings up the display
but all
> >> the
> >>>>>>> values are 0:
> >>>>>>>
> >>>>>>>> ncview FCT.nc
> >>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling
> it
> >> to
> >>>>>>> interpret it at a MET NetCDF file. That results in the
following
> >>>> error:
> >>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps
'name="APCP";
> >>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
> >>>>>>> terminate called after throwing an instance of
> >>>>>> 'netCDF::exceptions::NcChar'
> >>>>>>> what(): NcChar: Attempt to convert between text &
numbers
> >>>>>>> file: ncAtt.cpp line:104
> >>>>>>> Abort
> >>>>>>>
> >>>>>>> (4) Lastly, I ran (3) above through the debugger and found
that it
> is
> >>>>>>> indeed all those "string" types that are causing the
problem. I
> used
> >>>> the
> >>>>>>> ncatted utility to change those data types from "string" to
> >>>> "character".
> >>>>>>> After doing that and telling MET to interpret it as a CF-
compliant
> >>>> NetCDF
> >>>>>>> file, I was at least able to plot it. The plot looks bad
but at
> >> least
> >>>> it
> >>>>>>> works. Here are the very long commands I ran:
> >>>>>>>
> >>>>>>> # Run ncatted to switch types from strings to characters
> >>>>>>> ncatted FCT.nc \
> >>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
> 20170409_140422
> >>>>>> UTC on
> >>>>>>> host eslogin03 by the MET pcp_combine tool" \
> >>>>>>> -a MET_version,global,o,c,"V5.2" \
> >>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
> >>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
> >>>>>>> -a Projection,global,o,c,"LatLon" \
> >>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> >>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> >>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
> >>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
> >>>>>>> -a Nlat,global,o,c,"157 grid_points" \
> >>>>>>> -a Nlon,global,o,c,"144 grid_points" \
> >>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> >>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
> >>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> >>>>>>> -a source,global,o,c,"Eta40ens regional weather forecasting
model"
> \
> >>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
> >>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
> >>>>>>> -a increment,time,o,c,"24 hours in seconds" \
> >>>>>>> -a calendar,time,o,c,"standard" \
> >>>>>>> -a long_name,time,o,c,"Forecast target time" \
> >>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
> >>>>>>> -a long_name,member,o,c,"Members of the ensemble model
Eta40ens" \
> >>>>>>> -a long_name,lat,o,c,"latitude" \
> >>>>>>> -a units,lat,o,c,"degrees_north" \
> >>>>>>> -a standard_name,lat,o,c,"latitude" \
> >>>>>>> -a long_name,lon,o,c,"longitude" \
> >>>>>>> -a units,lon,o,c,"degrees_east" \
> >>>>>>> -a standard_name,lon,o,c,"longitude" \
> >>>>>>> -a Projection,APCP,o,c,"LatLon" \
> >>>>>>> -a units,APCP,o,c,"kg/m^2" \
> >>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation"
> \
> >>>>>>> -o FCT_edit.nc
> >>>>>>>
> >>>>>>> # Run plot_data_plane version 6.0 to plot the file
> >>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
> >>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
> >>>>>>>
> >>>>>>>
> >>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 >
> >>>>>>>>
> >>>>>>>> Hi John,
> >>>>>>>>
> >>>>>>>> I’ve created garcia_data and put the files in your incoming
ftp
> >> site.
> >>>>>>>> Thank you for your help.
> >>>>>>>>
> >>>>>>>> About those repeated strings that I suppose you are
referring to
> >>>> *._deg
> >>>>>>>> strings, I’had to create them because one of MET tools
complained
> >>>> about
> >>>>>> the
> >>>>>>>> lack of them, and I think it was grid_stat itself. To
generate
> them
> >> I
> >>>>>> took
> >>>>>>>> the pcp_combine output as a template but when running the
> grid_stat
> >>>>>> command
> >>>>>>>> it showed this message to me.
> >>>>>>>>
> >>>>>>>> Thank you again.
> >>>>>>>>
> >>>>>>>> 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 *****
> >>>>>>>> =================================
> >>>>>>>>
> >>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
> >>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>>>> JR Garcia,
> >>>>>>>>>
> >>>>>>>>> I see that you're having trouble reading this dataset, and
I
> >>>> certainly
> >>>>>>>>> agree, that error message isn't very helpful. I looked at
the
> >> ncdump
> >>>>>>>>> output you sent and don't see anything obviously wrong.
However,
> I
> >>>>>>>> haven't
> >>>>>>>>> seen all those repeated "string" values in ncdump output
before.
> >>>>>> Perhaps
> >>>>>>>>> there's a netcdf version issue going on.
> >>>>>>>>>
> >>>>>>>>> If possible, the easiest way for me to debug would be for
you to
> >>>> post a
> >>>>>>>>> sample file to our anonymous ftp site following these
> instructions:
> >>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> <
> >>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
> >>>>>>>>> Also please indicate the version of MET that you're using.
> >>>>>>>>>
> >>>>>>>>> If I can replicate the behavior here, it should be pretty
easy to
> >>>>>>>> determine
> >>>>>>>>> the problem.
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> John
> >>>>>>>>>
> >>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via
RT <
> >>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
> >>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
> >>>>>>>> roberto.garcia at inpe.br>
> >>>>>>>>>> Queue: met_help
> >>>>>>>>>> Subject: FileType_None error in GridStat tool
> >>>>>>>>>> Owner: Nobody
> >>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> >>>> roberto.garcia at inpe.br>
> >>>>>>>>>> Status: new
> >>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
> >>>> Ticket/Display.html?id=80092
> >>>>>> <
> >>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
> >>>>>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices
> >> has
> >>>>>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
> >>>>>> command
> >>>>>>>>>> for both FSCT.nc and OBS.nc.
> >>>>>>>>>>
> >>>>>>>>>> I'm running the following command:
> >>>>>>>>>>
> >>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
> >>>>>>>>>>
> >>>>>>>>>> And the entries for the forecast and observation fields
is
> >>>> configured
> >>>>>>>>>> inside GridStat.cfg are:
> >>>>>>>>>>
> >>>>>>>>>> // Forecast fields to be verified
==============================
> >>>>>>>>>> fcst = {
> >>>>>>>>>> field = [
> >>>>>>>>>> {
> >>>>>>>>>> name = "APCP";
> >>>>>>>>>> level = "(0,0,*,*)"; // 24-hour
> >> accumulation
> >>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
> ] //
> >>>>>> ORIGINAL
> >>>>>>>>>> }
> >>>>>>>>>> ];
> >>>>>>>>>> }
> >>>>>>>>>> // Observation fields to be verified
> >> ==============================
> >>>>>>>>>> obs = {
> >>>>>>>>>> field = [
> >>>>>>>>>> {
> >>>>>>>>>> name = "APCP";
> >>>>>>>>>> level = "(0,*,*)"; // 24-hour
> accumulation
> >>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
> ] //
> >>>>>> ORIGINAL
> >>>>>>>>>> }
> >>>>>>>>>> ];
> >>>>>>>>>> }
> >>>>>>>>>>
> >>>>>>>>>> I'm getting the following error:
> >>>>>>>>>>
> >>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
> >>>>>>>>>> GridStatConfig_default
> >>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>>>>>> DEBUG 4: Me
> >> Until the NCO sys admins can get it installed in a more general
area,
> this
> >> MET installation is available for use. We will be rolling out
some
> patches
> >> shortly, at which point I will update this installation.
> >> t2dDataFileFactory::new_met_2d_data_file() -> created
> >>>> new
> >>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>> ERROR :
> >>>>>>>>>> ERROR : Trouble reading forecast file
> >>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
> >>>>>>>> Eta40ens_00_036hs.nc"
> >>>>>>>>>> ERROR :
> >>>>>>>>>>
> >>>>>>>>>> The message is not clear but I suppose MET was not able
to find
> >> out
> >>>>>> the
> >>>>>>>>>> FCST file type. Could you help me, please?
> >>>>>>>>>>
> >>>>>>>>>> Best regards.
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> 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 <+55%2012%203208-7966>
> >>>>>>>>>> -------------------------------------------------------
> >>>>>>>>>> SAVE NATURAL RESOURCES!
> >>>>>>>>>> =======================================================
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>
> >>
> >>
>
>
>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: Garcia, J.R.M.
Time: Wed Apr 19 08:46:53 2017
Excuse-me John, I saw your quick response and answered it but the
email was not delivered. That was it.
Thanks John.
I understood but I’m afraid I can’t include this variable due to the
way my NetCDF file is structured. It has one specific forecasting lead
time, let’s say 36-hs forecasting, so it will have several model
initialization times from the whole evaluation period and I joined all
correspondent 36-hs forecasting to it.
I do the same for 24-hr, 48-hr, 60-hr, and so on….every lead time is
kept in a separated file. I’m a beginner in model evaluation and I
thought that as the evaluation must be per lead time I supposed that
separating them into distinct files would be feasible.
But I also think that this information does not affect my evaluation
since I know which forecasting time I’m dealing with, am I right?
Thanks
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 *****
=================================
> On 17 de abr de 2017, at 18:26, John Halley Gotway via RT
<met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>
> JR Garcia,
>
> In the CF-convention, the "time" value specifies the valid time.
And there
> is a convention for specifying the model initialization time. MET
computes
> the "lead_time" as the valid time minus the initialization time.
>
> Add a variable named "forecast_reference_time" that looks like this:
>
> double forecast_reference_time
> ;
>
> forecast_reference_time:long_name = "reference time"
> ;
>
> forecast_reference_time:units = "seconds since 1970-
1-1" ;
>
> Thanks,
> John
>
> On Mon, Apr 17, 2017 at 3:11 PM, Roberto Garcia (INPE) via RT <
> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>
>> Ok, John. Thanks again. It worked! I think we are getting there!
>>
>> Now, I'm wondering what element can change the Lead Time in the
file
>> name. Can it be changed using grid_stat or it is a standard name
format
>> that serves all MET tools and some of them can change it?
>>
>> grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
>>
>> 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 17/04/2017 17:48, John Halley Gotway via RT wrote:
>>> JR Garcia,
>>>
>>> Yes, you can set the "cat_thresh" separately for each entry in the
>>> "fcst.field" and "obs.field" arrays.
>>>
>>> Usually people run Grid-Stat to compare the same type of data from
both
>> the
>>> forecast and observation datasets but there is no reason why you
have to.
>>> For example, you have the flexibility to compare forecast
temperature to
>>> observed precipitation. That probably won't yield very meaningful
>> results,
>>> but if you did that, you'd probably want to specify different
thresholds
>>> for each field.
>>>
>>> But you're right, you can just specify "cat_thresh" once outside
the
>> "fcst"
>>> and "obs" settings and that one setting will be applied to both.
See
>>> example below.
>>>
>>> Next... MET supports 3 different flavors of NetCDF, and the timing
>>> information is stored differently in them. Please just try
telling MET
>> to
>>> interpret your data following the CF-conventions using: file_type
=
>>> NETCDF_NCCF; Since we want it apply to both the "fcst" and
"obs", I
>> just
>>> defined it once at the top-level context of the config file. And
I've
>> also
>>> included that in the Grid-Stat config example listed below.
>>>
>>> Thanks,
>>> John
>>>
>>> cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
>>> file_type = NETCDF_NCCF;
>>>
>>> // Forecast fields to be verified ==============================
>>> fcst = {
>>> field = [
>>> {
>>> name = "APCP";
>>> level = "(0,0,*,*)"; // 24-hour accumulation
>>> }
>>> ];
>>> }
>>> // Observation fields to be verified
==============================
>>> obs = {
>>> field = [
>>> {
>>> name = "APCP";
>>> level = "(0,*,*)"; // 24-hour accumulation
>>> }
>>> ];
>>> }
>>>
>>> As for the issue with the timestamps,
>>>
>>>
>>>
>>>
>>> On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT <
>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>>>
>>>> Dear John, can you clarify why the output files were generated to
>>>> 1970010 000000 valid time and 000000 lead time?
>>>>
>>>> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
>>>>
>>>> Below is the partial print of the forecasting NetCDF. Shouldn't
MET
>>>> calculate the correct time according to the time slice I
specified in
>>>> the config file *level = "(0,0,*,*)"* and its unit *"hours
since"*? What
>>>> I'm doing wrong?
>>>>
>>>> variables:
>>>> int time(time) ;
>>>> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
>>>> time:calendar = "standard" ;
>>>> time:long_name = "Forecast target time" ;
>>>>
>>>> time = 411036, 411060, 411084, 411108, 411132, 411156, 411180,
>> 411204,
>>>> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
411396,
>>>> 411420,
>>>> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
411612,
>>>> 411636,
>>>>
>>>>
>>>> Another questions regarding the config file, please. At the
highest
>>>> level of grid_stat config file there is a group of entries:
>>>>
>>>> cat_thresh = [ NA ];
>>>> cnt_thresh = [ NA ];
>>>> cnt_logic = UNION;
>>>> wind_thresh = [ NA ];
>>>> wind_logic = UNION;
>>>>
>>>> 1) Do them control the behavior of the verification in a general
aspect?
>>>> Concerning cat_thresh specifically, what happens if I set some
>>>> thresholds at it and also inside the fcst and/o obs entries?
>>>>
>>>> 2) Why there is cat_thresh entry for both fcst and obs entries?
Wouldn't
>>>> a general cat_thresh entry be enough? Does the use of different
>>>> cat_thresh values for obs and fcst make sense?
>>>>
>>>> Thank you
>>>>
>>>>
>>>> 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 <+55%2012%203208-7966>
>>>> -------------------------------------------------------
>>>> SAVE NATURAL RESOURCES!
>>>> =======================================================
>>>>
>>>> On 17/04/2017 15:07, John Halley Gotway via RT wrote:
>>>>> JR Garcia,
>>>>>
>>>>> You have the Nlat and Nlon global attributes set wrong in the
>>>>> MERGE_20161201_20170228.nc file:
>>>>> :Nlat = "245 grid_points" ;
>>>>> :Nlon = "313 grid_points" ;
>>>>>
>>>>> Those numbers don't match the lat/lon dimensions:
>>>>> dimensions:
>>>>> time = 90 ;
>>>>> lat = 313 ;
>>>>> lon = 245 ;
>>>>>
>>>>> I ran the following command to switch them:
>>>>>
>>>>> ncatted -a Nlat,global,o,c,"313 grid_points" \
>>>>> -a Nlon,global,o,c,"245 grid_points" \
>>>>> MERGE_20161201_20170228.nc \
>>>>> -o MERGE_20161201_20170228_PATCH.nc
>>>>>
>>>>> After switching that, MET version 5.2 processes them fine.
>>>>>
>>>>> Also, testing this out using version 6.0 revealed a little bug
we
>>>>> introduced when switching from NetCDF3 to NetCDF4. I'll post a
bugfix
>>>> for
>>>>> this as soon as one is available.
>>>>>
>>>>> In order to run this data through version 6.0, you'll need that
bugfix.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>>
>>>>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT <
>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>>>>>
>>>>>> Data are there!
>>>>>>
>>>>>> Thanks John.
>>>>>>
>>>>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
>>>>>>> JR Garcia,
>>>>>>>
>>>>>>> Can you please post a sample one of your converted files to
our ftp
>>>> site
>>>>>>> following these instructions:
>>>>>>>
>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>>>>>>
>>>>>>> I'll take a look at let you know what I find.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via RT
<
>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>
>>>>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br>
>>>>>>>> Queue: met_help
>>>>>>>> Subject: can't set corner for variable "APCP" error
>>>>>>>> Owner: Nobody
>>>>>>>> Requestors: roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br>
>>>>>>>> Status: new
>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
<https://rt.rap.ucar.edu/rt/Tic>
>>>> ket/Display.html?id=80169
>>>>>>>> Hi John, I converted all obs and fct NetCDF files to the
NetCDF 3
>>>>>>>> Classic version and issued the same command, could you please
help
>> me
>>>>>>>> interpret this error? What does "corner" refer to?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>>
>>>>>>>>> grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
>>>> rid.nc
>>>>>>>> GridStat.cfg -v 4
>>>>>>>>
>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>>>> GridStatConfig_default
>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>> new
>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>>>> DEBUG 4: lon_ll = 83
>>>>>>>> DEBUG 4: delta_lat = 0.4
>>>>>>>> DEBUG 4: delta_lon = 0.4
>>>>>>>> DEBUG 4: Nlat = 157
>>>>>>>> DEBUG 4: Nlon = 144
>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>> new
>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>>>> DEBUG 4: lon_ll = 82.8
>>>>>>>> DEBUG 4: delta_lat = 0.2
>>>>>>>> DEBUG 4: delta_lon = 0.2
>>>>>>>> DEBUG 4: Nlat = 144
>>>>>>>> DEBUG 4: Nlon = 157
>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
>> object
>>>> of
>>>>>>>> type "FileType_NcMet".
>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
>> object
>>>> of
>>>>>>>> type "FileType_NcMet".
>>>>>>>> WARNING:
>>>>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
interpolation
>>>>>>>> method, resetting method from "UW_MEAN" to "NEAREST" since
the
>>>>>>>> interpolation width is 1.
>>>>>>>> WARNING:
>>>>>>>> DEBUG 3: Use the forecast grid.
>>>>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny: 157
>> lat_ll:
>>>>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>>>>>>>> GSL_RNG_TYPE=mt19937
>>>>>>>> GSL_RNG_SEED=1639511128
>>>>>>>> DEBUG 1: Forecast File:
>>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
>>>> 00_036hs.nc
>>>>>>>> DEBUG 1: Observation File:
>>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>>>>>>>> 20161201_20170228_Eta40Grid.nc
>>>>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>>>>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
>>>>>>>> ERROR :
>>>>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const ->
can't
>>>> set
>>>>>>>> corner for variable "APCP"
>>>>>>>> ERROR :
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>> -------------------------------------------------------
>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>> =======================================================
>>>>>>>>
>>>>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>>>>>>>> JR Garcia,
>>>>>>>>>
>>>>>>>>> Thanks for sending the sample data file. This is definitely
a
>>>> NetCDF4
>>>>>>>> file
>>>>>>>>> using the enhanced data model. MET version 5.2 is not able
to read
>>>>>>>> NetCDF4
>>>>>>>>> files. The recent release of MET (version 6.0) has been
enhanced
>> to
>>>> do
>>>>>>>> so.
>>>>>>>>> I tried a few things:
>>>> Until the NCO sys admins can get it installed in a more general
area,
>> this
>>>> MET installation is available for use. We will be rolling out
some
>> patches
>>>> shortly, at which point I will update this installation.
>>>>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
>>>>>>>> command.
>>>>>>>>> That results in the following error:
>>>>>>>>>
>>>>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>>>>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
>>>>>>>>> Location: file nccopy.c; line 788
>>>>>>>>>
>>>>>>>>> (2) View your file using ncview. It brings up the display
but all
>>>> the
>>>>>>>>> values are 0:
>>>>>>>>>
>>>>>>>>>> ncview FCT.nc
>>>>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling
>> it
>>>> to
>>>>>>>>> interpret it at a MET NetCDF file. That results in the
following
>>>>>> error:
>>>>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps
'name="APCP";
>>>>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>>>>>>>> terminate called after throwing an instance of
>>>>>>>> 'netCDF::exceptions::NcChar'
>>>>>>>>> what(): NcChar: Attempt to convert between text &
numbers
>>>>>>>>> file: ncAtt.cpp line:104
>>>>>>>>> Abort
>>>>>>>>>
>>>>>>>>> (4) Lastly, I ran (3) above through the debugger and found
that it
>> is
>>>>>>>>> indeed all those "string" types that are causing the
problem. I
>> used
>>>>>> the
>>>>>>>>> ncatted utility to change those data types from "string" to
>>>>>> "character".
>>>>>>>>> After doing that and telling MET to interpret it as a CF-
compliant
>>>>>> NetCDF
>>>>>>>>> file, I was at least able to plot it. The plot looks bad
but at
>>>> least
>>>>>> it
>>>>>>>>> works. Here are the very long commands I ran:
>>>>>>>>>
>>>>>>>>> # Run ncatted to switch types from strings to characters
>>>>>>>>> ncatted FCT.nc \
>>>>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
>> 20170409_140422
>>>>>>>> UTC on
>>>>>>>>> host eslogin03 by the MET pcp_combine tool" \
>>>>>>>>> -a MET_version,global,o,c,"V5.2" \
>>>>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
>>>>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>>>>>>>> -a Projection,global,o,c,"LatLon" \
>>>>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>>>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>>>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>>>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>>>>>>>> -a Nlat,global,o,c,"157 grid_points" \
>>>>>>>>> -a Nlon,global,o,c,"144 grid_points" \
>>>>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>>>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>>>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>>>>>>>> -a source,global,o,c,"Eta40ens regional weather forecasting
model"
>> \
>>>>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>>>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
>>>>>>>>> -a increment,time,o,c,"24 hours in seconds" \
>>>>>>>>> -a calendar,time,o,c,"standard" \
>>>>>>>>> -a long_name,time,o,c,"Forecast target time" \
>>>>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>>>>>>>> -a long_name,member,o,c,"Members of the ensemble model
Eta40ens" \
>>>>>>>>> -a long_name,lat,o,c,"latitude" \
>>>>>>>>> -a units,lat,o,c,"degrees_north" \
>>>>>>>>> -a standard_name,lat,o,c,"latitude" \
>>>>>>>>> -a long_name,lon,o,c,"longitude" \
>>>>>>>>> -a units,lon,o,c,"degrees_east" \
>>>>>>>>> -a standard_name,lon,o,c,"longitude" \
>>>>>>>>> -a Projection,APCP,o,c,"LatLon" \
>>>>>>>>> -a units,APCP,o,c,"kg/m^2" \
>>>>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
precipitation"
>> \
>>>>>>>>> -o FCT_edit.nc
>>>>>>>>>
>>>>>>>>> # Run plot_data_plane version 6.0 to plot the file
>>>>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
>>>>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>>>>>>>
>>>>>>>>>> Hi John,
>>>>>>>>>>
>>>>>>>>>> I’ve created garcia_data and put the files in your incoming
ftp
>>>> site.
>>>>>>>>>> Thank you for your help.
>>>>>>>>>>
>>>>>>>>>> About those repeated strings that I suppose you are
referring to
>>>>>> *._deg
>>>>>>>>>> strings, I’had to create them because one of MET tools
complained
>>>>>> about
>>>>>>>> the
>>>>>>>>>> lack of them, and I think it was grid_stat itself. To
generate
>> them
>>>> I
>>>>>>>> took
>>>>>>>>>> the pcp_combine output as a template but when running the
>> grid_stat
>>>>>>>> command
>>>>>>>>>> it showed this message to me.
>>>>>>>>>>
>>>>>>>>>> Thank you again.
>>>>>>>>>>
>>>>>>>>>> JR Garcia
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> =================================
>>>>>>>>>> Jose Roberto Motta Garcia, PhD
>>>>>>>>>>
>>>>>>>>>> www.cptec.inpe.br <http://www.cptec.inpe.br/>
<http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>>
>>>>>>>>>> www.inpe.br <http://www.inpe.br/> <http://www.inpe.br/
<http://www.inpe.br/>>
>>>>>>>>>> Tel.: (55) 12 3186-7966
>>>>>>>>>> ----------------------------------------------------------
>>>>>>>>>> ***** Save natural resources *****
>>>>>>>>>> =================================
>>>>>>>>>>
>>>>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT <
>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>>>>> JR Garcia,
>>>>>>>>>>>
>>>>>>>>>>> I see that you're having trouble reading this dataset, and
I
>>>>>> certainly
>>>>>>>>>>> agree, that error message isn't very helpful. I looked at
the
>>>> ncdump
>>>>>>>>>>> output you sent and don't see anything obviously wrong.
However,
>> I
>>>>>>>>>> haven't
>>>>>>>>>>> seen all those repeated "string" values in ncdump output
before.
>>>>>>>> Perhaps
>>>>>>>>>>> there's a netcdf version issue going on.
>>>>>>>>>>>
>>>>>>>>>>> If possible, the easiest way for me to debug would be for
you to
>>>>>> post a
>>>>>>>>>>> sample file to our anonymous ftp site following these
>> instructions:
>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>> <
>>>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp>>
>>>>>>>>>>> Also please indicate the version of MET that you're using.
>>>>>>>>>>>
>>>>>>>>>>> If I can replicate the behavior here, it should be pretty
easy to
>>>>>>>>>> determine
>>>>>>>>>>> the problem.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> John
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE) via
RT <
>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br> <mailto:
>>>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
>>>>>>>>>>>> Queue: met_help
>>>>>>>>>>>> Subject: FileType_None error in GridStat tool
>>>>>>>>>>>> Owner: Nobody
>>>>>>>>>>>> Requestors: roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br> <mailto:
>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
>>>>>>>>>>>> Status: new
>>>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
<https://rt.rap.ucar.edu/rt/>
>>>>>> Ticket/Display.html?id=80092
>>>>>>>> <
>>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>> >
>>>>>>>>>>>> Dear John, that met-help ticket which manipulated 90 time
slices
>>>> has
>>>>>>>>>>>> increased to 101 time slices. Attached are headers of the
ncdump
>>>>>>>> command
>>>>>>>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>>>>>>>
>>>>>>>>>>>> I'm running the following command:
>>>>>>>>>>>>
>>>>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>>>>>>>
>>>>>>>>>>>> And the entries for the forecast and observation fields
is
>>>>>> configured
>>>>>>>>>>>> inside GridStat.cfg are:
>>>>>>>>>>>>
>>>>>>>>>>>> // Forecast fields to be verified
==============================
>>>>>>>>>>>> fcst = {
>>>>>>>>>>>> field = [
>>>>>>>>>>>> {
>>>>>>>>>>>> name = "APCP";
>>>>>>>>>>>> level = "(0,0,*,*)"; // 24-hour
>>>> accumulation
>>>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
>> ] //
>>>>>>>> ORIGINAL
>>>>>>>>>>>> }
>>>>>>>>>>>> ];
>>>>>>>>>>>> }
>>>>>>>>>>>> // Observation fields to be verified
>>>> ==============================
>>>>>>>>>>>> obs = {
>>>>>>>>>>>> field = [
>>>>>>>>>>>> {
>>>>>>>>>>>> name = "APCP";
>>>>>>>>>>>> level = "(0,*,*)"; // 24-hour
>> accumulation
>>>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
>> ] //
>>>>>>>> ORIGINAL
>>>>>>>>>>>> }
>>>>>>>>>>>> ];
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> I'm getting the following error:
>>>>>>>>>>>>
>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
>>>>>>>>>>>> GridStatConfig_default
>>>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>>>>>> DEBUG 4: Me
>>>> Until the NCO sys admins can get it installed in a more general
area,
>> this
>>>> MET installation is available for use. We will be rolling out
some
>> patches
>>>> shortly, at which point I will update this installation.
>>>> t2dDataFileFactory::new_met_2d_data_file() -> created
>>>>>> new
>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>> ERROR :
>>>>>>>>>>>> ERROR : Trouble reading forecast file
>>>>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>>>>>>>> Eta40ens_00_036hs.nc"
>>>>>>>>>>>> ERROR :
>>>>>>>>>>>>
>>>>>>>>>>>> The message is not clear but I suppose MET was not able
to find
>>>> out
>>>>>>>> the
>>>>>>>>>>>> FCST file type. Could you help me, please?
>>>>>>>>>>>>
>>>>>>>>>>>> Best regards.
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>>>>>> =======================================================
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: John Halley Gotway
Time: Wed Apr 19 10:06:59 2017
JR Garcia,
OK, I understand the problem. You've put data for multiple
initialization
times into the same file. That is problematic when using the
CF-convention. I've never seen data structured that way, mixing
multiple
init times into the same file.
The most common way of organizing this type of data is to keep the
init
time fixed for each file and put multiple lead times in there. Or if
you've post-processed WRF output files using the unified post-
processor
(UPP), you'd have a separate GRIB output file for each lead time of
each
model initialization.
You may "know" the timing information of your data, but unless there's
something in the MET header columns to accurately define it, it'll be
confusing to do analysis on it.
If you'd like to keep your data structured in this way, I'd recommend
considering the following two options:
(1) Use met-6.0 and set the description entry in the config file
("desc")
to describe the timing information of your data. Whatever you put
there
will be passed through to the DESC output column.
(2) When you set up scripts to run met, after running Grid-Stat or
Point-Stat to generate output, run the ".stat" output files through
the
STAT-Analysis tool. Do a "filter" job to just read the input lines
and
write them to the output, but use the "-set_hdr" job command option to
explicitly override the timing information columns.
If it were me, I'd suggest following existing conventions to get the
timing
info correct in the first place. But of course, it's up to you to
process
your data as you see fit.
Thanks,
John
On Wed, Apr 19, 2017 at 8:46 AM, Garcia, J.R.M. via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>
> Excuse-me John, I saw your quick response and answered it but the
email
> was not delivered. That was it.
>
> Thanks John.
>
> I understood but I’m afraid I can’t include this variable due to the
way
> my NetCDF file is structured. It has one specific forecasting lead
time,
> let’s say 36-hs forecasting, so it will have several model
initialization
> times from the whole evaluation period and I joined all
correspondent 36-hs
> forecasting to it.
>
> I do the same for 24-hr, 48-hr, 60-hr, and so on….every lead time is
kept
> in a separated file. I’m a beginner in model evaluation and I
thought that
> as the evaluation must be per lead time I supposed that separating
them
> into distinct files would be feasible.
>
> But I also think that this information does not affect my evaluation
since
> I know which forecasting time I’m dealing with, am I right?
>
> Thanks
>
> 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 *****
> =================================
>
> > On 17 de abr de 2017, at 18:26, John Halley Gotway via RT <
> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >
> > JR Garcia,
> >
> > In the CF-convention, the "time" value specifies the valid time.
And
> there
> > is a convention for specifying the model initialization time. MET
> computes
> > the "lead_time" as the valid time minus the initialization time.
> >
> > Add a variable named "forecast_reference_time" that looks like
this:
> >
> > double forecast_reference_time
> > ;
> >
> > forecast_reference_time:long_name = "reference
time"
> > ;
> >
> > forecast_reference_time:units = "seconds since
1970-1-1" ;
> >
> > Thanks,
> > John
> >
> > On Mon, Apr 17, 2017 at 3:11 PM, Roberto Garcia (INPE) via RT <
> > met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 <
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
> >>
> >> Ok, John. Thanks again. It worked! I think we are getting there!
> >>
> >> Now, I'm wondering what element can change the Lead Time in the
file
> >> name. Can it be changed using grid_stat or it is a standard name
format
> >> that serves all MET tools and some of them can change it?
> >>
> >> grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
> >>
> >> 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 17/04/2017 17:48, John Halley Gotway via RT wrote:
> >>> JR Garcia,
> >>>
> >>> Yes, you can set the "cat_thresh" separately for each entry in
the
> >>> "fcst.field" and "obs.field" arrays.
> >>>
> >>> Usually people run Grid-Stat to compare the same type of data
from both
> >> the
> >>> forecast and observation datasets but there is no reason why you
have
> to.
> >>> For example, you have the flexibility to compare forecast
temperature
> to
> >>> observed precipitation. That probably won't yield very
meaningful
> >> results,
> >>> but if you did that, you'd probably want to specify different
> thresholds
> >>> for each field.
> >>>
> >>> But you're right, you can just specify "cat_thresh" once outside
the
> >> "fcst"
> >>> and "obs" settings and that one setting will be applied to both.
See
> >>> example below.
> >>>
> >>> Next... MET supports 3 different flavors of NetCDF, and the
timing
> >>> information is stored differently in them. Please just try
telling MET
> >> to
> >>> interpret your data following the CF-conventions using:
file_type =
> >>> NETCDF_NCCF; Since we want it apply to both the "fcst" and
"obs", I
> >> just
> >>> defined it once at the top-level context of the config file.
And I've
> >> also
> >>> included that in the Grid-Stat config example listed below.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
> >>> file_type = NETCDF_NCCF;
> >>>
> >>> // Forecast fields to be verified ==============================
> >>> fcst = {
> >>> field = [
> >>> {
> >>> name = "APCP";
> >>> level = "(0,0,*,*)"; // 24-hour accumulation
> >>> }
> >>> ];
> >>> }
> >>> // Observation fields to be verified
==============================
> >>> obs = {
> >>> field = [
> >>> {
> >>> name = "APCP";
> >>> level = "(0,*,*)"; // 24-hour accumulation
> >>> }
> >>> ];
> >>> }
> >>>
> >>> As for the issue with the timestamps,
> >>>
> >>>
> >>>
> >>>
> >>> On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT <
> >>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 <
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
> >>>>
> >>>> Dear John, can you clarify why the output files were generated
to
> >>>> 1970010 000000 valid time and 000000 lead time?
> >>>>
> >>>> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
> >>>>
> >>>> Below is the partial print of the forecasting NetCDF. Shouldn't
MET
> >>>> calculate the correct time according to the time slice I
specified in
> >>>> the config file *level = "(0,0,*,*)"* and its unit *"hours
since"*?
> What
> >>>> I'm doing wrong?
> >>>>
> >>>> variables:
> >>>> int time(time) ;
> >>>> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
> >>>> time:calendar = "standard" ;
> >>>> time:long_name = "Forecast target time" ;
> >>>>
> >>>> time = 411036, 411060, 411084, 411108, 411132, 411156,
411180,
> >> 411204,
> >>>> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
411396,
> >>>> 411420,
> >>>> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
411612,
> >>>> 411636,
> >>>>
> >>>>
> >>>> Another questions regarding the config file, please. At the
highest
> >>>> level of grid_stat config file there is a group of entries:
> >>>>
> >>>> cat_thresh = [ NA ];
> >>>> cnt_thresh = [ NA ];
> >>>> cnt_logic = UNION;
> >>>> wind_thresh = [ NA ];
> >>>> wind_logic = UNION;
> >>>>
> >>>> 1) Do them control the behavior of the verification in a
general
> aspect?
> >>>> Concerning cat_thresh specifically, what happens if I set some
> >>>> thresholds at it and also inside the fcst and/o obs entries?
> >>>>
> >>>> 2) Why there is cat_thresh entry for both fcst and obs entries?
> Wouldn't
> >>>> a general cat_thresh entry be enough? Does the use of different
> >>>> cat_thresh values for obs and fcst make sense?
> >>>>
> >>>> Thank you
> >>>>
> >>>>
> >>>> 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 <+55%2012%203208-7966>
> >>>> -------------------------------------------------------
> >>>> SAVE NATURAL RESOURCES!
> >>>> =======================================================
> >>>>
> >>>> On 17/04/2017 15:07, John Halley Gotway via RT wrote:
> >>>>> JR Garcia,
> >>>>>
> >>>>> You have the Nlat and Nlon global attributes set wrong in the
> >>>>> MERGE_20161201_20170228.nc file:
> >>>>> :Nlat = "245 grid_points" ;
> >>>>> :Nlon = "313 grid_points" ;
> >>>>>
> >>>>> Those numbers don't match the lat/lon dimensions:
> >>>>> dimensions:
> >>>>> time = 90 ;
> >>>>> lat = 313 ;
> >>>>> lon = 245 ;
> >>>>>
> >>>>> I ran the following command to switch them:
> >>>>>
> >>>>> ncatted -a Nlat,global,o,c,"313 grid_points" \
> >>>>> -a Nlon,global,o,c,"245 grid_points" \
> >>>>> MERGE_20161201_20170228.nc \
> >>>>> -o MERGE_20161201_20170228_PATCH.nc
> >>>>>
> >>>>> After switching that, MET version 5.2 processes them fine.
> >>>>>
> >>>>> Also, testing this out using version 6.0 revealed a little bug
we
> >>>>> introduced when switching from NetCDF3 to NetCDF4. I'll post
a
> bugfix
> >>>> for
> >>>>> this as soon as one is available.
> >>>>>
> >>>>> In order to run this data through version 6.0, you'll need
that
> bugfix.
> >>>>>
> >>>>> Thanks,
> >>>>> John
> >>>>>
> >>>>>
> >>>>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT
<
> >>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
> >>>>>>
> >>>>>> Data are there!
> >>>>>>
> >>>>>> Thanks John.
> >>>>>>
> >>>>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
> >>>>>>> JR Garcia,
> >>>>>>>
> >>>>>>> Can you please post a sample one of your converted files to
our ftp
> >>>> site
> >>>>>>> following these instructions:
> >>>>>>>
> >>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp <
> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
> >>>>>>>
> >>>>>>> I'll take a look at let you know what I find.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> John
> >>>>>>>
> >>>>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via
RT <
> >>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>>
> >>>>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
> >>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
> roberto.garcia at inpe.br>
> >>>>>>>> Queue: met_help
> >>>>>>>> Subject: can't set corner for variable "APCP" error
> >>>>>>>> Owner: Nobody
> >>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> roberto.garcia at inpe.br>
> >>>>>>>> Status: new
> >>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic <
> https://rt.rap.ucar.edu/rt/Tic>
> >>>> ket/Display.html?id=80169
> >>>>>>>> Hi John, I converted all obs and fct NetCDF files to the
NetCDF 3
> >>>>>>>> Classic version and issued the same command, could you
please help
> >> me
> >>>>>>>> interpret this error? What does "corner" refer to?
> >>>>>>>>
> >>>>>>>> Thanks
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
> >>>> rid.nc
> >>>>>>>> GridStat.cfg -v 4
> >>>>>>>>
> >>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
> >>>>>>>> GridStatConfig_default
> >>>>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> >> new
> >>>>>>>> Met2dDataFile object of type "FileType_NcMet".
> >>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>>>>>> DEBUG 4: lat_ll = -50.2
> >>>>>>>> DEBUG 4: lon_ll = 83
> >>>>>>>> DEBUG 4: delta_lat = 0.4
> >>>>>>>> DEBUG 4: delta_lon = 0.4
> >>>>>>>> DEBUG 4: Nlat = 157
> >>>>>>>> DEBUG 4: Nlon = 144
> >>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> >> new
> >>>>>>>> Met2dDataFile object of type "FileType_NcMet".
> >>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>>>>>> DEBUG 4: lat_ll = -50.2
> >>>>>>>> DEBUG 4: lon_ll = 82.8
> >>>>>>>> DEBUG 4: delta_lat = 0.2
> >>>>>>>> DEBUG 4: delta_lon = 0.2
> >>>>>>>> DEBUG 4: Nlat = 144
> >>>>>>>> DEBUG 4: Nlon = 157
> >>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
> >> object
> >>>> of
> >>>>>>>> type "FileType_NcMet".
> >>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
> >> object
> >>>> of
> >>>>>>>> type "FileType_NcMet".
> >>>>>>>> WARNING:
> >>>>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
> interpolation
> >>>>>>>> method, resetting method from "UW_MEAN" to "NEAREST" since
the
> >>>>>>>> interpolation width is 1.
> >>>>>>>> WARNING:
> >>>>>>>> DEBUG 3: Use the forecast grid.
> >>>>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny:
157
> >> lat_ll:
> >>>>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
> >>>>>>>> GSL_RNG_TYPE=mt19937
> >>>>>>>> GSL_RNG_SEED=1639511128
> >>>>>>>> DEBUG 1: Forecast File:
> >>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
> >>>> 00_036hs.nc
> >>>>>>>> DEBUG 1: Observation File:
> >>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
> >>>>>>>> 20161201_20170228_Eta40Grid.nc
> >>>>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
> >>>>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
> >>>>>>>> ERROR :
> >>>>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const
->
> can't
> >>>> set
> >>>>>>>> corner for variable "APCP"
> >>>>>>>> ERROR :
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> 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 <+55%2012%203208-7966>
> >>>>>>>> -------------------------------------------------------
> >>>>>>>> SAVE NATURAL RESOURCES!
> >>>>>>>> =======================================================
> >>>>>>>>
> >>>>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
> >>>>>>>>> JR Garcia,
> >>>>>>>>>
> >>>>>>>>> Thanks for sending the sample data file. This is
definitely a
> >>>> NetCDF4
> >>>>>>>> file
> >>>>>>>>> using the enhanced data model. MET version 5.2 is not
able to
> read
> >>>>>>>> NetCDF4
> >>>>>>>>> files. The recent release of MET (version 6.0) has been
enhanced
> >> to
> >>>> do
> >>>>>>>> so.
> >>>>>>>>> I tried a few things:
> >>>> Until the NCO sys admins can get it installed in a more general
area,
> >> this
> >>>> MET installation is available for use. We will be rolling out
some
> >> patches
> >>>> shortly, at which point I will update this installation.
> >>>>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
> >>>>>>>> command.
> >>>>>>>>> That results in the following error:
> >>>>>>>>>
> >>>>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
> >>>>>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
> >>>>>>>>> Location: file nccopy.c; line 788
> >>>>>>>>>
> >>>>>>>>> (2) View your file using ncview. It brings up the display
but
> all
> >>>> the
> >>>>>>>>> values are 0:
> >>>>>>>>>
> >>>>>>>>>> ncview FCT.nc
> >>>>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling
> >> it
> >>>> to
> >>>>>>>>> interpret it at a MET NetCDF file. That results in the
following
> >>>>>> error:
> >>>>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps
'name="APCP";
> >>>>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
> >>>>>>>>> terminate called after throwing an instance of
> >>>>>>>> 'netCDF::exceptions::NcChar'
> >>>>>>>>> what(): NcChar: Attempt to convert between text &
numbers
> >>>>>>>>> file: ncAtt.cpp line:104
> >>>>>>>>> Abort
> >>>>>>>>>
> >>>>>>>>> (4) Lastly, I ran (3) above through the debugger and found
that
> it
> >> is
> >>>>>>>>> indeed all those "string" types that are causing the
problem. I
> >> used
> >>>>>> the
> >>>>>>>>> ncatted utility to change those data types from "string"
to
> >>>>>> "character".
> >>>>>>>>> After doing that and telling MET to interpret it as a
> CF-compliant
> >>>>>> NetCDF
> >>>>>>>>> file, I was at least able to plot it. The plot looks bad
but at
> >>>> least
> >>>>>> it
> >>>>>>>>> works. Here are the very long commands I ran:
> >>>>>>>>>
> >>>>>>>>> # Run ncatted to switch types from strings to characters
> >>>>>>>>> ncatted FCT.nc \
> >>>>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
> >> 20170409_140422
> >>>>>>>> UTC on
> >>>>>>>>> host eslogin03 by the MET pcp_combine tool" \
> >>>>>>>>> -a MET_version,global,o,c,"V5.2" \
> >>>>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
> >>>>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
> >>>>>>>>> -a Projection,global,o,c,"LatLon" \
> >>>>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> >>>>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> >>>>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
> >>>>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
> >>>>>>>>> -a Nlat,global,o,c,"157 grid_points" \
> >>>>>>>>> -a Nlon,global,o,c,"144 grid_points" \
> >>>>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> >>>>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
> >>>>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> >>>>>>>>> -a source,global,o,c,"Eta40ens regional weather
forecasting
> model"
> >> \
> >>>>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
> >>>>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
> >>>>>>>>> -a increment,time,o,c,"24 hours in seconds" \
> >>>>>>>>> -a calendar,time,o,c,"standard" \
> >>>>>>>>> -a long_name,time,o,c,"Forecast target time" \
> >>>>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
> >>>>>>>>> -a long_name,member,o,c,"Members of the ensemble model
Eta40ens"
> \
> >>>>>>>>> -a long_name,lat,o,c,"latitude" \
> >>>>>>>>> -a units,lat,o,c,"degrees_north" \
> >>>>>>>>> -a standard_name,lat,o,c,"latitude" \
> >>>>>>>>> -a long_name,lon,o,c,"longitude" \
> >>>>>>>>> -a units,lon,o,c,"degrees_east" \
> >>>>>>>>> -a standard_name,lon,o,c,"longitude" \
> >>>>>>>>> -a Projection,APCP,o,c,"LatLon" \
> >>>>>>>>> -a units,APCP,o,c,"kg/m^2" \
> >>>>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
> precipitation"
> >> \
> >>>>>>>>> -o FCT_edit.nc
> >>>>>>>>>
> >>>>>>>>> # Run plot_data_plane version 6.0 to plot the file
> >>>>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
> >>>>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
> >>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 <
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
> >>>>>>>>>>
> >>>>>>>>>> Hi John,
> >>>>>>>>>>
> >>>>>>>>>> I’ve created garcia_data and put the files in your
incoming ftp
> >>>> site.
> >>>>>>>>>> Thank you for your help.
> >>>>>>>>>>
> >>>>>>>>>> About those repeated strings that I suppose you are
referring to
> >>>>>> *._deg
> >>>>>>>>>> strings, I’had to create them because one of MET tools
> complained
> >>>>>> about
> >>>>>>>> the
> >>>>>>>>>> lack of them, and I think it was grid_stat itself. To
generate
> >> them
> >>>> I
> >>>>>>>> took
> >>>>>>>>>> the pcp_combine output as a template but when running the
> >> grid_stat
> >>>>>>>> command
> >>>>>>>>>> it showed this message to me.
> >>>>>>>>>>
> >>>>>>>>>> Thank you again.
> >>>>>>>>>>
> >>>>>>>>>> JR Garcia
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> =================================
> >>>>>>>>>> Jose Roberto Motta Garcia, PhD
> >>>>>>>>>>
> >>>>>>>>>> www.cptec.inpe.br <http://www.cptec.inpe.br/> <
> http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>>
> >>>>>>>>>> www.inpe.br <http://www.inpe.br/> <http://www.inpe.br/ <
> http://www.inpe.br/>>
> >>>>>>>>>> Tel.: (55) 12 3186-7966
> >>>>>>>>>>
----------------------------------------------------------
> >>>>>>>>>> ***** Save natural resources *****
> >>>>>>>>>> =================================
> >>>>>>>>>>
> >>>>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT
<
> >>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu> <mailto:
> met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
> >>>>>>>>>>> JR Garcia,
> >>>>>>>>>>>
> >>>>>>>>>>> I see that you're having trouble reading this dataset,
and I
> >>>>>> certainly
> >>>>>>>>>>> agree, that error message isn't very helpful. I looked
at the
> >>>> ncdump
> >>>>>>>>>>> output you sent and don't see anything obviously wrong.
> However,
> >> I
> >>>>>>>>>> haven't
> >>>>>>>>>>> seen all those repeated "string" values in ncdump output
> before.
> >>>>>>>> Perhaps
> >>>>>>>>>>> there's a netcdf version issue going on.
> >>>>>>>>>>>
> >>>>>>>>>>> If possible, the easiest way for me to debug would be
for you
> to
> >>>>>> post a
> >>>>>>>>>>> sample file to our anonymous ftp site following these
> >> instructions:
> >>>>>>>>>>> http://www.dtcenter.org/met/
> users/support/met_help.php#ftp <http://www.dtcenter.org/met/
> users/support/met_help.php#ftp>
> >> <
> >>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
> http://www.dtcenter.org/met/users/support/met_help.php#ftp>>
> >>>>>>>>>>> Also please indicate the version of MET that you're
using.
> >>>>>>>>>>>
> >>>>>>>>>>> If I can replicate the behavior here, it should be
pretty easy
> to
> >>>>>>>>>> determine
> >>>>>>>>>>> the problem.
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> John
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE)
via RT <
> >>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu> <mailto:
> met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
> >>>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
> <mailto:roberto.garcia at inpe.br> <mailto:
> >>>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
> >>>>>>>>>>>> Queue: met_help
> >>>>>>>>>>>> Subject: FileType_None error in GridStat tool
> >>>>>>>>>>>> Owner: Nobody
> >>>>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> roberto.garcia at inpe.br> <mailto:
> >>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
> >>>>>>>>>>>> Status: new
> >>>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/ <
> https://rt.rap.ucar.edu/rt/>
> >>>>>> Ticket/Display.html?id=80092
> >>>>>>>> <
> >>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 <
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>> >
> >>>>>>>>>>>> Dear John, that met-help ticket which manipulated 90
time
> slices
> >>>> has
> >>>>>>>>>>>> increased to 101 time slices. Attached are headers of
the
> ncdump
> >>>>>>>> command
> >>>>>>>>>>>> for both FSCT.nc and OBS.nc.
> >>>>>>>>>>>>
> >>>>>>>>>>>> I'm running the following command:
> >>>>>>>>>>>>
> >>>>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
> >>>>>>>>>>>>
> >>>>>>>>>>>> And the entries for the forecast and observation fields
is
> >>>>>> configured
> >>>>>>>>>>>> inside GridStat.cfg are:
> >>>>>>>>>>>>
> >>>>>>>>>>>> // Forecast fields to be verified
> ==============================
> >>>>>>>>>>>> fcst = {
> >>>>>>>>>>>> field = [
> >>>>>>>>>>>> {
> >>>>>>>>>>>> name = "APCP";
> >>>>>>>>>>>> level = "(0,0,*,*)"; // 24-hour
> >>>> accumulation
> >>>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
> >> ] //
> >>>>>>>> ORIGINAL
> >>>>>>>>>>>> }
> >>>>>>>>>>>> ];
> >>>>>>>>>>>> }
> >>>>>>>>>>>> // Observation fields to be verified
> >>>> ==============================
> >>>>>>>>>>>> obs = {
> >>>>>>>>>>>> field = [
> >>>>>>>>>>>> {
> >>>>>>>>>>>> name = "APCP";
> >>>>>>>>>>>> level = "(0,*,*)"; // 24-hour
> >> accumulation
> >>>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
> >> ] //
> >>>>>>>> ORIGINAL
> >>>>>>>>>>>> }
> >>>>>>>>>>>> ];
> >>>>>>>>>>>> }
> >>>>>>>>>>>>
> >>>>>>>>>>>> I'm getting the following error:
> >>>>>>>>>>>>
> >>>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
> >>>>>>>>>>>> GridStatConfig_default
> >>>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>>>>>>>> DEBUG 4: Me
> >>>> Until the NCO sys admins can get it installed in a more general
area,
> >> this
> >>>> MET installation is available for use. We will be rolling out
some
> >> patches
> >>>> shortly, at which point I will update this installation.
> >>>> t2dDataFileFactory::new_met_2d_data_file() -> created
> >>>>>> new
> >>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>>> ERROR :
> >>>>>>>>>>>> ERROR : Trouble reading forecast file
> >>>>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
> >>>>>>>>>> Eta40ens_00_036hs.nc"
> >>>>>>>>>>>> ERROR :
> >>>>>>>>>>>>
> >>>>>>>>>>>> The message is not clear but I suppose MET was not able
to
> find
> >>>> out
> >>>>>>>> the
> >>>>>>>>>>>> FCST file type. Could you help me, please?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Best regards.
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> 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 <+55%2012%203208-7966>
> >>>>>>>>>>>> -------------------------------------------------------
> >>>>>>>>>>>> SAVE NATURAL RESOURCES!
> >>>>>>>>>>>> =======================================================
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #80169] can't set corner for variable "APCP" error
From: Roberto Garcia (INPE)
Time: Wed Apr 19 10:57:55 2017
Ok John, I got it. To build this structure I copied the idea from
ASCII
files I'm used to manipulate, NetCDF is new for me. I "know" I'd get
there in this way but I'll redirect my efforts to follow the CF-
convention.
I don't know if I'll find it somewhere but could you please answer me
if
the CF-convention allows four dimension APCP? I'm thinking about
storing
each ensemble member values together like [member, time, lat, lon] for
ensemble data. Will I have problems on running MET in such kind of
files? Or it is only another dimension I have to take care when
specifying the level entry? What is the recommendation?
Thank you very much.
Best regards.
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 19/04/2017 13:06, John Halley Gotway via RT wrote:
> JR Garcia,
>
> OK, I understand the problem. You've put data for multiple
initialization
> times into the same file. That is problematic when using the
> CF-convention. I've never seen data structured that way, mixing
multiple
> init times into the same file.
>
> The most common way of organizing this type of data is to keep the
init
> time fixed for each file and put multiple lead times in there. Or
if
> you've post-processed WRF output files using the unified post-
processor
> (UPP), you'd have a separate GRIB output file for each lead time of
each
> model initialization.
>
> You may "know" the timing information of your data, but unless
there's
> something in the MET header columns to accurately define it, it'll
be
> confusing to do analysis on it.
>
> If you'd like to keep your data structured in this way, I'd
recommend
> considering the following two options:
>
> (1) Use met-6.0 and set the description entry in the config file
("desc")
> to describe the timing information of your data. Whatever you put
there
> will be passed through to the DESC output column.
>
> (2) When you set up scripts to run met, after running Grid-Stat or
> Point-Stat to generate output, run the ".stat" output files through
the
> STAT-Analysis tool. Do a "filter" job to just read the input lines
and
> write them to the output, but use the "-set_hdr" job command option
to
> explicitly override the timing information columns.
>
> If it were me, I'd suggest following existing conventions to get the
timing
> info correct in the first place. But of course, it's up to you to
process
> your data as you see fit.
>
> Thanks,
> John
>
> On Wed, Apr 19, 2017 at 8:46 AM, Garcia, J.R.M. via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>>
>> Excuse-me John, I saw your quick response and answered it but the
email
>> was not delivered. That was it.
>>
>> Thanks John.
>>
>> I understood but I’m afraid I can’t include this variable due to
the way
>> my NetCDF file is structured. It has one specific forecasting lead
time,
>> let’s say 36-hs forecasting, so it will have several model
initialization
>> times from the whole evaluation period and I joined all
correspondent 36-hs
>> forecasting to it.
>>
>> I do the same for 24-hr, 48-hr, 60-hr, and so on….every lead time
is kept
>> in a separated file. I’m a beginner in model evaluation and I
thought that
>> as the evaluation must be per lead time I supposed that separating
them
>> into distinct files would be feasible.
>>
>> But I also think that this information does not affect my
evaluation since
>> I know which forecasting time I’m dealing with, am I right?
>>
>> Thanks
>>
>> 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 *****
>> =================================
>>
>>> On 17 de abr de 2017, at 18:26, John Halley Gotway via RT <
>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>> JR Garcia,
>>>
>>> In the CF-convention, the "time" value specifies the valid time.
And
>> there
>>> is a convention for specifying the model initialization time. MET
>> computes
>>> the "lead_time" as the valid time minus the initialization time.
>>>
>>> Add a variable named "forecast_reference_time" that looks like
this:
>>>
>>> double forecast_reference_time
>>> ;
>>>
>>> forecast_reference_time:long_name = "reference
time"
>>> ;
>>>
>>> forecast_reference_time:units = "seconds since
1970-1-1" ;
>>>
>>> Thanks,
>>> John
>>>
>>> On Mon, Apr 17, 2017 at 3:11 PM, Roberto Garcia (INPE) via RT <
>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 <
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>>> Ok, John. Thanks again. It worked! I think we are getting there!
>>>>
>>>> Now, I'm wondering what element can change the Lead Time in the
file
>>>> name. Can it be changed using grid_stat or it is a standard name
format
>>>> that serves all MET tools and some of them can change it?
>>>>
>>>> grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
>>>>
>>>> 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 17/04/2017 17:48, John Halley Gotway via RT wrote:
>>>>> JR Garcia,
>>>>>
>>>>> Yes, you can set the "cat_thresh" separately for each entry in
the
>>>>> "fcst.field" and "obs.field" arrays.
>>>>>
>>>>> Usually people run Grid-Stat to compare the same type of data
from both
>>>> the
>>>>> forecast and observation datasets but there is no reason why you
have
>> to.
>>>>> For example, you have the flexibility to compare forecast
temperature
>> to
>>>>> observed precipitation. That probably won't yield very
meaningful
>>>> results,
>>>>> but if you did that, you'd probably want to specify different
>> thresholds
>>>>> for each field.
>>>>>
>>>>> But you're right, you can just specify "cat_thresh" once outside
the
>>>> "fcst"
>>>>> and "obs" settings and that one setting will be applied to both.
See
>>>>> example below.
>>>>>
>>>>> Next... MET supports 3 different flavors of NetCDF, and the
timing
>>>>> information is stored differently in them. Please just try
telling MET
>>>> to
>>>>> interpret your data following the CF-conventions using:
file_type =
>>>>> NETCDF_NCCF; Since we want it apply to both the "fcst" and
"obs", I
>>>> just
>>>>> defined it once at the top-level context of the config file.
And I've
>>>> also
>>>>> included that in the Grid-Stat config example listed below.
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
>>>>> file_type = NETCDF_NCCF;
>>>>>
>>>>> // Forecast fields to be verified ==============================
>>>>> fcst = {
>>>>> field = [
>>>>> {
>>>>> name = "APCP";
>>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
>>>>> }
>>>>> ];
>>>>> }
>>>>> // Observation fields to be verified
==============================
>>>>> obs = {
>>>>> field = [
>>>>> {
>>>>> name = "APCP";
>>>>> level = "(0,*,*)"; // 24-hour accumulation
>>>>> }
>>>>> ];
>>>>> }
>>>>>
>>>>> As for the issue with the timestamps,
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT <
>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 <
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>>>>> Dear John, can you clarify why the output files were generated
to
>>>>>> 1970010 000000 valid time and 000000 lead time?
>>>>>>
>>>>>> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
>>>>>>
>>>>>> Below is the partial print of the forecasting NetCDF. Shouldn't
MET
>>>>>> calculate the correct time according to the time slice I
specified in
>>>>>> the config file *level = "(0,0,*,*)"* and its unit *"hours
since"*?
>> What
>>>>>> I'm doing wrong?
>>>>>>
>>>>>> variables:
>>>>>> int time(time) ;
>>>>>> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
>>>>>> time:calendar = "standard" ;
>>>>>> time:long_name = "Forecast target time" ;
>>>>>>
>>>>>> time = 411036, 411060, 411084, 411108, 411132, 411156,
411180,
>>>> 411204,
>>>>>> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
411396,
>>>>>> 411420,
>>>>>> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
411612,
>>>>>> 411636,
>>>>>>
>>>>>>
>>>>>> Another questions regarding the config file, please. At the
highest
>>>>>> level of grid_stat config file there is a group of entries:
>>>>>>
>>>>>> cat_thresh = [ NA ];
>>>>>> cnt_thresh = [ NA ];
>>>>>> cnt_logic = UNION;
>>>>>> wind_thresh = [ NA ];
>>>>>> wind_logic = UNION;
>>>>>>
>>>>>> 1) Do them control the behavior of the verification in a
general
>> aspect?
>>>>>> Concerning cat_thresh specifically, what happens if I set some
>>>>>> thresholds at it and also inside the fcst and/o obs entries?
>>>>>>
>>>>>> 2) Why there is cat_thresh entry for both fcst and obs entries?
>> Wouldn't
>>>>>> a general cat_thresh entry be enough? Does the use of different
>>>>>> cat_thresh values for obs and fcst make sense?
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>>
>>>>>> 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 <+55%2012%203208-7966>
>>>>>> -------------------------------------------------------
>>>>>> SAVE NATURAL RESOURCES!
>>>>>> =======================================================
>>>>>>
>>>>>> On 17/04/2017 15:07, John Halley Gotway via RT wrote:
>>>>>>> JR Garcia,
>>>>>>>
>>>>>>> You have the Nlat and Nlon global attributes set wrong in the
>>>>>>> MERGE_20161201_20170228.nc file:
>>>>>>> :Nlat = "245 grid_points" ;
>>>>>>> :Nlon = "313 grid_points" ;
>>>>>>>
>>>>>>> Those numbers don't match the lat/lon dimensions:
>>>>>>> dimensions:
>>>>>>> time = 90 ;
>>>>>>> lat = 313 ;
>>>>>>> lon = 245 ;
>>>>>>>
>>>>>>> I ran the following command to switch them:
>>>>>>>
>>>>>>> ncatted -a Nlat,global,o,c,"313 grid_points" \
>>>>>>> -a Nlon,global,o,c,"245 grid_points" \
>>>>>>> MERGE_20161201_20170228.nc \
>>>>>>> -o MERGE_20161201_20170228_PATCH.nc
>>>>>>>
>>>>>>> After switching that, MET version 5.2 processes them fine.
>>>>>>>
>>>>>>> Also, testing this out using version 6.0 revealed a little bug
we
>>>>>>> introduced when switching from NetCDF3 to NetCDF4. I'll post
a
>> bugfix
>>>>>> for
>>>>>>> this as soon as one is available.
>>>>>>>
>>>>>>> In order to run this data through version 6.0, you'll need
that
>> bugfix.
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via RT
<
>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>>>>>>> Data are there!
>>>>>>>>
>>>>>>>> Thanks John.
>>>>>>>>
>>>>>>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
>>>>>>>>> JR Garcia,
>>>>>>>>>
>>>>>>>>> Can you please post a sample one of your converted files to
our ftp
>>>>>> site
>>>>>>>>> following these instructions:
>>>>>>>>>
>>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
>>>>>>>>> I'll take a look at let you know what I find.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via
RT <
>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>>>>>>>>>
>>>>>>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
>> roberto.garcia at inpe.br>
>>>>>>>>>> Queue: met_help
>>>>>>>>>> Subject: can't set corner for variable "APCP" error
>>>>>>>>>> Owner: Nobody
>>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
>> roberto.garcia at inpe.br>
>>>>>>>>>> Status: new
>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic <
>> https://rt.rap.ucar.edu/rt/Tic>
>>>>>> ket/Display.html?id=80169
>>>>>>>>>> Hi John, I converted all obs and fct NetCDF files to the
NetCDF 3
>>>>>>>>>> Classic version and issued the same command, could you
please help
>>>> me
>>>>>>>>>> interpret this error? What does "corner" refer to?
>>>>>>>>>>
>>>>>>>>>> Thanks
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
>>>>>> rid.nc
>>>>>>>>>> GridStat.cfg -v 4
>>>>>>>>>>
>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-5.2/share/met/config/
>>>>>>>>>> GridStatConfig_default
>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>>>> new
>>>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>>>>>> DEBUG 4: lon_ll = 83
>>>>>>>>>> DEBUG 4: delta_lat = 0.4
>>>>>>>>>> DEBUG 4: delta_lon = 0.4
>>>>>>>>>> DEBUG 4: Nlat = 157
>>>>>>>>>> DEBUG 4: Nlon = 144
>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>>>> new
>>>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>>>>>> DEBUG 4: lon_ll = 82.8
>>>>>>>>>> DEBUG 4: delta_lat = 0.2
>>>>>>>>>> DEBUG 4: delta_lon = 0.2
>>>>>>>>>> DEBUG 4: Nlat = 144
>>>>>>>>>> DEBUG 4: Nlon = 157
>>>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
>>>> object
>>>>>> of
>>>>>>>>>> type "FileType_NcMet".
>>>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
>>>> object
>>>>>> of
>>>>>>>>>> type "FileType_NcMet".
>>>>>>>>>> WARNING:
>>>>>>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
>> interpolation
>>>>>>>>>> method, resetting method from "UW_MEAN" to "NEAREST" since
the
>>>>>>>>>> interpolation width is 1.
>>>>>>>>>> WARNING:
>>>>>>>>>> DEBUG 3: Use the forecast grid.
>>>>>>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny:
157
>>>> lat_ll:
>>>>>>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>>>>>>>>>> GSL_RNG_TYPE=mt19937
>>>>>>>>>> GSL_RNG_SEED=1639511128
>>>>>>>>>> DEBUG 1: Forecast File:
>>>>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
>>>>>> 00_036hs.nc
>>>>>>>>>> DEBUG 1: Observation File:
>>>>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>>>>>>>>>> 20161201_20170228_Eta40Grid.nc
>>>>>>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>>>>>>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
>>>>>>>>>> ERROR :
>>>>>>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &) const
->
>> can't
>>>>>> set
>>>>>>>>>> corner for variable "APCP"
>>>>>>>>>> ERROR :
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>>>> =======================================================
>>>>>>>>>>
>>>>>>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>>>>>>>>>> JR Garcia,
>>>>>>>>>>>
>>>>>>>>>>> Thanks for sending the sample data file. This is
definitely a
>>>>>> NetCDF4
>>>>>>>>>> file
>>>>>>>>>>> using the enhanced data model. MET version 5.2 is not
able to
>> read
>>>>>>>>>> NetCDF4
>>>>>>>>>>> files. The recent release of MET (version 6.0) has been
enhanced
>>>> to
>>>>>> do
>>>>>>>>>> so.
>>>>>>>>>>> I tried a few things:
>>>>>> Until the NCO sys admins can get it installed in a more general
area,
>>>> this
>>>>>> MET installation is available for use. We will be rolling out
some
>>>> patches
>>>>>> shortly, at which point I will update this installation.
>>>>>>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using the
nccopy
>>>>>>>>>> command.
>>>>>>>>>>> That results in the following error:
>>>>>>>>>>>
>>>>>>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>>>>>>>>>> NetCDF: Not a valid data type or _FillValue type mismatch
>>>>>>>>>>> Location: file nccopy.c; line 788
>>>>>>>>>>>
>>>>>>>>>>> (2) View your file using ncview. It brings up the display
but
>> all
>>>>>> the
>>>>>>>>>>> values are 0:
>>>>>>>>>>>
>>>>>>>>>>>> ncview FCT.nc
>>>>>>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that file
telling
>>>> it
>>>>>> to
>>>>>>>>>>> interpret it at a MET NetCDF file. That results in the
following
>>>>>>>> error:
>>>>>>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps
'name="APCP";
>>>>>>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>>>>>>>>>> terminate called after throwing an instance of
>>>>>>>>>> 'netCDF::exceptions::NcChar'
>>>>>>>>>>> what(): NcChar: Attempt to convert between text &
numbers
>>>>>>>>>>> file: ncAtt.cpp line:104
>>>>>>>>>>> Abort
>>>>>>>>>>>
>>>>>>>>>>> (4) Lastly, I ran (3) above through the debugger and found
that
>> it
>>>> is
>>>>>>>>>>> indeed all those "string" types that are causing the
problem. I
>>>> used
>>>>>>>> the
>>>>>>>>>>> ncatted utility to change those data types from "string"
to
>>>>>>>> "character".
>>>>>>>>>>> After doing that and telling MET to interpret it as a
>> CF-compliant
>>>>>>>> NetCDF
>>>>>>>>>>> file, I was at least able to plot it. The plot looks bad
but at
>>>>>> least
>>>>>>>> it
>>>>>>>>>>> works. Here are the very long commands I ran:
>>>>>>>>>>>
>>>>>>>>>>> # Run ncatted to switch types from strings to characters
>>>>>>>>>>> ncatted FCT.nc \
>>>>>>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
>>>> 20170409_140422
>>>>>>>>>> UTC on
>>>>>>>>>>> host eslogin03 by the MET pcp_combine tool" \
>>>>>>>>>>> -a MET_version,global,o,c,"V5.2" \
>>>>>>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
>>>>>>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>>>>>>>>>> -a Projection,global,o,c,"LatLon" \
>>>>>>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>>>>>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>>>>>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>>>>>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>>>>>>>>>> -a Nlat,global,o,c,"157 grid_points" \
>>>>>>>>>>> -a Nlon,global,o,c,"144 grid_points" \
>>>>>>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>>>>>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>>>>>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>>>>>>>>>> -a source,global,o,c,"Eta40ens regional weather
forecasting
>> model"
>>>> \
>>>>>>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>>>>>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC" \
>>>>>>>>>>> -a increment,time,o,c,"24 hours in seconds" \
>>>>>>>>>>> -a calendar,time,o,c,"standard" \
>>>>>>>>>>> -a long_name,time,o,c,"Forecast target time" \
>>>>>>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>>>>>>>>>> -a long_name,member,o,c,"Members of the ensemble model
Eta40ens"
>> \
>>>>>>>>>>> -a long_name,lat,o,c,"latitude" \
>>>>>>>>>>> -a units,lat,o,c,"degrees_north" \
>>>>>>>>>>> -a standard_name,lat,o,c,"latitude" \
>>>>>>>>>>> -a long_name,lon,o,c,"longitude" \
>>>>>>>>>>> -a units,lon,o,c,"degrees_east" \
>>>>>>>>>>> -a standard_name,lon,o,c,"longitude" \
>>>>>>>>>>> -a Projection,APCP,o,c,"LatLon" \
>>>>>>>>>>> -a units,APCP,o,c,"kg/m^2" \
>>>>>>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
>> precipitation"
>>>> \
>>>>>>>>>>> -o FCT_edit.nc
>>>>>>>>>>>
>>>>>>>>>>> # Run plot_data_plane version 6.0 to plot the file
>>>>>>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
'name="APCP";
>>>>>>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 <
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
>>>>>>>>>>>> Hi John,
>>>>>>>>>>>>
>>>>>>>>>>>> I’ve created garcia_data and put the files in your
incoming ftp
>>>>>> site.
>>>>>>>>>>>> Thank you for your help.
>>>>>>>>>>>>
>>>>>>>>>>>> About those repeated strings that I suppose you are
referring to
>>>>>>>> *._deg
>>>>>>>>>>>> strings, I’had to create them because one of MET tools
>> complained
>>>>>>>> about
>>>>>>>>>> the
>>>>>>>>>>>> lack of them, and I think it was grid_stat itself. To
generate
>>>> them
>>>>>> I
>>>>>>>>>> took
>>>>>>>>>>>> the pcp_combine output as a template but when running the
>>>> grid_stat
>>>>>>>>>> command
>>>>>>>>>>>> it showed this message to me.
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you again.
>>>>>>>>>>>>
>>>>>>>>>>>> JR Garcia
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> =================================
>>>>>>>>>>>> Jose Roberto Motta Garcia, PhD
>>>>>>>>>>>>
>>>>>>>>>>>> www.cptec.inpe.br <http://www.cptec.inpe.br/> <
>> http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>>
>>>>>>>>>>>> www.inpe.br <http://www.inpe.br/> <http://www.inpe.br/ <
>> http://www.inpe.br/>>
>>>>>>>>>>>> Tel.: (55) 12 3186-7966
>>>>>>>>>>>>
----------------------------------------------------------
>>>>>>>>>>>> ***** Save natural resources *****
>>>>>>>>>>>> =================================
>>>>>>>>>>>>
>>>>>>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via RT
<
>>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu> <mailto:
>> met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>>>>>>> JR Garcia,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I see that you're having trouble reading this dataset,
and I
>>>>>>>> certainly
>>>>>>>>>>>>> agree, that error message isn't very helpful. I looked
at the
>>>>>> ncdump
>>>>>>>>>>>>> output you sent and don't see anything obviously wrong.
>> However,
>>>> I
>>>>>>>>>>>> haven't
>>>>>>>>>>>>> seen all those repeated "string" values in ncdump output
>> before.
>>>>>>>>>> Perhaps
>>>>>>>>>>>>> there's a netcdf version issue going on.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If possible, the easiest way for me to debug would be
for you
>> to
>>>>>>>> post a
>>>>>>>>>>>>> sample file to our anonymous ftp site following these
>>>> instructions:
>>>>>>>>>>>>> http://www.dtcenter.org/met/
>> users/support/met_help.php#ftp <http://www.dtcenter.org/met/
>> users/support/met_help.php#ftp>
>>>> <
>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp>>
>>>>>>>>>>>>> Also please indicate the version of MET that you're
using.
>>>>>>>>>>>>>
>>>>>>>>>>>>> If I can replicate the behavior here, it should be
pretty easy
>> to
>>>>>>>>>>>> determine
>>>>>>>>>>>>> the problem.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> John
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE)
via RT <
>>>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu> <mailto:
>> met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted upon.
>>>>>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
>> <mailto:roberto.garcia at inpe.br> <mailto:
>>>>>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
>>>>>>>>>>>>>> Queue: met_help
>>>>>>>>>>>>>> Subject: FileType_None error in GridStat tool
>>>>>>>>>>>>>> Owner: Nobody
>>>>>>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
>> roberto.garcia at inpe.br> <mailto:
>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
>>>>>>>>>>>>>> Status: new
>>>>>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/ <
>> https://rt.rap.ucar.edu/rt/>
>>>>>>>> Ticket/Display.html?id=80092
>>>>>>>>>> <
>>>>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092 <
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>> >
>>>>>>>>>>>>>> Dear John, that met-help ticket which manipulated 90
time
>> slices
>>>>>> has
>>>>>>>>>>>>>> increased to 101 time slices. Attached are headers of
the
>> ncdump
>>>>>>>>>> command
>>>>>>>>>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm running the following command:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> And the entries for the forecast and observation fields
is
>>>>>>>> configured
>>>>>>>>>>>>>> inside GridStat.cfg are:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> // Forecast fields to be verified
>> ==============================
>>>>>>>>>>>>>> fcst = {
>>>>>>>>>>>>>> field = [
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> name = "APCP";
>>>>>>>>>>>>>> level = "(0,0,*,*)"; // 24-hour
>>>>>> accumulation
>>>>>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
>>>> ] //
>>>>>>>>>> ORIGINAL
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>> ];
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>> // Observation fields to be verified
>>>>>> ==============================
>>>>>>>>>>>>>> obs = {
>>>>>>>>>>>>>> field = [
>>>>>>>>>>>>>> {
>>>>>>>>>>>>>> name = "APCP";
>>>>>>>>>>>>>> level = "(0,*,*)"; // 24-hour
>>>> accumulation
>>>>>>>>>>>>>> cat_thresh = [ NA ]; // [ >1.0,
>=5.0
>>>> ] //
>>>>>>>>>> ORIGINAL
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>> ];
>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm getting the following error:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
>>>>>>>>>>>>>> GridStatConfig_default
>>>>>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>>>>>>>> DEBUG 4: Me
>>>>>> Until the NCO sys admins can get it installed in a more general
area,
>>>> this
>>>>>> MET installation is available for use. We will be rolling out
some
>>>> patches
>>>>>> shortly, at which point I will update this installation.
>>>>>> t2dDataFileFactory::new_met_2d_data_file() -> created
>>>>>>>> new
>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>>> ERROR :
>>>>>>>>>>>>>> ERROR : Trouble reading forecast file
>>>>>>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>>>>>>>>>> Eta40ens_00_036hs.nc"
>>>>>>>>>>>>>> ERROR :
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The message is not clear but I suppose MET was not able
to
>> find
>>>>>> out
>>>>>>>>>> the
>>>>>>>>>>>>>> FCST file type. Could you help me, please?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Best regards.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>>>>>>>> =======================================================
>>
>>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: John Halley Gotway
Time: Thu Apr 20 16:21:44 2017
JR Garcia,
The CF-convention does allow for 4-dimensional variables, but I think
you'll have trouble configuring MET to handle that.
Presumably, with ensemble data you'd want to run the MET Ensemble-Stat
tool. That tool expects you to pass it N files, 1 for each ensemble
member. And it extracts the same field from each input file. If all
members are contained within the same file, that logic won't work.
Here's the most typical way I've seen people store this type of
data...
Place all output times for each a single initialization time in the
same
file. Write different NetCDF files for each ensemble member.
If your data is on a lat/lon grid, using the CF-convention is very
easy.
If it's on some other projection (lambert conformal, polar
sterographic, or
mercator) defining that projection info gets very confusing.
Thanks,
John
On Wed, Apr 19, 2017 at 10:57 AM, Roberto Garcia (INPE) via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
>
> Ok John, I got it. To build this structure I copied the idea from
ASCII
> files I'm used to manipulate, NetCDF is new for me. I "know" I'd get
> there in this way but I'll redirect my efforts to follow the CF-
convention.
>
> I don't know if I'll find it somewhere but could you please answer
me if
> the CF-convention allows four dimension APCP? I'm thinking about
storing
> each ensemble member values together like [member, time, lat, lon]
for
> ensemble data. Will I have problems on running MET in such kind of
> files? Or it is only another dimension I have to take care when
> specifying the level entry? What is the recommendation?
>
> Thank you very much.
>
> Best regards.
>
> 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 19/04/2017 13:06, John Halley Gotway via RT wrote:
> > JR Garcia,
> >
> > OK, I understand the problem. You've put data for multiple
> initialization
> > times into the same file. That is problematic when using the
> > CF-convention. I've never seen data structured that way, mixing
multiple
> > init times into the same file.
> >
> > The most common way of organizing this type of data is to keep the
init
> > time fixed for each file and put multiple lead times in there. Or
if
> > you've post-processed WRF output files using the unified post-
processor
> > (UPP), you'd have a separate GRIB output file for each lead time
of each
> > model initialization.
> >
> > You may "know" the timing information of your data, but unless
there's
> > something in the MET header columns to accurately define it, it'll
be
> > confusing to do analysis on it.
> >
> > If you'd like to keep your data structured in this way, I'd
recommend
> > considering the following two options:
> >
> > (1) Use met-6.0 and set the description entry in the config file
("desc")
> > to describe the timing information of your data. Whatever you put
there
> > will be passed through to the DESC output column.
> >
> > (2) When you set up scripts to run met, after running Grid-Stat or
> > Point-Stat to generate output, run the ".stat" output files
through the
> > STAT-Analysis tool. Do a "filter" job to just read the input
lines and
> > write them to the output, but use the "-set_hdr" job command
option to
> > explicitly override the timing information columns.
> >
> > If it were me, I'd suggest following existing conventions to get
the
> timing
> > info correct in the first place. But of course, it's up to you to
> process
> > your data as you see fit.
> >
> > Thanks,
> > John
> >
> > On Wed, Apr 19, 2017 at 8:46 AM, Garcia, J.R.M. via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 >
> >>
> >> Excuse-me John, I saw your quick response and answered it but the
email
> >> was not delivered. That was it.
> >>
> >> Thanks John.
> >>
> >> I understood but I’m afraid I can’t include this variable due to
the way
> >> my NetCDF file is structured. It has one specific forecasting
lead time,
> >> let’s say 36-hs forecasting, so it will have several model
> initialization
> >> times from the whole evaluation period and I joined all
correspondent
> 36-hs
> >> forecasting to it.
> >>
> >> I do the same for 24-hr, 48-hr, 60-hr, and so on….every lead time
is
> kept
> >> in a separated file. I’m a beginner in model evaluation and I
thought
> that
> >> as the evaluation must be per lead time I supposed that
separating them
> >> into distinct files would be feasible.
> >>
> >> But I also think that this information does not affect my
evaluation
> since
> >> I know which forecasting time I’m dealing with, am I right?
> >>
> >> Thanks
> >>
> >> 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 *****
> >> =================================
> >>
> >>> On 17 de abr de 2017, at 18:26, John Halley Gotway via RT <
> >> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>> JR Garcia,
> >>>
> >>> In the CF-convention, the "time" value specifies the valid time.
And
> >> there
> >>> is a convention for specifying the model initialization time.
MET
> >> computes
> >>> the "lead_time" as the valid time minus the initialization time.
> >>>
> >>> Add a variable named "forecast_reference_time" that looks like
this:
> >>>
> >>> double forecast_reference_time
> >>> ;
> >>>
> >>> forecast_reference_time:long_name = "reference
time"
> >>> ;
> >>>
> >>> forecast_reference_time:units = "seconds since
> 1970-1-1" ;
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> On Mon, Apr 17, 2017 at 3:11 PM, Roberto Garcia (INPE) via RT <
> >>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 <
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
> >>>> Ok, John. Thanks again. It worked! I think we are getting
there!
> >>>>
> >>>> Now, I'm wondering what element can change the Lead Time in the
file
> >>>> name. Can it be changed using grid_stat or it is a standard
name
> format
> >>>> that serves all MET tools and some of them can change it?
> >>>>
> >>>> grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
> >>>>
> >>>> 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 17/04/2017 17:48, John Halley Gotway via RT wrote:
> >>>>> JR Garcia,
> >>>>>
> >>>>> Yes, you can set the "cat_thresh" separately for each entry in
the
> >>>>> "fcst.field" and "obs.field" arrays.
> >>>>>
> >>>>> Usually people run Grid-Stat to compare the same type of data
from
> both
> >>>> the
> >>>>> forecast and observation datasets but there is no reason why
you have
> >> to.
> >>>>> For example, you have the flexibility to compare forecast
temperature
> >> to
> >>>>> observed precipitation. That probably won't yield very
meaningful
> >>>> results,
> >>>>> but if you did that, you'd probably want to specify different
> >> thresholds
> >>>>> for each field.
> >>>>>
> >>>>> But you're right, you can just specify "cat_thresh" once
outside the
> >>>> "fcst"
> >>>>> and "obs" settings and that one setting will be applied to
both. See
> >>>>> example below.
> >>>>>
> >>>>> Next... MET supports 3 different flavors of NetCDF, and the
timing
> >>>>> information is stored differently in them. Please just try
telling
> MET
> >>>> to
> >>>>> interpret your data following the CF-conventions using:
file_type =
> >>>>> NETCDF_NCCF; Since we want it apply to both the "fcst" and
"obs", I
> >>>> just
> >>>>> defined it once at the top-level context of the config file.
And
> I've
> >>>> also
> >>>>> included that in the Grid-Stat config example listed below.
> >>>>>
> >>>>> Thanks,
> >>>>> John
> >>>>>
> >>>>> cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
> >>>>> file_type = NETCDF_NCCF;
> >>>>>
> >>>>> // Forecast fields to be verified
==============================
> >>>>> fcst = {
> >>>>> field = [
> >>>>> {
> >>>>> name = "APCP";
> >>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
> >>>>> }
> >>>>> ];
> >>>>> }
> >>>>> // Observation fields to be verified
==============================
> >>>>> obs = {
> >>>>> field = [
> >>>>> {
> >>>>> name = "APCP";
> >>>>> level = "(0,*,*)"; // 24-hour
accumulation
> >>>>> }
> >>>>> ];
> >>>>> }
> >>>>>
> >>>>> As for the issue with the timestamps,
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT
<
> >>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
> >>>>>> Dear John, can you clarify why the output files were
generated to
> >>>>>> 1970010 000000 valid time and 000000 lead time?
> >>>>>>
> >>>>>> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
> >>>>>>
> >>>>>> Below is the partial print of the forecasting NetCDF.
Shouldn't MET
> >>>>>> calculate the correct time according to the time slice I
specified
> in
> >>>>>> the config file *level = "(0,0,*,*)"* and its unit *"hours
since"*?
> >> What
> >>>>>> I'm doing wrong?
> >>>>>>
> >>>>>> variables:
> >>>>>> int time(time) ;
> >>>>>> time:units = "hours since 1970-01-01 00:00:00 UTC"
;
> >>>>>> time:calendar = "standard" ;
> >>>>>> time:long_name = "Forecast target time" ;
> >>>>>>
> >>>>>> time = 411036, 411060, 411084, 411108, 411132, 411156,
411180,
> >>>> 411204,
> >>>>>> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
> 411396,
> >>>>>> 411420,
> >>>>>> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
> 411612,
> >>>>>> 411636,
> >>>>>>
> >>>>>>
> >>>>>> Another questions regarding the config file, please. At the
highest
> >>>>>> level of grid_stat config file there is a group of entries:
> >>>>>>
> >>>>>> cat_thresh = [ NA ];
> >>>>>> cnt_thresh = [ NA ];
> >>>>>> cnt_logic = UNION;
> >>>>>> wind_thresh = [ NA ];
> >>>>>> wind_logic = UNION;
> >>>>>>
> >>>>>> 1) Do them control the behavior of the verification in a
general
> >> aspect?
> >>>>>> Concerning cat_thresh specifically, what happens if I set
some
> >>>>>> thresholds at it and also inside the fcst and/o obs entries?
> >>>>>>
> >>>>>> 2) Why there is cat_thresh entry for both fcst and obs
entries?
> >> Wouldn't
> >>>>>> a general cat_thresh entry be enough? Does the use of
different
> >>>>>> cat_thresh values for obs and fcst make sense?
> >>>>>>
> >>>>>> Thank you
> >>>>>>
> >>>>>>
> >>>>>> 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 <+55%2012%203208-7966>
> >>>>>> -------------------------------------------------------
> >>>>>> SAVE NATURAL RESOURCES!
> >>>>>> =======================================================
> >>>>>>
> >>>>>> On 17/04/2017 15:07, John Halley Gotway via RT wrote:
> >>>>>>> JR Garcia,
> >>>>>>>
> >>>>>>> You have the Nlat and Nlon global attributes set wrong in
the
> >>>>>>> MERGE_20161201_20170228.nc file:
> >>>>>>> :Nlat = "245 grid_points" ;
> >>>>>>> :Nlon = "313 grid_points" ;
> >>>>>>>
> >>>>>>> Those numbers don't match the lat/lon dimensions:
> >>>>>>> dimensions:
> >>>>>>> time = 90 ;
> >>>>>>> lat = 313 ;
> >>>>>>> lon = 245 ;
> >>>>>>>
> >>>>>>> I ran the following command to switch them:
> >>>>>>>
> >>>>>>> ncatted -a Nlat,global,o,c,"313 grid_points" \
> >>>>>>> -a Nlon,global,o,c,"245 grid_points" \
> >>>>>>> MERGE_20161201_20170228.nc \
> >>>>>>> -o MERGE_20161201_20170228_PATCH.nc
> >>>>>>>
> >>>>>>> After switching that, MET version 5.2 processes them fine.
> >>>>>>>
> >>>>>>> Also, testing this out using version 6.0 revealed a little
bug we
> >>>>>>> introduced when switching from NetCDF3 to NetCDF4. I'll
post a
> >> bugfix
> >>>>>> for
> >>>>>>> this as soon as one is available.
> >>>>>>>
> >>>>>>> In order to run this data through version 6.0, you'll need
that
> >> bugfix.
> >>>>>>> Thanks,
> >>>>>>> John
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via
RT <
> >>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169 <
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
> >>>>>>>> Data are there!
> >>>>>>>>
> >>>>>>>> Thanks John.
> >>>>>>>>
> >>>>>>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
> >>>>>>>>> JR Garcia,
> >>>>>>>>>
> >>>>>>>>> Can you please post a sample one of your converted files
to our
> ftp
> >>>>>> site
> >>>>>>>>> following these instructions:
> >>>>>>>>>
> >>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<
> >> http://www.dtcenter.org/met/users/support/met_help.php#ftp>
> >>>>>>>>> I'll take a look at let you know what I find.
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> John
> >>>>>>>>>
> >>>>>>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via
RT <
> >>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
> >>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:
> >> roberto.garcia at inpe.br>
> >>>>>>>>>> Queue: met_help
> >>>>>>>>>> Subject: can't set corner for variable "APCP"
error
> >>>>>>>>>> Owner: Nobody
> >>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> >> roberto.garcia at inpe.br>
> >>>>>>>>>> Status: new
> >>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic <
> >> https://rt.rap.ucar.edu/rt/Tic>
> >>>>>> ket/Display.html?id=80169
> >>>>>>>>>> Hi John, I converted all obs and fct NetCDF files to the
NetCDF
> 3
> >>>>>>>>>> Classic version and issued the same command, could you
please
> help
> >>>> me
> >>>>>>>>>> interpret this error? What does "corner" refer to?
> >>>>>>>>>>
> >>>>>>>>>> Thanks
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>> grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
> >>>>>> rid.nc
> >>>>>>>>>> GridStat.cfg -v 4
> >>>>>>>>>>
> >>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
> >>>>>>>>>> GridStatConfig_default
> >>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
> created
> >>>> new
> >>>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
> >>>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>>>>>>>> DEBUG 4: lat_ll = -50.2
> >>>>>>>>>> DEBUG 4: lon_ll = 83
> >>>>>>>>>> DEBUG 4: delta_lat = 0.4
> >>>>>>>>>> DEBUG 4: delta_lon = 0.4
> >>>>>>>>>> DEBUG 4: Nlat = 157
> >>>>>>>>>> DEBUG 4: Nlon = 144
> >>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
> created
> >>>> new
> >>>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
> >>>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
> >>>>>>>>>> DEBUG 4: lat_ll = -50.2
> >>>>>>>>>> DEBUG 4: lon_ll = 82.8
> >>>>>>>>>> DEBUG 4: delta_lat = 0.2
> >>>>>>>>>> DEBUG 4: delta_lon = 0.2
> >>>>>>>>>> DEBUG 4: Nlat = 144
> >>>>>>>>>> DEBUG 4: Nlon = 157
> >>>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
> >>>> object
> >>>>>> of
> >>>>>>>>>> type "FileType_NcMet".
> >>>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
> >>>> object
> >>>>>> of
> >>>>>>>>>> type "FileType_NcMet".
> >>>>>>>>>> WARNING:
> >>>>>>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
> >> interpolation
> >>>>>>>>>> method, resetting method from "UW_MEAN" to "NEAREST"
since the
> >>>>>>>>>> interpolation width is 1.
> >>>>>>>>>> WARNING:
> >>>>>>>>>> DEBUG 3: Use the forecast grid.
> >>>>>>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny:
157
> >>>> lat_ll:
> >>>>>>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
> >>>>>>>>>> GSL_RNG_TYPE=mt19937
> >>>>>>>>>> GSL_RNG_SEED=1639511128
> >>>>>>>>>> DEBUG 1: Forecast File:
> >>>>>>>>>>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
> >>>>>> 00_036hs.nc
> >>>>>>>>>> DEBUG 1: Observation File:
> >>>>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
> >>>>>>>>>> 20161201_20170228_Eta40Grid.nc
> >>>>>>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
> >>>>>>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
> >>>>>>>>>> ERROR :
> >>>>>>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &)
const ->
> >> can't
> >>>>>> set
> >>>>>>>>>> corner for variable "APCP"
> >>>>>>>>>> ERROR :
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 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 <+55%2012%203208-7966>
> >>>>>>>>>> -------------------------------------------------------
> >>>>>>>>>> SAVE NATURAL RESOURCES!
> >>>>>>>>>> =======================================================
> >>>>>>>>>>
> >>>>>>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
> >>>>>>>>>>> JR Garcia,
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks for sending the sample data file. This is
definitely a
> >>>>>> NetCDF4
> >>>>>>>>>> file
> >>>>>>>>>>> using the enhanced data model. MET version 5.2 is not
able to
> >> read
> >>>>>>>>>> NetCDF4
> >>>>>>>>>>> files. The recent release of MET (version 6.0) has been
> enhanced
> >>>> to
> >>>>>> do
> >>>>>>>>>> so.
> >>>>>>>>>>> I tried a few things:
> >>>>>> Until the NCO sys admins can get it installed in a more
general
> area,
> >>>> this
> >>>>>> MET installation is available for use. We will be rolling
out some
> >>>> patches
> >>>>>> shortly, at which point I will update this installation.
> >>>>>>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using
the
> nccopy
> >>>>>>>>>> command.
> >>>>>>>>>>> That results in the following error:
> >>>>>>>>>>>
> >>>>>>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
> >>>>>>>>>>> NetCDF: Not a valid data type or _FillValue type
mismatch
> >>>>>>>>>>> Location: file nccopy.c; line 788
> >>>>>>>>>>>
> >>>>>>>>>>> (2) View your file using ncview. It brings up the
display but
> >> all
> >>>>>> the
> >>>>>>>>>>> values are 0:
> >>>>>>>>>>>
> >>>>>>>>>>>> ncview FCT.nc
> >>>>>>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that
file
> telling
> >>>> it
> >>>>>> to
> >>>>>>>>>>> interpret it at a MET NetCDF file. That results in the
> following
> >>>>>>>> error:
> >>>>>>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps
'name="APCP";
> >>>>>>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
> >>>>>>>>>>> terminate called after throwing an instance of
> >>>>>>>>>> 'netCDF::exceptions::NcChar'
> >>>>>>>>>>> what(): NcChar: Attempt to convert between text &
> numbers
> >>>>>>>>>>> file: ncAtt.cpp line:104
> >>>>>>>>>>> Abort
> >>>>>>>>>>>
> >>>>>>>>>>> (4) Lastly, I ran (3) above through the debugger and
found that
> >> it
> >>>> is
> >>>>>>>>>>> indeed all those "string" types that are causing the
problem.
> I
> >>>> used
> >>>>>>>> the
> >>>>>>>>>>> ncatted utility to change those data types from "string"
to
> >>>>>>>> "character".
> >>>>>>>>>>> After doing that and telling MET to interpret it as a
> >> CF-compliant
> >>>>>>>> NetCDF
> >>>>>>>>>>> file, I was at least able to plot it. The plot looks
bad but
> at
> >>>>>> least
> >>>>>>>> it
> >>>>>>>>>>> works. Here are the very long commands I ran:
> >>>>>>>>>>>
> >>>>>>>>>>> # Run ncatted to switch types from strings to characters
> >>>>>>>>>>> ncatted FCT.nc \
> >>>>>>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
> >>>> 20170409_140422
> >>>>>>>>>> UTC on
> >>>>>>>>>>> host eslogin03 by the MET pcp_combine tool" \
> >>>>>>>>>>> -a MET_version,global,o,c,"V5.2" \
> >>>>>>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
> >>>>>>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
> >>>>>>>>>>> -a Projection,global,o,c,"LatLon" \
> >>>>>>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
> >>>>>>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
> >>>>>>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
> >>>>>>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
> >>>>>>>>>>> -a Nlat,global,o,c,"157 grid_points" \
> >>>>>>>>>>> -a Nlon,global,o,c,"144 grid_points" \
> >>>>>>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
> >>>>>>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
> >>>>>>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
> >>>>>>>>>>> -a source,global,o,c,"Eta40ens regional weather
forecasting
> >> model"
> >>>> \
> >>>>>>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
> >>>>>>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC"
\
> >>>>>>>>>>> -a increment,time,o,c,"24 hours in seconds" \
> >>>>>>>>>>> -a calendar,time,o,c,"standard" \
> >>>>>>>>>>> -a long_name,time,o,c,"Forecast target time" \
> >>>>>>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
> >>>>>>>>>>> -a long_name,member,o,c,"Members of the ensemble model
> Eta40ens"
> >> \
> >>>>>>>>>>> -a long_name,lat,o,c,"latitude" \
> >>>>>>>>>>> -a units,lat,o,c,"degrees_north" \
> >>>>>>>>>>> -a standard_name,lat,o,c,"latitude" \
> >>>>>>>>>>> -a long_name,lon,o,c,"longitude" \
> >>>>>>>>>>> -a units,lon,o,c,"degrees_east" \
> >>>>>>>>>>> -a standard_name,lon,o,c,"longitude" \
> >>>>>>>>>>> -a Projection,APCP,o,c,"LatLon" \
> >>>>>>>>>>> -a units,APCP,o,c,"kg/m^2" \
> >>>>>>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
> >> precipitation"
> >>>> \
> >>>>>>>>>>> -o FCT_edit.nc
> >>>>>>>>>>>
> >>>>>>>>>>> # Run plot_data_plane version 6.0 to plot the file
> >>>>>>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
> 'name="APCP";
> >>>>>>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
> >>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
> <
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> >
> >>>>>>>>>>>> Hi John,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I’ve created garcia_data and put the files in your
incoming
> ftp
> >>>>>> site.
> >>>>>>>>>>>> Thank you for your help.
> >>>>>>>>>>>>
> >>>>>>>>>>>> About those repeated strings that I suppose you are
referring
> to
> >>>>>>>> *._deg
> >>>>>>>>>>>> strings, I’had to create them because one of MET tools
> >> complained
> >>>>>>>> about
> >>>>>>>>>> the
> >>>>>>>>>>>> lack of them, and I think it was grid_stat itself. To
generate
> >>>> them
> >>>>>> I
> >>>>>>>>>> took
> >>>>>>>>>>>> the pcp_combine output as a template but when running
the
> >>>> grid_stat
> >>>>>>>>>> command
> >>>>>>>>>>>> it showed this message to me.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thank you again.
> >>>>>>>>>>>>
> >>>>>>>>>>>> JR Garcia
> >>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> =================================
> >>>>>>>>>>>> Jose Roberto Motta Garcia, PhD
> >>>>>>>>>>>>
> >>>>>>>>>>>> www.cptec.inpe.br <http://www.cptec.inpe.br/> <
> >> http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>>
> >>>>>>>>>>>> www.inpe.br <http://www.inpe.br/> <http://www.inpe.br/
<
> >> http://www.inpe.br/>>
> >>>>>>>>>>>> Tel.: (55) 12 3186-7966
> >>>>>>>>>>>>
----------------------------------------------------------
> >>>>>>>>>>>> ***** Save natural resources *****
> >>>>>>>>>>>> =================================
> >>>>>>>>>>>>
> >>>>>>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via
RT <
> >>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu> <mailto:
> >> met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
> >>>>>>>>>>>>> JR Garcia,
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I see that you're having trouble reading this dataset,
and I
> >>>>>>>> certainly
> >>>>>>>>>>>>> agree, that error message isn't very helpful. I
looked at
> the
> >>>>>> ncdump
> >>>>>>>>>>>>> output you sent and don't see anything obviously
wrong.
> >> However,
> >>>> I
> >>>>>>>>>>>> haven't
> >>>>>>>>>>>>> seen all those repeated "string" values in ncdump
output
> >> before.
> >>>>>>>>>> Perhaps
> >>>>>>>>>>>>> there's a netcdf version issue going on.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If possible, the easiest way for me to debug would be
for you
> >> to
> >>>>>>>> post a
> >>>>>>>>>>>>> sample file to our anonymous ftp site following these
> >>>> instructions:
> >>>>>>>>>>>>> http://www.dtcenter.org/met/
> >> users/support/met_help.php#ftp <http://www.dtcenter.org/met/
> >> users/support/met_help.php#ftp>
> >>>> <
> >>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp <
> >> http://www.dtcenter.org/met/users/support/met_help.php#ftp>>
> >>>>>>>>>>>>> Also please indicate the version of MET that you're
using.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If I can replicate the behavior here, it should be
pretty
> easy
> >> to
> >>>>>>>>>>>> determine
> >>>>>>>>>>>>> the problem.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>> John
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE)
via
> RT <
> >>>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu> <mailto:
> >> met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
> >>>>>>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted
upon.
> >>>>>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
> >> <mailto:roberto.garcia at inpe.br> <mailto:
> >>>>>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
> >>>>>>>>>>>>>> Queue: met_help
> >>>>>>>>>>>>>> Subject: FileType_None error in GridStat tool
> >>>>>>>>>>>>>> Owner: Nobody
> >>>>>>>>>>>>>> Requestors: roberto.garcia at inpe.br <mailto:
> >> roberto.garcia at inpe.br> <mailto:
> >>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
> >>>>>>>>>>>>>> Status: new
> >>>>>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/ <
> >> https://rt.rap.ucar.edu/rt/>
> >>>>>>>> Ticket/Display.html?id=80092
> >>>>>>>>>> <
> >>>>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>> >
> >>>>>>>>>>>>>> Dear John, that met-help ticket which manipulated 90
time
> >> slices
> >>>>>> has
> >>>>>>>>>>>>>> increased to 101 time slices. Attached are headers of
the
> >> ncdump
> >>>>>>>>>> command
> >>>>>>>>>>>>>> for both FSCT.nc and OBS.nc.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'm running the following command:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> And the entries for the forecast and observation
fields is
> >>>>>>>> configured
> >>>>>>>>>>>>>> inside GridStat.cfg are:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> // Forecast fields to be verified
> >> ==============================
> >>>>>>>>>>>>>> fcst = {
> >>>>>>>>>>>>>> field = [
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> name = "APCP";
> >>>>>>>>>>>>>> level = "(0,0,*,*)"; // 24-
hour
> >>>>>> accumulation
> >>>>>>>>>>>>>> cat_thresh = [ NA ]; // [
>1.0,
> >=5.0
> >>>> ] //
> >>>>>>>>>> ORIGINAL
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>> ];
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>> // Observation fields to be verified
> >>>>>> ==============================
> >>>>>>>>>>>>>> obs = {
> >>>>>>>>>>>>>> field = [
> >>>>>>>>>>>>>> {
> >>>>>>>>>>>>>> name = "APCP";
> >>>>>>>>>>>>>> level = "(0,*,*)"; // 24-hour
> >>>> accumulation
> >>>>>>>>>>>>>> cat_thresh = [ NA ]; // [
>1.0,
> >=5.0
> >>>> ] //
> >>>>>>>>>> ORIGINAL
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>> ];
> >>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'm getting the following error:
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
> >>>>>>>>>>>>>> GridStatConfig_default
> >>>>>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
> >>>>>>>>>>>>>> DEBUG 4: Me
> >>>>>> Until the NCO sys admins can get it installed in a more
general
> area,
> >>>> this
> >>>>>> MET installation is available for use. We will be rolling
out some
> >>>> patches
> >>>>>> shortly, at which point I will update this installation.
> >>>>>> t2dDataFileFactory::new_met_2d_data_file() -> created
> >>>>>>>> new
> >>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>>>>> ERROR :
> >>>>>>>>>>>>>> ERROR : Trouble reading forecast file
> >>>>>>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
> >>>>>>>>>>>> Eta40ens_00_036hs.nc"
> >>>>>>>>>>>>>> ERROR :
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> The message is not clear but I suppose MET was not
able to
> >> find
> >>>>>> out
> >>>>>>>>>> the
> >>>>>>>>>>>>>> FCST file type. Could you help me, please?
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Best regards.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> 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 <+55%2012%203208-7966>
> >>>>>>>>>>>>>>
-------------------------------------------------------
> >>>>>>>>>>>>>> SAVE NATURAL RESOURCES!
> >>>>>>>>>>>>>>
=======================================================
> >>
> >>
>
>
>
------------------------------------------------
Subject: can't set corner for variable "APCP" error
From: Garcia, J.R.M.
Time: Fri Apr 21 05:23:36 2017
Ok John, I got it.
I’ll build this way.
Thank you very much for your help and advices.
Best regards.
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 *****
=================================
> On 20 de abr de 2017, at 19:21, John Halley Gotway via RT
<met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>
> JR Garcia,
>
> The CF-convention does allow for 4-dimensional variables, but I
think
> you'll have trouble configuring MET to handle that.
>
> Presumably, with ensemble data you'd want to run the MET Ensemble-
Stat
> tool. That tool expects you to pass it N files, 1 for each ensemble
> member. And it extracts the same field from each input file. If
all
> members are contained within the same file, that logic won't work.
>
> Here's the most typical way I've seen people store this type of
data...
> Place all output times for each a single initialization time in the
same
> file. Write different NetCDF files for each ensemble member.
>
> If your data is on a lat/lon grid, using the CF-convention is very
easy.
> If it's on some other projection (lambert conformal, polar
sterographic, or
> mercator) defining that projection info gets very confusing.
>
> Thanks,
> John
>
> On Wed, Apr 19, 2017 at 10:57 AM, Roberto Garcia (INPE) via RT <
> met_help at ucar.edu <mailto:met_help at ucar.edu>> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>
>> Ok John, I got it. To build this structure I copied the idea from
ASCII
>> files I'm used to manipulate, NetCDF is new for me. I "know" I'd
get
>> there in this way but I'll redirect my efforts to follow the CF-
convention.
>>
>> I don't know if I'll find it somewhere but could you please answer
me if
>> the CF-convention allows four dimension APCP? I'm thinking about
storing
>> each ensemble member values together like [member, time, lat, lon]
for
>> ensemble data. Will I have problems on running MET in such kind of
>> files? Or it is only another dimension I have to take care when
>> specifying the level entry? What is the recommendation?
>>
>> Thank you very much.
>>
>> Best regards.
>>
>> 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 19/04/2017 13:06, John Halley Gotway via RT wrote:
>>> JR Garcia,
>>>
>>> OK, I understand the problem. You've put data for multiple
>> initialization
>>> times into the same file. That is problematic when using the
>>> CF-convention. I've never seen data structured that way, mixing
multiple
>>> init times into the same file.
>>>
>>> The most common way of organizing this type of data is to keep the
init
>>> time fixed for each file and put multiple lead times in there. Or
if
>>> you've post-processed WRF output files using the unified post-
processor
>>> (UPP), you'd have a separate GRIB output file for each lead time
of each
>>> model initialization.
>>>
>>> You may "know" the timing information of your data, but unless
there's
>>> something in the MET header columns to accurately define it, it'll
be
>>> confusing to do analysis on it.
>>>
>>> If you'd like to keep your data structured in this way, I'd
recommend
>>> considering the following two options:
>>>
>>> (1) Use met-6.0 and set the description entry in the config file
("desc")
>>> to describe the timing information of your data. Whatever you put
there
>>> will be passed through to the DESC output column.
>>>
>>> (2) When you set up scripts to run met, after running Grid-Stat or
>>> Point-Stat to generate output, run the ".stat" output files
through the
>>> STAT-Analysis tool. Do a "filter" job to just read the input
lines and
>>> write them to the output, but use the "-set_hdr" job command
option to
>>> explicitly override the timing information columns.
>>>
>>> If it were me, I'd suggest following existing conventions to get
the
>> timing
>>> info correct in the first place. But of course, it's up to you to
>> process
>>> your data as you see fit.
>>>
>>> Thanks,
>>> John
>>>
>>> On Wed, Apr 19, 2017 at 8:46 AM, Garcia, J.R.M. via RT <
>> met_help at ucar.edu <mailto:met_help at ucar.edu>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> >
>>>>
>>>> Excuse-me John, I saw your quick response and answered it but the
email
>>>> was not delivered. That was it.
>>>>
>>>> Thanks John.
>>>>
>>>> I understood but I’m afraid I can’t include this variable due to
the way
>>>> my NetCDF file is structured. It has one specific forecasting
lead time,
>>>> let’s say 36-hs forecasting, so it will have several model
>> initialization
>>>> times from the whole evaluation period and I joined all
correspondent
>> 36-hs
>>>> forecasting to it.
>>>>
>>>> I do the same for 24-hr, 48-hr, 60-hr, and so on….every lead time
is
>> kept
>>>> in a separated file. I’m a beginner in model evaluation and I
thought
>> that
>>>> as the evaluation must be per lead time I supposed that
separating them
>>>> into distinct files would be feasible.
>>>>
>>>> But I also think that this information does not affect my
evaluation
>> since
>>>> I know which forecasting time I’m dealing with, am I right?
>>>>
>>>> Thanks
>>>>
>>>> JR Garcia
>>>>
>>>> --
>>>> =================================
>>>> Jose Roberto Motta Garcia, PhD
>>>>
>>>> www.cptec.inpe.br <http://www.cptec.inpe.br/>
<http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>>
>>>> www.inpe.br <http://www.inpe.br/> <http://www.inpe.br/
<http://www.inpe.br/>>
>>>> Tel.: (55) 12 3186-7966
>>>> ----------------------------------------------------------
>>>> ***** Save natural resources *****
>>>> =================================
>>>>
>>>>> On 17 de abr de 2017, at 18:26, John Halley Gotway via RT <
>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>> JR Garcia,
>>>>>
>>>>> In the CF-convention, the "time" value specifies the valid time.
And
>>>> there
>>>>> is a convention for specifying the model initialization time.
MET
>>>> computes
>>>>> the "lead_time" as the valid time minus the initialization time.
>>>>>
>>>>> Add a variable named "forecast_reference_time" that looks like
this:
>>>>>
>>>>> double forecast_reference_time
>>>>> ;
>>>>>
>>>>> forecast_reference_time:long_name = "reference
time"
>>>>> ;
>>>>>
>>>>> forecast_reference_time:units = "seconds since
>> 1970-1-1" ;
>>>>>
>>>>> Thanks,
>>>>> John
>>>>>
>>>>> On Mon, Apr 17, 2017 at 3:11 PM, Roberto Garcia (INPE) via RT <
>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> <
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169>> >
>>>>>> Ok, John. Thanks again. It worked! I think we are getting
there!
>>>>>>
>>>>>> Now, I'm wondering what element can change the Lead Time in the
file
>>>>>> name. Can it be changed using grid_stat or it is a standard
name
>> format
>>>>>> that serves all MET tools and some of them can change it?
>>>>>>
>>>>>> grid_stat_Eta40ens_NCTRL_000000L_20161121_120000V.stat
>>>>>>
>>>>>> 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 17/04/2017 17:48, John Halley Gotway via RT wrote:
>>>>>>> JR Garcia,
>>>>>>>
>>>>>>> Yes, you can set the "cat_thresh" separately for each entry in
the
>>>>>>> "fcst.field" and "obs.field" arrays.
>>>>>>>
>>>>>>> Usually people run Grid-Stat to compare the same type of data
from
>> both
>>>>>> the
>>>>>>> forecast and observation datasets but there is no reason why
you have
>>>> to.
>>>>>>> For example, you have the flexibility to compare forecast
temperature
>>>> to
>>>>>>> observed precipitation. That probably won't yield very
meaningful
>>>>>> results,
>>>>>>> but if you did that, you'd probably want to specify different
>>>> thresholds
>>>>>>> for each field.
>>>>>>>
>>>>>>> But you're right, you can just specify "cat_thresh" once
outside the
>>>>>> "fcst"
>>>>>>> and "obs" settings and that one setting will be applied to
both. See
>>>>>>> example below.
>>>>>>>
>>>>>>> Next... MET supports 3 different flavors of NetCDF, and the
timing
>>>>>>> information is stored differently in them. Please just try
telling
>> MET
>>>>>> to
>>>>>>> interpret your data following the CF-conventions using:
file_type =
>>>>>>> NETCDF_NCCF; Since we want it apply to both the "fcst" and
"obs", I
>>>>>> just
>>>>>>> defined it once at the top-level context of the config file.
And
>> I've
>>>>>> also
>>>>>>> included that in the Grid-Stat config example listed below.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> John
>>>>>>>
>>>>>>> cat_thresh = [ gt1.0, gt2.0, gt3.0 ];
>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>
>>>>>>> // Forecast fields to be verified
==============================
>>>>>>> fcst = {
>>>>>>> field = [
>>>>>>> {
>>>>>>> name = "APCP";
>>>>>>> level = "(0,0,*,*)"; // 24-hour
accumulation
>>>>>>> }
>>>>>>> ];
>>>>>>> }
>>>>>>> // Observation fields to be verified
==============================
>>>>>>> obs = {
>>>>>>> field = [
>>>>>>> {
>>>>>>> name = "APCP";
>>>>>>> level = "(0,*,*)"; // 24-hour accumulation
>>>>>>> }
>>>>>>> ];
>>>>>>> }
>>>>>>>
>>>>>>> As for the issue with the timestamps,
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Apr 17, 2017 at 1:56 PM, Roberto Garcia (INPE) via RT
<
>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> <
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169>> >
>>>>>>>> Dear John, can you clarify why the output files were
generated to
>>>>>>>> 1970010 000000 valid time and 000000 lead time?
>>>>>>>>
>>>>>>>> As in grid_stat_Eta40ens_000000L_19700101_000000V.stat
>>>>>>>>
>>>>>>>> Below is the partial print of the forecasting NetCDF.
Shouldn't MET
>>>>>>>> calculate the correct time according to the time slice I
specified
>> in
>>>>>>>> the config file *level = "(0,0,*,*)"* and its unit *"hours
since"*?
>>>> What
>>>>>>>> I'm doing wrong?
>>>>>>>>
>>>>>>>> variables:
>>>>>>>> int time(time) ;
>>>>>>>> time:units = "hours since 1970-01-01 00:00:00 UTC" ;
>>>>>>>> time:calendar = "standard" ;
>>>>>>>> time:long_name = "Forecast target time" ;
>>>>>>>>
>>>>>>>> time = 411036, 411060, 411084, 411108, 411132, 411156,
411180,
>>>>>> 411204,
>>>>>>>> 411228, 411252, 411276, 411300, 411324, 411348, 411372,
>> 411396,
>>>>>>>> 411420,
>>>>>>>> 411444, 411468, 411492, 411516, 411540, 411564, 411588,
>> 411612,
>>>>>>>> 411636,
>>>>>>>>
>>>>>>>>
>>>>>>>> Another questions regarding the config file, please. At the
highest
>>>>>>>> level of grid_stat config file there is a group of entries:
>>>>>>>>
>>>>>>>> cat_thresh = [ NA ];
>>>>>>>> cnt_thresh = [ NA ];
>>>>>>>> cnt_logic = UNION;
>>>>>>>> wind_thresh = [ NA ];
>>>>>>>> wind_logic = UNION;
>>>>>>>>
>>>>>>>> 1) Do them control the behavior of the verification in a
general
>>>> aspect?
>>>>>>>> Concerning cat_thresh specifically, what happens if I set
some
>>>>>>>> thresholds at it and also inside the fcst and/o obs entries?
>>>>>>>>
>>>>>>>> 2) Why there is cat_thresh entry for both fcst and obs
entries?
>>>> Wouldn't
>>>>>>>> a general cat_thresh entry be enough? Does the use of
different
>>>>>>>> cat_thresh values for obs and fcst make sense?
>>>>>>>>
>>>>>>>> Thank you
>>>>>>>>
>>>>>>>>
>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>> -------------------------------------------------------
>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>> =======================================================
>>>>>>>>
>>>>>>>> On 17/04/2017 15:07, John Halley Gotway via RT wrote:
>>>>>>>>> JR Garcia,
>>>>>>>>>
>>>>>>>>> You have the Nlat and Nlon global attributes set wrong in
the
>>>>>>>>> MERGE_20161201_20170228.nc file:
>>>>>>>>> :Nlat = "245 grid_points" ;
>>>>>>>>> :Nlon = "313 grid_points" ;
>>>>>>>>>
>>>>>>>>> Those numbers don't match the lat/lon dimensions:
>>>>>>>>> dimensions:
>>>>>>>>> time = 90 ;
>>>>>>>>> lat = 313 ;
>>>>>>>>> lon = 245 ;
>>>>>>>>>
>>>>>>>>> I ran the following command to switch them:
>>>>>>>>>
>>>>>>>>> ncatted -a Nlat,global,o,c,"313 grid_points" \
>>>>>>>>> -a Nlon,global,o,c,"245 grid_points" \
>>>>>>>>> MERGE_20161201_20170228.nc \
>>>>>>>>> -o MERGE_20161201_20170228_PATCH.nc
>>>>>>>>>
>>>>>>>>> After switching that, MET version 5.2 processes them fine.
>>>>>>>>>
>>>>>>>>> Also, testing this out using version 6.0 revealed a little
bug we
>>>>>>>>> introduced when switching from NetCDF3 to NetCDF4. I'll
post a
>>>> bugfix
>>>>>>>> for
>>>>>>>>> this as soon as one is available.
>>>>>>>>>
>>>>>>>>> In order to run this data through version 6.0, you'll need
that
>>>> bugfix.
>>>>>>>>> Thanks,
>>>>>>>>> John
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Apr 17, 2017 at 11:18 AM, Roberto Garcia (INPE) via
RT <
>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169> <
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80169>> >
>>>>>>>>>> Data are there!
>>>>>>>>>>
>>>>>>>>>> Thanks John.
>>>>>>>>>>
>>>>>>>>>> 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 17/04/2017 13:26, John Halley Gotway via RT wrote:
>>>>>>>>>>> JR Garcia,
>>>>>>>>>>>
>>>>>>>>>>> Can you please post a sample one of your converted files
to our
>> ftp
>>>>>>>> site
>>>>>>>>>>> following these instructions:
>>>>>>>>>>>
>>>>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp> <
>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp>>
>>>>>>>>>>> I'll take a look at let you know what I find.
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> John
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Apr 17, 2017 at 6:49 AM, Roberto Garcia (INPE) via
RT <
>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Mon Apr 17 06:49:10 2017: Request 80169 was acted upon.
>>>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br> <mailto:
>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
>>>>>>>>>>>> Queue: met_help
>>>>>>>>>>>> Subject: can't set corner for variable "APCP"
error
>>>>>>>>>>>> Owner: Nobody
>>>>>>>>>>>> Requestors: roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br> <mailto:
>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
>>>>>>>>>>>> Status: new
>>>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/Tic
<https://rt.rap.ucar.edu/rt/Tic> <
>>>> https://rt.rap.ucar.edu/rt/Tic <https://rt.rap.ucar.edu/rt/Tic>>
>>>>>>>> ket/Display.html?id=80169
>>>>>>>>>>>> Hi John, I converted all obs and fct NetCDF files to the
NetCDF
>> 3
>>>>>>>>>>>> Classic version and issued the same command, could you
please
>> help
>>>>>> me
>>>>>>>>>>>> interpret this error? What does "corner" refer to?
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>> grid_stat Eta40ens_00_036hs.nc
MERGE_20161201_20170228_Eta40G
>>>>>>>> rid.nc
>>>>>>>>>>>> GridStat.cfg -v 4
>>>>>>>>>>>>
>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
>>>>>>>>>>>> GridStatConfig_default
>>>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
>> created
>>>>>> new
>>>>>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>>>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>>>>>>>> DEBUG 4: lon_ll = 83
>>>>>>>>>>>> DEBUG 4: delta_lat = 0.4
>>>>>>>>>>>> DEBUG 4: delta_lon = 0.4
>>>>>>>>>>>> DEBUG 4: Nlat = 157
>>>>>>>>>>>> DEBUG 4: Nlon = 144
>>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
>> created
>>>>>> new
>>>>>>>>>>>> Met2dDataFile object of type "FileType_NcMet".
>>>>>>>>>>>> DEBUG 4: Latitude/Longitude Grid Data:
>>>>>>>>>>>> DEBUG 4: lat_ll = -50.2
>>>>>>>>>>>> DEBUG 4: lon_ll = 82.8
>>>>>>>>>>>> DEBUG 4: delta_lat = 0.2
>>>>>>>>>>>> DEBUG 4: delta_lon = 0.2
>>>>>>>>>>>> DEBUG 4: Nlat = 144
>>>>>>>>>>>> DEBUG 4: Nlon = 157
>>>>>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
>>>>>> object
>>>>>>>> of
>>>>>>>>>>>> type "FileType_NcMet".
>>>>>>>>>>>> DEBUG 4: VarInfoFactory::new_var_info() -> created new
VarInfo
>>>>>> object
>>>>>>>> of
>>>>>>>>>>>> type "FileType_NcMet".
>>>>>>>>>>>> WARNING:
>>>>>>>>>>>> WARNING: parse_conf_interp() -> For neareast neighbor
>>>> interpolation
>>>>>>>>>>>> method, resetting method from "UW_MEAN" to "NEAREST"
since the
>>>>>>>>>>>> interpolation width is 1.
>>>>>>>>>>>> WARNING:
>>>>>>>>>>>> DEBUG 3: Use the forecast grid.
>>>>>>>>>>>> DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 144 Ny:
157
>>>>>> lat_ll:
>>>>>>>>>>>> -50.200 lon_ll: 83.000 delta_lat: 0.400 delta_lon: 0.400
>>>>>>>>>>>> GSL_RNG_TYPE=mt19937
>>>>>>>>>>>> GSL_RNG_SEED=1639511128
>>>>>>>>>>>> DEBUG 1: Forecast File:
>>>>>>>>>>>>
/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/Eta40ens_
>>>>>>>> 00_036hs.nc
>>>>>>>>>>>> DEBUG 1: Observation File:
>>>>>>>>>>>> /stornext/grupos/pesq_dop/roberto.garcia/MERGE/MERGE_
>>>>>>>>>>>> 20161201_20170228_Eta40Grid.nc
>>>>>>>>>>>> DEBUG 3: Reading forecast data for APCP(0,0,*,*).
>>>>>>>>>>>> DEBUG 3: Reading observation data for APCP(0,*,*).
>>>>>>>>>>>> ERROR :
>>>>>>>>>>>> ERROR : MetNcFile::data(NcVar *, const LongArray &)
const ->
>>>> can't
>>>>>>>> set
>>>>>>>>>>>> corner for variable "APCP"
>>>>>>>>>>>> ERROR :
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>>>>>> -------------------------------------------------------
>>>>>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>>>>>> =======================================================
>>>>>>>>>>>>
>>>>>>>>>>>> On 10/04/2017 16:51, John Halley Gotway via RT wrote:
>>>>>>>>>>>>> JR Garcia,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks for sending the sample data file. This is
definitely a
>>>>>>>> NetCDF4
>>>>>>>>>>>> file
>>>>>>>>>>>>> using the enhanced data model. MET version 5.2 is not
able to
>>>> read
>>>>>>>>>>>> NetCDF4
>>>>>>>>>>>>> files. The recent release of MET (version 6.0) has been
>> enhanced
>>>>>> to
>>>>>>>> do
>>>>>>>>>>>> so.
>>>>>>>>>>>>> I tried a few things:
>>>>>>>> Until the NCO sys admins can get it installed in a more
general
>> area,
>>>>>> this
>>>>>>>> MET installation is available for use. We will be rolling
out some
>>>>>> patches
>>>>>>>> shortly, at which point I will update this installation.
>>>>>>>>>>>>> (1) Convert your forecast file from NetCDF4 to 3 using
the
>> nccopy
>>>>>>>>>>>> command.
>>>>>>>>>>>>> That results in the following error:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> nccopy -3 FCT.nc FCT_nc3.nc
>>>>>>>>>>>>> NetCDF: Not a valid data type or _FillValue type
mismatch
>>>>>>>>>>>>> Location: file nccopy.c; line 788
>>>>>>>>>>>>>
>>>>>>>>>>>>> (2) View your file using ncview. It brings up the
display but
>>>> all
>>>>>>>> the
>>>>>>>>>>>>> values are 0:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> ncview FCT.nc
>>>>>>>>>>>>> (3) Run MET version 6.0 plot_data_plane to plot that
file
>> telling
>>>>>> it
>>>>>>>> to
>>>>>>>>>>>>> interpret it at a MET NetCDF file. That results in the
>> following
>>>>>>>>>> error:
>>>>>>>>>>>>>> met-6.0/bin/plot_data_plane FCT.nc FCT_APCP.ps
'name="APCP";
>>>>>>>>>>>>> level="(0,0,*,*)"; file_type=NETCDF_MET;'
>>>>>>>>>>>>> terminate called after throwing an instance of
>>>>>>>>>>>> 'netCDF::exceptions::NcChar'
>>>>>>>>>>>>> what(): NcChar: Attempt to convert between text &
>> numbers
>>>>>>>>>>>>> file: ncAtt.cpp line:104
>>>>>>>>>>>>> Abort
>>>>>>>>>>>>>
>>>>>>>>>>>>> (4) Lastly, I ran (3) above through the debugger and
found that
>>>> it
>>>>>> is
>>>>>>>>>>>>> indeed all those "string" types that are causing the
problem.
>> I
>>>>>> used
>>>>>>>>>> the
>>>>>>>>>>>>> ncatted utility to change those data types from "string"
to
>>>>>>>>>> "character".
>>>>>>>>>>>>> After doing that and telling MET to interpret it as a
>>>> CF-compliant
>>>>>>>>>> NetCDF
>>>>>>>>>>>>> file, I was at least able to plot it. The plot looks
bad but
>> at
>>>>>>>> least
>>>>>>>>>> it
>>>>>>>>>>>>> works. Here are the very long commands I ran:
>>>>>>>>>>>>>
>>>>>>>>>>>>> # Run ncatted to switch types from strings to characters
>>>>>>>>>>>>> ncatted FCT.nc \
>>>>>>>>>>>>> -a FileOrigins,global,o,c,"File example.nc generated
>>>>>> 20170409_140422
>>>>>>>>>>>> UTC on
>>>>>>>>>>>>> host eslogin03 by the MET pcp_combine tool" \
>>>>>>>>>>>>> -a MET_version,global,o,c,"V5.2" \
>>>>>>>>>>>>> -a MET_tool,global,o,c,"pcp_combine" \
>>>>>>>>>>>>> -a RunCommand,global,o,c,"Addition: 1 files." \
>>>>>>>>>>>>> -a Projection,global,o,c,"LatLon" \
>>>>>>>>>>>>> -a lat_ll,global,o,c,"-50.200000 degrees_north" \
>>>>>>>>>>>>> -a lon_ll,global,o,c,"-83.000000 degrees_east" \
>>>>>>>>>>>>> -a delta_lat,global,o,c,"0.400000 degrees" \
>>>>>>>>>>>>> -a delta_lon,global,o,c,"0.400000 degrees" \
>>>>>>>>>>>>> -a Nlat,global,o,c,"157 grid_points" \
>>>>>>>>>>>>> -a Nlon,global,o,c,"144 grid_points" \
>>>>>>>>>>>>> -a Generator,global,o,c,"MET::pcp_combine + NCL" \
>>>>>>>>>>>>> -a institution,global,o,c,"DMD / CPTEC / INPE" \
>>>>>>>>>>>>> -a author,global,o,c,"Jose Roberto Motta Garcia, PhD" \
>>>>>>>>>>>>> -a source,global,o,c,"Eta40ens regional weather
forecasting
>>>> model"
>>>>>> \
>>>>>>>>>>>>> -a title,global,o,c,"24-hr accummulated precipitation" \
>>>>>>>>>>>>> -a units,time,o,c,"hours since 1970-01-01 00:00:00 UTC"
\
>>>>>>>>>>>>> -a increment,time,o,c,"24 hours in seconds" \
>>>>>>>>>>>>> -a calendar,time,o,c,"standard" \
>>>>>>>>>>>>> -a long_name,time,o,c,"Forecast target time" \
>>>>>>>>>>>>> -a units,member,o,c,"Values from 0 to #_of_members-1" \
>>>>>>>>>>>>> -a long_name,member,o,c,"Members of the ensemble model
>> Eta40ens"
>>>> \
>>>>>>>>>>>>> -a long_name,lat,o,c,"latitude" \
>>>>>>>>>>>>> -a units,lat,o,c,"degrees_north" \
>>>>>>>>>>>>> -a standard_name,lat,o,c,"latitude" \
>>>>>>>>>>>>> -a long_name,lon,o,c,"longitude" \
>>>>>>>>>>>>> -a units,lon,o,c,"degrees_east" \
>>>>>>>>>>>>> -a standard_name,lon,o,c,"longitude" \
>>>>>>>>>>>>> -a Projection,APCP,o,c,"LatLon" \
>>>>>>>>>>>>> -a units,APCP,o,c,"kg/m^2" \
>>>>>>>>>>>>> -a long_name,APCP,o,c,"Eta40ens 24-hour accumulated
>>>> precipitation"
>>>>>> \
>>>>>>>>>>>>> -o FCT_edit.nc
>>>>>>>>>>>>>
>>>>>>>>>>>>> # Run plot_data_plane version 6.0 to plot the file
>>>>>>>>>>>>> met-6.0/bin/plot_data_plane FCT_edit.nc FCT_APCP.ps
>> 'name="APCP";
>>>>>>>>>>>>> level="(0,1,*,*)"; file_type=NETCDF_NCCF;'
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sun, Apr 9, 2017 at 8:51 AM, Garcia, J.R.M. via RT <
>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>
>> <
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>> >
>>>>>>>>>>>>>> Hi John,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I’ve created garcia_data and put the files in your
incoming
>> ftp
>>>>>>>> site.
>>>>>>>>>>>>>> Thank you for your help.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> About those repeated strings that I suppose you are
referring
>> to
>>>>>>>>>> *._deg
>>>>>>>>>>>>>> strings, I’had to create them because one of MET tools
>>>> complained
>>>>>>>>>> about
>>>>>>>>>>>> the
>>>>>>>>>>>>>> lack of them, and I think it was grid_stat itself. To
generate
>>>>>> them
>>>>>>>> I
>>>>>>>>>>>> took
>>>>>>>>>>>>>> the pcp_combine output as a template but when running
the
>>>>>> grid_stat
>>>>>>>>>>>> command
>>>>>>>>>>>>>> it showed this message to me.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thank you again.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> JR Garcia
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> =================================
>>>>>>>>>>>>>> Jose Roberto Motta Garcia, PhD
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> www.cptec.inpe.br <http://www.cptec.inpe.br/>
<http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>> <
>>>> http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>
<http://www.cptec.inpe.br/ <http://www.cptec.inpe.br/>>>
>>>>>>>>>>>>>> www.inpe.br <http://www.inpe.br/> <http://www.inpe.br/
<http://www.inpe.br/>> <http://www.inpe.br/ <http://www.inpe.br/> <
>>>> http://www.inpe.br/ <http://www.inpe.br/>>>
>>>>>>>>>>>>>> Tel.: (55) 12 3186-7966
>>>>>>>>>>>>>>
----------------------------------------------------------
>>>>>>>>>>>>>> ***** Save natural resources *****
>>>>>>>>>>>>>> =================================
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On 7 de abr de 2017, at 19:15, John Halley Gotway via
RT <
>>>>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>> <mailto:
>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>> wrote:
>>>>>>>>>>>>>>> JR Garcia,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I see that you're having trouble reading this dataset,
and I
>>>>>>>>>> certainly
>>>>>>>>>>>>>>> agree, that error message isn't very helpful. I
looked at
>> the
>>>>>>>> ncdump
>>>>>>>>>>>>>>> output you sent and don't see anything obviously
wrong.
>>>> However,
>>>>>> I
>>>>>>>>>>>>>> haven't
>>>>>>>>>>>>>>> seen all those repeated "string" values in ncdump
output
>>>> before.
>>>>>>>>>>>> Perhaps
>>>>>>>>>>>>>>> there's a netcdf version issue going on.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If possible, the easiest way for me to debug would be
for you
>>>> to
>>>>>>>>>> post a
>>>>>>>>>>>>>>> sample file to our anonymous ftp site following these
>>>>>> instructions:
>>>>>>>>>>>>>>> http://www.dtcenter.org/met/
<http://www.dtcenter.org/met/>
>>>> users/support/met_help.php#ftp <http://www.dtcenter.org/met/
<http://www.dtcenter.org/met/>
>>>> users/support/met_help.php#ftp>
>>>>>> <
>>>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp> <
>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
<http://www.dtcenter.org/met/users/support/met_help.php#ftp>>>
>>>>>>>>>>>>>>> Also please indicate the version of MET that you're
using.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If I can replicate the behavior here, it should be
pretty
>> easy
>>>> to
>>>>>>>>>>>>>> determine
>>>>>>>>>>>>>>> the problem.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> John
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Fri, Apr 7, 2017 at 12:04 PM, Roberto Garcia (INPE)
via
>> RT <
>>>>>>>>>>>>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>> <mailto:
>>>> met_help at ucar.edu <mailto:met_help at ucar.edu>
<mailto:met_help at ucar.edu <mailto:met_help at ucar.edu>>>> wrote:
>>>>>>>>>>>>>>>> Fri Apr 07 12:04:46 2017: Request 80092 was acted
upon.
>>>>>>>>>>>>>>>> Transaction: Ticket created by roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br>
>>>> <mailto:roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>
<mailto:
>>>>>>>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>
<mailto:roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>>
>>>>>>>>>>>>>>>> Queue: met_help
>>>>>>>>>>>>>>>> Subject: FileType_None error in GridStat tool
>>>>>>>>>>>>>>>> Owner: Nobody
>>>>>>>>>>>>>>>> Requestors: roberto.garcia at inpe.br
<mailto:roberto.garcia at inpe.br> <mailto:
>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>> <mailto:
>>>>>>>>>> roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>
<mailto:roberto.garcia at inpe.br <mailto:roberto.garcia at inpe.br>>>
>>>>>>>>>>>>>>>> Status: new
>>>>>>>>>>>>>>>> Ticket <URL: https://rt.rap.ucar.edu/rt/
<https://rt.rap.ucar.edu/rt/> <
>>>> https://rt.rap.ucar.edu/rt/ <https://rt.rap.ucar.edu/rt/>>
>>>>>>>>>> Ticket/Display.html?id=80092
>>>>>>>>>>>> <
>>>>>>>>>>>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092> <
>>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092
<https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80092>>> >
>>>>>>>>>>>>>>>> Dear John, that met-help ticket which manipulated 90
time
>>>> slices
>>>>>>>> has
>>>>>>>>>>>>>>>> increased to 101 time slices. Attached are headers of
the
>>>> ncdump
>>>>>>>>>>>> command
>>>>>>>>>>>>>>>> for both FSCT.nc and OBS.nc.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I'm running the following command:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> grid_stat FCT.nc OBS.nc GridStat.cfg -v 4
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> And the entries for the forecast and observation
fields is
>>>>>>>>>> configured
>>>>>>>>>>>>>>>> inside GridStat.cfg are:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> // Forecast fields to be verified
>>>> ==============================
>>>>>>>>>>>>>>>> fcst = {
>>>>>>>>>>>>>>>> field = [
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> name = "APCP";
>>>>>>>>>>>>>>>> level = "(0,0,*,*)"; // 24-
hour
>>>>>>>> accumulation
>>>>>>>>>>>>>>>> cat_thresh = [ NA ]; // [
>1.0,
>>> =5.0
>>>>>> ] //
>>>>>>>>>>>> ORIGINAL
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>> ];
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>> // Observation fields to be verified
>>>>>>>> ==============================
>>>>>>>>>>>>>>>> obs = {
>>>>>>>>>>>>>>>> field = [
>>>>>>>>>>>>>>>> {
>>>>>>>>>>>>>>>> name = "APCP";
>>>>>>>>>>>>>>>> level = "(0,*,*)"; // 24-hour
>>>>>> accumulation
>>>>>>>>>>>>>>>> cat_thresh = [ NA ]; // [
>1.0,
>>> =5.0
>>>>>> ] //
>>>>>>>>>>>> ORIGINAL
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>> ];
>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I'm getting the following error:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>>>>> /stornext/home/roberto.garcia/sfw/met-
5.2/share/met/config/
>>>>>>>>>>>>>>>> GridStatConfig_default
>>>>>>>>>>>>>>>> DEBUG 1: User Config File: GridStat.cfg
>>>>>>>>>>>>>>>> DEBUG 4: Me
>>>>>>>> Until the NCO sys admins can get it installed in a more
general
>> area,
>>>>>> this
>>>>>>>> MET installation is available for use. We will be rolling
out some
>>>>>> patches
>>>>>>>> shortly, at which point I will update this installation.
>>>>>>>> t2dDataFileFactory::new_met_2d_data_file() -> created
>>>>>>>>>> new
>>>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>>>>> ERROR :
>>>>>>>>>>>>>>>> ERROR : Trouble reading forecast file
>>>>>>>>>>>>>>>> "/stornext/grupos/pesq_dop/roberto.garcia/Eta40ens/
>>>>>>>>>>>>>> Eta40ens_00_036hs.nc"
>>>>>>>>>>>>>>>> ERROR :
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> The message is not clear but I suppose MET was not
able to
>>>> find
>>>>>>>> out
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>> FCST file type. Could you help me, please?
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Best regards.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> 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 <+55%2012%203208-7966>
>>>>>>>>>>>>>>>>
-------------------------------------------------------
>>>>>>>>>>>>>>>> SAVE NATURAL RESOURCES!
>>>>>>>>>>>>>>>>
=======================================================
>>>>
>>>>
>>
>>
>>
>
------------------------------------------------
More information about the Met_help
mailing list