[Met_help] [rt.rap.ucar.edu #75202] History for MODE Time Dimension (MTD) troubleshooting
John Halley Gotway via RT
met_help at ucar.edu
Tue Feb 23 10:47:25 MST 2016
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear MET Help,
I am trying to use the MODE Time Dimension tool on some data that works
with the MODE tool in version 5.1. The NetCDF files are pre-processed by me
to add in the global and variable attributes required for MODE to work,
which it does. However, when running the MTD tool, I get the following
output that concludes with an error:
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Lambert Conformal Grid Data:
DEBUG 4: scale_lat_1 = 30
DEBUG 4: scale_lat_2 = 60
DEBUG 4: lat_pin = 40.8521
DEBUG 4: lon_pin = 72.8817
DEBUG 4: x_pin = 400
DEBUG 4: y_pin = 400
DEBUG 4: lon_orient = 77.6
DEBUG 4: d_km = 2
DEBUG 4: r_km = 6371.2
DEBUG 4: nx = 801
DEBUG 4: ny = 801
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Lambert Conformal Grid Data:
DEBUG 4: scale_lat_1 = 30
DEBUG 4: scale_lat_2 = 60
DEBUG 4: lat_pin = 40.8521
DEBUG 4: lon_pin = 72.8817
DEBUG 4: x_pin = 400
DEBUG 4: y_pin = 400
DEBUG 4: lon_orient = 77.6
DEBUG 4: d_km = 2
DEBUG 4: r_km = 6371.2
DEBUG 4: nx = 801
DEBUG 4: ny = 801
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".
DEBUG 2: mtd_read_data() -> processing file
"/home/sara/MET/met-5.1/stitched/20101226/cf/st_20101226_1405.nc"
DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_NcMet".
DEBUG 4: Lambert Conformal Grid Data:
DEBUG 4: scale_lat_1 = 30
DEBUG 4: scale_lat_2 = 60
DEBUG 4: lat_pin = 40.8521
DEBUG 4: lon_pin = 72.8817
DEBUG 4: x_pin = 400
DEBUG 4: y_pin = 400
DEBUG 4: lon_orient = 77.6
DEBUG 4: d_km = 2
DEBUG 4: r_km = 6371.2
DEBUG 4: nx = 801
DEBUG 4: ny = 801
ERROR :
ERROR :
ERROR : mtd_read_data() -> unable to get data plane at time 0
ERROR :
Are there different global/variable attributes that mtd_read_data() is
looking for within the file? I've been testing with just two files at a
time for now. The data are 5-minute radar composite NetCDF files and I've
been using them as both the forecast and analysis files at this stage for
testing. Here's the header information for both of my files:
## File 1:
netcdf st_20101226_1405 {
dimensions:
time = 1 ;
lat = 801 ;
lon = 801 ;
variables:
int time ;
time:long_name = "time" ;
time:units = "seconds since 1970-1-1" ;
float dbz(time, lat, lon) ;
dbz:long_name = "dbz" ;
dbz:units = "dbz" ;
dbz:level = "1kmAGL" ;
dbz:_FillValue = -9999.f ;
dbz:init_time = "20101226_1405" ;
dbz:valid_time = "20101226_1405" ;
dbz:init_time_ut = 1293372300 ;
dbz:valid_time_ut = 1293372300 ;
dbz:accum_time_sec = 300 ;
dbz:accum_time = "5" ;
float lons(lat, lon) ;
lons:long_name = "longitude" ;
lons:units = "degrees_east" ;
lons:standard_name = "longitude" ;
lons:name = "longitude" ;
lons:_FillValue = -9999.f ;
float lats(lat, lon) ;
lats:long_name = "latitude" ;
lats:units = "degrees_north" ;
lats:standard_name = "latitude" ;
lats:name = "latitude" ;
lats:_FillValue = -9999.f ;
// global attributes:
:MET_version = "v5.1" ;
:nx = "801" ;
:ny = "801 grid_points" ;
:Projection = "Lambert Conformal" ;
:scale_lat_1 = "30.000000" ;
:scale_lat_2 = "60.000000" ;
:lat_pin = "40.8521" ;
:lon_pin = "-72.8817" ;
:x_pin = "400" ;
:y_pin = "400" ;
:lon_orient = "-77.600000" ;
:d_km = "2.0000" ;
:r_km = "6371.200000" ;
:nco_openmp_thread_number = 1 ;
:history = "Mon Feb 22 11:45:59 2016: ncatted -O -a
history,global,d,, st_20101226_1405.nc" ;
}
## File #2:
netcdf st_20101226_1410 {
dimensions:
time = 1 ;
lat = 801 ;
lon = 801 ;
variables:
int time ;
time:long_name = "time" ;
time:units = "seconds since 1970-1-1" ;
float dbz(time, lat, lon) ;
dbz:long_name = "dbz" ;
dbz:units = "dbz" ;
dbz:level = "1kmAGL" ;
dbz:_FillValue = -9999.f ;
dbz:init_time = "20101226_1405" ;
dbz:valid_time = "20101226_1410" ;
dbz:init_time_ut = 1293372300 ;
dbz:valid_time_ut = 1293372600 ;
dbz:accum_time_sec = 300 ;
dbz:accum_time = "5" ;
float lons(lat, lon) ;
lons:long_name = "longitude" ;
lons:units = "degrees_east" ;
lons:standard_name = "longitude" ;
lons:name = "longitude" ;
lons:_FillValue = -9999.f ;
float lats(lat, lon) ;
lats:long_name = "latitude" ;
lats:units = "degrees_north" ;
lats:standard_name = "latitude" ;
lats:name = "latitude" ;
lats:_FillValue = -9999.f ;
// global attributes:
:MET_version = "v5.1" ;
:nx = "801" ;
:ny = "801 grid_points" ;
:Projection = "Lambert Conformal" ;
:scale_lat_1 = "30.000000" ;
:scale_lat_2 = "60.000000" ;
:lat_pin = "40.8521" ;
:lon_pin = "-72.8817" ;
:x_pin = "400" ;
:y_pin = "400" ;
:lon_orient = "-77.600000" ;
:d_km = "2.0000" ;
:r_km = "6371.200000" ;
:nco_openmp_thread_number = 1 ;
:history = "Mon Feb 22 11:46:05 2016: ncatted -O -a
history,global,d,, st_20101226_1410.nc" ;
}
Finally, to be all-inclusive I am also providing how I am calling MTD and
the configure file.
$ /met-5.1/bin/mtd -fcst st_*.nc -obs st_*.nc
/met-5.1/data/config/MTDConfig_test -log mtd.log -v 4
////////////////////////////////////////////////////////////////////////////////
//
// MODE Time Domain configuration file.
//
// For additional information, see the MET_BASE/config/README file.
//
////////////////////////////////////////////////////////////////////////////////
//
// Output model name to be written
//
model = "WRF";
//
// Output observation type to be written
//
obtype = "OBS";
////////////////////////////////////////////////////////////////////////////////
//
// Verification grid
//
regrid = {
to_grid = NONE;
vld_thresh = 0.5;
method = NEAREST;
width = 1;
}
////////////////////////////////////////////////////////////////////////////////
//
// Approximate grid resolution (km)
//
grid_res = 2;
////////////////////////////////////////////////////////////////////////////////
//
// Forecast and observation fields to be verified
//
fcst = {
field = {
name = "dbz";
level = "(0,*,*)";
}
raw_thresh = >=28;
conv_radius = 5; // 13.3/grid_res; // in grid squares
conv_thresh = >=5.0;
vld_thresh = 0.5;
area_thresh = NA;
inten_perc_value = 100;
inten_perc_thresh = NA;
merge_thresh = >=1.25;
merge_flag = NONE;
}
obs = {
field = {
name = "dbz";
level = "(0,*,*)";
}
raw_thresh = >=28;
conv_radius = 1; // 13.3/grid_res; // in grid squares
conv_thresh = >=15.0;
vld_thresh = 0.75;
area_thresh = NA;
inten_perc_value = 100;
inten_perc_thresh = NA;
merge_thresh = >=1.25;
merge_flag = NONE;
}
////////////////////////////////////////////////////////////////////////////////
//
// Throw away 3D objects with volumes smaller than this
//
min_volume = 2000;
////////////////////////////////////////////////////////////////////////////////
//
// Fuzzy engine weights
//
weight = {
space_centroid_dist = 1.0;
time_centroid_delta = 1.0;
speed_delta = 1.0;
direction_diff = 1.0;
volume_ratio = 1.0;
axis_angle_diff = 1.0;
start_time_delta = 1.0;
end_time_delta = 1.0;
}
////////////////////////////////////////////////////////////////////////////////
//
// Fuzzy engine interest functions
//
interest_function = {
space_centroid_dist = (
( 0.0, 1.0 )
( 50.0, 0.5 )
( 100.0, 0.0 )
);
time_centroid_delta = (
( -3.0, 0.0 )
( -2.0, 0.5 )
( -1.0, 0.8 )
( 0.0, 1.0 )
( 1.0, 0.8 )
( 2.0, 0.5 )
( 3.0, 0.0 )
);
speed_delta = (
( -10.0, 0.0 )
( -5.0, 0.5 )
( 0.0, 1.0 )
( 5.0, 0.5 )
( 10.0, 0.0 )
);
direction_diff = (
( 0.0, 1.0 )
( 90.0, 0.0 )
( 180.0, 0.0 )
);
volume_ratio = (
( 0.0, 0.0 )
( 0.5, 0.5 )
( 1.0, 1.0 )
( 1.5, 0.5 )
( 2.0, 0.0 )
);
axis_angle_diff = (
( 0.0, 1.0 )
( 30.0, 1.0 )
( 90.0, 0.0 )
);
start_time_delta = (
( 0.0, 1.0 )
( 3.0, 0.5 )
( 5.0, 0.0 )
);
end_time_delta = (
( 0.0, 1.0 )
( 3.0, 0.5 )
( 5.0, 0.0 )
);
} // interest functions
////////////////////////////////////////////////////////////////////////////////
//
// Total interest threshold for determining matches
//
total_interest_thresh = 0.7;
////////////////////////////////////////////////////////////////////////////////
//
// Output flags
//
nc_output = {
latlon = true;
raw = true;
object_id = true;
cluster_id = true;
}
txt_output = {
attributes_2d = true;
attributes_3d = true;
}
////////////////////////////////////////////////////////////////////////////////
output_prefix = "";
version = "V5.1";
////////////////////////////////////////////////////////////////////////////////
Thank you in advance for your help!
Take care,
Sara Ganetis
PhD Candidate
Stony Brook University
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MODE Time Dimension (MTD) troubleshooting
From: John Halley Gotway
Time: Mon Feb 22 10:35:00 2016
Hi Sara,
Thanks for sending all these great details, it really helps a lot.
MET
supports a few different flavors of gridded NetCDF data, but I think
the
issue here is that you're mixing two of them together. Your NetCDF
files
look very, very similar to the output of the pcp_combine tool but
you're
using a time dimension which is not used by pcp_combine. I suspect
that's
causing the issue.
Please try editing one of your NetCDF files by removing the time
dimension,
like this:
netcdf st_20101226_1410 {
dimensions:
lat = 801 ;
lon = 801 ;
variables:
float dbz(lat, lon) ;
dbz:long_name = "dbz" ;
dbz:units = "dbz" ;
dbz:level = "1kmAGL" ;
dbz:_FillValue = -9999.f ;
dbz:init_time = "20101226_1405" ;
dbz:valid_time = "20101226_1410" ;
dbz:init_time_ut = 1293372300 ;
dbz:valid_time_ut = 1293372600 ;
dbz:accum_time_sec = 300 ;
dbz:accum_time = "5" ;
Once you've removed that, try running the plot_data_plane tool.
That's a
great way of easily testing to see if MET can read your gridded data:
met-5.1/bin/plot_data_plane /home/sara/MET/met-
5.1/stitched/20101226/cf/
st_20101226_1405.nc plot_dbz.ps 'name="dbz"; level="(*,*)";'
That will create a PostScript file which can be converted to png like
this:
convert -rotate 90 -background white plot_dbz.ps plot_dbz.png
If removing the "time" dimension and variable doesn't fix the problem,
please post a sample data file to our anonymous ftp site following
these
instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John Halley Gotway
met_help at ucar.edu
On Mon, Feb 22, 2016 at 10:10 AM, Sara Ganetis via RT
<met_help at ucar.edu>
wrote:
>
> Mon Feb 22 10:10:56 2016: Request 75202 was acted upon.
> Transaction: Ticket created by sara.ganetis at stonybrook.edu
> Queue: met_help
> Subject: MODE Time Dimension (MTD) troubleshooting
> Owner: Nobody
> Requestors: sara.ganetis at stonybrook.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202 >
>
>
> Dear MET Help,
>
> I am trying to use the MODE Time Dimension tool on some data that
works
> with the MODE tool in version 5.1. The NetCDF files are pre-
processed by me
> to add in the global and variable attributes required for MODE to
work,
> which it does. However, when running the MTD tool, I get the
following
> output that concludes with an error:
>
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Lambert Conformal Grid Data:
> DEBUG 4: scale_lat_1 = 30
> DEBUG 4: scale_lat_2 = 60
> DEBUG 4: lat_pin = 40.8521
> DEBUG 4: lon_pin = 72.8817
> DEBUG 4: x_pin = 400
> DEBUG 4: y_pin = 400
> DEBUG 4: lon_orient = 77.6
> DEBUG 4: d_km = 2
> DEBUG 4: r_km = 6371.2
> DEBUG 4: nx = 801
> DEBUG 4: ny = 801
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Lambert Conformal Grid Data:
> DEBUG 4: scale_lat_1 = 30
> DEBUG 4: scale_lat_2 = 60
> DEBUG 4: lat_pin = 40.8521
> DEBUG 4: lon_pin = 72.8817
> DEBUG 4: x_pin = 400
> DEBUG 4: y_pin = 400
> DEBUG 4: lon_orient = 77.6
> DEBUG 4: d_km = 2
> DEBUG 4: r_km = 6371.2
> DEBUG 4: nx = 801
> DEBUG 4: ny = 801
> 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".
> DEBUG 2: mtd_read_data() -> processing file
> "/home/sara/MET/met-5.1/stitched/20101226/cf/st_20101226_1405.nc"
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_NcMet".
> DEBUG 4: Lambert Conformal Grid Data:
> DEBUG 4: scale_lat_1 = 30
> DEBUG 4: scale_lat_2 = 60
> DEBUG 4: lat_pin = 40.8521
> DEBUG 4: lon_pin = 72.8817
> DEBUG 4: x_pin = 400
> DEBUG 4: y_pin = 400
> DEBUG 4: lon_orient = 77.6
> DEBUG 4: d_km = 2
> DEBUG 4: r_km = 6371.2
> DEBUG 4: nx = 801
> DEBUG 4: ny = 801
> ERROR :
> ERROR :
> ERROR : mtd_read_data() -> unable to get data plane at time 0
> ERROR :
>
> Are there different global/variable attributes that mtd_read_data()
is
> looking for within the file? I've been testing with just two files
at a
> time for now. The data are 5-minute radar composite NetCDF files and
I've
> been using them as both the forecast and analysis files at this
stage for
> testing. Here's the header information for both of my files:
>
> ## File 1:
>
> netcdf st_20101226_1405 {
> dimensions:
> time = 1 ;
> lat = 801 ;
> lon = 801 ;
> variables:
> int time ;
> time:long_name = "time" ;
> time:units = "seconds since 1970-1-1" ;
> float dbz(time, lat, lon) ;
> dbz:long_name = "dbz" ;
> dbz:units = "dbz" ;
> dbz:level = "1kmAGL" ;
> dbz:_FillValue = -9999.f ;
> dbz:init_time = "20101226_1405" ;
> dbz:valid_time = "20101226_1405" ;
> dbz:init_time_ut = 1293372300 ;
> dbz:valid_time_ut = 1293372300 ;
> dbz:accum_time_sec = 300 ;
> dbz:accum_time = "5" ;
> float lons(lat, lon) ;
> lons:long_name = "longitude" ;
> lons:units = "degrees_east" ;
> lons:standard_name = "longitude" ;
> lons:name = "longitude" ;
> lons:_FillValue = -9999.f ;
> float lats(lat, lon) ;
> lats:long_name = "latitude" ;
> lats:units = "degrees_north" ;
> lats:standard_name = "latitude" ;
> lats:name = "latitude" ;
> lats:_FillValue = -9999.f ;
>
> // global attributes:
> :MET_version = "v5.1" ;
> :nx = "801" ;
> :ny = "801 grid_points" ;
> :Projection = "Lambert Conformal" ;
> :scale_lat_1 = "30.000000" ;
> :scale_lat_2 = "60.000000" ;
> :lat_pin = "40.8521" ;
> :lon_pin = "-72.8817" ;
> :x_pin = "400" ;
> :y_pin = "400" ;
> :lon_orient = "-77.600000" ;
> :d_km = "2.0000" ;
> :r_km = "6371.200000" ;
> :nco_openmp_thread_number = 1 ;
> :history = "Mon Feb 22 11:45:59 2016: ncatted -O -a
> history,global,d,, st_20101226_1405.nc" ;
> }
>
> ## File #2:
>
> netcdf st_20101226_1410 {
> dimensions:
> time = 1 ;
> lat = 801 ;
> lon = 801 ;
> variables:
> int time ;
> time:long_name = "time" ;
> time:units = "seconds since 1970-1-1" ;
> float dbz(time, lat, lon) ;
> dbz:long_name = "dbz" ;
> dbz:units = "dbz" ;
> dbz:level = "1kmAGL" ;
> dbz:_FillValue = -9999.f ;
> dbz:init_time = "20101226_1405" ;
> dbz:valid_time = "20101226_1410" ;
> dbz:init_time_ut = 1293372300 ;
> dbz:valid_time_ut = 1293372600 ;
> dbz:accum_time_sec = 300 ;
> dbz:accum_time = "5" ;
> float lons(lat, lon) ;
> lons:long_name = "longitude" ;
> lons:units = "degrees_east" ;
> lons:standard_name = "longitude" ;
> lons:name = "longitude" ;
> lons:_FillValue = -9999.f ;
> float lats(lat, lon) ;
> lats:long_name = "latitude" ;
> lats:units = "degrees_north" ;
> lats:standard_name = "latitude" ;
> lats:name = "latitude" ;
> lats:_FillValue = -9999.f ;
>
> // global attributes:
> :MET_version = "v5.1" ;
> :nx = "801" ;
> :ny = "801 grid_points" ;
> :Projection = "Lambert Conformal" ;
> :scale_lat_1 = "30.000000" ;
> :scale_lat_2 = "60.000000" ;
> :lat_pin = "40.8521" ;
> :lon_pin = "-72.8817" ;
> :x_pin = "400" ;
> :y_pin = "400" ;
> :lon_orient = "-77.600000" ;
> :d_km = "2.0000" ;
> :r_km = "6371.200000" ;
> :nco_openmp_thread_number = 1 ;
> :history = "Mon Feb 22 11:46:05 2016: ncatted -O -a
> history,global,d,, st_20101226_1410.nc" ;
> }
>
> Finally, to be all-inclusive I am also providing how I am calling
MTD and
> the configure file.
>
> $ /met-5.1/bin/mtd -fcst st_*.nc -obs st_*.nc
> /met-5.1/data/config/MTDConfig_test -log mtd.log -v 4
>
>
>
>
////////////////////////////////////////////////////////////////////////////////
> //
> // MODE Time Domain configuration file.
> //
> // For additional information, see the MET_BASE/config/README file.
> //
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Output model name to be written
> //
>
> model = "WRF";
>
> //
> // Output observation type to be written
> //
>
> obtype = "OBS";
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Verification grid
> //
>
> regrid = {
> to_grid = NONE;
> vld_thresh = 0.5;
> method = NEAREST;
> width = 1;
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Approximate grid resolution (km)
> //
>
> grid_res = 2;
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Forecast and observation fields to be verified
> //
>
> fcst = {
> field = {
> name = "dbz";
> level = "(0,*,*)";
> }
>
> raw_thresh = >=28;
> conv_radius = 5; // 13.3/grid_res; // in grid squares
> conv_thresh = >=5.0;
> vld_thresh = 0.5;
> area_thresh = NA;
> inten_perc_value = 100;
> inten_perc_thresh = NA;
> merge_thresh = >=1.25;
> merge_flag = NONE;
> }
>
> obs = {
> field = {
> name = "dbz";
> level = "(0,*,*)";
> }
>
> raw_thresh = >=28;
> conv_radius = 1; // 13.3/grid_res; // in grid squares
> conv_thresh = >=15.0;
> vld_thresh = 0.75;
> area_thresh = NA;
> inten_perc_value = 100;
> inten_perc_thresh = NA;
> merge_thresh = >=1.25;
> merge_flag = NONE;
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Throw away 3D objects with volumes smaller than this
> //
>
> min_volume = 2000;
>
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Fuzzy engine weights
> //
>
> weight = {
>
> space_centroid_dist = 1.0;
>
> time_centroid_delta = 1.0;
>
> speed_delta = 1.0;
>
> direction_diff = 1.0;
>
> volume_ratio = 1.0;
>
> axis_angle_diff = 1.0;
>
> start_time_delta = 1.0;
>
> end_time_delta = 1.0;
>
> }
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Fuzzy engine interest functions
> //
>
> interest_function = {
>
> space_centroid_dist = (
>
> ( 0.0, 1.0 )
> ( 50.0, 0.5 )
> ( 100.0, 0.0 )
>
> );
>
> time_centroid_delta = (
>
> ( -3.0, 0.0 )
> ( -2.0, 0.5 )
> ( -1.0, 0.8 )
> ( 0.0, 1.0 )
> ( 1.0, 0.8 )
> ( 2.0, 0.5 )
> ( 3.0, 0.0 )
>
> );
>
> speed_delta = (
>
> ( -10.0, 0.0 )
> ( -5.0, 0.5 )
> ( 0.0, 1.0 )
> ( 5.0, 0.5 )
> ( 10.0, 0.0 )
>
> );
>
> direction_diff = (
>
> ( 0.0, 1.0 )
> ( 90.0, 0.0 )
> ( 180.0, 0.0 )
>
> );
>
> volume_ratio = (
>
> ( 0.0, 0.0 )
> ( 0.5, 0.5 )
> ( 1.0, 1.0 )
> ( 1.5, 0.5 )
> ( 2.0, 0.0 )
>
> );
>
> axis_angle_diff = (
>
> ( 0.0, 1.0 )
> ( 30.0, 1.0 )
> ( 90.0, 0.0 )
>
> );
>
> start_time_delta = (
>
> ( 0.0, 1.0 )
> ( 3.0, 0.5 )
> ( 5.0, 0.0 )
>
> );
>
> end_time_delta = (
>
> ( 0.0, 1.0 )
> ( 3.0, 0.5 )
> ( 5.0, 0.0 )
>
> );
>
> } // interest functions
>
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Total interest threshold for determining matches
> //
>
> total_interest_thresh = 0.7;
>
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
> //
> // Output flags
> //
>
> nc_output = {
>
> latlon = true;
> raw = true;
> object_id = true;
> cluster_id = true;
>
> }
>
> txt_output = {
>
> attributes_2d = true;
> attributes_3d = true;
>
> }
>
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
>
> output_prefix = "";
>
> version = "V5.1";
>
>
>
////////////////////////////////////////////////////////////////////////////////
>
>
> Thank you in advance for your help!
>
> Take care,
>
> Sara Ganetis
> PhD Candidate
> Stony Brook University
>
>
------------------------------------------------
Subject: MODE Time Dimension (MTD) troubleshooting
From: Sara Ganetis
Time: Mon Feb 22 11:15:23 2016
Hi John,
Thank you for your quick response! I removed the time dimension from
both
test files and MTD produced the same error as before.
The plot_data_plane tool ran successfully on the data both before
removing
the time dimension and after removing the time dimension.
I uploaded the two data files I'm testing (because MTD requires at
least
two files, right?). Let me know if you need any more information.
Thanks so much for your help!
Take care,
Sara Ganetis
On Mon, Feb 22, 2016 at 12:35 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi Sara,
>
> Thanks for sending all these great details, it really helps a lot.
MET
> supports a few different flavors of gridded NetCDF data, but I think
the
> issue here is that you're mixing two of them together. Your NetCDF
files
> look very, very similar to the output of the pcp_combine tool but
you're
> using a time dimension which is not used by pcp_combine. I suspect
that's
> causing the issue.
>
> Please try editing one of your NetCDF files by removing the time
dimension,
> like this:
>
> netcdf st_20101226_1410 {
> dimensions:
> lat = 801 ;
> lon = 801 ;
> variables:
> float dbz(lat, lon) ;
> dbz:long_name = "dbz" ;
> dbz:units = "dbz" ;
> dbz:level = "1kmAGL" ;
> dbz:_FillValue = -9999.f ;
> dbz:init_time = "20101226_1405" ;
> dbz:valid_time = "20101226_1410" ;
> dbz:init_time_ut = 1293372300 ;
> dbz:valid_time_ut = 1293372600 ;
> dbz:accum_time_sec = 300 ;
> dbz:accum_time = "5" ;
>
> Once you've removed that, try running the plot_data_plane tool.
That's a
> great way of easily testing to see if MET can read your gridded
data:
> met-5.1/bin/plot_data_plane /home/sara/MET/met-
5.1/stitched/20101226/cf/
> st_20101226_1405.nc plot_dbz.ps 'name="dbz"; level="(*,*)";'
>
> That will create a PostScript file which can be converted to png
like this:
> convert -rotate 90 -background white plot_dbz.ps plot_dbz.png
>
> If removing the "time" dimension and variable doesn't fix the
problem,
> please post a sample data file to our anonymous ftp site following
these
> instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On Mon, Feb 22, 2016 at 10:10 AM, Sara Ganetis via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Mon Feb 22 10:10:56 2016: Request 75202 was acted upon.
> > Transaction: Ticket created by sara.ganetis at stonybrook.edu
> > Queue: met_help
> > Subject: MODE Time Dimension (MTD) troubleshooting
> > Owner: Nobody
> > Requestors: sara.ganetis at stonybrook.edu
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202 >
> >
> >
> > Dear MET Help,
> >
> > I am trying to use the MODE Time Dimension tool on some data that
works
> > with the MODE tool in version 5.1. The NetCDF files are pre-
processed by
> me
> > to add in the global and variable attributes required for MODE to
work,
> > which it does. However, when running the MTD tool, I get the
following
> > output that concludes with an error:
> >
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Lambert Conformal Grid Data:
> > DEBUG 4: scale_lat_1 = 30
> > DEBUG 4: scale_lat_2 = 60
> > DEBUG 4: lat_pin = 40.8521
> > DEBUG 4: lon_pin = 72.8817
> > DEBUG 4: x_pin = 400
> > DEBUG 4: y_pin = 400
> > DEBUG 4: lon_orient = 77.6
> > DEBUG 4: d_km = 2
> > DEBUG 4: r_km = 6371.2
> > DEBUG 4: nx = 801
> > DEBUG 4: ny = 801
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Lambert Conformal Grid Data:
> > DEBUG 4: scale_lat_1 = 30
> > DEBUG 4: scale_lat_2 = 60
> > DEBUG 4: lat_pin = 40.8521
> > DEBUG 4: lon_pin = 72.8817
> > DEBUG 4: x_pin = 400
> > DEBUG 4: y_pin = 400
> > DEBUG 4: lon_orient = 77.6
> > DEBUG 4: d_km = 2
> > DEBUG 4: r_km = 6371.2
> > DEBUG 4: nx = 801
> > DEBUG 4: ny = 801
> > 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".
> > DEBUG 2: mtd_read_data() -> processing file
> > "/home/sara/MET/met-5.1/stitched/20101226/cf/st_20101226_1405.nc"
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_NcMet".
> > DEBUG 4: Lambert Conformal Grid Data:
> > DEBUG 4: scale_lat_1 = 30
> > DEBUG 4: scale_lat_2 = 60
> > DEBUG 4: lat_pin = 40.8521
> > DEBUG 4: lon_pin = 72.8817
> > DEBUG 4: x_pin = 400
> > DEBUG 4: y_pin = 400
> > DEBUG 4: lon_orient = 77.6
> > DEBUG 4: d_km = 2
> > DEBUG 4: r_km = 6371.2
> > DEBUG 4: nx = 801
> > DEBUG 4: ny = 801
> > ERROR :
> > ERROR :
> > ERROR : mtd_read_data() -> unable to get data plane at time 0
> > ERROR :
> >
> > Are there different global/variable attributes that
mtd_read_data() is
> > looking for within the file? I've been testing with just two files
at a
> > time for now. The data are 5-minute radar composite NetCDF files
and I've
> > been using them as both the forecast and analysis files at this
stage for
> > testing. Here's the header information for both of my files:
> >
> > ## File 1:
> >
> > netcdf st_20101226_1405 {
> > dimensions:
> > time = 1 ;
> > lat = 801 ;
> > lon = 801 ;
> > variables:
> > int time ;
> > time:long_name = "time" ;
> > time:units = "seconds since 1970-1-1" ;
> > float dbz(time, lat, lon) ;
> > dbz:long_name = "dbz" ;
> > dbz:units = "dbz" ;
> > dbz:level = "1kmAGL" ;
> > dbz:_FillValue = -9999.f ;
> > dbz:init_time = "20101226_1405" ;
> > dbz:valid_time = "20101226_1405" ;
> > dbz:init_time_ut = 1293372300 ;
> > dbz:valid_time_ut = 1293372300 ;
> > dbz:accum_time_sec = 300 ;
> > dbz:accum_time = "5" ;
> > float lons(lat, lon) ;
> > lons:long_name = "longitude" ;
> > lons:units = "degrees_east" ;
> > lons:standard_name = "longitude" ;
> > lons:name = "longitude" ;
> > lons:_FillValue = -9999.f ;
> > float lats(lat, lon) ;
> > lats:long_name = "latitude" ;
> > lats:units = "degrees_north" ;
> > lats:standard_name = "latitude" ;
> > lats:name = "latitude" ;
> > lats:_FillValue = -9999.f ;
> >
> > // global attributes:
> > :MET_version = "v5.1" ;
> > :nx = "801" ;
> > :ny = "801 grid_points" ;
> > :Projection = "Lambert Conformal" ;
> > :scale_lat_1 = "30.000000" ;
> > :scale_lat_2 = "60.000000" ;
> > :lat_pin = "40.8521" ;
> > :lon_pin = "-72.8817" ;
> > :x_pin = "400" ;
> > :y_pin = "400" ;
> > :lon_orient = "-77.600000" ;
> > :d_km = "2.0000" ;
> > :r_km = "6371.200000" ;
> > :nco_openmp_thread_number = 1 ;
> > :history = "Mon Feb 22 11:45:59 2016: ncatted -O -a
> > history,global,d,, st_20101226_1405.nc" ;
> > }
> >
> > ## File #2:
> >
> > netcdf st_20101226_1410 {
> > dimensions:
> > time = 1 ;
> > lat = 801 ;
> > lon = 801 ;
> > variables:
> > int time ;
> > time:long_name = "time" ;
> > time:units = "seconds since 1970-1-1" ;
> > float dbz(time, lat, lon) ;
> > dbz:long_name = "dbz" ;
> > dbz:units = "dbz" ;
> > dbz:level = "1kmAGL" ;
> > dbz:_FillValue = -9999.f ;
> > dbz:init_time = "20101226_1405" ;
> > dbz:valid_time = "20101226_1410" ;
> > dbz:init_time_ut = 1293372300 ;
> > dbz:valid_time_ut = 1293372600 ;
> > dbz:accum_time_sec = 300 ;
> > dbz:accum_time = "5" ;
> > float lons(lat, lon) ;
> > lons:long_name = "longitude" ;
> > lons:units = "degrees_east" ;
> > lons:standard_name = "longitude" ;
> > lons:name = "longitude" ;
> > lons:_FillValue = -9999.f ;
> > float lats(lat, lon) ;
> > lats:long_name = "latitude" ;
> > lats:units = "degrees_north" ;
> > lats:standard_name = "latitude" ;
> > lats:name = "latitude" ;
> > lats:_FillValue = -9999.f ;
> >
> > // global attributes:
> > :MET_version = "v5.1" ;
> > :nx = "801" ;
> > :ny = "801 grid_points" ;
> > :Projection = "Lambert Conformal" ;
> > :scale_lat_1 = "30.000000" ;
> > :scale_lat_2 = "60.000000" ;
> > :lat_pin = "40.8521" ;
> > :lon_pin = "-72.8817" ;
> > :x_pin = "400" ;
> > :y_pin = "400" ;
> > :lon_orient = "-77.600000" ;
> > :d_km = "2.0000" ;
> > :r_km = "6371.200000" ;
> > :nco_openmp_thread_number = 1 ;
> > :history = "Mon Feb 22 11:46:05 2016: ncatted -O -a
> > history,global,d,, st_20101226_1410.nc" ;
> > }
> >
> > Finally, to be all-inclusive I am also providing how I am calling
MTD and
> > the configure file.
> >
> > $ /met-5.1/bin/mtd -fcst st_*.nc -obs st_*.nc
> > /met-5.1/data/config/MTDConfig_test -log mtd.log -v 4
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > //
> > // MODE Time Domain configuration file.
> > //
> > // For additional information, see the MET_BASE/config/README
file.
> > //
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Output model name to be written
> > //
> >
> > model = "WRF";
> >
> > //
> > // Output observation type to be written
> > //
> >
> > obtype = "OBS";
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Verification grid
> > //
> >
> > regrid = {
> > to_grid = NONE;
> > vld_thresh = 0.5;
> > method = NEAREST;
> > width = 1;
> > }
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Approximate grid resolution (km)
> > //
> >
> > grid_res = 2;
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Forecast and observation fields to be verified
> > //
> >
> > fcst = {
> > field = {
> > name = "dbz";
> > level = "(0,*,*)";
> > }
> >
> > raw_thresh = >=28;
> > conv_radius = 5; // 13.3/grid_res; // in grid squares
> > conv_thresh = >=5.0;
> > vld_thresh = 0.5;
> > area_thresh = NA;
> > inten_perc_value = 100;
> > inten_perc_thresh = NA;
> > merge_thresh = >=1.25;
> > merge_flag = NONE;
> > }
> >
> > obs = {
> > field = {
> > name = "dbz";
> > level = "(0,*,*)";
> > }
> >
> > raw_thresh = >=28;
> > conv_radius = 1; // 13.3/grid_res; // in grid squares
> > conv_thresh = >=15.0;
> > vld_thresh = 0.75;
> > area_thresh = NA;
> > inten_perc_value = 100;
> > inten_perc_thresh = NA;
> > merge_thresh = >=1.25;
> > merge_flag = NONE;
> > }
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Throw away 3D objects with volumes smaller than this
> > //
> >
> > min_volume = 2000;
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Fuzzy engine weights
> > //
> >
> > weight = {
> >
> > space_centroid_dist = 1.0;
> >
> > time_centroid_delta = 1.0;
> >
> > speed_delta = 1.0;
> >
> > direction_diff = 1.0;
> >
> > volume_ratio = 1.0;
> >
> > axis_angle_diff = 1.0;
> >
> > start_time_delta = 1.0;
> >
> > end_time_delta = 1.0;
> >
> > }
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Fuzzy engine interest functions
> > //
> >
> > interest_function = {
> >
> > space_centroid_dist = (
> >
> > ( 0.0, 1.0 )
> > ( 50.0, 0.5 )
> > ( 100.0, 0.0 )
> >
> > );
> >
> > time_centroid_delta = (
> >
> > ( -3.0, 0.0 )
> > ( -2.0, 0.5 )
> > ( -1.0, 0.8 )
> > ( 0.0, 1.0 )
> > ( 1.0, 0.8 )
> > ( 2.0, 0.5 )
> > ( 3.0, 0.0 )
> >
> > );
> >
> > speed_delta = (
> >
> > ( -10.0, 0.0 )
> > ( -5.0, 0.5 )
> > ( 0.0, 1.0 )
> > ( 5.0, 0.5 )
> > ( 10.0, 0.0 )
> >
> > );
> >
> > direction_diff = (
> >
> > ( 0.0, 1.0 )
> > ( 90.0, 0.0 )
> > ( 180.0, 0.0 )
> >
> > );
> >
> > volume_ratio = (
> >
> > ( 0.0, 0.0 )
> > ( 0.5, 0.5 )
> > ( 1.0, 1.0 )
> > ( 1.5, 0.5 )
> > ( 2.0, 0.0 )
> >
> > );
> >
> > axis_angle_diff = (
> >
> > ( 0.0, 1.0 )
> > ( 30.0, 1.0 )
> > ( 90.0, 0.0 )
> >
> > );
> >
> > start_time_delta = (
> >
> > ( 0.0, 1.0 )
> > ( 3.0, 0.5 )
> > ( 5.0, 0.0 )
> >
> > );
> >
> > end_time_delta = (
> >
> > ( 0.0, 1.0 )
> > ( 3.0, 0.5 )
> > ( 5.0, 0.0 )
> >
> > );
> >
> > } // interest functions
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Total interest threshold for determining matches
> > //
> >
> > total_interest_thresh = 0.7;
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> > //
> > // Output flags
> > //
> >
> > nc_output = {
> >
> > latlon = true;
> > raw = true;
> > object_id = true;
> > cluster_id = true;
> >
> > }
> >
> > txt_output = {
> >
> > attributes_2d = true;
> > attributes_3d = true;
> >
> > }
> >
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> >
> > output_prefix = "";
> >
> > version = "V5.1";
> >
> >
> >
>
////////////////////////////////////////////////////////////////////////////////
> >
> >
> > Thank you in advance for your help!
> >
> > Take care,
> >
> > Sara Ganetis
> > PhD Candidate
> > Stony Brook University
> >
> >
>
>
------------------------------------------------
Subject: MODE Time Dimension (MTD) troubleshooting
From: John Halley Gotway
Time: Mon Feb 22 16:05:21 2016
Sara,
Thanks for sending the sample data. I used that, along with your
config
file, to run mtd like this:
met-5.1/bin/mtd -fcst st*.nc -obs st*.nc -config MTDConfig -outdir
out
-v 4 -log run_mtd.log
That resulted in this error:
ERROR : MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
->
needed 2 arguments for variable dbz, got 3
So I edited the config file like this:
fcst = {
field = {
name = "dbz";
level = "(*,*)";
}
...
obs = {
field = {
name = "dbz";
level = "(*,*)";
}
...
And rerunning produced good output. See attached log file.
Are you sure you're still getting the same error? I'll need to be
able to
replicate that behavior here before being able to debug it.
Any thoughts?
Also note that you can run mtd using the "-single" option instead of
the
"-fcst" and "-obs" options. That'll run MODE time domain on a single
input
data source and define objects without comparing them to another
field.
Thanks,
John
On Mon, Feb 22, 2016 at 11:15 AM, Sara Ganetis via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202 >
>
> Hi John,
>
> Thank you for your quick response! I removed the time dimension from
both
> test files and MTD produced the same error as before.
>
> The plot_data_plane tool ran successfully on the data both before
removing
> the time dimension and after removing the time dimension.
>
> I uploaded the two data files I'm testing (because MTD requires at
least
> two files, right?). Let me know if you need any more information.
>
> Thanks so much for your help!
>
> Take care,
> Sara Ganetis
>
> On Mon, Feb 22, 2016 at 12:35 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hi Sara,
> >
> > Thanks for sending all these great details, it really helps a lot.
MET
> > supports a few different flavors of gridded NetCDF data, but I
think the
> > issue here is that you're mixing two of them together. Your
NetCDF files
> > look very, very similar to the output of the pcp_combine tool but
you're
> > using a time dimension which is not used by pcp_combine. I
suspect
> that's
> > causing the issue.
> >
> > Please try editing one of your NetCDF files by removing the time
> dimension,
> > like this:
> >
> > netcdf st_20101226_1410 {
> > dimensions:
> > lat = 801 ;
> > lon = 801 ;
> > variables:
> > float dbz(lat, lon) ;
> > dbz:long_name = "dbz" ;
> > dbz:units = "dbz" ;
> > dbz:level = "1kmAGL" ;
> > dbz:_FillValue = -9999.f ;
> > dbz:init_time = "20101226_1405" ;
> > dbz:valid_time = "20101226_1410" ;
> > dbz:init_time_ut = 1293372300 ;
> > dbz:valid_time_ut = 1293372600 ;
> > dbz:accum_time_sec = 300 ;
> > dbz:accum_time = "5" ;
> >
> > Once you've removed that, try running the plot_data_plane tool.
That's a
> > great way of easily testing to see if MET can read your gridded
data:
> > met-5.1/bin/plot_data_plane
> /home/sara/MET/met-5.1/stitched/20101226/cf/
> > st_20101226_1405.nc plot_dbz.ps 'name="dbz"; level="(*,*)";'
> >
> > That will create a PostScript file which can be converted to png
like
> this:
> > convert -rotate 90 -background white plot_dbz.ps plot_dbz.png
> >
> > If removing the "time" dimension and variable doesn't fix the
problem,
> > please post a sample data file to our anonymous ftp site following
these
> > instructions:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > Thanks,
> > John Halley Gotway
> > met_help at ucar.edu
> >
> > On Mon, Feb 22, 2016 at 10:10 AM, Sara Ganetis via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> > >
> > > Mon Feb 22 10:10:56 2016: Request 75202 was acted upon.
> > > Transaction: Ticket created by sara.ganetis at stonybrook.edu
> > > Queue: met_help
> > > Subject: MODE Time Dimension (MTD) troubleshooting
> > > Owner: Nobody
> > > Requestors: sara.ganetis at stonybrook.edu
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202
> >
> > >
> > >
> > > Dear MET Help,
> > >
> > > I am trying to use the MODE Time Dimension tool on some data
that works
> > > with the MODE tool in version 5.1. The NetCDF files are pre-
processed
> by
> > me
> > > to add in the global and variable attributes required for MODE
to work,
> > > which it does. However, when running the MTD tool, I get the
following
> > > output that concludes with an error:
> > >
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Lambert Conformal Grid Data:
> > > DEBUG 4: scale_lat_1 = 30
> > > DEBUG 4: scale_lat_2 = 60
> > > DEBUG 4: lat_pin = 40.8521
> > > DEBUG 4: lon_pin = 72.8817
> > > DEBUG 4: x_pin = 400
> > > DEBUG 4: y_pin = 400
> > > DEBUG 4: lon_orient = 77.6
> > > DEBUG 4: d_km = 2
> > > DEBUG 4: r_km = 6371.2
> > > DEBUG 4: nx = 801
> > > DEBUG 4: ny = 801
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Lambert Conformal Grid Data:
> > > DEBUG 4: scale_lat_1 = 30
> > > DEBUG 4: scale_lat_2 = 60
> > > DEBUG 4: lat_pin = 40.8521
> > > DEBUG 4: lon_pin = 72.8817
> > > DEBUG 4: x_pin = 400
> > > DEBUG 4: y_pin = 400
> > > DEBUG 4: lon_orient = 77.6
> > > DEBUG 4: d_km = 2
> > > DEBUG 4: r_km = 6371.2
> > > DEBUG 4: nx = 801
> > > DEBUG 4: ny = 801
> > > 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".
> > > DEBUG 2: mtd_read_data() -> processing file
> > > "/home/sara/MET/met-
5.1/stitched/20101226/cf/st_20101226_1405.nc"
> > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > > Met2dDataFile object of type "FileType_NcMet".
> > > DEBUG 4: Lambert Conformal Grid Data:
> > > DEBUG 4: scale_lat_1 = 30
> > > DEBUG 4: scale_lat_2 = 60
> > > DEBUG 4: lat_pin = 40.8521
> > > DEBUG 4: lon_pin = 72.8817
> > > DEBUG 4: x_pin = 400
> > > DEBUG 4: y_pin = 400
> > > DEBUG 4: lon_orient = 77.6
> > > DEBUG 4: d_km = 2
> > > DEBUG 4: r_km = 6371.2
> > > DEBUG 4: nx = 801
> > > DEBUG 4: ny = 801
> > > ERROR :
> > > ERROR :
> > > ERROR : mtd_read_data() -> unable to get data plane at time 0
> > > ERROR :
> > >
> > > Are there different global/variable attributes that
mtd_read_data() is
> > > looking for within the file? I've been testing with just two
files at a
> > > time for now. The data are 5-minute radar composite NetCDF files
and
> I've
> > > been using them as both the forecast and analysis files at this
stage
> for
> > > testing. Here's the header information for both of my files:
> > >
> > > ## File 1:
> > >
> > > netcdf st_20101226_1405 {
> > > dimensions:
> > > time = 1 ;
> > > lat = 801 ;
> > > lon = 801 ;
> > > variables:
> > > int time ;
> > > time:long_name = "time" ;
> > > time:units = "seconds since 1970-1-1" ;
> > > float dbz(time, lat, lon) ;
> > > dbz:long_name = "dbz" ;
> > > dbz:units = "dbz" ;
> > > dbz:level = "1kmAGL" ;
> > > dbz:_FillValue = -9999.f ;
> > > dbz:init_time = "20101226_1405" ;
> > > dbz:valid_time = "20101226_1405" ;
> > > dbz:init_time_ut = 1293372300 ;
> > > dbz:valid_time_ut = 1293372300 ;
> > > dbz:accum_time_sec = 300 ;
> > > dbz:accum_time = "5" ;
> > > float lons(lat, lon) ;
> > > lons:long_name = "longitude" ;
> > > lons:units = "degrees_east" ;
> > > lons:standard_name = "longitude" ;
> > > lons:name = "longitude" ;
> > > lons:_FillValue = -9999.f ;
> > > float lats(lat, lon) ;
> > > lats:long_name = "latitude" ;
> > > lats:units = "degrees_north" ;
> > > lats:standard_name = "latitude" ;
> > > lats:name = "latitude" ;
> > > lats:_FillValue = -9999.f ;
> > >
> > > // global attributes:
> > > :MET_version = "v5.1" ;
> > > :nx = "801" ;
> > > :ny = "801 grid_points" ;
> > > :Projection = "Lambert Conformal" ;
> > > :scale_lat_1 = "30.000000" ;
> > > :scale_lat_2 = "60.000000" ;
> > > :lat_pin = "40.8521" ;
> > > :lon_pin = "-72.8817" ;
> > > :x_pin = "400" ;
> > > :y_pin = "400" ;
> > > :lon_orient = "-77.600000" ;
> > > :d_km = "2.0000" ;
> > > :r_km = "6371.200000" ;
> > > :nco_openmp_thread_number = 1 ;
> > > :history = "Mon Feb 22 11:45:59 2016: ncatted -O -a
> > > history,global,d,, st_20101226_1405.nc" ;
> > > }
> > >
> > > ## File #2:
> > >
> > > netcdf st_20101226_1410 {
> > > dimensions:
> > > time = 1 ;
> > > lat = 801 ;
> > > lon = 801 ;
> > > variables:
> > > int time ;
> > > time:long_name = "time" ;
> > > time:units = "seconds since 1970-1-1" ;
> > > float dbz(time, lat, lon) ;
> > > dbz:long_name = "dbz" ;
> > > dbz:units = "dbz" ;
> > > dbz:level = "1kmAGL" ;
> > > dbz:_FillValue = -9999.f ;
> > > dbz:init_time = "20101226_1405" ;
> > > dbz:valid_time = "20101226_1410" ;
> > > dbz:init_time_ut = 1293372300 ;
> > > dbz:valid_time_ut = 1293372600 ;
> > > dbz:accum_time_sec = 300 ;
> > > dbz:accum_time = "5" ;
> > > float lons(lat, lon) ;
> > > lons:long_name = "longitude" ;
> > > lons:units = "degrees_east" ;
> > > lons:standard_name = "longitude" ;
> > > lons:name = "longitude" ;
> > > lons:_FillValue = -9999.f ;
> > > float lats(lat, lon) ;
> > > lats:long_name = "latitude" ;
> > > lats:units = "degrees_north" ;
> > > lats:standard_name = "latitude" ;
> > > lats:name = "latitude" ;
> > > lats:_FillValue = -9999.f ;
> > >
> > > // global attributes:
> > > :MET_version = "v5.1" ;
> > > :nx = "801" ;
> > > :ny = "801 grid_points" ;
> > > :Projection = "Lambert Conformal" ;
> > > :scale_lat_1 = "30.000000" ;
> > > :scale_lat_2 = "60.000000" ;
> > > :lat_pin = "40.8521" ;
> > > :lon_pin = "-72.8817" ;
> > > :x_pin = "400" ;
> > > :y_pin = "400" ;
> > > :lon_orient = "-77.600000" ;
> > > :d_km = "2.0000" ;
> > > :r_km = "6371.200000" ;
> > > :nco_openmp_thread_number = 1 ;
> > > :history = "Mon Feb 22 11:46:05 2016: ncatted -O -a
> > > history,global,d,, st_20101226_1410.nc" ;
> > > }
> > >
> > > Finally, to be all-inclusive I am also providing how I am
calling MTD
> and
> > > the configure file.
> > >
> > > $ /met-5.1/bin/mtd -fcst st_*.nc -obs st_*.nc
> > > /met-5.1/data/config/MTDConfig_test -log mtd.log -v 4
> > >
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > //
> > > // MODE Time Domain configuration file.
> > > //
> > > // For additional information, see the MET_BASE/config/README
file.
> > > //
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Output model name to be written
> > > //
> > >
> > > model = "WRF";
> > >
> > > //
> > > // Output observation type to be written
> > > //
> > >
> > > obtype = "OBS";
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Verification grid
> > > //
> > >
> > > regrid = {
> > > to_grid = NONE;
> > > vld_thresh = 0.5;
> > > method = NEAREST;
> > > width = 1;
> > > }
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Approximate grid resolution (km)
> > > //
> > >
> > > grid_res = 2;
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Forecast and observation fields to be verified
> > > //
> > >
> > > fcst = {
> > > field = {
> > > name = "dbz";
> > > level = "(0,*,*)";
> > > }
> > >
> > > raw_thresh = >=28;
> > > conv_radius = 5; // 13.3/grid_res; // in grid squares
> > > conv_thresh = >=5.0;
> > > vld_thresh = 0.5;
> > > area_thresh = NA;
> > > inten_perc_value = 100;
> > > inten_perc_thresh = NA;
> > > merge_thresh = >=1.25;
> > > merge_flag = NONE;
> > > }
> > >
> > > obs = {
> > > field = {
> > > name = "dbz";
> > > level = "(0,*,*)";
> > > }
> > >
> > > raw_thresh = >=28;
> > > conv_radius = 1; // 13.3/grid_res; // in grid squares
> > > conv_thresh = >=15.0;
> > > vld_thresh = 0.75;
> > > area_thresh = NA;
> > > inten_perc_value = 100;
> > > inten_perc_thresh = NA;
> > > merge_thresh = >=1.25;
> > > merge_flag = NONE;
> > > }
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Throw away 3D objects with volumes smaller than this
> > > //
> > >
> > > min_volume = 2000;
> > >
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Fuzzy engine weights
> > > //
> > >
> > > weight = {
> > >
> > > space_centroid_dist = 1.0;
> > >
> > > time_centroid_delta = 1.0;
> > >
> > > speed_delta = 1.0;
> > >
> > > direction_diff = 1.0;
> > >
> > > volume_ratio = 1.0;
> > >
> > > axis_angle_diff = 1.0;
> > >
> > > start_time_delta = 1.0;
> > >
> > > end_time_delta = 1.0;
> > >
> > > }
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Fuzzy engine interest functions
> > > //
> > >
> > > interest_function = {
> > >
> > > space_centroid_dist = (
> > >
> > > ( 0.0, 1.0 )
> > > ( 50.0, 0.5 )
> > > ( 100.0, 0.0 )
> > >
> > > );
> > >
> > > time_centroid_delta = (
> > >
> > > ( -3.0, 0.0 )
> > > ( -2.0, 0.5 )
> > > ( -1.0, 0.8 )
> > > ( 0.0, 1.0 )
> > > ( 1.0, 0.8 )
> > > ( 2.0, 0.5 )
> > > ( 3.0, 0.0 )
> > >
> > > );
> > >
> > > speed_delta = (
> > >
> > > ( -10.0, 0.0 )
> > > ( -5.0, 0.5 )
> > > ( 0.0, 1.0 )
> > > ( 5.0, 0.5 )
> > > ( 10.0, 0.0 )
> > >
> > > );
> > >
> > > direction_diff = (
> > >
> > > ( 0.0, 1.0 )
> > > ( 90.0, 0.0 )
> > > ( 180.0, 0.0 )
> > >
> > > );
> > >
> > > volume_ratio = (
> > >
> > > ( 0.0, 0.0 )
> > > ( 0.5, 0.5 )
> > > ( 1.0, 1.0 )
> > > ( 1.5, 0.5 )
> > > ( 2.0, 0.0 )
> > >
> > > );
> > >
> > > axis_angle_diff = (
> > >
> > > ( 0.0, 1.0 )
> > > ( 30.0, 1.0 )
> > > ( 90.0, 0.0 )
> > >
> > > );
> > >
> > > start_time_delta = (
> > >
> > > ( 0.0, 1.0 )
> > > ( 3.0, 0.5 )
> > > ( 5.0, 0.0 )
> > >
> > > );
> > >
> > > end_time_delta = (
> > >
> > > ( 0.0, 1.0 )
> > > ( 3.0, 0.5 )
> > > ( 5.0, 0.0 )
> > >
> > > );
> > >
> > > } // interest functions
> > >
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Total interest threshold for determining matches
> > > //
> > >
> > > total_interest_thresh = 0.7;
> > >
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > > //
> > > // Output flags
> > > //
> > >
> > > nc_output = {
> > >
> > > latlon = true;
> > > raw = true;
> > > object_id = true;
> > > cluster_id = true;
> > >
> > > }
> > >
> > > txt_output = {
> > >
> > > attributes_2d = true;
> > > attributes_3d = true;
> > >
> > > }
> > >
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > >
> > > output_prefix = "";
> > >
> > > version = "V5.1";
> > >
> > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > >
> > >
> > > Thank you in advance for your help!
> > >
> > > Take care,
> > >
> > > Sara Ganetis
> > > PhD Candidate
> > > Stony Brook University
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE Time Dimension (MTD) troubleshooting
From: Sara Ganetis
Time: Mon Feb 22 16:20:23 2016
Hi John,
Well, this is embarrassing-- I had forgotten the "-config" argument
before
specifying the configure file when calling mtd. I only just noticed it
when
I entered everything as you had provided on the command line. I had
been
using a script that must had lost the "-config" at some point and I
failed
to notice that. I, like Garfield, blame Mondays.
MTD works great with no error messages now so I'll go ahead and remove
the
time dimension from the rest of the files. Thanks for all of your help
and
quick replies!
Take care,
Sara Ganetis
On Mon, Feb 22, 2016 at 6:05 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Sara,
>
> Thanks for sending the sample data. I used that, along with your
config
> file, to run mtd like this:
> met-5.1/bin/mtd -fcst st*.nc -obs st*.nc -config MTDConfig
-outdir out
> -v 4 -log run_mtd.log
>
> That resulted in this error:
> ERROR : MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
->
> needed 2 arguments for variable dbz, got 3
>
> So I edited the config file like this:
>
> fcst = {
> field = {
> name = "dbz";
> level = "(*,*)";
> }
> ...
> obs = {
> field = {
> name = "dbz";
> level = "(*,*)";
> }
> ...
>
> And rerunning produced good output. See attached log file.
>
> Are you sure you're still getting the same error? I'll need to be
able to
> replicate that behavior here before being able to debug it.
>
> Any thoughts?
>
> Also note that you can run mtd using the "-single" option instead of
the
> "-fcst" and "-obs" options. That'll run MODE time domain on a
single input
> data source and define objects without comparing them to another
field.
>
> Thanks,
> John
>
> On Mon, Feb 22, 2016 at 11:15 AM, Sara Ganetis via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202 >
> >
> > Hi John,
> >
> > Thank you for your quick response! I removed the time dimension
from both
> > test files and MTD produced the same error as before.
> >
> > The plot_data_plane tool ran successfully on the data both before
> removing
> > the time dimension and after removing the time dimension.
> >
> > I uploaded the two data files I'm testing (because MTD requires at
least
> > two files, right?). Let me know if you need any more information.
> >
> > Thanks so much for your help!
> >
> > Take care,
> > Sara Ganetis
> >
> > On Mon, Feb 22, 2016 at 12:35 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Hi Sara,
> > >
> > > Thanks for sending all these great details, it really helps a
lot. MET
> > > supports a few different flavors of gridded NetCDF data, but I
think
> the
> > > issue here is that you're mixing two of them together. Your
NetCDF
> files
> > > look very, very similar to the output of the pcp_combine tool
but
> you're
> > > using a time dimension which is not used by pcp_combine. I
suspect
> > that's
> > > causing the issue.
> > >
> > > Please try editing one of your NetCDF files by removing the time
> > dimension,
> > > like this:
> > >
> > > netcdf st_20101226_1410 {
> > > dimensions:
> > > lat = 801 ;
> > > lon = 801 ;
> > > variables:
> > > float dbz(lat, lon) ;
> > > dbz:long_name = "dbz" ;
> > > dbz:units = "dbz" ;
> > > dbz:level = "1kmAGL" ;
> > > dbz:_FillValue = -9999.f ;
> > > dbz:init_time = "20101226_1405" ;
> > > dbz:valid_time = "20101226_1410" ;
> > > dbz:init_time_ut = 1293372300 ;
> > > dbz:valid_time_ut = 1293372600 ;
> > > dbz:accum_time_sec = 300 ;
> > > dbz:accum_time = "5" ;
> > >
> > > Once you've removed that, try running the plot_data_plane tool.
> That's a
> > > great way of easily testing to see if MET can read your gridded
data:
> > > met-5.1/bin/plot_data_plane
> > /home/sara/MET/met-5.1/stitched/20101226/cf/
> > > st_20101226_1405.nc plot_dbz.ps 'name="dbz"; level="(*,*)";'
> > >
> > > That will create a PostScript file which can be converted to png
like
> > this:
> > > convert -rotate 90 -background white plot_dbz.ps plot_dbz.png
> > >
> > > If removing the "time" dimension and variable doesn't fix the
problem,
> > > please post a sample data file to our anonymous ftp site
following
> these
> > > instructions:
> > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >
> > > Thanks,
> > > John Halley Gotway
> > > met_help at ucar.edu
> > >
> > > On Mon, Feb 22, 2016 at 10:10 AM, Sara Ganetis via RT <
> met_help at ucar.edu
> > >
> > > wrote:
> > >
> > > >
> > > > Mon Feb 22 10:10:56 2016: Request 75202 was acted upon.
> > > > Transaction: Ticket created by sara.ganetis at stonybrook.edu
> > > > Queue: met_help
> > > > Subject: MODE Time Dimension (MTD) troubleshooting
> > > > Owner: Nobody
> > > > Requestors: sara.ganetis at stonybrook.edu
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202
> > >
> > > >
> > > >
> > > > Dear MET Help,
> > > >
> > > > I am trying to use the MODE Time Dimension tool on some data
that
> works
> > > > with the MODE tool in version 5.1. The NetCDF files are pre-
processed
> > by
> > > me
> > > > to add in the global and variable attributes required for MODE
to
> work,
> > > > which it does. However, when running the MTD tool, I get the
> following
> > > > output that concludes with an error:
> > > >
> > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> > > > Met2dDataFile object of type "FileType_NcMet".
> > > > DEBUG 4: Lambert Conformal Grid Data:
> > > > DEBUG 4: scale_lat_1 = 30
> > > > DEBUG 4: scale_lat_2 = 60
> > > > DEBUG 4: lat_pin = 40.8521
> > > > DEBUG 4: lon_pin = 72.8817
> > > > DEBUG 4: x_pin = 400
> > > > DEBUG 4: y_pin = 400
> > > > DEBUG 4: lon_orient = 77.6
> > > > DEBUG 4: d_km = 2
> > > > DEBUG 4: r_km = 6371.2
> > > > DEBUG 4: nx = 801
> > > > DEBUG 4: ny = 801
> > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> > > > Met2dDataFile object of type "FileType_NcMet".
> > > > DEBUG 4: Lambert Conformal Grid Data:
> > > > DEBUG 4: scale_lat_1 = 30
> > > > DEBUG 4: scale_lat_2 = 60
> > > > DEBUG 4: lat_pin = 40.8521
> > > > DEBUG 4: lon_pin = 72.8817
> > > > DEBUG 4: x_pin = 400
> > > > DEBUG 4: y_pin = 400
> > > > DEBUG 4: lon_orient = 77.6
> > > > DEBUG 4: d_km = 2
> > > > DEBUG 4: r_km = 6371.2
> > > > DEBUG 4: nx = 801
> > > > DEBUG 4: ny = 801
> > > > 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".
> > > > DEBUG 2: mtd_read_data() -> processing file
> > > > "/home/sara/MET/met-
5.1/stitched/20101226/cf/st_20101226_1405.nc"
> > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> > > > Met2dDataFile object of type "FileType_NcMet".
> > > > DEBUG 4: Lambert Conformal Grid Data:
> > > > DEBUG 4: scale_lat_1 = 30
> > > > DEBUG 4: scale_lat_2 = 60
> > > > DEBUG 4: lat_pin = 40.8521
> > > > DEBUG 4: lon_pin = 72.8817
> > > > DEBUG 4: x_pin = 400
> > > > DEBUG 4: y_pin = 400
> > > > DEBUG 4: lon_orient = 77.6
> > > > DEBUG 4: d_km = 2
> > > > DEBUG 4: r_km = 6371.2
> > > > DEBUG 4: nx = 801
> > > > DEBUG 4: ny = 801
> > > > ERROR :
> > > > ERROR :
> > > > ERROR : mtd_read_data() -> unable to get data plane at time
0
> > > > ERROR :
> > > >
> > > > Are there different global/variable attributes that
mtd_read_data()
> is
> > > > looking for within the file? I've been testing with just two
files
> at a
> > > > time for now. The data are 5-minute radar composite NetCDF
files and
> > I've
> > > > been using them as both the forecast and analysis files at
this stage
> > for
> > > > testing. Here's the header information for both of my files:
> > > >
> > > > ## File 1:
> > > >
> > > > netcdf st_20101226_1405 {
> > > > dimensions:
> > > > time = 1 ;
> > > > lat = 801 ;
> > > > lon = 801 ;
> > > > variables:
> > > > int time ;
> > > > time:long_name = "time" ;
> > > > time:units = "seconds since 1970-1-1" ;
> > > > float dbz(time, lat, lon) ;
> > > > dbz:long_name = "dbz" ;
> > > > dbz:units = "dbz" ;
> > > > dbz:level = "1kmAGL" ;
> > > > dbz:_FillValue = -9999.f ;
> > > > dbz:init_time = "20101226_1405" ;
> > > > dbz:valid_time = "20101226_1405" ;
> > > > dbz:init_time_ut = 1293372300 ;
> > > > dbz:valid_time_ut = 1293372300 ;
> > > > dbz:accum_time_sec = 300 ;
> > > > dbz:accum_time = "5" ;
> > > > float lons(lat, lon) ;
> > > > lons:long_name = "longitude" ;
> > > > lons:units = "degrees_east" ;
> > > > lons:standard_name = "longitude" ;
> > > > lons:name = "longitude" ;
> > > > lons:_FillValue = -9999.f ;
> > > > float lats(lat, lon) ;
> > > > lats:long_name = "latitude" ;
> > > > lats:units = "degrees_north" ;
> > > > lats:standard_name = "latitude" ;
> > > > lats:name = "latitude" ;
> > > > lats:_FillValue = -9999.f ;
> > > >
> > > > // global attributes:
> > > > :MET_version = "v5.1" ;
> > > > :nx = "801" ;
> > > > :ny = "801 grid_points" ;
> > > > :Projection = "Lambert Conformal" ;
> > > > :scale_lat_1 = "30.000000" ;
> > > > :scale_lat_2 = "60.000000" ;
> > > > :lat_pin = "40.8521" ;
> > > > :lon_pin = "-72.8817" ;
> > > > :x_pin = "400" ;
> > > > :y_pin = "400" ;
> > > > :lon_orient = "-77.600000" ;
> > > > :d_km = "2.0000" ;
> > > > :r_km = "6371.200000" ;
> > > > :nco_openmp_thread_number = 1 ;
> > > > :history = "Mon Feb 22 11:45:59 2016: ncatted -O -a
> > > > history,global,d,, st_20101226_1405.nc" ;
> > > > }
> > > >
> > > > ## File #2:
> > > >
> > > > netcdf st_20101226_1410 {
> > > > dimensions:
> > > > time = 1 ;
> > > > lat = 801 ;
> > > > lon = 801 ;
> > > > variables:
> > > > int time ;
> > > > time:long_name = "time" ;
> > > > time:units = "seconds since 1970-1-1" ;
> > > > float dbz(time, lat, lon) ;
> > > > dbz:long_name = "dbz" ;
> > > > dbz:units = "dbz" ;
> > > > dbz:level = "1kmAGL" ;
> > > > dbz:_FillValue = -9999.f ;
> > > > dbz:init_time = "20101226_1405" ;
> > > > dbz:valid_time = "20101226_1410" ;
> > > > dbz:init_time_ut = 1293372300 ;
> > > > dbz:valid_time_ut = 1293372600 ;
> > > > dbz:accum_time_sec = 300 ;
> > > > dbz:accum_time = "5" ;
> > > > float lons(lat, lon) ;
> > > > lons:long_name = "longitude" ;
> > > > lons:units = "degrees_east" ;
> > > > lons:standard_name = "longitude" ;
> > > > lons:name = "longitude" ;
> > > > lons:_FillValue = -9999.f ;
> > > > float lats(lat, lon) ;
> > > > lats:long_name = "latitude" ;
> > > > lats:units = "degrees_north" ;
> > > > lats:standard_name = "latitude" ;
> > > > lats:name = "latitude" ;
> > > > lats:_FillValue = -9999.f ;
> > > >
> > > > // global attributes:
> > > > :MET_version = "v5.1" ;
> > > > :nx = "801" ;
> > > > :ny = "801 grid_points" ;
> > > > :Projection = "Lambert Conformal" ;
> > > > :scale_lat_1 = "30.000000" ;
> > > > :scale_lat_2 = "60.000000" ;
> > > > :lat_pin = "40.8521" ;
> > > > :lon_pin = "-72.8817" ;
> > > > :x_pin = "400" ;
> > > > :y_pin = "400" ;
> > > > :lon_orient = "-77.600000" ;
> > > > :d_km = "2.0000" ;
> > > > :r_km = "6371.200000" ;
> > > > :nco_openmp_thread_number = 1 ;
> > > > :history = "Mon Feb 22 11:46:05 2016: ncatted -O -a
> > > > history,global,d,, st_20101226_1410.nc" ;
> > > > }
> > > >
> > > > Finally, to be all-inclusive I am also providing how I am
calling MTD
> > and
> > > > the configure file.
> > > >
> > > > $ /met-5.1/bin/mtd -fcst st_*.nc -obs st_*.nc
> > > > /met-5.1/data/config/MTDConfig_test -log mtd.log -v 4
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > //
> > > > // MODE Time Domain configuration file.
> > > > //
> > > > // For additional information, see the MET_BASE/config/README
file.
> > > > //
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Output model name to be written
> > > > //
> > > >
> > > > model = "WRF";
> > > >
> > > > //
> > > > // Output observation type to be written
> > > > //
> > > >
> > > > obtype = "OBS";
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Verification grid
> > > > //
> > > >
> > > > regrid = {
> > > > to_grid = NONE;
> > > > vld_thresh = 0.5;
> > > > method = NEAREST;
> > > > width = 1;
> > > > }
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Approximate grid resolution (km)
> > > > //
> > > >
> > > > grid_res = 2;
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Forecast and observation fields to be verified
> > > > //
> > > >
> > > > fcst = {
> > > > field = {
> > > > name = "dbz";
> > > > level = "(0,*,*)";
> > > > }
> > > >
> > > > raw_thresh = >=28;
> > > > conv_radius = 5; // 13.3/grid_res; // in grid squares
> > > > conv_thresh = >=5.0;
> > > > vld_thresh = 0.5;
> > > > area_thresh = NA;
> > > > inten_perc_value = 100;
> > > > inten_perc_thresh = NA;
> > > > merge_thresh = >=1.25;
> > > > merge_flag = NONE;
> > > > }
> > > >
> > > > obs = {
> > > > field = {
> > > > name = "dbz";
> > > > level = "(0,*,*)";
> > > > }
> > > >
> > > > raw_thresh = >=28;
> > > > conv_radius = 1; // 13.3/grid_res; // in grid squares
> > > > conv_thresh = >=15.0;
> > > > vld_thresh = 0.75;
> > > > area_thresh = NA;
> > > > inten_perc_value = 100;
> > > > inten_perc_thresh = NA;
> > > > merge_thresh = >=1.25;
> > > > merge_flag = NONE;
> > > > }
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Throw away 3D objects with volumes smaller than this
> > > > //
> > > >
> > > > min_volume = 2000;
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Fuzzy engine weights
> > > > //
> > > >
> > > > weight = {
> > > >
> > > > space_centroid_dist = 1.0;
> > > >
> > > > time_centroid_delta = 1.0;
> > > >
> > > > speed_delta = 1.0;
> > > >
> > > > direction_diff = 1.0;
> > > >
> > > > volume_ratio = 1.0;
> > > >
> > > > axis_angle_diff = 1.0;
> > > >
> > > > start_time_delta = 1.0;
> > > >
> > > > end_time_delta = 1.0;
> > > >
> > > > }
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Fuzzy engine interest functions
> > > > //
> > > >
> > > > interest_function = {
> > > >
> > > > space_centroid_dist = (
> > > >
> > > > ( 0.0, 1.0 )
> > > > ( 50.0, 0.5 )
> > > > ( 100.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > time_centroid_delta = (
> > > >
> > > > ( -3.0, 0.0 )
> > > > ( -2.0, 0.5 )
> > > > ( -1.0, 0.8 )
> > > > ( 0.0, 1.0 )
> > > > ( 1.0, 0.8 )
> > > > ( 2.0, 0.5 )
> > > > ( 3.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > speed_delta = (
> > > >
> > > > ( -10.0, 0.0 )
> > > > ( -5.0, 0.5 )
> > > > ( 0.0, 1.0 )
> > > > ( 5.0, 0.5 )
> > > > ( 10.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > direction_diff = (
> > > >
> > > > ( 0.0, 1.0 )
> > > > ( 90.0, 0.0 )
> > > > ( 180.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > volume_ratio = (
> > > >
> > > > ( 0.0, 0.0 )
> > > > ( 0.5, 0.5 )
> > > > ( 1.0, 1.0 )
> > > > ( 1.5, 0.5 )
> > > > ( 2.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > axis_angle_diff = (
> > > >
> > > > ( 0.0, 1.0 )
> > > > ( 30.0, 1.0 )
> > > > ( 90.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > start_time_delta = (
> > > >
> > > > ( 0.0, 1.0 )
> > > > ( 3.0, 0.5 )
> > > > ( 5.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > end_time_delta = (
> > > >
> > > > ( 0.0, 1.0 )
> > > > ( 3.0, 0.5 )
> > > > ( 5.0, 0.0 )
> > > >
> > > > );
> > > >
> > > > } // interest functions
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Total interest threshold for determining matches
> > > > //
> > > >
> > > > total_interest_thresh = 0.7;
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > > //
> > > > // Output flags
> > > > //
> > > >
> > > > nc_output = {
> > > >
> > > > latlon = true;
> > > > raw = true;
> > > > object_id = true;
> > > > cluster_id = true;
> > > >
> > > > }
> > > >
> > > > txt_output = {
> > > >
> > > > attributes_2d = true;
> > > > attributes_3d = true;
> > > >
> > > > }
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > >
> > > > output_prefix = "";
> > > >
> > > > version = "V5.1";
> > > >
> > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > >
> > > >
> > > > Thank you in advance for your help!
> > > >
> > > > Take care,
> > > >
> > > > Sara Ganetis
> > > > PhD Candidate
> > > > Stony Brook University
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE Time Dimension (MTD) troubleshooting
From: John Halley Gotway
Time: Tue Feb 23 10:46:51 2016
Sara,
That's great. I'm glad you were able to figure it out! I missed that
detail in the output you sent.
Since the "-config" option is required, I updated the development
version
of the code to make sure that it's set. If this happens in future
versions, you'll see the following error instead:
ERROR :
ERROR : mtd: must specify a configuration file using the "-config"
command line option.
ERROR
That's what happens with new code... it takes a while to shake out the
details and make it more user friendly.
Please let us know if you run across other things that are confusing
or not
very user friendly.
I'll go ahead and resolve this ticket now.
Thanks,
John
On Mon, Feb 22, 2016 at 4:20 PM, Sara Ganetis via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202 >
>
> Hi John,
>
> Well, this is embarrassing-- I had forgotten the "-config" argument
before
> specifying the configure file when calling mtd. I only just noticed
it when
> I entered everything as you had provided on the command line. I had
been
> using a script that must had lost the "-config" at some point and I
failed
> to notice that. I, like Garfield, blame Mondays.
>
> MTD works great with no error messages now so I'll go ahead and
remove the
> time dimension from the rest of the files. Thanks for all of your
help and
> quick replies!
>
> Take care,
> Sara Ganetis
>
> On Mon, Feb 22, 2016 at 6:05 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Sara,
> >
> > Thanks for sending the sample data. I used that, along with your
config
> > file, to run mtd like this:
> > met-5.1/bin/mtd -fcst st*.nc -obs st*.nc -config MTDConfig
-outdir out
> > -v 4 -log run_mtd.log
> >
> > That resulted in this error:
> > ERROR : MetNcFile::data(NcVar *, const LongArray &, DataPlane
&) ->
> > needed 2 arguments for variable dbz, got 3
> >
> > So I edited the config file like this:
> >
> > fcst = {
> > field = {
> > name = "dbz";
> > level = "(*,*)";
> > }
> > ...
> > obs = {
> > field = {
> > name = "dbz";
> > level = "(*,*)";
> > }
> > ...
> >
> > And rerunning produced good output. See attached log file.
> >
> > Are you sure you're still getting the same error? I'll need to be
able
> to
> > replicate that behavior here before being able to debug it.
> >
> > Any thoughts?
> >
> > Also note that you can run mtd using the "-single" option instead
of the
> > "-fcst" and "-obs" options. That'll run MODE time domain on a
single
> input
> > data source and define objects without comparing them to another
field.
> >
> > Thanks,
> > John
> >
> > On Mon, Feb 22, 2016 at 11:15 AM, Sara Ganetis via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202 >
> > >
> > > Hi John,
> > >
> > > Thank you for your quick response! I removed the time dimension
from
> both
> > > test files and MTD produced the same error as before.
> > >
> > > The plot_data_plane tool ran successfully on the data both
before
> > removing
> > > the time dimension and after removing the time dimension.
> > >
> > > I uploaded the two data files I'm testing (because MTD requires
at
> least
> > > two files, right?). Let me know if you need any more
information.
> > >
> > > Thanks so much for your help!
> > >
> > > Take care,
> > > Sara Ganetis
> > >
> > > On Mon, Feb 22, 2016 at 12:35 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Hi Sara,
> > > >
> > > > Thanks for sending all these great details, it really helps a
lot.
> MET
> > > > supports a few different flavors of gridded NetCDF data, but I
think
> > the
> > > > issue here is that you're mixing two of them together. Your
NetCDF
> > files
> > > > look very, very similar to the output of the pcp_combine tool
but
> > you're
> > > > using a time dimension which is not used by pcp_combine. I
suspect
> > > that's
> > > > causing the issue.
> > > >
> > > > Please try editing one of your NetCDF files by removing the
time
> > > dimension,
> > > > like this:
> > > >
> > > > netcdf st_20101226_1410 {
> > > > dimensions:
> > > > lat = 801 ;
> > > > lon = 801 ;
> > > > variables:
> > > > float dbz(lat, lon) ;
> > > > dbz:long_name = "dbz" ;
> > > > dbz:units = "dbz" ;
> > > > dbz:level = "1kmAGL" ;
> > > > dbz:_FillValue = -9999.f ;
> > > > dbz:init_time = "20101226_1405" ;
> > > > dbz:valid_time = "20101226_1410" ;
> > > > dbz:init_time_ut = 1293372300 ;
> > > > dbz:valid_time_ut = 1293372600 ;
> > > > dbz:accum_time_sec = 300 ;
> > > > dbz:accum_time = "5" ;
> > > >
> > > > Once you've removed that, try running the plot_data_plane
tool.
> > That's a
> > > > great way of easily testing to see if MET can read your
gridded data:
> > > > met-5.1/bin/plot_data_plane
> > > /home/sara/MET/met-5.1/stitched/20101226/cf/
> > > > st_20101226_1405.nc plot_dbz.ps 'name="dbz"; level="(*,*)";'
> > > >
> > > > That will create a PostScript file which can be converted to
png like
> > > this:
> > > > convert -rotate 90 -background white plot_dbz.ps
plot_dbz.png
> > > >
> > > > If removing the "time" dimension and variable doesn't fix the
> problem,
> > > > please post a sample data file to our anonymous ftp site
following
> > these
> > > > instructions:
> > > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > > >
> > > > Thanks,
> > > > John Halley Gotway
> > > > met_help at ucar.edu
> > > >
> > > > On Mon, Feb 22, 2016 at 10:10 AM, Sara Ganetis via RT <
> > met_help at ucar.edu
> > > >
> > > > wrote:
> > > >
> > > > >
> > > > > Mon Feb 22 10:10:56 2016: Request 75202 was acted upon.
> > > > > Transaction: Ticket created by sara.ganetis at stonybrook.edu
> > > > > Queue: met_help
> > > > > Subject: MODE Time Dimension (MTD) troubleshooting
> > > > > Owner: Nobody
> > > > > Requestors: sara.ganetis at stonybrook.edu
> > > > > Status: new
> > > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=75202
> > > >
> > > > >
> > > > >
> > > > > Dear MET Help,
> > > > >
> > > > > I am trying to use the MODE Time Dimension tool on some data
that
> > works
> > > > > with the MODE tool in version 5.1. The NetCDF files are
> pre-processed
> > > by
> > > > me
> > > > > to add in the global and variable attributes required for
MODE to
> > work,
> > > > > which it does. However, when running the MTD tool, I get the
> > following
> > > > > output that concludes with an error:
> > > > >
> > > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> > > > > Met2dDataFile object of type "FileType_NcMet".
> > > > > DEBUG 4: Lambert Conformal Grid Data:
> > > > > DEBUG 4: scale_lat_1 = 30
> > > > > DEBUG 4: scale_lat_2 = 60
> > > > > DEBUG 4: lat_pin = 40.8521
> > > > > DEBUG 4: lon_pin = 72.8817
> > > > > DEBUG 4: x_pin = 400
> > > > > DEBUG 4: y_pin = 400
> > > > > DEBUG 4: lon_orient = 77.6
> > > > > DEBUG 4: d_km = 2
> > > > > DEBUG 4: r_km = 6371.2
> > > > > DEBUG 4: nx = 801
> > > > > DEBUG 4: ny = 801
> > > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> > > > > Met2dDataFile object of type "FileType_NcMet".
> > > > > DEBUG 4: Lambert Conformal Grid Data:
> > > > > DEBUG 4: scale_lat_1 = 30
> > > > > DEBUG 4: scale_lat_2 = 60
> > > > > DEBUG 4: lat_pin = 40.8521
> > > > > DEBUG 4: lon_pin = 72.8817
> > > > > DEBUG 4: x_pin = 400
> > > > > DEBUG 4: y_pin = 400
> > > > > DEBUG 4: lon_orient = 77.6
> > > > > DEBUG 4: d_km = 2
> > > > > DEBUG 4: r_km = 6371.2
> > > > > DEBUG 4: nx = 801
> > > > > DEBUG 4: ny = 801
> > > > > 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".
> > > > > DEBUG 2: mtd_read_data() -> processing file
> > > > > "/home/sara/MET/met-
5.1/stitched/20101226/cf/st_20101226_1405.nc"
> > > > > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> > > > > Met2dDataFile object of type "FileType_NcMet".
> > > > > DEBUG 4: Lambert Conformal Grid Data:
> > > > > DEBUG 4: scale_lat_1 = 30
> > > > > DEBUG 4: scale_lat_2 = 60
> > > > > DEBUG 4: lat_pin = 40.8521
> > > > > DEBUG 4: lon_pin = 72.8817
> > > > > DEBUG 4: x_pin = 400
> > > > > DEBUG 4: y_pin = 400
> > > > > DEBUG 4: lon_orient = 77.6
> > > > > DEBUG 4: d_km = 2
> > > > > DEBUG 4: r_km = 6371.2
> > > > > DEBUG 4: nx = 801
> > > > > DEBUG 4: ny = 801
> > > > > ERROR :
> > > > > ERROR :
> > > > > ERROR : mtd_read_data() -> unable to get data plane at
time 0
> > > > > ERROR :
> > > > >
> > > > > Are there different global/variable attributes that
mtd_read_data()
> > is
> > > > > looking for within the file? I've been testing with just two
files
> > at a
> > > > > time for now. The data are 5-minute radar composite NetCDF
files
> and
> > > I've
> > > > > been using them as both the forecast and analysis files at
this
> stage
> > > for
> > > > > testing. Here's the header information for both of my files:
> > > > >
> > > > > ## File 1:
> > > > >
> > > > > netcdf st_20101226_1405 {
> > > > > dimensions:
> > > > > time = 1 ;
> > > > > lat = 801 ;
> > > > > lon = 801 ;
> > > > > variables:
> > > > > int time ;
> > > > > time:long_name = "time" ;
> > > > > time:units = "seconds since 1970-1-1" ;
> > > > > float dbz(time, lat, lon) ;
> > > > > dbz:long_name = "dbz" ;
> > > > > dbz:units = "dbz" ;
> > > > > dbz:level = "1kmAGL" ;
> > > > > dbz:_FillValue = -9999.f ;
> > > > > dbz:init_time = "20101226_1405" ;
> > > > > dbz:valid_time = "20101226_1405" ;
> > > > > dbz:init_time_ut = 1293372300 ;
> > > > > dbz:valid_time_ut = 1293372300 ;
> > > > > dbz:accum_time_sec = 300 ;
> > > > > dbz:accum_time = "5" ;
> > > > > float lons(lat, lon) ;
> > > > > lons:long_name = "longitude" ;
> > > > > lons:units = "degrees_east" ;
> > > > > lons:standard_name = "longitude" ;
> > > > > lons:name = "longitude" ;
> > > > > lons:_FillValue = -9999.f ;
> > > > > float lats(lat, lon) ;
> > > > > lats:long_name = "latitude" ;
> > > > > lats:units = "degrees_north" ;
> > > > > lats:standard_name = "latitude" ;
> > > > > lats:name = "latitude" ;
> > > > > lats:_FillValue = -9999.f ;
> > > > >
> > > > > // global attributes:
> > > > > :MET_version = "v5.1" ;
> > > > > :nx = "801" ;
> > > > > :ny = "801 grid_points" ;
> > > > > :Projection = "Lambert Conformal" ;
> > > > > :scale_lat_1 = "30.000000" ;
> > > > > :scale_lat_2 = "60.000000" ;
> > > > > :lat_pin = "40.8521" ;
> > > > > :lon_pin = "-72.8817" ;
> > > > > :x_pin = "400" ;
> > > > > :y_pin = "400" ;
> > > > > :lon_orient = "-77.600000" ;
> > > > > :d_km = "2.0000" ;
> > > > > :r_km = "6371.200000" ;
> > > > > :nco_openmp_thread_number = 1 ;
> > > > > :history = "Mon Feb 22 11:45:59 2016: ncatted -O -a
> > > > > history,global,d,, st_20101226_1405.nc" ;
> > > > > }
> > > > >
> > > > > ## File #2:
> > > > >
> > > > > netcdf st_20101226_1410 {
> > > > > dimensions:
> > > > > time = 1 ;
> > > > > lat = 801 ;
> > > > > lon = 801 ;
> > > > > variables:
> > > > > int time ;
> > > > > time:long_name = "time" ;
> > > > > time:units = "seconds since 1970-1-1" ;
> > > > > float dbz(time, lat, lon) ;
> > > > > dbz:long_name = "dbz" ;
> > > > > dbz:units = "dbz" ;
> > > > > dbz:level = "1kmAGL" ;
> > > > > dbz:_FillValue = -9999.f ;
> > > > > dbz:init_time = "20101226_1405" ;
> > > > > dbz:valid_time = "20101226_1410" ;
> > > > > dbz:init_time_ut = 1293372300 ;
> > > > > dbz:valid_time_ut = 1293372600 ;
> > > > > dbz:accum_time_sec = 300 ;
> > > > > dbz:accum_time = "5" ;
> > > > > float lons(lat, lon) ;
> > > > > lons:long_name = "longitude" ;
> > > > > lons:units = "degrees_east" ;
> > > > > lons:standard_name = "longitude" ;
> > > > > lons:name = "longitude" ;
> > > > > lons:_FillValue = -9999.f ;
> > > > > float lats(lat, lon) ;
> > > > > lats:long_name = "latitude" ;
> > > > > lats:units = "degrees_north" ;
> > > > > lats:standard_name = "latitude" ;
> > > > > lats:name = "latitude" ;
> > > > > lats:_FillValue = -9999.f ;
> > > > >
> > > > > // global attributes:
> > > > > :MET_version = "v5.1" ;
> > > > > :nx = "801" ;
> > > > > :ny = "801 grid_points" ;
> > > > > :Projection = "Lambert Conformal" ;
> > > > > :scale_lat_1 = "30.000000" ;
> > > > > :scale_lat_2 = "60.000000" ;
> > > > > :lat_pin = "40.8521" ;
> > > > > :lon_pin = "-72.8817" ;
> > > > > :x_pin = "400" ;
> > > > > :y_pin = "400" ;
> > > > > :lon_orient = "-77.600000" ;
> > > > > :d_km = "2.0000" ;
> > > > > :r_km = "6371.200000" ;
> > > > > :nco_openmp_thread_number = 1 ;
> > > > > :history = "Mon Feb 22 11:46:05 2016: ncatted -O -a
> > > > > history,global,d,, st_20101226_1410.nc" ;
> > > > > }
> > > > >
> > > > > Finally, to be all-inclusive I am also providing how I am
calling
> MTD
> > > and
> > > > > the configure file.
> > > > >
> > > > > $ /met-5.1/bin/mtd -fcst st_*.nc -obs st_*.nc
> > > > > /met-5.1/data/config/MTDConfig_test -log mtd.log -v 4
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > > //
> > > > > // MODE Time Domain configuration file.
> > > > > //
> > > > > // For additional information, see the
MET_BASE/config/README file.
> > > > > //
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Output model name to be written
> > > > > //
> > > > >
> > > > > model = "WRF";
> > > > >
> > > > > //
> > > > > // Output observation type to be written
> > > > > //
> > > > >
> > > > > obtype = "OBS";
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Verification grid
> > > > > //
> > > > >
> > > > > regrid = {
> > > > > to_grid = NONE;
> > > > > vld_thresh = 0.5;
> > > > > method = NEAREST;
> > > > > width = 1;
> > > > > }
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Approximate grid resolution (km)
> > > > > //
> > > > >
> > > > > grid_res = 2;
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Forecast and observation fields to be verified
> > > > > //
> > > > >
> > > > > fcst = {
> > > > > field = {
> > > > > name = "dbz";
> > > > > level = "(0,*,*)";
> > > > > }
> > > > >
> > > > > raw_thresh = >=28;
> > > > > conv_radius = 5; // 13.3/grid_res; // in grid
squares
> > > > > conv_thresh = >=5.0;
> > > > > vld_thresh = 0.5;
> > > > > area_thresh = NA;
> > > > > inten_perc_value = 100;
> > > > > inten_perc_thresh = NA;
> > > > > merge_thresh = >=1.25;
> > > > > merge_flag = NONE;
> > > > > }
> > > > >
> > > > > obs = {
> > > > > field = {
> > > > > name = "dbz";
> > > > > level = "(0,*,*)";
> > > > > }
> > > > >
> > > > > raw_thresh = >=28;
> > > > > conv_radius = 1; // 13.3/grid_res; // in grid
squares
> > > > > conv_thresh = >=15.0;
> > > > > vld_thresh = 0.75;
> > > > > area_thresh = NA;
> > > > > inten_perc_value = 100;
> > > > > inten_perc_thresh = NA;
> > > > > merge_thresh = >=1.25;
> > > > > merge_flag = NONE;
> > > > > }
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Throw away 3D objects with volumes smaller than this
> > > > > //
> > > > >
> > > > > min_volume = 2000;
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Fuzzy engine weights
> > > > > //
> > > > >
> > > > > weight = {
> > > > >
> > > > > space_centroid_dist = 1.0;
> > > > >
> > > > > time_centroid_delta = 1.0;
> > > > >
> > > > > speed_delta = 1.0;
> > > > >
> > > > > direction_diff = 1.0;
> > > > >
> > > > > volume_ratio = 1.0;
> > > > >
> > > > > axis_angle_diff = 1.0;
> > > > >
> > > > > start_time_delta = 1.0;
> > > > >
> > > > > end_time_delta = 1.0;
> > > > >
> > > > > }
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Fuzzy engine interest functions
> > > > > //
> > > > >
> > > > > interest_function = {
> > > > >
> > > > > space_centroid_dist = (
> > > > >
> > > > > ( 0.0, 1.0 )
> > > > > ( 50.0, 0.5 )
> > > > > ( 100.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > time_centroid_delta = (
> > > > >
> > > > > ( -3.0, 0.0 )
> > > > > ( -2.0, 0.5 )
> > > > > ( -1.0, 0.8 )
> > > > > ( 0.0, 1.0 )
> > > > > ( 1.0, 0.8 )
> > > > > ( 2.0, 0.5 )
> > > > > ( 3.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > speed_delta = (
> > > > >
> > > > > ( -10.0, 0.0 )
> > > > > ( -5.0, 0.5 )
> > > > > ( 0.0, 1.0 )
> > > > > ( 5.0, 0.5 )
> > > > > ( 10.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > direction_diff = (
> > > > >
> > > > > ( 0.0, 1.0 )
> > > > > ( 90.0, 0.0 )
> > > > > ( 180.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > volume_ratio = (
> > > > >
> > > > > ( 0.0, 0.0 )
> > > > > ( 0.5, 0.5 )
> > > > > ( 1.0, 1.0 )
> > > > > ( 1.5, 0.5 )
> > > > > ( 2.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > axis_angle_diff = (
> > > > >
> > > > > ( 0.0, 1.0 )
> > > > > ( 30.0, 1.0 )
> > > > > ( 90.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > start_time_delta = (
> > > > >
> > > > > ( 0.0, 1.0 )
> > > > > ( 3.0, 0.5 )
> > > > > ( 5.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > end_time_delta = (
> > > > >
> > > > > ( 0.0, 1.0 )
> > > > > ( 3.0, 0.5 )
> > > > > ( 5.0, 0.0 )
> > > > >
> > > > > );
> > > > >
> > > > > } // interest functions
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Total interest threshold for determining matches
> > > > > //
> > > > >
> > > > > total_interest_thresh = 0.7;
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > > //
> > > > > // Output flags
> > > > > //
> > > > >
> > > > > nc_output = {
> > > > >
> > > > > latlon = true;
> > > > > raw = true;
> > > > > object_id = true;
> > > > > cluster_id = true;
> > > > >
> > > > > }
> > > > >
> > > > > txt_output = {
> > > > >
> > > > > attributes_2d = true;
> > > > > attributes_3d = true;
> > > > >
> > > > > }
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > >
> > > > > output_prefix = "";
> > > > >
> > > > > version = "V5.1";
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
////////////////////////////////////////////////////////////////////////////////
> > > > >
> > > > >
> > > > > Thank you in advance for your help!
> > > > >
> > > > > Take care,
> > > > >
> > > > > Sara Ganetis
> > > > > PhD Candidate
> > > > > Stony Brook University
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list