[Met_help] [rt.rap.ucar.edu #91179] History for MODE issue reading input file
John Halley Gotway via RT
met_help at ucar.edu
Tue Jul 23 09:51:02 MDT 2019
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Good morning MET help team,
I am a new user of MET and specifically of MODE. I would like to use MODE
to identify precipitation systems from output of an idealized simulation.
I have interpolated my model output to a lat-lon grid; however, when trying
to run MODE I get the following error:
ERROR : Trouble reading observation file
"/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
latlon_copy.nc"
Here is the ncdump of my file:
netcdf latlon_copy {
dimensions:
lat = 20 ;
lon = 360 ;
variables:
float lat(lat) ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
lat:standard_name = "latitude" ;
lat:Projection = "latitude longitude" ;
float lon(lon) ;
lon:standard_name = "longitude" ;
lon:long_name = "longitude" ;
lon:units = "degrees_east" ;
lon:Projection = "latitude longitude" ;
float olrtoa(lat, lon) ;
olrtoa:Projection = "latitude longitude" ;
olrtoa:cell_methods = "Time: mean" ;
float rainc(lat, lon) ;
rainc:Projection = "latitude longitude" ;
rainc:cell_methods = "Time: mean" ;
float rainnc(lat, lon) ;
rainnc:Projection = "latitude longitude" ;
rainnc:cell_methods = "Time: mean" ;
float mslp(lat, lon) ;
mslp:Projection = "latitude longitude" ;
mslp:cell_methods = "Time: mean" ;
I understand that the file is supposed to be CF-compliant, but I am unsure
how much additional information is needed in the NetCDF file for lat-lon
projection.
For reference, here are the contents of my config file:
////////////////////////////////////////////////////////////////////////////////
//
// MODE configuration file.
//
// For additional information, see the MET_BASE/config/README file.
//
////////////////////////////////////////////////////////////////////////////////
//
// Output model name to be written
//
model = "MPAS";
//
// Output description to be written
//
desc = "MPAS";
//
// Output observation type to be written
//
obtype = "MPAS";
////////////////////////////////////////////////////////////////////////////////
//
// Verification grid
// May be set separately in each "field" entry
//
regrid = {
to_grid = NONE;
method = NEAREST;
width = 1;
vld_thresh = 0.5;
shape = SQUARE;
}
////////////////////////////////////////////////////////////////////////////////
//
// Approximate grid resolution (km)
//
grid_res = 120;
////////////////////////////////////////////////////////////////////////////////
//
// Run all permutations of radius and threshold
//
quilt = FALSE;
//
// Forecast and observation fields to be verified
//
fcst = {
field = {
name = "mslp";
level = "(*,*)";
}
censor_thresh = [];
censor_val = [];
conv_radius = 5; // in grid squares
conv_thresh = <=1000.0;
vld_thresh = 0.5;
filter_attr_name = [];
filter_attr_thresh = [];
merge_thresh = >=1.25;
merge_flag = NONE;
}
obs = fcst;
...
Everything else is the same as in the default config file. Could you please
provide guidance as to what might be wrong with my input data or my config
file?
Many thanks!
Rosimar
--
_______________________________________________________________________
Rosimar Rios-Berrios, PhD
Postdoctoral Fellow | Advanced Study Program
Scientist I (beginning Aug. 12) | Mesoscale and Microscale Meteorology
National Center for Atmospheric Research
https://rosimarwx.github.io/
_______________________________________________________________________
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MODE issue reading input file
From: John Halley Gotway
Time: Mon Jul 22 11:23:27 2019
Rosimar,
I see that you'd like to run the MODE tool on some NetCDF data, but
you're
having trouble getting it to read your data.
When getting started with a new dataset in MET, I usually recommend
that
people start by running the plot_data_plane tool. That's a MET tool
which
reads a single field of data and creates a plot of it. There's no
config
file... you just specify what data you want on the command line. This
is
very useful in making sure that the MET tools can read you data and
place
it on the right place on earth. One issue I see is that the NetCDF
header
is missing the "Conventions" attribute which indicates CF-compliance.
So
MET doesn't know to interpret it as such. You can fix this by adding
that
global attribute:
Conventions = "CF-1.7";
Alternatively, you can use the "file_type" option to explicitly
specify the
input file type. I logged on to cheyenne and ran these commands:
*> module use /glade/p/ral/jntp/MET/MET_releases/modulefiles*
*> module load met/8.1*
*> plot_data_plane
/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/latlon_copy.nc
<http://latlon_copy.nc> plot.ps <http://plot.ps> 'name="olrtoa";
level="(*,*)"; file_type=NETCDF_NCCF;'*
DEBUG 1: Opening data file:
/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/latlon_copy.nc
WARNING:
WARNING: NcCfFile::open() -> could not determine the valid time, using
0.
WARNING:
DEBUG 1: Creating postscript file: plot.ps
And that produced the attached plot. I see that you have a long,
skinny
latitude band. Is that what you expected?
Note that I used "file_type = NETCDF_NCCF;" to tell MET to interpret
it as
such. Also, note that the warning that MET could get the valid time.
Fix
this by adding a "time" dimension with a coordinate variable to
specify the
timing info. Listed below is an example CF-compliant NetCDF file
which
includes timing info. Note that it also includes the
"forecast_reference_time" which is the CF-compliant way of specifying
a
model initialization time.
Thanks,
John
netcdf gtg_obs_forecast.20130730.i00.f00 {
dimensions:
lat = 361 ;
lon = 720 ;
z = 26 ;
name_len = 32 ;
time = 1 ;
variables:
int grid_mapping ;
grid_mapping:grid_mapping_name = "latitude_longitude"
;
grid_mapping:semi_major_axis = 6371000. ;
grid_mapping:inverse_flattening = 0 ;
double time(time) ;
time:long_name = "forecast time" ;
time:units = "seconds since 1970-1-1" ;
time:axis = "T" ;
double forecast_reference_time ;
forecast_reference_time:long_name = "reference time" ;
forecast_reference_time:units = "seconds since 1970-1-
1" ;
int forecast_period ;
forecast_period:units = "seconds" ;
double lat(lat) ;
lat:units = "degrees_north" ;
lat:long_name = "latitude coordinate" ;
lat:standard_name = "latitude" ;
lat:_CoordinateAxisType = "Lat" ;
double lon(lon) ;
lon:units = "degrees_east" ;
lon:long_name = "longitude coordinate" ;
lon:standard_name = "longitude" ;
lon:_CoordinateAxisType = "Lon" ;
double z(z) ;
z:standard_name = "altitude" ;
z:long_name = "flight_level" ;
z:units = "feet" ;
z:positive = "up" ;
z:axis = "Z" ;
int field_id ;
field_id:long_name = "field indentification number" ;
char field_name(name_len) ;
field_name:long_name = "field name" ;
float edr(time, z, lat, lon) ;
edr:units = "m^(2/3) s^-1" ;
edr:long_name = "Median eddy dissipation rate" ;
edr:coordinates = "lat lon" ;
edr:_FillValue = -9999.f ;
edr:grid_mapping = "grid_mapping" ;
// global attributes:
:Conventions = "CF-1.4" ;
:Originating_center = "NCAR" ;
:Product_Status = "Experimental Products" ;
:Product_Type = "Forecast/Uninitialized Analysis" ;
:DataType = "GRID" ;
:DatasetLocation = "" ;
data:
time = 1375142400 ;
}
On Mon, Jul 22, 2019 at 9:00 AM Rosimar Rios-Berrios via RT <
met_help at ucar.edu> wrote:
>
> Mon Jul 22 08:59:41 2019: Request 91179 was acted upon.
> Transaction: Ticket created by rberrios at ucar.edu
> Queue: met_help
> Subject: MODE issue reading input file
> Owner: Nobody
> Requestors: rberrios at ucar.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91179 >
>
>
> Good morning MET help team,
>
> I am a new user of MET and specifically of MODE. I would like to use
MODE
> to identify precipitation systems from output of an idealized
simulation.
>
> I have interpolated my model output to a lat-lon grid; however, when
trying
> to run MODE I get the following error:
>
> ERROR : Trouble reading observation file
> "/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> latlon_copy.nc"
>
> Here is the ncdump of my file:
>
> netcdf latlon_copy {
>
> dimensions:
>
> lat = 20 ;
>
> lon = 360 ;
>
> variables:
>
> float lat(lat) ;
>
> lat:long_name = "latitude" ;
>
> lat:units = "degrees_north" ;
>
> lat:standard_name = "latitude" ;
>
> lat:Projection = "latitude longitude" ;
>
> float lon(lon) ;
>
> lon:standard_name = "longitude" ;
>
> lon:long_name = "longitude" ;
>
> lon:units = "degrees_east" ;
>
> lon:Projection = "latitude longitude" ;
>
> float olrtoa(lat, lon) ;
>
> olrtoa:Projection = "latitude longitude" ;
>
> olrtoa:cell_methods = "Time: mean" ;
>
> float rainc(lat, lon) ;
>
> rainc:Projection = "latitude longitude" ;
>
> rainc:cell_methods = "Time: mean" ;
>
> float rainnc(lat, lon) ;
>
> rainnc:Projection = "latitude longitude" ;
>
> rainnc:cell_methods = "Time: mean" ;
>
> float mslp(lat, lon) ;
>
> mslp:Projection = "latitude longitude" ;
>
> mslp:cell_methods = "Time: mean" ;
>
> I understand that the file is supposed to be CF-compliant, but I am
unsure
> how much additional information is needed in the NetCDF file for
lat-lon
> projection.
>
> For reference, here are the contents of my config file:
>
>
>
////////////////////////////////////////////////////////////////////////////////
> //
> // MODE configuration file.
> //
> // For additional information, see the MET_BASE/config/README file.
> //
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Output model name to be written
> //
> model = "MPAS";
>
> //
> // Output description to be written
> //
> desc = "MPAS";
>
> //
> // Output observation type to be written
> //
> obtype = "MPAS";
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Verification grid
> // May be set separately in each "field" entry
> //
> regrid = {
> to_grid = NONE;
> method = NEAREST;
> width = 1;
> vld_thresh = 0.5;
> shape = SQUARE;
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Approximate grid resolution (km)
> //
> grid_res = 120;
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Run all permutations of radius and threshold
> //
> quilt = FALSE;
>
> //
> // Forecast and observation fields to be verified
> //
> fcst = {
> field = {
> name = "mslp";
> level = "(*,*)";
> }
>
> censor_thresh = [];
> censor_val = [];
> conv_radius = 5; // in grid squares
> conv_thresh = <=1000.0;
> vld_thresh = 0.5;
> filter_attr_name = [];
> filter_attr_thresh = [];
> merge_thresh = >=1.25;
> merge_flag = NONE;
> }
> obs = fcst;
>
> ...
>
> Everything else is the same as in the default config file. Could you
please
> provide guidance as to what might be wrong with my input data or my
config
> file?
>
> Many thanks!
> Rosimar
>
> --
>
_______________________________________________________________________
> Rosimar Rios-Berrios, PhD
> Postdoctoral Fellow | Advanced Study Program
> Scientist I (beginning Aug. 12) | Mesoscale and Microscale
Meteorology
> National Center for Atmospheric Research
> https://rosimarwx.github.io/
>
_______________________________________________________________________
>
>
------------------------------------------------
Subject: MODE issue reading input file
From: Rosimar Rios-Berrios
Time: Mon Jul 22 14:44:44 2019
Hi John,
Thank you very much for your help and for even running a test with my
dataset.
The domain that you obtained is correct - a narrow band around the
globe.
After adding the global attribute and time variables, I was able to
plot my
output with plot_data_plane. I was also able to run several tests with
MODE. I still get a warning:
WARNING: MetNcCFDataFile::data_plane(VarInfo &, DataPlane &) ->
returns the
first available time for "olrtoa" variable).
I assume this is related to how I defined my time and
forecast_reference_time variables. I will dig around more to try to
fix
this.
Thank you very much!
Rosimar
On Mon, Jul 22, 2019 at 11:23 AM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Rosimar,
>
> I see that you'd like to run the MODE tool on some NetCDF data, but
you're
> having trouble getting it to read your data.
>
> When getting started with a new dataset in MET, I usually recommend
that
> people start by running the plot_data_plane tool. That's a MET tool
which
> reads a single field of data and creates a plot of it. There's no
config
> file... you just specify what data you want on the command line.
This is
> very useful in making sure that the MET tools can read you data and
place
> it on the right place on earth. One issue I see is that the NetCDF
header
> is missing the "Conventions" attribute which indicates CF-
compliance. So
> MET doesn't know to interpret it as such. You can fix this by
adding that
> global attribute:
> Conventions = "CF-1.7";
>
> Alternatively, you can use the "file_type" option to explicitly
specify the
> input file type. I logged on to cheyenne and ran these commands:
>
>
> *> module use /glade/p/ral/jntp/MET/MET_releases/modulefiles*
> *> module load met/8.1*
> *> plot_data_plane
> /glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> latlon_copy.nc
> <http://latlon_copy.nc> plot.ps <http://plot.ps> 'name="olrtoa";
> level="(*,*)"; file_type=NETCDF_NCCF;'*
> DEBUG 1: Opening data file:
> /glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> latlon_copy.nc
> WARNING:
> WARNING: NcCfFile::open() -> could not determine the valid time,
using 0.
> WARNING:
> DEBUG 1: Creating postscript file: plot.ps
>
> And that produced the attached plot. I see that you have a long,
skinny
> latitude band. Is that what you expected?
>
> Note that I used "file_type = NETCDF_NCCF;" to tell MET to interpret
it as
> such. Also, note that the warning that MET could get the valid
time. Fix
> this by adding a "time" dimension with a coordinate variable to
specify the
> timing info. Listed below is an example CF-compliant NetCDF file
which
> includes timing info. Note that it also includes the
> "forecast_reference_time" which is the CF-compliant way of
specifying a
> model initialization time.
>
> Thanks,
> John
>
> netcdf gtg_obs_forecast.20130730.i00.f00 {
> dimensions:
> lat = 361 ;
> lon = 720 ;
> z = 26 ;
> name_len = 32 ;
> time = 1 ;
> variables:
> int grid_mapping ;
> grid_mapping:grid_mapping_name =
"latitude_longitude" ;
> grid_mapping:semi_major_axis = 6371000. ;
> grid_mapping:inverse_flattening = 0 ;
> double time(time) ;
> time:long_name = "forecast time" ;
> time:units = "seconds since 1970-1-1" ;
> time:axis = "T" ;
> double forecast_reference_time ;
> forecast_reference_time:long_name = "reference time"
;
> forecast_reference_time:units = "seconds since 1970-
1-1" ;
> int forecast_period ;
> forecast_period:units = "seconds" ;
> double lat(lat) ;
> lat:units = "degrees_north" ;
> lat:long_name = "latitude coordinate" ;
> lat:standard_name = "latitude" ;
> lat:_CoordinateAxisType = "Lat" ;
> double lon(lon) ;
> lon:units = "degrees_east" ;
> lon:long_name = "longitude coordinate" ;
> lon:standard_name = "longitude" ;
> lon:_CoordinateAxisType = "Lon" ;
> double z(z) ;
> z:standard_name = "altitude" ;
> z:long_name = "flight_level" ;
> z:units = "feet" ;
> z:positive = "up" ;
> z:axis = "Z" ;
> int field_id ;
> field_id:long_name = "field indentification number"
;
> char field_name(name_len) ;
> field_name:long_name = "field name" ;
> float edr(time, z, lat, lon) ;
> edr:units = "m^(2/3) s^-1" ;
> edr:long_name = "Median eddy dissipation rate" ;
> edr:coordinates = "lat lon" ;
> edr:_FillValue = -9999.f ;
> edr:grid_mapping = "grid_mapping" ;
>
> // global attributes:
> :Conventions = "CF-1.4" ;
> :Originating_center = "NCAR" ;
> :Product_Status = "Experimental Products" ;
> :Product_Type = "Forecast/Uninitialized Analysis" ;
> :DataType = "GRID" ;
> :DatasetLocation = "" ;
> data:
>
> time = 1375142400 ;
> }
>
>
> On Mon, Jul 22, 2019 at 9:00 AM Rosimar Rios-Berrios via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Jul 22 08:59:41 2019: Request 91179 was acted upon.
> > Transaction: Ticket created by rberrios at ucar.edu
> > Queue: met_help
> > Subject: MODE issue reading input file
> > Owner: Nobody
> > Requestors: rberrios at ucar.edu
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91179 >
> >
> >
> > Good morning MET help team,
> >
> > I am a new user of MET and specifically of MODE. I would like to
use MODE
> > to identify precipitation systems from output of an idealized
simulation.
> >
> > I have interpolated my model output to a lat-lon grid; however,
when
> trying
> > to run MODE I get the following error:
> >
> > ERROR : Trouble reading observation file
> > "/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > latlon_copy.nc"
> >
> > Here is the ncdump of my file:
> >
> > netcdf latlon_copy {
> >
> > dimensions:
> >
> > lat = 20 ;
> >
> > lon = 360 ;
> >
> > variables:
> >
> > float lat(lat) ;
> >
> > lat:long_name = "latitude" ;
> >
> > lat:units = "degrees_north" ;
> >
> > lat:standard_name = "latitude" ;
> >
> > lat:Projection = "latitude longitude" ;
> >
> > float lon(lon) ;
> >
> > lon:standard_name = "longitude" ;
> >
> > lon:long_name = "longitude" ;
> >
> > lon:units = "degrees_east" ;
> >
> > lon:Projection = "latitude longitude" ;
> >
> > float olrtoa(lat, lon) ;
> >
> > olrtoa:Projection = "latitude longitude" ;
> >
> > olrtoa:cell_methods = "Time: mean" ;
> >
> > float rainc(lat, lon) ;
> >
> > rainc:Projection = "latitude longitude" ;
> >
> > rainc:cell_methods = "Time: mean" ;
> >
> > float rainnc(lat, lon) ;
> >
> > rainnc:Projection = "latitude longitude" ;
> >
> > rainnc:cell_methods = "Time: mean" ;
> >
> > float mslp(lat, lon) ;
> >
> > mslp:Projection = "latitude longitude" ;
> >
> > mslp:cell_methods = "Time: mean" ;
> >
> > I understand that the file is supposed to be CF-compliant, but I
am
> unsure
> > how much additional information is needed in the NetCDF file for
lat-lon
> > projection.
> >
> > For reference, here are the contents of my config file:
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > //
> > // MODE configuration file.
> > //
> > // For additional information, see the MET_BASE/config/README
file.
> > //
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Output model name to be written
> > //
> > model = "MPAS";
> >
> > //
> > // Output description to be written
> > //
> > desc = "MPAS";
> >
> > //
> > // Output observation type to be written
> > //
> > obtype = "MPAS";
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Verification grid
> > // May be set separately in each "field" entry
> > //
> > regrid = {
> > to_grid = NONE;
> > method = NEAREST;
> > width = 1;
> > vld_thresh = 0.5;
> > shape = SQUARE;
> > }
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Approximate grid resolution (km)
> > //
> > grid_res = 120;
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Run all permutations of radius and threshold
> > //
> > quilt = FALSE;
> >
> > //
> > // Forecast and observation fields to be verified
> > //
> > fcst = {
> > field = {
> > name = "mslp";
> > level = "(*,*)";
> > }
> >
> > censor_thresh = [];
> > censor_val = [];
> > conv_radius = 5; // in grid squares
> > conv_thresh = <=1000.0;
> > vld_thresh = 0.5;
> > filter_attr_name = [];
> > filter_attr_thresh = [];
> > merge_thresh = >=1.25;
> > merge_flag = NONE;
> > }
> > obs = fcst;
> >
> > ...
> >
> > Everything else is the same as in the default config file. Could
you
> please
> > provide guidance as to what might be wrong with my input data or
my
> config
> > file?
> >
> > Many thanks!
> > Rosimar
> >
> > --
> >
_______________________________________________________________________
> > Rosimar Rios-Berrios, PhD
> > Postdoctoral Fellow | Advanced Study Program
> > Scientist I (beginning Aug. 12) | Mesoscale and Microscale
Meteorology
> > National Center for Atmospheric Research
> > https://rosimarwx.github.io/
> >
_______________________________________________________________________
> >
> >
>
>
--
_______________________________________________________________________
Rosimar Rios-Berrios, PhD
Postdoctoral Fellow | Advanced Study Program
Scientist I (beginning Aug. 12) | Mesoscale and Microscale Meteorology
National Center for Atmospheric Research
https://rosimarwx.github.io/
_______________________________________________________________________
------------------------------------------------
Subject: MODE issue reading input file
From: John Halley Gotway
Time: Mon Jul 22 17:04:15 2019
OK, I'm looking at this file, assuming its your latest since it has
the
most recent timestamp:
> *ncdump -h
/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/latlon.nc
<http://latlon.nc>*
netcdf latlon {
dimensions:
Time = UNLIMITED ; // (4 currently)
lat = 20 ;
lon = 360 ;
variables:
float lat(lat) ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
float lon(lon) ;
lon:units = "degrees_east" ;
lon:long_name = "longitude" ;
float olrtoa(Time, lat, lon) ;
float rainc(Time, lat, lon) ;
float rainnc(Time, lat, lon) ;
float mslp(Time, lat, lon) ;
You have added a time dimension, but no time variable. That's why
it's a
problem. Here's what I did:
*cd /glade/p/ral/jntp/johnhg/MET_Help/rios_berros_data_20190722*
*ncdump
/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/latlon.nc
<http://latlon.nc> > latlon.ncdump*
Edit latlon.ncdump by adding a "time" variable.
I made up 4 unixtime values using the following date commands:
date -ud ''2018-08-07' UTC '00:00:00'' +%s
date -ud ''2018-08-07' UTC '06:00:00'' +%s
date -ud ''2018-08-07' UTC '12:00:00'' +%s
date -ud ''2018-08-07' UTC '18:00:00'' +%s
You should obviously put in the actual times for your data. Then run
ncgen
to regenerate the NetCDF file:
*ncgen -o latlon_mod.nc <http://latlon_mod.nc> latlon.ncdump*
And now plot the result to confirm that the warning goes away:
*plot_data_plane latlon_mod.nc <http://latlon_mod.nc> plot.ps
<http://plot.ps> 'name="olrtoa"; level="(0,*,*)";' -v 4*
At verbosity level 4 (-v 4), it'll print out the timing info it read
from
the input file:
DEBUG 4: Data plane information:
DEBUG 4: plane min: 86.3835
DEBUG 4: plane max: 308.888
DEBUG 4: valid time: 20180807_000000
DEBUG 4: lead time: 000000
DEBUG 4: init time: 20180807_000000
DEBUG 4: accum time: 000000
Hope that gets you going.
Thanks,
John
On Mon, Jul 22, 2019 at 2:45 PM Rosimar Rios-Berrios via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91179 >
>
> Hi John,
>
> Thank you very much for your help and for even running a test with
my
> dataset.
>
> The domain that you obtained is correct - a narrow band around the
globe.
> After adding the global attribute and time variables, I was able to
plot my
> output with plot_data_plane. I was also able to run several tests
with
> MODE. I still get a warning:
>
> WARNING: MetNcCFDataFile::data_plane(VarInfo &, DataPlane &) ->
returns the
> first available time for "olrtoa" variable).
>
> I assume this is related to how I defined my time and
> forecast_reference_time variables. I will dig around more to try to
fix
> this.
>
> Thank you very much!
> Rosimar
>
> On Mon, Jul 22, 2019 at 11:23 AM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Rosimar,
> >
> > I see that you'd like to run the MODE tool on some NetCDF data,
but
> you're
> > having trouble getting it to read your data.
> >
> > When getting started with a new dataset in MET, I usually
recommend that
> > people start by running the plot_data_plane tool. That's a MET
tool
> which
> > reads a single field of data and creates a plot of it. There's no
config
> > file... you just specify what data you want on the command line.
This is
> > very useful in making sure that the MET tools can read you data
and place
> > it on the right place on earth. One issue I see is that the
NetCDF
> header
> > is missing the "Conventions" attribute which indicates CF-
compliance. So
> > MET doesn't know to interpret it as such. You can fix this by
adding
> that
> > global attribute:
> > Conventions = "CF-1.7";
> >
> > Alternatively, you can use the "file_type" option to explicitly
specify
> the
> > input file type. I logged on to cheyenne and ran these commands:
> >
> >
> > *> module use /glade/p/ral/jntp/MET/MET_releases/modulefiles*
> > *> module load met/8.1*
> > *> plot_data_plane
> > /glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > latlon_copy.nc
> > <http://latlon_copy.nc> plot.ps <http://plot.ps> 'name="olrtoa";
> > level="(*,*)"; file_type=NETCDF_NCCF;'*
> > DEBUG 1: Opening data file:
> > /glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > latlon_copy.nc
> > WARNING:
> > WARNING: NcCfFile::open() -> could not determine the valid time,
using 0.
> > WARNING:
> > DEBUG 1: Creating postscript file: plot.ps
> >
> > And that produced the attached plot. I see that you have a long,
skinny
> > latitude band. Is that what you expected?
> >
> > Note that I used "file_type = NETCDF_NCCF;" to tell MET to
interpret it
> as
> > such. Also, note that the warning that MET could get the valid
time.
> Fix
> > this by adding a "time" dimension with a coordinate variable to
specify
> the
> > timing info. Listed below is an example CF-compliant NetCDF file
which
> > includes timing info. Note that it also includes the
> > "forecast_reference_time" which is the CF-compliant way of
specifying a
> > model initialization time.
> >
> > Thanks,
> > John
> >
> > netcdf gtg_obs_forecast.20130730.i00.f00 {
> > dimensions:
> > lat = 361 ;
> > lon = 720 ;
> > z = 26 ;
> > name_len = 32 ;
> > time = 1 ;
> > variables:
> > int grid_mapping ;
> > grid_mapping:grid_mapping_name =
"latitude_longitude" ;
> > grid_mapping:semi_major_axis = 6371000. ;
> > grid_mapping:inverse_flattening = 0 ;
> > double time(time) ;
> > time:long_name = "forecast time" ;
> > time:units = "seconds since 1970-1-1" ;
> > time:axis = "T" ;
> > double forecast_reference_time ;
> > forecast_reference_time:long_name = "reference
time" ;
> > forecast_reference_time:units = "seconds since
1970-1-1"
> ;
> > int forecast_period ;
> > forecast_period:units = "seconds" ;
> > double lat(lat) ;
> > lat:units = "degrees_north" ;
> > lat:long_name = "latitude coordinate" ;
> > lat:standard_name = "latitude" ;
> > lat:_CoordinateAxisType = "Lat" ;
> > double lon(lon) ;
> > lon:units = "degrees_east" ;
> > lon:long_name = "longitude coordinate" ;
> > lon:standard_name = "longitude" ;
> > lon:_CoordinateAxisType = "Lon" ;
> > double z(z) ;
> > z:standard_name = "altitude" ;
> > z:long_name = "flight_level" ;
> > z:units = "feet" ;
> > z:positive = "up" ;
> > z:axis = "Z" ;
> > int field_id ;
> > field_id:long_name = "field indentification
number" ;
> > char field_name(name_len) ;
> > field_name:long_name = "field name" ;
> > float edr(time, z, lat, lon) ;
> > edr:units = "m^(2/3) s^-1" ;
> > edr:long_name = "Median eddy dissipation rate" ;
> > edr:coordinates = "lat lon" ;
> > edr:_FillValue = -9999.f ;
> > edr:grid_mapping = "grid_mapping" ;
> >
> > // global attributes:
> > :Conventions = "CF-1.4" ;
> > :Originating_center = "NCAR" ;
> > :Product_Status = "Experimental Products" ;
> > :Product_Type = "Forecast/Uninitialized Analysis"
;
> > :DataType = "GRID" ;
> > :DatasetLocation = "" ;
> > data:
> >
> > time = 1375142400 ;
> > }
> >
> >
> > On Mon, Jul 22, 2019 at 9:00 AM Rosimar Rios-Berrios via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Mon Jul 22 08:59:41 2019: Request 91179 was acted upon.
> > > Transaction: Ticket created by rberrios at ucar.edu
> > > Queue: met_help
> > > Subject: MODE issue reading input file
> > > Owner: Nobody
> > > Requestors: rberrios at ucar.edu
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91179
> >
> > >
> > >
> > > Good morning MET help team,
> > >
> > > I am a new user of MET and specifically of MODE. I would like to
use
> MODE
> > > to identify precipitation systems from output of an idealized
> simulation.
> > >
> > > I have interpolated my model output to a lat-lon grid; however,
when
> > trying
> > > to run MODE I get the following error:
> > >
> > > ERROR : Trouble reading observation file
> > > "/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > > latlon_copy.nc"
> > >
> > > Here is the ncdump of my file:
> > >
> > > netcdf latlon_copy {
> > >
> > > dimensions:
> > >
> > > lat = 20 ;
> > >
> > > lon = 360 ;
> > >
> > > variables:
> > >
> > > float lat(lat) ;
> > >
> > > lat:long_name = "latitude" ;
> > >
> > > lat:units = "degrees_north" ;
> > >
> > > lat:standard_name = "latitude" ;
> > >
> > > lat:Projection = "latitude longitude" ;
> > >
> > > float lon(lon) ;
> > >
> > > lon:standard_name = "longitude" ;
> > >
> > > lon:long_name = "longitude" ;
> > >
> > > lon:units = "degrees_east" ;
> > >
> > > lon:Projection = "latitude longitude" ;
> > >
> > > float olrtoa(lat, lon) ;
> > >
> > > olrtoa:Projection = "latitude longitude" ;
> > >
> > > olrtoa:cell_methods = "Time: mean" ;
> > >
> > > float rainc(lat, lon) ;
> > >
> > > rainc:Projection = "latitude longitude" ;
> > >
> > > rainc:cell_methods = "Time: mean" ;
> > >
> > > float rainnc(lat, lon) ;
> > >
> > > rainnc:Projection = "latitude longitude" ;
> > >
> > > rainnc:cell_methods = "Time: mean" ;
> > >
> > > float mslp(lat, lon) ;
> > >
> > > mslp:Projection = "latitude longitude" ;
> > >
> > > mslp:cell_methods = "Time: mean" ;
> > >
> > > I understand that the file is supposed to be CF-compliant, but I
am
> > unsure
> > > how much additional information is needed in the NetCDF file for
> lat-lon
> > > projection.
> > >
> > > For reference, here are the contents of my config file:
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > //
> > > // MODE configuration file.
> > > //
> > > // For additional information, see the MET_BASE/config/README
file.
> > > //
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Output model name to be written
> > > //
> > > model = "MPAS";
> > >
> > > //
> > > // Output description to be written
> > > //
> > > desc = "MPAS";
> > >
> > > //
> > > // Output observation type to be written
> > > //
> > > obtype = "MPAS";
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Verification grid
> > > // May be set separately in each "field" entry
> > > //
> > > regrid = {
> > > to_grid = NONE;
> > > method = NEAREST;
> > > width = 1;
> > > vld_thresh = 0.5;
> > > shape = SQUARE;
> > > }
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Approximate grid resolution (km)
> > > //
> > > grid_res = 120;
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Run all permutations of radius and threshold
> > > //
> > > quilt = FALSE;
> > >
> > > //
> > > // Forecast and observation fields to be verified
> > > //
> > > fcst = {
> > > field = {
> > > name = "mslp";
> > > level = "(*,*)";
> > > }
> > >
> > > censor_thresh = [];
> > > censor_val = [];
> > > conv_radius = 5; // in grid squares
> > > conv_thresh = <=1000.0;
> > > vld_thresh = 0.5;
> > > filter_attr_name = [];
> > > filter_attr_thresh = [];
> > > merge_thresh = >=1.25;
> > > merge_flag = NONE;
> > > }
> > > obs = fcst;
> > >
> > > ...
> > >
> > > Everything else is the same as in the default config file. Could
you
> > please
> > > provide guidance as to what might be wrong with my input data or
my
> > config
> > > file?
> > >
> > > Many thanks!
> > > Rosimar
> > >
> > > --
> > >
_______________________________________________________________________
> > > Rosimar Rios-Berrios, PhD
> > > Postdoctoral Fellow | Advanced Study Program
> > > Scientist I (beginning Aug. 12) | Mesoscale and Microscale
Meteorology
> > > National Center for Atmospheric Research
> > > https://rosimarwx.github.io/
> > >
_______________________________________________________________________
> > >
> > >
> >
> >
>
> --
>
_______________________________________________________________________
> Rosimar Rios-Berrios, PhD
> Postdoctoral Fellow | Advanced Study Program
> Scientist I (beginning Aug. 12) | Mesoscale and Microscale
Meteorology
> National Center for Atmospheric Research
> https://rosimarwx.github.io/
>
_______________________________________________________________________
>
>
------------------------------------------------
Subject: MODE issue reading input file
From: Rosimar Rios-Berrios
Time: Mon Jul 22 17:34:11 2019
I was using a different file, but I suspect that I had not specified
the
correct attributes. I fixed the issues by following similar steps as
yours
except using nco:
ncap2 -s 'Time[$Time]=array(1077710400,1077710400,$Time)' latlon2.nc
latlon2.nc
ncatted -a units,Time,a,c,"seconds since 1970-1-1" latlon2.nc
Now ncdump gives me:
netcdf latlon2 {
dimensions:
Time = UNLIMITED ; // (1 currently)
lat = 20 ;
lon = 360 ;
variables:
int Time(Time) ;
Time:units = "seconds since 1970-1-1" ;
float lat(lat) ;
lat:long_name = "latitude" ;
lat:units = "degrees_north" ;
float lon(lon) ;
lon:units = "degrees_east" ;
lon:long_name = "longitude" ;
float olrtoa(Time, lat, lon) ;
float rainc(Time, lat, lon) ;
float rainnc(Time, lat, lon) ;
float mslp(Time, lat, lon) ;
// global attributes:
:Conventions = "CF-1.7" ;
Voila! Both plot_data_plane and mode run without warnings. Thank you
very
much for your help!
Best,
Rosimar
On Mon, Jul 22, 2019 at 5:04 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> OK, I'm looking at this file, assuming its your latest since it has
the
> most recent timestamp:
> > *ncdump -h
>
/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/latlon.nc
> <http://latlon.nc>*
>
> netcdf latlon {
> dimensions:
> Time = UNLIMITED ; // (4 currently)
> lat = 20 ;
> lon = 360 ;
> variables:
> float lat(lat) ;
> lat:long_name = "latitude" ;
> lat:units = "degrees_north" ;
> float lon(lon) ;
> lon:units = "degrees_east" ;
> lon:long_name = "longitude" ;
> float olrtoa(Time, lat, lon) ;
> float rainc(Time, lat, lon) ;
> float rainnc(Time, lat, lon) ;
> float mslp(Time, lat, lon) ;
>
> You have added a time dimension, but no time variable. That's why
it's a
> problem. Here's what I did:
>
> *cd /glade/p/ral/jntp/johnhg/MET_Help/rios_berros_data_20190722*
> *ncdump
>
/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/latlon.nc
> <http://latlon.nc> > latlon.ncdump*
>
> Edit latlon.ncdump by adding a "time" variable.
> I made up 4 unixtime values using the following date commands:
> date -ud ''2018-08-07' UTC '00:00:00'' +%s
> date -ud ''2018-08-07' UTC '06:00:00'' +%s
> date -ud ''2018-08-07' UTC '12:00:00'' +%s
> date -ud ''2018-08-07' UTC '18:00:00'' +%s
>
> You should obviously put in the actual times for your data. Then
run ncgen
> to regenerate the NetCDF file:
> *ncgen -o latlon_mod.nc <http://latlon_mod.nc> latlon.ncdump*
>
> And now plot the result to confirm that the warning goes away:
> *plot_data_plane latlon_mod.nc <http://latlon_mod.nc> plot.ps
> <http://plot.ps> 'name="olrtoa"; level="(0,*,*)";' -v 4*
>
> At verbosity level 4 (-v 4), it'll print out the timing info it read
from
> the input file:
> DEBUG 4: Data plane information:
> DEBUG 4: plane min: 86.3835
> DEBUG 4: plane max: 308.888
> DEBUG 4: valid time: 20180807_000000
> DEBUG 4: lead time: 000000
> DEBUG 4: init time: 20180807_000000
> DEBUG 4: accum time: 000000
>
> Hope that gets you going.
>
> Thanks,
> John
>
>
>
>
> On Mon, Jul 22, 2019 at 2:45 PM Rosimar Rios-Berrios via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91179 >
> >
> > Hi John,
> >
> > Thank you very much for your help and for even running a test with
my
> > dataset.
> >
> > The domain that you obtained is correct - a narrow band around the
globe.
> > After adding the global attribute and time variables, I was able
to plot
> my
> > output with plot_data_plane. I was also able to run several tests
with
> > MODE. I still get a warning:
> >
> > WARNING: MetNcCFDataFile::data_plane(VarInfo &, DataPlane &) ->
returns
> the
> > first available time for "olrtoa" variable).
> >
> > I assume this is related to how I defined my time and
> > forecast_reference_time variables. I will dig around more to try
to fix
> > this.
> >
> > Thank you very much!
> > Rosimar
> >
> > On Mon, Jul 22, 2019 at 11:23 AM John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Rosimar,
> > >
> > > I see that you'd like to run the MODE tool on some NetCDF data,
but
> > you're
> > > having trouble getting it to read your data.
> > >
> > > When getting started with a new dataset in MET, I usually
recommend
> that
> > > people start by running the plot_data_plane tool. That's a MET
tool
> > which
> > > reads a single field of data and creates a plot of it. There's
no
> config
> > > file... you just specify what data you want on the command line.
This
> is
> > > very useful in making sure that the MET tools can read you data
and
> place
> > > it on the right place on earth. One issue I see is that the
NetCDF
> > header
> > > is missing the "Conventions" attribute which indicates CF-
compliance.
> So
> > > MET doesn't know to interpret it as such. You can fix this by
adding
> > that
> > > global attribute:
> > > Conventions = "CF-1.7";
> > >
> > > Alternatively, you can use the "file_type" option to explicitly
specify
> > the
> > > input file type. I logged on to cheyenne and ran these
commands:
> > >
> > >
> > > *> module use /glade/p/ral/jntp/MET/MET_releases/modulefiles*
> > > *> module load met/8.1*
> > > *> plot_data_plane
> > > /glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > > latlon_copy.nc
> > > <http://latlon_copy.nc> plot.ps <http://plot.ps> 'name="olrtoa";
> > > level="(*,*)"; file_type=NETCDF_NCCF;'*
> > > DEBUG 1: Opening data file:
> > > /glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > > latlon_copy.nc
> > > WARNING:
> > > WARNING: NcCfFile::open() -> could not determine the valid time,
using
> 0.
> > > WARNING:
> > > DEBUG 1: Creating postscript file: plot.ps
> > >
> > > And that produced the attached plot. I see that you have a
long,
> skinny
> > > latitude band. Is that what you expected?
> > >
> > > Note that I used "file_type = NETCDF_NCCF;" to tell MET to
interpret it
> > as
> > > such. Also, note that the warning that MET could get the valid
time.
> > Fix
> > > this by adding a "time" dimension with a coordinate variable to
specify
> > the
> > > timing info. Listed below is an example CF-compliant NetCDF
file which
> > > includes timing info. Note that it also includes the
> > > "forecast_reference_time" which is the CF-compliant way of
specifying a
> > > model initialization time.
> > >
> > > Thanks,
> > > John
> > >
> > > netcdf gtg_obs_forecast.20130730.i00.f00 {
> > > dimensions:
> > > lat = 361 ;
> > > lon = 720 ;
> > > z = 26 ;
> > > name_len = 32 ;
> > > time = 1 ;
> > > variables:
> > > int grid_mapping ;
> > > grid_mapping:grid_mapping_name =
"latitude_longitude" ;
> > > grid_mapping:semi_major_axis = 6371000. ;
> > > grid_mapping:inverse_flattening = 0 ;
> > > double time(time) ;
> > > time:long_name = "forecast time" ;
> > > time:units = "seconds since 1970-1-1" ;
> > > time:axis = "T" ;
> > > double forecast_reference_time ;
> > > forecast_reference_time:long_name = "reference
time" ;
> > > forecast_reference_time:units = "seconds since
> 1970-1-1"
> > ;
> > > int forecast_period ;
> > > forecast_period:units = "seconds" ;
> > > double lat(lat) ;
> > > lat:units = "degrees_north" ;
> > > lat:long_name = "latitude coordinate" ;
> > > lat:standard_name = "latitude" ;
> > > lat:_CoordinateAxisType = "Lat" ;
> > > double lon(lon) ;
> > > lon:units = "degrees_east" ;
> > > lon:long_name = "longitude coordinate" ;
> > > lon:standard_name = "longitude" ;
> > > lon:_CoordinateAxisType = "Lon" ;
> > > double z(z) ;
> > > z:standard_name = "altitude" ;
> > > z:long_name = "flight_level" ;
> > > z:units = "feet" ;
> > > z:positive = "up" ;
> > > z:axis = "Z" ;
> > > int field_id ;
> > > field_id:long_name = "field indentification
number" ;
> > > char field_name(name_len) ;
> > > field_name:long_name = "field name" ;
> > > float edr(time, z, lat, lon) ;
> > > edr:units = "m^(2/3) s^-1" ;
> > > edr:long_name = "Median eddy dissipation rate" ;
> > > edr:coordinates = "lat lon" ;
> > > edr:_FillValue = -9999.f ;
> > > edr:grid_mapping = "grid_mapping" ;
> > >
> > > // global attributes:
> > > :Conventions = "CF-1.4" ;
> > > :Originating_center = "NCAR" ;
> > > :Product_Status = "Experimental Products" ;
> > > :Product_Type = "Forecast/Uninitialized
Analysis" ;
> > > :DataType = "GRID" ;
> > > :DatasetLocation = "" ;
> > > data:
> > >
> > > time = 1375142400 ;
> > > }
> > >
> > >
> > > On Mon, Jul 22, 2019 at 9:00 AM Rosimar Rios-Berrios via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Mon Jul 22 08:59:41 2019: Request 91179 was acted upon.
> > > > Transaction: Ticket created by rberrios at ucar.edu
> > > > Queue: met_help
> > > > Subject: MODE issue reading input file
> > > > Owner: Nobody
> > > > Requestors: rberrios at ucar.edu
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=91179
> > >
> > > >
> > > >
> > > > Good morning MET help team,
> > > >
> > > > I am a new user of MET and specifically of MODE. I would like
to use
> > MODE
> > > > to identify precipitation systems from output of an idealized
> > simulation.
> > > >
> > > > I have interpolated my model output to a lat-lon grid;
however, when
> > > trying
> > > > to run MODE I get the following error:
> > > >
> > > > ERROR : Trouble reading observation file
> > > >
"/glade/scratch/rberrios/MPAS_APE/aqua_qobs/120km_alb06/latlon/
> > > > latlon_copy.nc"
> > > >
> > > > Here is the ncdump of my file:
> > > >
> > > > netcdf latlon_copy {
> > > >
> > > > dimensions:
> > > >
> > > > lat = 20 ;
> > > >
> > > > lon = 360 ;
> > > >
> > > > variables:
> > > >
> > > > float lat(lat) ;
> > > >
> > > > lat:long_name = "latitude" ;
> > > >
> > > > lat:units = "degrees_north" ;
> > > >
> > > > lat:standard_name = "latitude" ;
> > > >
> > > > lat:Projection = "latitude longitude" ;
> > > >
> > > > float lon(lon) ;
> > > >
> > > > lon:standard_name = "longitude" ;
> > > >
> > > > lon:long_name = "longitude" ;
> > > >
> > > > lon:units = "degrees_east" ;
> > > >
> > > > lon:Projection = "latitude longitude" ;
> > > >
> > > > float olrtoa(lat, lon) ;
> > > >
> > > > olrtoa:Projection = "latitude longitude" ;
> > > >
> > > > olrtoa:cell_methods = "Time: mean" ;
> > > >
> > > > float rainc(lat, lon) ;
> > > >
> > > > rainc:Projection = "latitude longitude" ;
> > > >
> > > > rainc:cell_methods = "Time: mean" ;
> > > >
> > > > float rainnc(lat, lon) ;
> > > >
> > > > rainnc:Projection = "latitude longitude" ;
> > > >
> > > > rainnc:cell_methods = "Time: mean" ;
> > > >
> > > > float mslp(lat, lon) ;
> > > >
> > > > mslp:Projection = "latitude longitude" ;
> > > >
> > > > mslp:cell_methods = "Time: mean" ;
> > > >
> > > > I understand that the file is supposed to be CF-compliant, but
I am
> > > unsure
> > > > how much additional information is needed in the NetCDF file
for
> > lat-lon
> > > > projection.
> > > >
> > > > For reference, here are the contents of my config file:
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > //
> > > > // MODE configuration file.
> > > > //
> > > > // For additional information, see the MET_BASE/config/README
file.
> > > > //
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Output model name to be written
> > > > //
> > > > model = "MPAS";
> > > >
> > > > //
> > > > // Output description to be written
> > > > //
> > > > desc = "MPAS";
> > > >
> > > > //
> > > > // Output observation type to be written
> > > > //
> > > > obtype = "MPAS";
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Verification grid
> > > > // May be set separately in each "field" entry
> > > > //
> > > > regrid = {
> > > > to_grid = NONE;
> > > > method = NEAREST;
> > > > width = 1;
> > > > vld_thresh = 0.5;
> > > > shape = SQUARE;
> > > > }
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Approximate grid resolution (km)
> > > > //
> > > > grid_res = 120;
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Run all permutations of radius and threshold
> > > > //
> > > > quilt = FALSE;
> > > >
> > > > //
> > > > // Forecast and observation fields to be verified
> > > > //
> > > > fcst = {
> > > > field = {
> > > > name = "mslp";
> > > > level = "(*,*)";
> > > > }
> > > >
> > > > censor_thresh = [];
> > > > censor_val = [];
> > > > conv_radius = 5; // in grid squares
> > > > conv_thresh = <=1000.0;
> > > > vld_thresh = 0.5;
> > > > filter_attr_name = [];
> > > > filter_attr_thresh = [];
> > > > merge_thresh = >=1.25;
> > > > merge_flag = NONE;
> > > > }
> > > > obs = fcst;
> > > >
> > > > ...
> > > >
> > > > Everything else is the same as in the default config file.
Could you
> > > please
> > > > provide guidance as to what might be wrong with my input data
or my
> > > config
> > > > file?
> > > >
> > > > Many thanks!
> > > > Rosimar
> > > >
> > > > --
> > > >
>
_______________________________________________________________________
> > > > Rosimar Rios-Berrios, PhD
> > > > Postdoctoral Fellow | Advanced Study Program
> > > > Scientist I (beginning Aug. 12) | Mesoscale and Microscale
> Meteorology
> > > > National Center for Atmospheric Research
> > > > https://rosimarwx.github.io/
> > > >
>
_______________________________________________________________________
> > > >
> > > >
> > >
> > >
> >
> > --
> >
_______________________________________________________________________
> > Rosimar Rios-Berrios, PhD
> > Postdoctoral Fellow | Advanced Study Program
> > Scientist I (beginning Aug. 12) | Mesoscale and Microscale
Meteorology
> > National Center for Atmospheric Research
> > https://rosimarwx.github.io/
> >
_______________________________________________________________________
> >
> >
>
>
--
_______________________________________________________________________
Rosimar Rios-Berrios, PhD
Postdoctoral Fellow | Advanced Study Program
Scientist I (beginning Aug. 12) | Mesoscale and Microscale Meteorology
National Center for Atmospheric Research
https://rosimarwx.github.io/
_______________________________________________________________________
------------------------------------------------
More information about the Met_help
mailing list