[Met_help] [rt.rap.ucar.edu #70248] History for grid stat err

[John Halley Gotway via RT]

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

hi john. 
i have 3-4 queries. i am trying to run grid_stat tool and I am interested in the neighborhood methods of verification. 
1. how is the ConfigConstants file being used???. 
2. what more can I add in the user defined Config file. 
3. I was reading the README but couldn't get across file_type, initi_time, valid_time etc variables. 

4. As you can see I have not specified these in my config file. 

I m waiting for your response
geeta 
 		 	   		  

----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: grid stat err
From: John Halley Gotway
Time: Tue Jan 06 13:38:05 2015

Geeta,

I just got back in the office today and see several met-help
questions.  I
see that Julie's provided some feedback, but I'll do my best to
address
your remaining questions.  I went ahead and deleted the first couple
of
questions because it looks like you were able to figure out the issues
with
your Grid-Stat configuration file.

To answer these questions in this ticket...
- ConfigConstants is a configuration file that defines several
constants
used in the other configuration files.  This should in general not be
modified by the user.  For example, in the Grid-Stat configuration
file,
you control the output line types by setting them to NONE, BOTH, or
STAT.
Those tokens are defined in ConfigConstants to values of 1, 2, and 3,
respectively.  We define things like this to make the configuration
files
more human readable.  I can't think of a good reason for you to edit
that
file.
- The MET configuration files support the entries described in the
data/config/README and data/config/README_TC files.  If you add new
entries
to them, the MET source code wouldn't actually parse them from the
file and
it wouldn't have any impact on the functionality of the tools.
- The file_type, init_time, and valid_time entries can be used to
further
refine what data should be read from the input gridded data files.
But you
probably won't need to use them.  When MET reads a gridded data file,
it
first tries to interpret it's type using the file's suffix (e.g. .nc
for
NetCDF, .grb for GRIB1).  If that doesn't work, it'll look inside the
file
to try to figure it out.  If for some reason, MET is not interpreting
the
file type correctly, you can use "file_type" to explicitly tell it how
read
the data.  The init_time and valid_time options are only useful when
your
files contain data for multiple output times.  Suppose you have a
single
GRIB file containing output for all forecast times.  You'd need to
list
some timing information to tell MET which record you want to use.
Otherwise, it'll just use the first match it finds.

You should not need to use these filtering options for your data.

John



On Sun, Jan 4, 2015 at 10:30 AM, Geeta Geeta via RT
<met_help at ucar.edu>
wrote:

>
> Sun Jan 04 10:30:24 2015: Request 70248 was acted upon.
> Transaction: Ticket created by geeta124 at hotmail.com
>        Queue: met_help
>      Subject: grid stat err
>        Owner: Nobody
>   Requestors: geeta124 at hotmail.com
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=70248 >
>
>
> hi john.
> i have 3-4 queries. i am trying to run grid_stat tool and I am
interested
> in the neighborhood methods of verification.
> 1. how is the ConfigConstants file being used???.
> 2. what more can I add in the user defined Config file.
> 3. I was reading the README but couldn't get across file_type,
initi_time,
> valid_time etc variables.
>
> 4. As you can see I have not specified these in my config file.
>
> I m waiting for your response
> geeta
>
>

------------------------------------------------