[Met_help] [rt.rap.ucar.edu #81768] History for Met_v6 - Issues using Point Stat

Julie Prestopnik via RT met_help at ucar.edu
Tue Feb 27 08:56:49 MST 2018


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

Dear Sir/ Madam,

I'm a french environmental consultant and I'm currently working on a 
project mainly focus on the evaluation and validation of modeled 
meteorological data  recently modeled using WRF over France(wind speed, 
direction, temperature, pressure, rainfall..). I would like to assess 
and to validate by comparison to MEDAR meteorological observation data.

Following Online Tutorial for *MET version 6.0*, I have recently modify 
Metar data using Madis2nc in order to use them in Point Stat.

However, I have some issues when I use Point Stat and it seems that 
these issues are linked to my WRF data (as you can see on the following 
screen-shoot). Also, I changed the Point Stat Configuration with only 
Temperature. Please you can find it in attachment.

Can you confirm that I can use WRF data with Point Stat or shall I need 
to modify/ post-process them ?

Best regards,--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 | E: 
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com


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

Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Mon Aug 28 09:44:16 2017

Hello Adrien.

I would be happy to help you.  However, before I'm able to provide you
with
direct assistance, you'll need to fill out the free registration form
on
the MET website.  Go to:

   http://www.dtcenter.org/met/users/downloads/index.php

Enter your email address and hit enter to be taken to the registration
page.  We require that all users register before receiving direct
assistance so as to ensure that we remain in compliance with the
international export laws of the United States.

Please let me know when you've registered, and I can help you with
this.

Thanks,
Julie

On Mon, Aug 28, 2017 at 9:10 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> Mon Aug 28 09:10:42 2017: Request 81768 was acted upon.
> Transaction: Ticket created by amichel at atmoterra.com
>        Queue: met_help
>      Subject: Met_v6 - Issues using Point Stat
>        Owner: Nobody
>   Requestors: amichel at atmoterra.com
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
>
> Dear Sir/ Madam,
>
> I'm a french environmental consultant and I'm currently working on a
> project mainly focus on the evaluation and validation of modeled
> meteorological data  recently modeled using WRF over France(wind
speed,
> direction, temperature, pressure, rainfall..). I would like to
assess
> and to validate by comparison to MEDAR meteorological observation
data.
>
> Following Online Tutorial for *MET version 6.0*, I have recently
modify
> Metar data using Madis2nc in order to use them in Point Stat.
>
> However, I have some issues when I use Point Stat and it seems that
> these issues are linked to my WRF data (as you can see on the
following
> screen-shoot). Also, I changed the Point Stat Configuration with
only
> Temperature. Please you can find it in attachment.
>
> Can you confirm that I can use WRF data with Point Stat or shall I
need
> to modify/ post-process them ?
>
> Best regards,--
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Tue Aug 29 01:22:49 2017

Hello Julie,

Thank you for answering, I am now register to MET website.

Best regards,

Adrien


Le 28/08/2017 à 17:44, Julie Prestopnik via RT a écrit :
> Hello Adrien.
>
> I would be happy to help you.  However, before I'm able to provide
you with
> direct assistance, you'll need to fill out the free registration
form on
> the MET website.  Go to:
>
>     http://www.dtcenter.org/met/users/downloads/index.php
>
> Enter your email address and hit enter to be taken to the
registration
> page.  We require that all users register before receiving direct
> assistance so as to ensure that we remain in compliance with the
> international export laws of the United States.
>
> Please let me know when you've registered, and I can help you with
this.
>
> Thanks,
> Julie
>
> On Mon, Aug 28, 2017 at 9:10 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> Mon Aug 28 09:10:42 2017: Request 81768 was acted upon.
>> Transaction: Ticket created by amichel at atmoterra.com
>>         Queue: met_help
>>       Subject: Met_v6 - Issues using Point Stat
>>         Owner: Nobody
>>    Requestors: amichel at atmoterra.com
>>        Status: new
>>   Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>>
>> Dear Sir/ Madam,
>>
>> I'm a french environmental consultant and I'm currently working on
a
>> project mainly focus on the evaluation and validation of modeled
>> meteorological data  recently modeled using WRF over France(wind
speed,
>> direction, temperature, pressure, rainfall..). I would like to
assess
>> and to validate by comparison to MEDAR meteorological observation
data.
>>
>> Following Online Tutorial for *MET version 6.0*, I have recently
modify
>> Metar data using Madis2nc in order to use them in Point Stat.
>>
>> However, I have some issues when I use Point Stat and it seems that
>> these issues are linked to my WRF data (as you can see on the
following
>> screen-shoot). Also, I changed the Point Stat Configuration with
only
>> Temperature. Please you can find it in attachment.
>>
>> Can you confirm that I can use WRF data with Point Stat or shall I
need
>> to modify/ post-process them ?
>>
>> Best regards,--
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Tue Aug 29 09:16:45 2017

Hi Adrien.  Thank you for registering.

I see you have questions about verifying WRF output files with METAR
files.

Unfortunately, MET does not read the NetCDF output of WRF directly.
There
are two main issues here.  First, wrfout files are on hybrid pressure
levels in the vertical, and second, some of the output variables are
defined on a staggered grid.  Some sort of post-processing is required
prior to verifying this data in MET.

You have two options.  The wrf_interp utility is reads WRF-ARW output
and
converts from hybrid vertical levels to pressure levels.  MET is able
to
read the output of wrf_interp, but only variables defined on the
non-staggered dimension.  So temperatures are fine, but not winds.

The second option is running the unified postprocessor (UPP).  It
reads
WRF-ARW and WRF-NMM, interpolates to pressure levels, computes many
derived
variables, and can interpolate to whatever output grid you'd like.
It's
output is GRIB1 or GRIB2 which MET can easily read.  For these
reasons, we
recommend using UPP instead of wrf_interp.

I hope that helps.

Julie

On Tue, Aug 29, 2017 at 1:22 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hello Julie,
>
> Thank you for answering, I am now register to MET website.
>
> Best regards,
>
> Adrien
>
>
> Le 28/08/2017 à 17:44, Julie Prestopnik via RT a écrit :
> > Hello Adrien.
> >
> > I would be happy to help you.  However, before I'm able to provide
you
> with
> > direct assistance, you'll need to fill out the free registration
form on
> > the MET website.  Go to:
> >
> >     http://www.dtcenter.org/met/users/downloads/index.php
> >
> > Enter your email address and hit enter to be taken to the
registration
> > page.  We require that all users register before receiving direct
> > assistance so as to ensure that we remain in compliance with the
> > international export laws of the United States.
> >
> > Please let me know when you've registered, and I can help you with
this.
> >
> > Thanks,
> > Julie
> >
> > On Mon, Aug 28, 2017 at 9:10 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> Mon Aug 28 09:10:42 2017: Request 81768 was acted upon.
> >> Transaction: Ticket created by amichel at atmoterra.com
> >>         Queue: met_help
> >>       Subject: Met_v6 - Issues using Point Stat
> >>         Owner: Nobody
> >>    Requestors: amichel at atmoterra.com
> >>        Status: new
> >>   Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> >>
> >>
> >> Dear Sir/ Madam,
> >>
> >> I'm a french environmental consultant and I'm currently working
on a
> >> project mainly focus on the evaluation and validation of modeled
> >> meteorological data  recently modeled using WRF over France(wind
speed,
> >> direction, temperature, pressure, rainfall..). I would like to
assess
> >> and to validate by comparison to MEDAR meteorological observation
data.
> >>
> >> Following Online Tutorial for *MET version 6.0*, I have recently
modify
> >> Metar data using Madis2nc in order to use them in Point Stat.
> >>
> >> However, I have some issues when I use Point Stat and it seems
that
> >> these issues are linked to my WRF data (as you can see on the
following
> >> screen-shoot). Also, I changed the Point Stat Configuration with
only
> >> Temperature. Please you can find it in attachment.
> >>
> >> Can you confirm that I can use WRF data with Point Stat or shall
I need
> >> to modify/ post-process them ?
> >>
> >> Best regards,--
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Wed Aug 30 05:40:24 2017

Hi Julie,

Thank you for you quick response and for you help!

I will definitely try to run the unified post processor (UPP). This
option is fully in line with my study.

Best regards,

Adrien



Le 29/08/2017 à 17:16, Julie Prestopnik via RT a écrit :
> Hi Adrien.  Thank you for registering.
>
> I see you have questions about verifying WRF output files with METAR
files.
>
> Unfortunately, MET does not read the NetCDF output of WRF directly.
There
> are two main issues here.  First, wrfout files are on hybrid
pressure
> levels in the vertical, and second, some of the output variables are
> defined on a staggered grid.  Some sort of post-processing is
required
> prior to verifying this data in MET.
>
> You have two options.  The wrf_interp utility is reads WRF-ARW
output and
> converts from hybrid vertical levels to pressure levels.  MET is
able to
> read the output of wrf_interp, but only variables defined on the
> non-staggered dimension.  So temperatures are fine, but not winds.
>
> The second option is running the unified postprocessor (UPP).  It
reads
> WRF-ARW and WRF-NMM, interpolates to pressure levels, computes many
derived
> variables, and can interpolate to whatever output grid you'd like.
It's
> output is GRIB1 or GRIB2 which MET can easily read.  For these
reasons, we
> recommend using UPP instead of wrf_interp.
>
> I hope that helps.
>
> Julie
>
> On Tue, Aug 29, 2017 at 1:22 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hello Julie,
>>
>> Thank you for answering, I am now register to MET website.
>>
>> Best regards,
>>
>> Adrien
>>
>>
>> Le 28/08/2017 à 17:44, Julie Prestopnik via RT a écrit :
>>> Hello Adrien.
>>>
>>> I would be happy to help you.  However, before I'm able to provide
you
>> with
>>> direct assistance, you'll need to fill out the free registration
form on
>>> the MET website.  Go to:
>>>
>>>      http://www.dtcenter.org/met/users/downloads/index.php
>>>
>>> Enter your email address and hit enter to be taken to the
registration
>>> page.  We require that all users register before receiving direct
>>> assistance so as to ensure that we remain in compliance with the
>>> international export laws of the United States.
>>>
>>> Please let me know when you've registered, and I can help you with
this.
>>>
>>> Thanks,
>>> Julie
>>>
>>> On Mon, Aug 28, 2017 at 9:10 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> Mon Aug 28 09:10:42 2017: Request 81768 was acted upon.
>>>> Transaction: Ticket created by amichel at atmoterra.com
>>>>          Queue: met_help
>>>>        Subject: Met_v6 - Issues using Point Stat
>>>>          Owner: Nobody
>>>>     Requestors: amichel at atmoterra.com
>>>>         Status: new
>>>>    Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>>>>
>>>> Dear Sir/ Madam,
>>>>
>>>> I'm a french environmental consultant and I'm currently working
on a
>>>> project mainly focus on the evaluation and validation of modeled
>>>> meteorological data  recently modeled using WRF over France(wind
speed,
>>>> direction, temperature, pressure, rainfall..). I would like to
assess
>>>> and to validate by comparison to MEDAR meteorological observation
data.
>>>>
>>>> Following Online Tutorial for *MET version 6.0*, I have recently
modify
>>>> Metar data using Madis2nc in order to use them in Point Stat.
>>>>
>>>> However, I have some issues when I use Point Stat and it seems
that
>>>> these issues are linked to my WRF data (as you can see on the
following
>>>> screen-shoot). Also, I changed the Point Stat Configuration with
only
>>>> Temperature. Please you can find it in attachment.
>>>>
>>>> Can you confirm that I can use WRF data with Point Stat or shall
I need
>>>> to modify/ post-process them ?
>>>>
>>>> Best regards,--
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
>> E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Wed Aug 30 08:45:06 2017

Thank you, Adrien.  I'll go ahead and close this ticket.  Please write
again if other issues arise.

Julie

On Wed, Aug 30, 2017 at 5:40 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi Julie,
>
> Thank you for you quick response and for you help!
>
> I will definitely try to run the unified post processor (UPP). This
> option is fully in line with my study.
>
> Best regards,
>
> Adrien
>
>
>
> Le 29/08/2017 à 17:16, Julie Prestopnik via RT a écrit :
> > Hi Adrien.  Thank you for registering.
> >
> > I see you have questions about verifying WRF output files with
METAR
> files.
> >
> > Unfortunately, MET does not read the NetCDF output of WRF
directly.
> There
> > are two main issues here.  First, wrfout files are on hybrid
pressure
> > levels in the vertical, and second, some of the output variables
are
> > defined on a staggered grid.  Some sort of post-processing is
required
> > prior to verifying this data in MET.
> >
> > You have two options.  The wrf_interp utility is reads WRF-ARW
output and
> > converts from hybrid vertical levels to pressure levels.  MET is
able to
> > read the output of wrf_interp, but only variables defined on the
> > non-staggered dimension.  So temperatures are fine, but not winds.
> >
> > The second option is running the unified postprocessor (UPP).  It
reads
> > WRF-ARW and WRF-NMM, interpolates to pressure levels, computes
many
> derived
> > variables, and can interpolate to whatever output grid you'd like.
It's
> > output is GRIB1 or GRIB2 which MET can easily read.  For these
reasons,
> we
> > recommend using UPP instead of wrf_interp.
> >
> > I hope that helps.
> >
> > Julie
> >
> > On Tue, Aug 29, 2017 at 1:22 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hello Julie,
> >>
> >> Thank you for answering, I am now register to MET website.
> >>
> >> Best regards,
> >>
> >> Adrien
> >>
> >>
> >> Le 28/08/2017 à 17:44, Julie Prestopnik via RT a écrit :
> >>> Hello Adrien.
> >>>
> >>> I would be happy to help you.  However, before I'm able to
provide you
> >> with
> >>> direct assistance, you'll need to fill out the free registration
form
> on
> >>> the MET website.  Go to:
> >>>
> >>>      http://www.dtcenter.org/met/users/downloads/index.php
> >>>
> >>> Enter your email address and hit enter to be taken to the
registration
> >>> page.  We require that all users register before receiving
direct
> >>> assistance so as to ensure that we remain in compliance with the
> >>> international export laws of the United States.
> >>>
> >>> Please let me know when you've registered, and I can help you
with
> this.
> >>>
> >>> Thanks,
> >>> Julie
> >>>
> >>> On Mon, Aug 28, 2017 at 9:10 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> Mon Aug 28 09:10:42 2017: Request 81768 was acted upon.
> >>>> Transaction: Ticket created by amichel at atmoterra.com
> >>>>          Queue: met_help
> >>>>        Subject: Met_v6 - Issues using Point Stat
> >>>>          Owner: Nobody
> >>>>     Requestors: amichel at atmoterra.com
> >>>>         Status: new
> >>>>    Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81768
> >>>>
> >>>> Dear Sir/ Madam,
> >>>>
> >>>> I'm a french environmental consultant and I'm currently working
on a
> >>>> project mainly focus on the evaluation and validation of
modeled
> >>>> meteorological data  recently modeled using WRF over
France(wind
> speed,
> >>>> direction, temperature, pressure, rainfall..). I would like to
assess
> >>>> and to validate by comparison to MEDAR meteorological
observation
> data.
> >>>>
> >>>> Following Online Tutorial for *MET version 6.0*, I have
recently
> modify
> >>>> Metar data using Madis2nc in order to use them in Point Stat.
> >>>>
> >>>> However, I have some issues when I use Point Stat and it seems
that
> >>>> these issues are linked to my WRF data (as you can see on the
> following
> >>>> screen-shoot). Also, I changed the Point Stat Configuration
with only
> >>>> Temperature. Please you can find it in attachment.
> >>>>
> >>>> Can you confirm that I can use WRF data with Point Stat or
shall I
> need
> >>>> to modify/ post-process them ?
> >>>>
> >>>> Best regards,--
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Mon Sep 11 02:55:51 2017

Hello Julie,

I have further questions about Madis2nc use. I would like to use the
'-mask_grid string' option. However there are very limited details on
how define the polyline masking file in the user guide. I should like
to
define the polyline masking file for Europe and especially for France.

Thank you in advance,

Regards.

Adrien


Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> According to our records, your request has been resolved. If you
have any
> further questions or concerns, please respond to this message.

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Mon Sep 11 13:13:13 2017

Hi Adrien.

I see that you have a question about how to define a polyline masking
file.  The -mask_grid option would take a named grid or a gridded data
file, while the -mask_poly option would definite a polyline masking
file.

If you'd only like to keep the points falling inside your model
domain, and
you have a gridded data file on that domain, using -mask_grid is very
simple:
   -mask_grid /path/to/gridded/data/file

However, if you'd prefer the flexibility of defining a polyline
masking
region, using -mask_poly would work too:
   -mask_poly /path/to/polyline/mask/file

To create a polyline mask, you simply create an ASCII file containing
a
list of lat/lons that define the region of interest.  For example,
take a
look in met-6.0/data/poly/SWC.poly.  The first line of the file
specifies
the name for the polyline, and the remaining lines contain lat/lon
values
for the boundary points.  The last point is connected back up to the
first
point to complete the area.  The example is named "SWC" and contains
33
points, and there is no real maximum.

I hope this helps.  Please let us know if you have other questions.

Thanks,
Julie

On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hello Julie,
>
> I have further questions about Madis2nc use. I would like to use the
> '-mask_grid string' option. However there are very limited details
on
> how define the polyline masking file in the user guide. I should
like to
> define the polyline masking file for Europe and especially for
France.
>
> Thank you in advance,
>
> Regards.
>
> Adrien
>
>
> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> > According to our records, your request has been resolved. If you
have any
> > further questions or concerns, please respond to this message.
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Tue Sep 12 07:01:00 2017

Hi Julie.

  I've done as you suggested and it ran without problem, thank you!

I come up with a another issue.. I'm trying to use Point-Stat :
- a forecast file (WRF file - CF compliance)
- a point observation file coming from Madis2nc

However, Point Stat seems to have issue to read my forecast file with
the following informations:
> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> met-6.0/data/Madis2nc_test/20130101_0200.nc
> met-6.0/data/Test/PointStatConfig -outdir
> /met-6.0/data/Point_Stat_Test -v 5
> DEBUG 1: Default Config File:
> /usr/local/share/met/config/PointStatConfig_default
> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
> Met2dDataFile object of type "FileType_None".
> ERROR  :
> ERROR  : Trouble reading forecast file
> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> ERROR  :
I was wondering if you had any insight on what I could be doing wrong.
I
appreciate any help you can give.
Thanks,

Adrien Michel/


/
Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> Hi Adrien.
>
> I see that you have a question about how to define a polyline
masking
> file.  The -mask_grid option would take a named grid or a gridded
data
> file, while the -mask_poly option would definite a polyline masking
file.
>
> If you'd only like to keep the points falling inside your model
domain, and
> you have a gridded data file on that domain, using -mask_grid is
very
> simple:
>     -mask_grid /path/to/gridded/data/file
>
> However, if you'd prefer the flexibility of defining a polyline
masking
> region, using -mask_poly would work too:
>     -mask_poly /path/to/polyline/mask/file
>
> To create a polyline mask, you simply create an ASCII file
containing a
> list of lat/lons that define the region of interest.  For example,
take a
> look in met-6.0/data/poly/SWC.poly.  The first line of the file
specifies
> the name for the polyline, and the remaining lines contain lat/lon
values
> for the boundary points.  The last point is connected back up to the
first
> point to complete the area.  The example is named "SWC" and contains
33
> points, and there is no real maximum.
>
> I hope this helps.  Please let us know if you have other questions.
>
> Thanks,
> Julie
>
> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hello Julie,
>>
>> I have further questions about Madis2nc use. I would like to use
the
>> '-mask_grid string' option. However there are very limited details
on
>> how define the polyline masking file in the user guide. I should
like to
>> define the polyline masking file for Europe and especially for
France.
>>
>> Thank you in advance,
>>
>> Regards.
>>
>> Adrien
>>
>>
>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>> According to our records, your request has been resolved. If you
have any
>>> further questions or concerns, please respond to this message.
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Tue Sep 12 11:09:34 2017

Hi Adrien.

It is difficult to tell the problem with the file without seeing it.
However, I have something for you to try that might work.  MET should
be
able to read CF compliant files, and you have stated that your NetCDF
file
is CF Compliant.  MET tries to figure out the type of file, but since
it is
having trouble, let's try explicitly telling the tools how to process
the
data by setting the following in your PointStat config file:

file_type = NETCDF_NCCF;

This entry should be defined within the "fcst" dictionary.  For
example:

fcst = {
file_type = NETCDF_NCCF;
...
}

If that works, please let us know.  If that does not work, please
upload
your file to our ftp server using the following instructions and let
us
know once you have done that so that we can get the file and take a
look.

http://www.dtcenter.org/met/users/support/met_help.php#ftp

Thanks!

Julie


On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi Julie.
>
>   I've done as you suggested and it ran without problem, thank you!
>
> I come up with a another issue.. I'm trying to use Point-Stat :
> - a forecast file (WRF file - CF compliance)
> - a point observation file coming from Madis2nc
>
> However, Point Stat seems to have issue to read my forecast file
with
> the following informations:
> > point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> > met-6.0/data/Madis2nc_test/20130101_0200.nc
> > met-6.0/data/Test/PointStatConfig -outdir
> > /met-6.0/data/Point_Stat_Test -v 5
> > DEBUG 1: Default Config File:
> > /usr/local/share/met/config/PointStatConfig_default
> > DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> > DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> > Met2dDataFile object of type "FileType_None".
> > ERROR  :
> > ERROR  : Trouble reading forecast file
> > "met-6.0/data/WRF_cf/wrfpost_output.nc"
> > ERROR  :
> I was wondering if you had any insight on what I could be doing
wrong. I
> appreciate any help you can give.
> Thanks,
>
> Adrien Michel/
>
>
> /
> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > I see that you have a question about how to define a polyline
masking
> > file.  The -mask_grid option would take a named grid or a gridded
data
> > file, while the -mask_poly option would definite a polyline
masking file.
> >
> > If you'd only like to keep the points falling inside your model
domain,
> and
> > you have a gridded data file on that domain, using -mask_grid is
very
> > simple:
> >     -mask_grid /path/to/gridded/data/file
> >
> > However, if you'd prefer the flexibility of defining a polyline
masking
> > region, using -mask_poly would work too:
> >     -mask_poly /path/to/polyline/mask/file
> >
> > To create a polyline mask, you simply create an ASCII file
containing a
> > list of lat/lons that define the region of interest.  For example,
take a
> > look in met-6.0/data/poly/SWC.poly.  The first line of the file
specifies
> > the name for the polyline, and the remaining lines contain lat/lon
values
> > for the boundary points.  The last point is connected back up to
the
> first
> > point to complete the area.  The example is named "SWC" and
contains 33
> > points, and there is no real maximum.
> >
> > I hope this helps.  Please let us know if you have other
questions.
> >
> > Thanks,
> > Julie
> >
> > On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hello Julie,
> >>
> >> I have further questions about Madis2nc use. I would like to use
the
> >> '-mask_grid string' option. However there are very limited
details on
> >> how define the polyline masking file in the user guide. I should
like to
> >> define the polyline masking file for Europe and especially for
France.
> >>
> >> Thank you in advance,
> >>
> >> Regards.
> >>
> >> Adrien
> >>
> >>
> >> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>> According to our records, your request has been resolved. If you
have
> any
> >>> further questions or concerns, please respond to this message.
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Wed Sep 13 09:57:24 2017

Hi Julie,

Many thank, I have done as you suggested and MET seems to read my CF
Compliant. However, I still have issues with the configuration of
Point-Stat.

So I  uploaded my file (name file: michel_data)
- a forecast file (WRF file - CF compliance) - daily file for 2013-01-
01

I would also provide you :
- point observation file from Madis2nc - hourly file for 2013-01-
01_02:00:00
- Point-Stat configuration

I'm grateful for you help.
Regards,

Adrien Michel


Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> Hi Adrien.
>
> It is difficult to tell the problem with the file without seeing it.
> However, I have something for you to try that might work.  MET
should be
> able to read CF compliant files, and you have stated that your
NetCDF file
> is CF Compliant.  MET tries to figure out the type of file, but
since it is
> having trouble, let's try explicitly telling the tools how to
process the
> data by setting the following in your PointStat config file:
>
> file_type = NETCDF_NCCF;
>
> This entry should be defined within the "fcst" dictionary.  For
example:
>
> fcst = {
> file_type = NETCDF_NCCF;
> ...
> }
>
> If that works, please let us know.  If that does not work, please
upload
> your file to our ftp server using the following instructions and let
us
> know once you have done that so that we can get the file and take a
look.
>
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks!
>
> Julie
>
>
> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hi Julie.
>>
>>    I've done as you suggested and it ran without problem, thank
you!
>>
>> I come up with a another issue.. I'm trying to use Point-Stat :
>> - a forecast file (WRF file - CF compliance)
>> - a point observation file coming from Madis2nc
>>
>> However, Point Stat seems to have issue to read my forecast file
with
>> the following informations:
>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>> met-6.0/data/Test/PointStatConfig -outdir
>>> /met-6.0/data/Point_Stat_Test -v 5
>>> DEBUG 1: Default Config File:
>>> /usr/local/share/met/config/PointStatConfig_default
>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>> Met2dDataFile object of type "FileType_None".
>>> ERROR  :
>>> ERROR  : Trouble reading forecast file
>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>> ERROR  :
>> I was wondering if you had any insight on what I could be doing
wrong. I
>> appreciate any help you can give.
>> Thanks,
>>
>> Adrien Michel/
>>
>>
>> /
>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>> Hi Adrien.
>>>
>>> I see that you have a question about how to define a polyline
masking
>>> file.  The -mask_grid option would take a named grid or a gridded
data
>>> file, while the -mask_poly option would definite a polyline
masking file.
>>>
>>> If you'd only like to keep the points falling inside your model
domain,
>> and
>>> you have a gridded data file on that domain, using -mask_grid is
very
>>> simple:
>>>      -mask_grid /path/to/gridded/data/file
>>>
>>> However, if you'd prefer the flexibility of defining a polyline
masking
>>> region, using -mask_poly would work too:
>>>      -mask_poly /path/to/polyline/mask/file
>>>
>>> To create a polyline mask, you simply create an ASCII file
containing a
>>> list of lat/lons that define the region of interest.  For example,
take a
>>> look in met-6.0/data/poly/SWC.poly.  The first line of the file
specifies
>>> the name for the polyline, and the remaining lines contain lat/lon
values
>>> for the boundary points.  The last point is connected back up to
the
>> first
>>> point to complete the area.  The example is named "SWC" and
contains 33
>>> points, and there is no real maximum.
>>>
>>> I hope this helps.  Please let us know if you have other
questions.
>>>
>>> Thanks,
>>> Julie
>>>
>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hello Julie,
>>>>
>>>> I have further questions about Madis2nc use. I would like to use
the
>>>> '-mask_grid string' option. However there are very limited
details on
>>>> how define the polyline masking file in the user guide. I should
like to
>>>> define the polyline masking file for Europe and especially for
France.
>>>>
>>>> Thank you in advance,
>>>>
>>>> Regards.
>>>>
>>>> Adrien
>>>>
>>>>
>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>>>> According to our records, your request has been resolved. If you
have
>> any
>>>>> further questions or concerns, please respond to this message.
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
>> E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Wed Sep 13 09:57:24 2017

////////////////////////////////////////////////////////////////////////////////
//
// Point-Stat configuration file.
//
// For additional information, see the MET_BASE/config/README file.
//
////////////////////////////////////////////////////////////////////////////////

//
// Output model name to be written
//
model = "WRF";

//
// Output description to be written
// May be set separately in each "obs.field" entry
//
desc = "NA";

////////////////////////////////////////////////////////////////////////////////

//
// Verification grid
//
regrid = {
   to_grid    = NONE;
   method     = NEAREST;
   width      = 1;
   vld_thresh = 0.5;
}

////////////////////////////////////////////////////////////////////////////////

cat_thresh  = [ NA ];
cnt_thresh  = [ NA ];
cnt_logic   = UNION;
wind_thresh =[ NA ];
wind_logic  = UNION;

//
// Forecast and observation fields to be verified
//
fcst = {
file_type = NETCDF_NCCF;
lead_time = "020000";
   field = [
      {
        name       = "T_sfc";
        level      = "(0,*,*)";
        cat_thresh = [ >278, >283, >288 ];
    }
   ];

}
obs = {
   field = [
      {
        name       = "TMP";
        level      = [ "Z2" ];
        cat_thresh = [ >278, >283, >288 ];
    }
   ];

}
////////////////////////////////////////////////////////////////////////////////

//
// Point observation filtering options
// May be set separately in each "obs.field" entry
//
message_type   = [ "ADPSFC" ];
sid_exc        = [];
obs_quality    = [];
duplicate_flag = NONE;
obs_summary    = NONE;
obs_perc_value = 50;

////////////////////////////////////////////////////////////////////////////////

//
// Climatology mean data
//
climo_mean = {

   file_name = [];
   field     = [];

   regrid = {
      method     = NEAREST;
      width      = 1;
      vld_thresh = 0.5;
   }

   time_interp_method = DW_MEAN;
   match_day          = FALSE;
   time_step          = 3600;
}

////////////////////////////////////////////////////////////////////////////////

//
// Point observation time window
//
obs_window = {
   beg = -5400;
   end =  5400;
}

////////////////////////////////////////////////////////////////////////////////

//
// Verification masking regions
//
mask = {
   grid    = [ "FULL" ];
   poly    = [];
   sid     = [];
}

////////////////////////////////////////////////////////////////////////////////

//
// Confidence interval settings
//
ci_alpha  = [ 0.05 ];

boot = {
   interval = PCTILE;
   rep_prop = 1.0;
   n_rep    = 0;
   rng      = "mt19937";
   seed     = "";
}

////////////////////////////////////////////////////////////////////////////////

//
// Interpolation methods
//
interp = {
   vld_thresh = 1.0;

   type = [
      {
         method = UW_MEAN;
         width  = 1;
      }
   ];
}

////////////////////////////////////////////////////////////////////////////////

//
// HiRA verification method
//
hira = {
   flag       = FALSE;
   width      = [ 2, 3, 4, 5 ];
   vld_thresh = 1.0;
   cov_thresh = [ ==0.25 ];
}

////////////////////////////////////////////////////////////////////////////////

//
// Statistical output types
//
output_flag = {
   fho    = BOTH;
   ctc    = BOTH;
   cts    = BOTH;
   mctc   = BOTH;
   mcts   = BOTH;
   cnt    = BOTH;
   sl1l2  = BOTH;
   sal1l2 = BOTH;
   vl1l2  = BOTH;
   val1l2 = BOTH;
   pct    = NONE;
   pstd   = NONE;
   pjc    = NONE;
   prc    = NONE;
   mpr    = BOTH;
}

////////////////////////////////////////////////////////////////////////////////

rank_corr_flag = FALSE;
tmp_dir        = "/tmp";
output_prefix  = "";
version        = "V6.0";

////////////////////////////////////////////////////////////////////////////////

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Howard Soh
Time: Wed Sep 13 11:24:53 2017

The global attribute Conventions from NetCDF:
	:Conventions = "CF 1.6, Standard Name Table v19" ;

Our code only checks "CF-" as NCCF file. I will allow "CF ", too.

Cheers,
Howard


On Wed Sep 13 09:57:24 2017, amichel at atmoterra.com wrote:
> Hi Julie,
>
> Many thank, I have done as you suggested and MET seems to read my CF
> Compliant. However, I still have issues with the configuration of
> Point-Stat.
>
> So I  uploaded my file (name file: michel_data)
> - a forecast file (WRF file - CF compliance) - daily file for 2013-
01-
> 01
>
> I would also provide you :
> - point observation file from Madis2nc - hourly file for 2013-01-
> 01_02:00:00
> - Point-Stat configuration
>
> I'm grateful for you help.
> Regards,
>
> Adrien Michel
>
>
> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > It is difficult to tell the problem with the file without seeing
it.
> > However, I have something for you to try that might work.  MET
should
> > be
> > able to read CF compliant files, and you have stated that your
NetCDF
> > file
> > is CF Compliant.  MET tries to figure out the type of file, but
since
> > it is
> > having trouble, let's try explicitly telling the tools how to
process
> > the
> > data by setting the following in your PointStat config file:
> >
> > file_type = NETCDF_NCCF;
> >
> > This entry should be defined within the "fcst" dictionary.  For
> > example:
> >
> > fcst = {
> > file_type = NETCDF_NCCF;
> > ...
> > }
> >
> > If that works, please let us know.  If that does not work, please
> > upload
> > your file to our ftp server using the following instructions and
let
> > us
> > know once you have done that so that we can get the file and take
a
> > look.
> >
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > Thanks!
> >
> > Julie
> >
> >
> > On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
> > <met_help at ucar.edu>
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hi Julie.
> >>
> >> I've done as you suggested and it ran without problem, thank you!
> >>
> >> I come up with a another issue.. I'm trying to use Point-Stat :
> >> - a forecast file (WRF file - CF compliance)
> >> - a point observation file coming from Madis2nc
> >>
> >> However, Point Stat seems to have issue to read my forecast file
> >> with
> >> the following informations:
> >>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>> met-6.0/data/Test/PointStatConfig -outdir
> >>> /met-6.0/data/Point_Stat_Test -v 5
> >>> DEBUG 1: Default Config File:
> >>> /usr/local/share/met/config/PointStatConfig_default
> >>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> >>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
> >>> new
> >>> Met2dDataFile object of type "FileType_None".
> >>> ERROR  :
> >>> ERROR  : Trouble reading forecast file
> >>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>> ERROR  :
> >> I was wondering if you had any insight on what I could be doing
> >> wrong. I
> >> appreciate any help you can give.
> >> Thanks,
> >>
> >> Adrien Michel/
> >>
> >>
> >> /
> >> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> I see that you have a question about how to define a polyline
> >>> masking
> >>> file.  The -mask_grid option would take a named grid or a
gridded
> >>> data
> >>> file, while the -mask_poly option would definite a polyline
masking
> >>> file.
> >>>
> >>> If you'd only like to keep the points falling inside your model
> >>> domain,
> >> and
> >>> you have a gridded data file on that domain, using -mask_grid is
> >>> very
> >>> simple:
> >>>      -mask_grid /path/to/gridded/data/file
> >>>
> >>> However, if you'd prefer the flexibility of defining a polyline
> >>> masking
> >>> region, using -mask_poly would work too:
> >>>      -mask_poly /path/to/polyline/mask/file
> >>>
> >>> To create a polyline mask, you simply create an ASCII file
> >>> containing a
> >>> list of lat/lons that define the region of interest.  For
example,
> >>> take a
> >>> look in met-6.0/data/poly/SWC.poly.  The first line of the file
> >>> specifies
> >>> the name for the polyline, and the remaining lines contain
lat/lon
> >>> values
> >>> for the boundary points.  The last point is connected back up to
> >>> the
> >> first
> >>> point to complete the area.  The example is named "SWC" and
> >>> contains 33
> >>> points, and there is no real maximum.
> >>>
> >>> I hope this helps.  Please let us know if you have other
questions.
> >>>
> >>> Thanks,
> >>> Julie
> >>>
> >>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
> >>> <met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hello Julie,
> >>>>
> >>>> I have further questions about Madis2nc use. I would like to
use
> >>>> the
> >>>> '-mask_grid string' option. However there are very limited
details
> >>>> on
> >>>> how define the polyline masking file in the user guide. I
should
> >>>> like to
> >>>> define the polyline masking file for Europe and especially for
> >>>> France.
> >>>>
> >>>> Thank you in advance,
> >>>>
> >>>> Regards.
> >>>>
> >>>> Adrien
> >>>>
> >>>>
> >>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>>>> According to our records, your request has been resolved. If
you
> >>>>> have
> >> any
> >>>>> further questions or concerns, please respond to this message.
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95
> >>>> 15 |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15
> >> | E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>



------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Wed Sep 13 11:28:58 2017

Hi Howard.  Thank you!  Do you know if there is a way he can get past
this
easily?

Thanks,
Julie

On Wed, Sep 13, 2017 at 11:24 AM, Howard Soh via RT <
met_help-comment at rap.ucar.edu> wrote:

> The global attribute Conventions from NetCDF:
>         :Conventions = "CF 1.6, Standard Name Table v19" ;
>
> Our code only checks "CF-" as NCCF file. I will allow "CF ", too.
>
> Cheers,
> Howard
>
>
> On Wed Sep 13 09:57:24 2017, amichel at atmoterra.com wrote:
> > Hi Julie,
> >
> > Many thank, I have done as you suggested and MET seems to read my
CF
> > Compliant. However, I still have issues with the configuration of
> > Point-Stat.
> >
> > So I  uploaded my file (name file: michel_data)
> > - a forecast file (WRF file - CF compliance) - daily file for
2013-01-
> > 01
> >
> > I would also provide you :
> > - point observation file from Madis2nc - hourly file for 2013-01-
> > 01_02:00:00
> > - Point-Stat configuration
> >
> > I'm grateful for you help.
> > Regards,
> >
> > Adrien Michel
> >
> >
> > Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> > > Hi Adrien.
> > >
> > > It is difficult to tell the problem with the file without seeing
it.
> > > However, I have something for you to try that might work.  MET
should
> > > be
> > > able to read CF compliant files, and you have stated that your
NetCDF
> > > file
> > > is CF Compliant.  MET tries to figure out the type of file, but
since
> > > it is
> > > having trouble, let's try explicitly telling the tools how to
process
> > > the
> > > data by setting the following in your PointStat config file:
> > >
> > > file_type = NETCDF_NCCF;
> > >
> > > This entry should be defined within the "fcst" dictionary.  For
> > > example:
> > >
> > > fcst = {
> > > file_type = NETCDF_NCCF;
> > > ...
> > > }
> > >
> > > If that works, please let us know.  If that does not work,
please
> > > upload
> > > your file to our ftp server using the following instructions and
let
> > > us
> > > know once you have done that so that we can get the file and
take a
> > > look.
> > >
> > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >
> > > Thanks!
> > >
> > > Julie
> > >
> > >
> > > On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
> > > <met_help at ucar.edu>
> > > wrote:
> > >
> > >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> > >>
> > >> Hi Julie.
> > >>
> > >> I've done as you suggested and it ran without problem, thank
you!
> > >>
> > >> I come up with a another issue.. I'm trying to use Point-Stat :
> > >> - a forecast file (WRF file - CF compliance)
> > >> - a point observation file coming from Madis2nc
> > >>
> > >> However, Point Stat seems to have issue to read my forecast
file
> > >> with
> > >> the following informations:
> > >>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> > >>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> > >>> met-6.0/data/Test/PointStatConfig -outdir
> > >>> /met-6.0/data/Point_Stat_Test -v 5
> > >>> DEBUG 1: Default Config File:
> > >>> /usr/local/share/met/config/PointStatConfig_default
> > >>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> > >>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> > >>> new
> > >>> Met2dDataFile object of type "FileType_None".
> > >>> ERROR  :
> > >>> ERROR  : Trouble reading forecast file
> > >>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> > >>> ERROR  :
> > >> I was wondering if you had any insight on what I could be doing
> > >> wrong. I
> > >> appreciate any help you can give.
> > >> Thanks,
> > >>
> > >> Adrien Michel/
> > >>
> > >>
> > >> /
> > >> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> > >>> Hi Adrien.
> > >>>
> > >>> I see that you have a question about how to define a polyline
> > >>> masking
> > >>> file.  The -mask_grid option would take a named grid or a
gridded
> > >>> data
> > >>> file, while the -mask_poly option would definite a polyline
masking
> > >>> file.
> > >>>
> > >>> If you'd only like to keep the points falling inside your
model
> > >>> domain,
> > >> and
> > >>> you have a gridded data file on that domain, using -mask_grid
is
> > >>> very
> > >>> simple:
> > >>>      -mask_grid /path/to/gridded/data/file
> > >>>
> > >>> However, if you'd prefer the flexibility of defining a
polyline
> > >>> masking
> > >>> region, using -mask_poly would work too:
> > >>>      -mask_poly /path/to/polyline/mask/file
> > >>>
> > >>> To create a polyline mask, you simply create an ASCII file
> > >>> containing a
> > >>> list of lat/lons that define the region of interest.  For
example,
> > >>> take a
> > >>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
> > >>> specifies
> > >>> the name for the polyline, and the remaining lines contain
lat/lon
> > >>> values
> > >>> for the boundary points.  The last point is connected back up
to
> > >>> the
> > >> first
> > >>> point to complete the area.  The example is named "SWC" and
> > >>> contains 33
> > >>> points, and there is no real maximum.
> > >>>
> > >>> I hope this helps.  Please let us know if you have other
questions.
> > >>>
> > >>> Thanks,
> > >>> Julie
> > >>>
> > >>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
> > >>> <met_help at ucar.edu
> > >>>
> > >>> wrote:
> > >>>
> > >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> > >>>>
> > >>>> Hello Julie,
> > >>>>
> > >>>> I have further questions about Madis2nc use. I would like to
use
> > >>>> the
> > >>>> '-mask_grid string' option. However there are very limited
details
> > >>>> on
> > >>>> how define the polyline masking file in the user guide. I
should
> > >>>> like to
> > >>>> define the polyline masking file for Europe and especially
for
> > >>>> France.
> > >>>>
> > >>>> Thank you in advance,
> > >>>>
> > >>>> Regards.
> > >>>>
> > >>>> Adrien
> > >>>>
> > >>>>
> > >>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> > >>>>> According to our records, your request has been resolved. If
you
> > >>>>> have
> > >> any
> > >>>>> further questions or concerns, please respond to this
message.
> > >>>> --
> > >>>> Adrien Michel
> > >>>> Environmental Consultant | Consultant Environnement
> > >>>>
> > >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95
> > >>>> 15 |
> > >> E:
> > >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >>>> Website: http://www.atmoterra.com
> > >>>>
> > >>>>
> > >> --
> > >> Adrien Michel
> > >> Environmental Consultant | Consultant Environnement
> > >>
> > >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> > >> | E:
> > >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >> Website: http://www.atmoterra.com
> > >>
> > >>
>
>
>
>

------------------------------------------------
Subject: Re: [Comment] Re: [rt.rap.ucar.edu #81768] Met_v6 - Issues using Point Stat
From: Howard Soh
Time: Wed Sep 13 12:02:51 2017

http://www.unidata.ucar.edu/software/netcdf/conventions.html

It is possible for a netCDF file to adhere to more than one set of
conventions, even when there is no inheritance relationship among the
conventions. In this case, the value of the `Conventions' attribute
may
be a single text string containing a list of the convention names
separated by blank space (recommended) or commas (if a convention name
contains blanks), for example

     :Conventions = "XXX YYY" ;

So, "CF 1.6," is interpreted as two convention sets: "CF" and "1.6".
The expected value for Conventions attribute is "CF-X.Y", X and Y as
CF
version numbers.

Step 1 Check the global attribute

ncdump -h wrfpot_cf_2013-01-01.nc | grep Conventions

                 :Conventions = "CF 1.6, Standard Name Table v19" ;


Step 2. Change the global attribute

         :Conventions = "CF 1.6, Standard Name Table v19" ;

==>
         :Conventions = "CF-1.6, Standard Name Table v19" ;


For example:
ncatted -a Conventions,global,m,c,"CF-1.6, Standard Name Table v19"
wrfpot_cf_2013-01-01.nc wrfpot_cf_2013-01-01.new.nc
mv wrfpot_cf_2013-01-01.new.nc wrfpot_cf_2013-01-01.nc

Cheers,
Howard

On 9/13/2017 11:28 AM, Julie Prestopnik via RT wrote:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> This is a comment.  It is not sent to the Requestor(s):
>
> Hi Howard.  Thank you!  Do you know if there is a way he can get
past this
> easily?
>
> Thanks,
> Julie
>
> On Wed, Sep 13, 2017 at 11:24 AM, Howard Soh via RT <
> met_help-comment at rap.ucar.edu> wrote:
>
>> The global attribute Conventions from NetCDF:
>>          :Conventions = "CF 1.6, Standard Name Table v19" ;
>>
>> Our code only checks "CF-" as NCCF file. I will allow "CF ", too.
>>
>> Cheers,
>> Howard
>>
>>
>> On Wed Sep 13 09:57:24 2017, amichel at atmoterra.com wrote:
>>> Hi Julie,
>>>
>>> Many thank, I have done as you suggested and MET seems to read my
CF
>>> Compliant. However, I still have issues with the configuration of
>>> Point-Stat.
>>>
>>> So I  uploaded my file (name file: michel_data)
>>> - a forecast file (WRF file - CF compliance) - daily file for
2013-01-
>>> 01
>>>
>>> I would also provide you :
>>> - point observation file from Madis2nc - hourly file for 2013-01-
>>> 01_02:00:00
>>> - Point-Stat configuration
>>>
>>> I'm grateful for you help.
>>> Regards,
>>>
>>> Adrien Michel
>>>
>>>
>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>> Hi Adrien.
>>>>
>>>> It is difficult to tell the problem with the file without seeing
it.
>>>> However, I have something for you to try that might work.  MET
should
>>>> be
>>>> able to read CF compliant files, and you have stated that your
NetCDF
>>>> file
>>>> is CF Compliant.  MET tries to figure out the type of file, but
since
>>>> it is
>>>> having trouble, let's try explicitly telling the tools how to
process
>>>> the
>>>> data by setting the following in your PointStat config file:
>>>>
>>>> file_type = NETCDF_NCCF;
>>>>
>>>> This entry should be defined within the "fcst" dictionary.  For
>>>> example:
>>>>
>>>> fcst = {
>>>> file_type = NETCDF_NCCF;
>>>> ...
>>>> }
>>>>
>>>> If that works, please let us know.  If that does not work, please
>>>> upload
>>>> your file to our ftp server using the following instructions and
let
>>>> us
>>>> know once you have done that so that we can get the file and take
a
>>>> look.
>>>>
>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>
>>>> Thanks!
>>>>
>>>> Julie
>>>>
>>>>
>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
>>>> <met_help at ucar.edu>
>>>> wrote:
>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>
>>>>> Hi Julie.
>>>>>
>>>>> I've done as you suggested and it ran without problem, thank
you!
>>>>>
>>>>> I come up with a another issue.. I'm trying to use Point-Stat :
>>>>> - a forecast file (WRF file - CF compliance)
>>>>> - a point observation file coming from Madis2nc
>>>>>
>>>>> However, Point Stat seems to have issue to read my forecast file
>>>>> with
>>>>> the following informations:
>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>> DEBUG 1: Default Config File:
>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>>>>>> new
>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>> ERROR  :
>>>>>> ERROR  : Trouble reading forecast file
>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>> ERROR  :
>>>>> I was wondering if you had any insight on what I could be doing
>>>>> wrong. I
>>>>> appreciate any help you can give.
>>>>> Thanks,
>>>>>
>>>>> Adrien Michel/
>>>>>
>>>>>
>>>>> /
>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>>> Hi Adrien.
>>>>>>
>>>>>> I see that you have a question about how to define a polyline
>>>>>> masking
>>>>>> file.  The -mask_grid option would take a named grid or a
gridded
>>>>>> data
>>>>>> file, while the -mask_poly option would definite a polyline
masking
>>>>>> file.
>>>>>>
>>>>>> If you'd only like to keep the points falling inside your model
>>>>>> domain,
>>>>> and
>>>>>> you have a gridded data file on that domain, using -mask_grid
is
>>>>>> very
>>>>>> simple:
>>>>>>       -mask_grid /path/to/gridded/data/file
>>>>>>
>>>>>> However, if you'd prefer the flexibility of defining a polyline
>>>>>> masking
>>>>>> region, using -mask_poly would work too:
>>>>>>       -mask_poly /path/to/polyline/mask/file
>>>>>>
>>>>>> To create a polyline mask, you simply create an ASCII file
>>>>>> containing a
>>>>>> list of lat/lons that define the region of interest.  For
example,
>>>>>> take a
>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the file
>>>>>> specifies
>>>>>> the name for the polyline, and the remaining lines contain
lat/lon
>>>>>> values
>>>>>> for the boundary points.  The last point is connected back up
to
>>>>>> the
>>>>> first
>>>>>> point to complete the area.  The example is named "SWC" and
>>>>>> contains 33
>>>>>> points, and there is no real maximum.
>>>>>>
>>>>>> I hope this helps.  Please let us know if you have other
questions.
>>>>>>
>>>>>> Thanks,
>>>>>> Julie
>>>>>>
>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
>>>>>> <met_help at ucar.edu
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>
>>>>>>> Hello Julie,
>>>>>>>
>>>>>>> I have further questions about Madis2nc use. I would like to
use
>>>>>>> the
>>>>>>> '-mask_grid string' option. However there are very limited
details
>>>>>>> on
>>>>>>> how define the polyline masking file in the user guide. I
should
>>>>>>> like to
>>>>>>> define the polyline masking file for Europe and especially for
>>>>>>> France.
>>>>>>>
>>>>>>> Thank you in advance,
>>>>>>>
>>>>>>> Regards.
>>>>>>>
>>>>>>> Adrien
>>>>>>>
>>>>>>>
>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>>>>>>> According to our records, your request has been resolved. If
you
>>>>>>>> have
>>>>> any
>>>>>>>> further questions or concerns, please respond to this
message.
>>>>>>> --
>>>>>>> Adrien Michel
>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>
>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95
>>>>>>> 15 |
>>>>> E:
>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>> Website: http://www.atmoterra.com
>>>>>>>
>>>>>>>
>>>>> --
>>>>> Adrien Michel
>>>>> Environmental Consultant | Consultant Environnement
>>>>>
>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15
>>>>> | E:
>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>> Website: http://www.atmoterra.com
>>>>>
>>>>>
>>
>>
>>


------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Wed Sep 13 12:13:07 2017

Thank you, Howard.  I decided to try to run point_stat here, and I see
that
our code actually gets passed the point that his does with only a
warning
about a variable name, so I think our future code handles this file
and he
just needs to update.  I'll follow up once I have verified this.

Thanks for your help.

Julie

On Wed, Sep 13, 2017 at 12:02 PM, Howard Soh via RT <
met_help-comment at rap.ucar.edu> wrote:

>
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> This is a comment.  It is not sent to the Requestor(s):
>
> http://www.unidata.ucar.edu/software/netcdf/conventions.html
>
> It is possible for a netCDF file to adhere to more than one set of
> conventions, even when there is no inheritance relationship among
the
> conventions. In this case, the value of the `Conventions' attribute
may
> be a single text string containing a list of the convention names
> separated by blank space (recommended) or commas (if a convention
name
> contains blanks), for example
>
>      :Conventions = "XXX YYY" ;
>
> So, "CF 1.6," is interpreted as two convention sets: "CF" and "1.6".
> The expected value for Conventions attribute is "CF-X.Y", X and Y as
CF
> version numbers.
>
> Step 1 Check the global attribute
>
> ncdump -h wrfpot_cf_2013-01-01.nc | grep Conventions
>
>                  :Conventions = "CF 1.6, Standard Name Table v19" ;
>
>
> Step 2. Change the global attribute
>
>          :Conventions = "CF 1.6, Standard Name Table v19" ;
>
> ==>
>          :Conventions = "CF-1.6, Standard Name Table v19" ;
>
>
> For example:
> ncatted -a Conventions,global,m,c,"CF-1.6, Standard Name Table v19"
> wrfpot_cf_2013-01-01.nc wrfpot_cf_2013-01-01.new.nc
> mv wrfpot_cf_2013-01-01.new.nc wrfpot_cf_2013-01-01.nc
>
> Cheers,
> Howard
>
> On 9/13/2017 11:28 AM, Julie Prestopnik via RT wrote:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> > This is a comment.  It is not sent to the Requestor(s):
> >
> > Hi Howard.  Thank you!  Do you know if there is a way he can get
past
> this
> > easily?
> >
> > Thanks,
> > Julie
> >
> > On Wed, Sep 13, 2017 at 11:24 AM, Howard Soh via RT <
> > met_help-comment at rap.ucar.edu> wrote:
> >
> >> The global attribute Conventions from NetCDF:
> >>          :Conventions = "CF 1.6, Standard Name Table v19" ;
> >>
> >> Our code only checks "CF-" as NCCF file. I will allow "CF ", too.
> >>
> >> Cheers,
> >> Howard
> >>
> >>
> >> On Wed Sep 13 09:57:24 2017, amichel at atmoterra.com wrote:
> >>> Hi Julie,
> >>>
> >>> Many thank, I have done as you suggested and MET seems to read
my CF
> >>> Compliant. However, I still have issues with the configuration
of
> >>> Point-Stat.
> >>>
> >>> So I  uploaded my file (name file: michel_data)
> >>> - a forecast file (WRF file - CF compliance) - daily file for
2013-01-
> >>> 01
> >>>
> >>> I would also provide you :
> >>> - point observation file from Madis2nc - hourly file for 2013-
01-
> >>> 01_02:00:00
> >>> - Point-Stat configuration
> >>>
> >>> I'm grateful for you help.
> >>> Regards,
> >>>
> >>> Adrien Michel
> >>>
> >>>
> >>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> >>>> Hi Adrien.
> >>>>
> >>>> It is difficult to tell the problem with the file without
seeing it.
> >>>> However, I have something for you to try that might work.  MET
should
> >>>> be
> >>>> able to read CF compliant files, and you have stated that your
NetCDF
> >>>> file
> >>>> is CF Compliant.  MET tries to figure out the type of file, but
since
> >>>> it is
> >>>> having trouble, let's try explicitly telling the tools how to
process
> >>>> the
> >>>> data by setting the following in your PointStat config file:
> >>>>
> >>>> file_type = NETCDF_NCCF;
> >>>>
> >>>> This entry should be defined within the "fcst" dictionary.  For
> >>>> example:
> >>>>
> >>>> fcst = {
> >>>> file_type = NETCDF_NCCF;
> >>>> ...
> >>>> }
> >>>>
> >>>> If that works, please let us know.  If that does not work,
please
> >>>> upload
> >>>> your file to our ftp server using the following instructions
and let
> >>>> us
> >>>> know once you have done that so that we can get the file and
take a
> >>>> look.
> >>>>
> >>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>
> >>>> Thanks!
> >>>>
> >>>> Julie
> >>>>
> >>>>
> >>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
> >>>> <met_help at ucar.edu>
> >>>> wrote:
> >>>>
> >>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>
> >>>>> Hi Julie.
> >>>>>
> >>>>> I've done as you suggested and it ran without problem, thank
you!
> >>>>>
> >>>>> I come up with a another issue.. I'm trying to use Point-Stat
:
> >>>>> - a forecast file (WRF file - CF compliance)
> >>>>> - a point observation file coming from Madis2nc
> >>>>>
> >>>>> However, Point Stat seems to have issue to read my forecast
file
> >>>>> with
> >>>>> the following informations:
> >>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>> DEBUG 1: Default Config File:
> >>>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> >>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> >>>>>> new
> >>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>> ERROR  :
> >>>>>> ERROR  : Trouble reading forecast file
> >>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>> ERROR  :
> >>>>> I was wondering if you had any insight on what I could be
doing
> >>>>> wrong. I
> >>>>> appreciate any help you can give.
> >>>>> Thanks,
> >>>>>
> >>>>> Adrien Michel/
> >>>>>
> >>>>>
> >>>>> /
> >>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>>>>> Hi Adrien.
> >>>>>>
> >>>>>> I see that you have a question about how to define a polyline
> >>>>>> masking
> >>>>>> file.  The -mask_grid option would take a named grid or a
gridded
> >>>>>> data
> >>>>>> file, while the -mask_poly option would definite a polyline
masking
> >>>>>> file.
> >>>>>>
> >>>>>> If you'd only like to keep the points falling inside your
model
> >>>>>> domain,
> >>>>> and
> >>>>>> you have a gridded data file on that domain, using -mask_grid
is
> >>>>>> very
> >>>>>> simple:
> >>>>>>       -mask_grid /path/to/gridded/data/file
> >>>>>>
> >>>>>> However, if you'd prefer the flexibility of defining a
polyline
> >>>>>> masking
> >>>>>> region, using -mask_poly would work too:
> >>>>>>       -mask_poly /path/to/polyline/mask/file
> >>>>>>
> >>>>>> To create a polyline mask, you simply create an ASCII file
> >>>>>> containing a
> >>>>>> list of lat/lons that define the region of interest.  For
example,
> >>>>>> take a
> >>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
> >>>>>> specifies
> >>>>>> the name for the polyline, and the remaining lines contain
lat/lon
> >>>>>> values
> >>>>>> for the boundary points.  The last point is connected back up
to
> >>>>>> the
> >>>>> first
> >>>>>> point to complete the area.  The example is named "SWC" and
> >>>>>> contains 33
> >>>>>> points, and there is no real maximum.
> >>>>>>
> >>>>>> I hope this helps.  Please let us know if you have other
questions.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Julie
> >>>>>>
> >>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
> >>>>>> <met_help at ucar.edu
> >>>>>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>
> >>>>>>> Hello Julie,
> >>>>>>>
> >>>>>>> I have further questions about Madis2nc use. I would like to
use
> >>>>>>> the
> >>>>>>> '-mask_grid string' option. However there are very limited
details
> >>>>>>> on
> >>>>>>> how define the polyline masking file in the user guide. I
should
> >>>>>>> like to
> >>>>>>> define the polyline masking file for Europe and especially
for
> >>>>>>> France.
> >>>>>>>
> >>>>>>> Thank you in advance,
> >>>>>>>
> >>>>>>> Regards.
> >>>>>>>
> >>>>>>> Adrien
> >>>>>>>
> >>>>>>>
> >>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>>>>>>> According to our records, your request has been resolved.
If you
> >>>>>>>> have
> >>>>> any
> >>>>>>>> further questions or concerns, please respond to this
message.
> >>>>>>> --
> >>>>>>> Adrien Michel
> >>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>
> >>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> >>>>>>> 15 |
> >>>>> E:
> >>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>> Website: http://www.atmoterra.com
> >>>>>>>
> >>>>>>>
> >>>>> --
> >>>>> Adrien Michel
> >>>>> Environmental Consultant | Consultant Environnement
> >>>>>
> >>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> >>>>> | E:
> >>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>> Website: http://www.atmoterra.com
> >>>>>
> >>>>>
> >>
> >>
> >>
>
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Wed Sep 13 14:03:12 2017

Hi Adrien.

I'm glad MET was able to read your CF compliant file.  Thank you for
uploading your data.

When I run point_stat with your data and configuration file, I see the
following warning:

DEBUG 2: Reading data for T_sfc(0,*,*).
WARNING:
WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc" variable, the
lead
time does not match the requested lead time: (000000 != 020000)
WARNING:
WARNING:
WARNING: process_fcst_climo_files() -> no fields matching T_sfc(0,*,*)
found in file: wrfpot_cf_2013-01-01.nc
WARNING:

There is a specific way in the CF-convention of specifying the
initialization time of the model.  You do so by defining a variable
named
"forecast_reference_time".  When that variable is not present, MET
sets the
forecast initialization time to the same value as the valid time,
which
results in a lead time of 0.

You need to add the "forecast_reference_time" variable to your model
files.  Take a look at this previous met_help ticket and see if that
helps:

http://mailman.ucar.edu/pipermail/met_help/2017-May/002867.html

Also, I see in your PointStatConfig file that you have defined
"lead_time"
in the fcst dictionary.  That is not necessary and could cause
problems.
MET determines the lead time by the time index of the time dimension
that
you specify in the "level" field:

        level      = "(0,*,*)";

I hope that helps.  Please let us know if you have any other
questions.

Thanks,
Julie




On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi Julie,
>
> Many thank, I have done as you suggested and MET seems to read my CF
> Compliant. However, I still have issues with the configuration of
> Point-Stat.
>
> So I  uploaded my file (name file: michel_data)
> - a forecast file (WRF file - CF compliance) - daily file for 2013-
01-01
>
> I would also provide you :
> - point observation file from Madis2nc - hourly file for
> 2013-01-01_02:00:00
> - Point-Stat configuration
>
> I'm grateful for you help.
> Regards,
>
> Adrien Michel
>
>
> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > It is difficult to tell the problem with the file without seeing
it.
> > However, I have something for you to try that might work.  MET
should be
> > able to read CF compliant files, and you have stated that your
NetCDF
> file
> > is CF Compliant.  MET tries to figure out the type of file, but
since it
> is
> > having trouble, let's try explicitly telling the tools how to
process the
> > data by setting the following in your PointStat config file:
> >
> > file_type = NETCDF_NCCF;
> >
> > This entry should be defined within the "fcst" dictionary.  For
example:
> >
> > fcst = {
> > file_type = NETCDF_NCCF;
> > ...
> > }
> >
> > If that works, please let us know.  If that does not work, please
upload
> > your file to our ftp server using the following instructions and
let us
> > know once you have done that so that we can get the file and take
a look.
> >
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > Thanks!
> >
> > Julie
> >
> >
> > On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hi Julie.
> >>
> >>    I've done as you suggested and it ran without problem, thank
you!
> >>
> >> I come up with a another issue.. I'm trying to use Point-Stat :
> >> - a forecast file (WRF file - CF compliance)
> >> - a point observation file coming from Madis2nc
> >>
> >> However, Point Stat seems to have issue to read my forecast file
with
> >> the following informations:
> >>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>> met-6.0/data/Test/PointStatConfig -outdir
> >>> /met-6.0/data/Point_Stat_Test -v 5
> >>> DEBUG 1: Default Config File:
> >>> /usr/local/share/met/config/PointStatConfig_default
> >>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> >>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
> >>> Met2dDataFile object of type "FileType_None".
> >>> ERROR  :
> >>> ERROR  : Trouble reading forecast file
> >>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>> ERROR  :
> >> I was wondering if you had any insight on what I could be doing
wrong. I
> >> appreciate any help you can give.
> >> Thanks,
> >>
> >> Adrien Michel/
> >>
> >>
> >> /
> >> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> I see that you have a question about how to define a polyline
masking
> >>> file.  The -mask_grid option would take a named grid or a
gridded data
> >>> file, while the -mask_poly option would definite a polyline
masking
> file.
> >>>
> >>> If you'd only like to keep the points falling inside your model
domain,
> >> and
> >>> you have a gridded data file on that domain, using -mask_grid is
very
> >>> simple:
> >>>      -mask_grid /path/to/gridded/data/file
> >>>
> >>> However, if you'd prefer the flexibility of defining a polyline
masking
> >>> region, using -mask_poly would work too:
> >>>      -mask_poly /path/to/polyline/mask/file
> >>>
> >>> To create a polyline mask, you simply create an ASCII file
containing a
> >>> list of lat/lons that define the region of interest.  For
example,
> take a
> >>> look in met-6.0/data/poly/SWC.poly.  The first line of the file
> specifies
> >>> the name for the polyline, and the remaining lines contain
lat/lon
> values
> >>> for the boundary points.  The last point is connected back up to
the
> >> first
> >>> point to complete the area.  The example is named "SWC" and
contains 33
> >>> points, and there is no real maximum.
> >>>
> >>> I hope this helps.  Please let us know if you have other
questions.
> >>>
> >>> Thanks,
> >>> Julie
> >>>
> >>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hello Julie,
> >>>>
> >>>> I have further questions about Madis2nc use. I would like to
use the
> >>>> '-mask_grid string' option. However there are very limited
details on
> >>>> how define the polyline masking file in the user guide. I
should like
> to
> >>>> define the polyline masking file for Europe and especially for
France.
> >>>>
> >>>> Thank you in advance,
> >>>>
> >>>> Regards.
> >>>>
> >>>> Adrien
> >>>>
> >>>>
> >>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>>>> According to our records, your request has been resolved. If
you have
> >> any
> >>>>> further questions or concerns, please respond to this message.
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Fri Sep 15 08:42:48 2017

Hi Julie,

Thanks to the previous met_help ticket, now that worked perfectly ! I
am
so grateful for your help, thank you. Now I will adapt this method for
all my data.

Another time, thank you. I'll definitely let you know if I have others
questions.

Best regards,

Adrien

Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> Hi Adrien.
>
> I'm glad MET was able to read your CF compliant file.  Thank you for
> uploading your data.
>
> When I run point_stat with your data and configuration file, I see
the
> following warning:
>
> DEBUG 2: Reading data for T_sfc(0,*,*).
> WARNING:
> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc" variable, the
lead
> time does not match the requested lead time: (000000 != 020000)
> WARNING:
> WARNING:
> WARNING: process_fcst_climo_files() -> no fields matching
T_sfc(0,*,*)
> found in file: wrfpot_cf_2013-01-01.nc
> WARNING:
>
> There is a specific way in the CF-convention of specifying the
> initialization time of the model.  You do so by defining a variable
named
> "forecast_reference_time".  When that variable is not present, MET
sets the
> forecast initialization time to the same value as the valid time,
which
> results in a lead time of 0.
>
> You need to add the "forecast_reference_time" variable to your model
> files.  Take a look at this previous met_help ticket and see if that
helps:
>
> http://mailman.ucar.edu/pipermail/met_help/2017-May/002867.html
>
> Also, I see in your PointStatConfig file that you have defined
"lead_time"
> in the fcst dictionary.  That is not necessary and could cause
problems.
> MET determines the lead time by the time index of the time dimension
that
> you specify in the "level" field:
>
>          level      = "(0,*,*)";
>
> I hope that helps.  Please let us know if you have any other
questions.
>
> Thanks,
> Julie
>
>
>
>
> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hi Julie,
>>
>> Many thank, I have done as you suggested and MET seems to read my
CF
>> Compliant. However, I still have issues with the configuration of
>> Point-Stat.
>>
>> So I  uploaded my file (name file: michel_data)
>> - a forecast file (WRF file - CF compliance) - daily file for 2013-
01-01
>>
>> I would also provide you :
>> - point observation file from Madis2nc - hourly file for
>> 2013-01-01_02:00:00
>> - Point-Stat configuration
>>
>> I'm grateful for you help.
>> Regards,
>>
>> Adrien Michel
>>
>>
>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>> Hi Adrien.
>>>
>>> It is difficult to tell the problem with the file without seeing
it.
>>> However, I have something for you to try that might work.  MET
should be
>>> able to read CF compliant files, and you have stated that your
NetCDF
>> file
>>> is CF Compliant.  MET tries to figure out the type of file, but
since it
>> is
>>> having trouble, let's try explicitly telling the tools how to
process the
>>> data by setting the following in your PointStat config file:
>>>
>>> file_type = NETCDF_NCCF;
>>>
>>> This entry should be defined within the "fcst" dictionary.  For
example:
>>>
>>> fcst = {
>>> file_type = NETCDF_NCCF;
>>> ...
>>> }
>>>
>>> If that works, please let us know.  If that does not work, please
upload
>>> your file to our ftp server using the following instructions and
let us
>>> know once you have done that so that we can get the file and take
a look.
>>>
>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>
>>> Thanks!
>>>
>>> Julie
>>>
>>>
>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hi Julie.
>>>>
>>>>     I've done as you suggested and it ran without problem, thank
you!
>>>>
>>>> I come up with a another issue.. I'm trying to use Point-Stat :
>>>> - a forecast file (WRF file - CF compliance)
>>>> - a point observation file coming from Madis2nc
>>>>
>>>> However, Point Stat seems to have issue to read my forecast file
with
>>>> the following informations:
>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>> DEBUG 1: Default Config File:
>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created
new
>>>>> Met2dDataFile object of type "FileType_None".
>>>>> ERROR  :
>>>>> ERROR  : Trouble reading forecast file
>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>> ERROR  :
>>>> I was wondering if you had any insight on what I could be doing
wrong. I
>>>> appreciate any help you can give.
>>>> Thanks,
>>>>
>>>> Adrien Michel/
>>>>
>>>>
>>>> /
>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>> Hi Adrien.
>>>>>
>>>>> I see that you have a question about how to define a polyline
masking
>>>>> file.  The -mask_grid option would take a named grid or a
gridded data
>>>>> file, while the -mask_poly option would definite a polyline
masking
>> file.
>>>>> If you'd only like to keep the points falling inside your model
domain,
>>>> and
>>>>> you have a gridded data file on that domain, using -mask_grid is
very
>>>>> simple:
>>>>>       -mask_grid /path/to/gridded/data/file
>>>>>
>>>>> However, if you'd prefer the flexibility of defining a polyline
masking
>>>>> region, using -mask_poly would work too:
>>>>>       -mask_poly /path/to/polyline/mask/file
>>>>>
>>>>> To create a polyline mask, you simply create an ASCII file
containing a
>>>>> list of lat/lons that define the region of interest.  For
example,
>> take a
>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the file
>> specifies
>>>>> the name for the polyline, and the remaining lines contain
lat/lon
>> values
>>>>> for the boundary points.  The last point is connected back up to
the
>>>> first
>>>>> point to complete the area.  The example is named "SWC" and
contains 33
>>>>> points, and there is no real maximum.
>>>>>
>>>>> I hope this helps.  Please let us know if you have other
questions.
>>>>>
>>>>> Thanks,
>>>>> Julie
>>>>>
>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hello Julie,
>>>>>>
>>>>>> I have further questions about Madis2nc use. I would like to
use the
>>>>>> '-mask_grid string' option. However there are very limited
details on
>>>>>> how define the polyline masking file in the user guide. I
should like
>> to
>>>>>> define the polyline masking file for Europe and especially for
France.
>>>>>>
>>>>>> Thank you in advance,
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>> Adrien
>>>>>>
>>>>>>
>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>>>>>> According to our records, your request has been resolved. If
you have
>>>> any
>>>>>>> further questions or concerns, please respond to this message.
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
>>>> E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
>> E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Fri Sep 15 10:20:32 2017

I'm glad to hear it, Adrien!  Thank you for letting us know.

Julie

On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi Julie,
>
> Thanks to the previous met_help ticket, now that worked perfectly !
I am
> so grateful for your help, thank you. Now I will adapt this method
for
> all my data.
>
> Another time, thank you. I'll definitely let you know if I have
others
> questions.
>
> Best regards,
>
> Adrien
>
> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > I'm glad MET was able to read your CF compliant file.  Thank you
for
> > uploading your data.
> >
> > When I run point_stat with your data and configuration file, I see
the
> > following warning:
> >
> > DEBUG 2: Reading data for T_sfc(0,*,*).
> > WARNING:
> > WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc" variable,
the lead
> > time does not match the requested lead time: (000000 != 020000)
> > WARNING:
> > WARNING:
> > WARNING: process_fcst_climo_files() -> no fields matching
T_sfc(0,*,*)
> > found in file: wrfpot_cf_2013-01-01.nc
> > WARNING:
> >
> > There is a specific way in the CF-convention of specifying the
> > initialization time of the model.  You do so by defining a
variable named
> > "forecast_reference_time".  When that variable is not present, MET
sets
> the
> > forecast initialization time to the same value as the valid time,
which
> > results in a lead time of 0.
> >
> > You need to add the "forecast_reference_time" variable to your
model
> > files.  Take a look at this previous met_help ticket and see if
that
> helps:
> >
> > http://mailman.ucar.edu/pipermail/met_help/2017-May/002867.html
> >
> > Also, I see in your PointStatConfig file that you have defined
> "lead_time"
> > in the fcst dictionary.  That is not necessary and could cause
problems.
> > MET determines the lead time by the time index of the time
dimension that
> > you specify in the "level" field:
> >
> >          level      = "(0,*,*)";
> >
> > I hope that helps.  Please let us know if you have any other
questions.
> >
> > Thanks,
> > Julie
> >
> >
> >
> >
> > On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hi Julie,
> >>
> >> Many thank, I have done as you suggested and MET seems to read my
CF
> >> Compliant. However, I still have issues with the configuration of
> >> Point-Stat.
> >>
> >> So I  uploaded my file (name file: michel_data)
> >> - a forecast file (WRF file - CF compliance) - daily file for
2013-01-01
> >>
> >> I would also provide you :
> >> - point observation file from Madis2nc - hourly file for
> >> 2013-01-01_02:00:00
> >> - Point-Stat configuration
> >>
> >> I'm grateful for you help.
> >> Regards,
> >>
> >> Adrien Michel
> >>
> >>
> >> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> It is difficult to tell the problem with the file without seeing
it.
> >>> However, I have something for you to try that might work.  MET
should
> be
> >>> able to read CF compliant files, and you have stated that your
NetCDF
> >> file
> >>> is CF Compliant.  MET tries to figure out the type of file, but
since
> it
> >> is
> >>> having trouble, let's try explicitly telling the tools how to
process
> the
> >>> data by setting the following in your PointStat config file:
> >>>
> >>> file_type = NETCDF_NCCF;
> >>>
> >>> This entry should be defined within the "fcst" dictionary.  For
> example:
> >>>
> >>> fcst = {
> >>> file_type = NETCDF_NCCF;
> >>> ...
> >>> }
> >>>
> >>> If that works, please let us know.  If that does not work,
please
> upload
> >>> your file to our ftp server using the following instructions and
let us
> >>> know once you have done that so that we can get the file and
take a
> look.
> >>>
> >>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>
> >>> Thanks!
> >>>
> >>> Julie
> >>>
> >>>
> >>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hi Julie.
> >>>>
> >>>>     I've done as you suggested and it ran without problem,
thank you!
> >>>>
> >>>> I come up with a another issue.. I'm trying to use Point-Stat :
> >>>> - a forecast file (WRF file - CF compliance)
> >>>> - a point observation file coming from Madis2nc
> >>>>
> >>>> However, Point Stat seems to have issue to read my forecast
file with
> >>>> the following informations:
> >>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>> DEBUG 1: Default Config File:
> >>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> >>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
> >>>>> Met2dDataFile object of type "FileType_None".
> >>>>> ERROR  :
> >>>>> ERROR  : Trouble reading forecast file
> >>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>> ERROR  :
> >>>> I was wondering if you had any insight on what I could be doing
> wrong. I
> >>>> appreciate any help you can give.
> >>>> Thanks,
> >>>>
> >>>> Adrien Michel/
> >>>>
> >>>>
> >>>> /
> >>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>>>> Hi Adrien.
> >>>>>
> >>>>> I see that you have a question about how to define a polyline
masking
> >>>>> file.  The -mask_grid option would take a named grid or a
gridded
> data
> >>>>> file, while the -mask_poly option would definite a polyline
masking
> >> file.
> >>>>> If you'd only like to keep the points falling inside your
model
> domain,
> >>>> and
> >>>>> you have a gridded data file on that domain, using -mask_grid
is very
> >>>>> simple:
> >>>>>       -mask_grid /path/to/gridded/data/file
> >>>>>
> >>>>> However, if you'd prefer the flexibility of defining a
polyline
> masking
> >>>>> region, using -mask_poly would work too:
> >>>>>       -mask_poly /path/to/polyline/mask/file
> >>>>>
> >>>>> To create a polyline mask, you simply create an ASCII file
> containing a
> >>>>> list of lat/lons that define the region of interest.  For
example,
> >> take a
> >>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
> >> specifies
> >>>>> the name for the polyline, and the remaining lines contain
lat/lon
> >> values
> >>>>> for the boundary points.  The last point is connected back up
to the
> >>>> first
> >>>>> point to complete the area.  The example is named "SWC" and
contains
> 33
> >>>>> points, and there is no real maximum.
> >>>>>
> >>>>> I hope this helps.  Please let us know if you have other
questions.
> >>>>>
> >>>>> Thanks,
> >>>>> Julie
> >>>>>
> >>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hello Julie,
> >>>>>>
> >>>>>> I have further questions about Madis2nc use. I would like to
use the
> >>>>>> '-mask_grid string' option. However there are very limited
details
> on
> >>>>>> how define the polyline masking file in the user guide. I
should
> like
> >> to
> >>>>>> define the polyline masking file for Europe and especially
for
> France.
> >>>>>>
> >>>>>> Thank you in advance,
> >>>>>>
> >>>>>> Regards.
> >>>>>>
> >>>>>> Adrien
> >>>>>>
> >>>>>>
> >>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>>>>>> According to our records, your request has been resolved. If
you
> have
> >>>> any
> >>>>>>> further questions or concerns, please respond to this
message.
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> |
> >>>> E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Fri Oct 13 01:17:42 2017

Hello Julie,

I am running Madis2nc tool for hourly basis metar data. Actually I
would
like to merge these hourly data in daily file. Do you have suggestion
or
recommendation on how to do it ? Is there option for that in MET ?


Regards,

Adrien


Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> I'm glad to hear it, Adrien!  Thank you for letting us know.
>
> Julie
>
> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hi Julie,
>>
>> Thanks to the previous met_help ticket, now that worked perfectly !
I am
>> so grateful for your help, thank you. Now I will adapt this method
for
>> all my data.
>>
>> Another time, thank you. I'll definitely let you know if I have
others
>> questions.
>>
>> Best regards,
>>
>> Adrien
>>
>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>> Hi Adrien.
>>>
>>> I'm glad MET was able to read your CF compliant file.  Thank you
for
>>> uploading your data.
>>>
>>> When I run point_stat with your data and configuration file, I see
the
>>> following warning:
>>>
>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>> WARNING:
>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc" variable,
the lead
>>> time does not match the requested lead time: (000000 != 020000)
>>> WARNING:
>>> WARNING:
>>> WARNING: process_fcst_climo_files() -> no fields matching
T_sfc(0,*,*)
>>> found in file: wrfpot_cf_2013-01-01.nc
>>> WARNING:
>>>
>>> There is a specific way in the CF-convention of specifying the
>>> initialization time of the model.  You do so by defining a
variable named
>>> "forecast_reference_time".  When that variable is not present, MET
sets
>> the
>>> forecast initialization time to the same value as the valid time,
which
>>> results in a lead time of 0.
>>>
>>> You need to add the "forecast_reference_time" variable to your
model
>>> files.  Take a look at this previous met_help ticket and see if
that
>> helps:
>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/002867.html
>>>
>>> Also, I see in your PointStatConfig file that you have defined
>> "lead_time"
>>> in the fcst dictionary.  That is not necessary and could cause
problems.
>>> MET determines the lead time by the time index of the time
dimension that
>>> you specify in the "level" field:
>>>
>>>           level      = "(0,*,*)";
>>>
>>> I hope that helps.  Please let us know if you have any other
questions.
>>>
>>> Thanks,
>>> Julie
>>>
>>>
>>>
>>>
>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hi Julie,
>>>>
>>>> Many thank, I have done as you suggested and MET seems to read my
CF
>>>> Compliant. However, I still have issues with the configuration of
>>>> Point-Stat.
>>>>
>>>> So I  uploaded my file (name file: michel_data)
>>>> - a forecast file (WRF file - CF compliance) - daily file for
2013-01-01
>>>>
>>>> I would also provide you :
>>>> - point observation file from Madis2nc - hourly file for
>>>> 2013-01-01_02:00:00
>>>> - Point-Stat configuration
>>>>
>>>> I'm grateful for you help.
>>>> Regards,
>>>>
>>>> Adrien Michel
>>>>
>>>>
>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>>> Hi Adrien.
>>>>>
>>>>> It is difficult to tell the problem with the file without seeing
it.
>>>>> However, I have something for you to try that might work.  MET
should
>> be
>>>>> able to read CF compliant files, and you have stated that your
NetCDF
>>>> file
>>>>> is CF Compliant.  MET tries to figure out the type of file, but
since
>> it
>>>> is
>>>>> having trouble, let's try explicitly telling the tools how to
process
>> the
>>>>> data by setting the following in your PointStat config file:
>>>>>
>>>>> file_type = NETCDF_NCCF;
>>>>>
>>>>> This entry should be defined within the "fcst" dictionary.  For
>> example:
>>>>> fcst = {
>>>>> file_type = NETCDF_NCCF;
>>>>> ...
>>>>> }
>>>>>
>>>>> If that works, please let us know.  If that does not work,
please
>> upload
>>>>> your file to our ftp server using the following instructions and
let us
>>>>> know once you have done that so that we can get the file and
take a
>> look.
>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>
>>>>> Thanks!
>>>>>
>>>>> Julie
>>>>>
>>>>>
>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hi Julie.
>>>>>>
>>>>>>      I've done as you suggested and it ran without problem,
thank you!
>>>>>>
>>>>>> I come up with a another issue.. I'm trying to use Point-Stat :
>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>> - a point observation file coming from Madis2nc
>>>>>>
>>>>>> However, Point Stat seems to have issue to read my forecast
file with
>>>>>> the following informations:
>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>> DEBUG 1: Default Config File:
>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created new
>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>> ERROR  :
>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>> ERROR  :
>>>>>> I was wondering if you had any insight on what I could be doing
>> wrong. I
>>>>>> appreciate any help you can give.
>>>>>> Thanks,
>>>>>>
>>>>>> Adrien Michel/
>>>>>>
>>>>>>
>>>>>> /
>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>>>> Hi Adrien.
>>>>>>>
>>>>>>> I see that you have a question about how to define a polyline
masking
>>>>>>> file.  The -mask_grid option would take a named grid or a
gridded
>> data
>>>>>>> file, while the -mask_poly option would definite a polyline
masking
>>>> file.
>>>>>>> If you'd only like to keep the points falling inside your
model
>> domain,
>>>>>> and
>>>>>>> you have a gridded data file on that domain, using -mask_grid
is very
>>>>>>> simple:
>>>>>>>        -mask_grid /path/to/gridded/data/file
>>>>>>>
>>>>>>> However, if you'd prefer the flexibility of defining a
polyline
>> masking
>>>>>>> region, using -mask_poly would work too:
>>>>>>>        -mask_poly /path/to/polyline/mask/file
>>>>>>>
>>>>>>> To create a polyline mask, you simply create an ASCII file
>> containing a
>>>>>>> list of lat/lons that define the region of interest.  For
example,
>>>> take a
>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
>>>> specifies
>>>>>>> the name for the polyline, and the remaining lines contain
lat/lon
>>>> values
>>>>>>> for the boundary points.  The last point is connected back up
to the
>>>>>> first
>>>>>>> point to complete the area.  The example is named "SWC" and
contains
>> 33
>>>>>>> points, and there is no real maximum.
>>>>>>>
>>>>>>> I hope this helps.  Please let us know if you have other
questions.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Julie
>>>>>>>
>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hello Julie,
>>>>>>>>
>>>>>>>> I have further questions about Madis2nc use. I would like to
use the
>>>>>>>> '-mask_grid string' option. However there are very limited
details
>> on
>>>>>>>> how define the polyline masking file in the user guide. I
should
>> like
>>>> to
>>>>>>>> define the polyline masking file for Europe and especially
for
>> France.
>>>>>>>> Thank you in advance,
>>>>>>>>
>>>>>>>> Regards.
>>>>>>>>
>>>>>>>> Adrien
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>>>>>>>> According to our records, your request has been resolved. If
you
>> have
>>>>>> any
>>>>>>>>> further questions or concerns, please respond to this
message.
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>> |
>>>>>> E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
>>>> E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
>> E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Fri Oct 13 09:20:37 2017

Hi Adrien.

There’s no “need” to merge the files.   You can pass multiple netcdf
point
observation files to point_stat and ensemble_stat.  However, if you
would
like to merge the files, you could consider using the "ncrcat" tool:

https://linux.die.net/man/1/ncrcat

from NCO:
http://nco.sourceforge.net/

I hope that helps!

Julie

On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hello Julie,
>
> I am running Madis2nc tool for hourly basis metar data. Actually I
would
> like to merge these hourly data in daily file. Do you have
suggestion or
> recommendation on how to do it ? Is there option for that in MET ?
>
>
> Regards,
>
> Adrien
>
>
> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> > I'm glad to hear it, Adrien!  Thank you for letting us know.
> >
> > Julie
> >
> > On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hi Julie,
> >>
> >> Thanks to the previous met_help ticket, now that worked perfectly
! I am
> >> so grateful for your help, thank you. Now I will adapt this
method for
> >> all my data.
> >>
> >> Another time, thank you. I'll definitely let you know if I have
others
> >> questions.
> >>
> >> Best regards,
> >>
> >> Adrien
> >>
> >> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> I'm glad MET was able to read your CF compliant file.  Thank you
for
> >>> uploading your data.
> >>>
> >>> When I run point_stat with your data and configuration file, I
see the
> >>> following warning:
> >>>
> >>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>> WARNING:
> >>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc" variable,
the
> lead
> >>> time does not match the requested lead time: (000000 != 020000)
> >>> WARNING:
> >>> WARNING:
> >>> WARNING: process_fcst_climo_files() -> no fields matching
T_sfc(0,*,*)
> >>> found in file: wrfpot_cf_2013-01-01.nc
> >>> WARNING:
> >>>
> >>> There is a specific way in the CF-convention of specifying the
> >>> initialization time of the model.  You do so by defining a
variable
> named
> >>> "forecast_reference_time".  When that variable is not present,
MET sets
> >> the
> >>> forecast initialization time to the same value as the valid
time, which
> >>> results in a lead time of 0.
> >>>
> >>> You need to add the "forecast_reference_time" variable to your
model
> >>> files.  Take a look at this previous met_help ticket and see if
that
> >> helps:
> >>> http://mailman.ucar.edu/pipermail/met_help/2017-May/002867.html
> >>>
> >>> Also, I see in your PointStatConfig file that you have defined
> >> "lead_time"
> >>> in the fcst dictionary.  That is not necessary and could cause
> problems.
> >>> MET determines the lead time by the time index of the time
dimension
> that
> >>> you specify in the "level" field:
> >>>
> >>>           level      = "(0,*,*)";
> >>>
> >>> I hope that helps.  Please let us know if you have any other
questions.
> >>>
> >>> Thanks,
> >>> Julie
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hi Julie,
> >>>>
> >>>> Many thank, I have done as you suggested and MET seems to read
my CF
> >>>> Compliant. However, I still have issues with the configuration
of
> >>>> Point-Stat.
> >>>>
> >>>> So I  uploaded my file (name file: michel_data)
> >>>> - a forecast file (WRF file - CF compliance) - daily file for
> 2013-01-01
> >>>>
> >>>> I would also provide you :
> >>>> - point observation file from Madis2nc - hourly file for
> >>>> 2013-01-01_02:00:00
> >>>> - Point-Stat configuration
> >>>>
> >>>> I'm grateful for you help.
> >>>> Regards,
> >>>>
> >>>> Adrien Michel
> >>>>
> >>>>
> >>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> >>>>> Hi Adrien.
> >>>>>
> >>>>> It is difficult to tell the problem with the file without
seeing it.
> >>>>> However, I have something for you to try that might work.  MET
should
> >> be
> >>>>> able to read CF compliant files, and you have stated that your
NetCDF
> >>>> file
> >>>>> is CF Compliant.  MET tries to figure out the type of file,
but since
> >> it
> >>>> is
> >>>>> having trouble, let's try explicitly telling the tools how to
process
> >> the
> >>>>> data by setting the following in your PointStat config file:
> >>>>>
> >>>>> file_type = NETCDF_NCCF;
> >>>>>
> >>>>> This entry should be defined within the "fcst" dictionary.
For
> >> example:
> >>>>> fcst = {
> >>>>> file_type = NETCDF_NCCF;
> >>>>> ...
> >>>>> }
> >>>>>
> >>>>> If that works, please let us know.  If that does not work,
please
> >> upload
> >>>>> your file to our ftp server using the following instructions
and let
> us
> >>>>> know once you have done that so that we can get the file and
take a
> >> look.
> >>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>
> >>>>> Thanks!
> >>>>>
> >>>>> Julie
> >>>>>
> >>>>>
> >>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hi Julie.
> >>>>>>
> >>>>>>      I've done as you suggested and it ran without problem,
thank
> you!
> >>>>>>
> >>>>>> I come up with a another issue.. I'm trying to use Point-Stat
:
> >>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>> - a point observation file coming from Madis2nc
> >>>>>>
> >>>>>> However, Point Stat seems to have issue to read my forecast
file
> with
> >>>>>> the following informations:
> >>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>> DEBUG 1: Default Config File:
> >>>>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
> >>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> new
> >>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>> ERROR  :
> >>>>>>> ERROR  : Trouble reading forecast file
> >>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>>> ERROR  :
> >>>>>> I was wondering if you had any insight on what I could be
doing
> >> wrong. I
> >>>>>> appreciate any help you can give.
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Adrien Michel/
> >>>>>>
> >>>>>>
> >>>>>> /
> >>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>>>>>> Hi Adrien.
> >>>>>>>
> >>>>>>> I see that you have a question about how to define a
polyline
> masking
> >>>>>>> file.  The -mask_grid option would take a named grid or a
gridded
> >> data
> >>>>>>> file, while the -mask_poly option would definite a polyline
masking
> >>>> file.
> >>>>>>> If you'd only like to keep the points falling inside your
model
> >> domain,
> >>>>>> and
> >>>>>>> you have a gridded data file on that domain, using
-mask_grid is
> very
> >>>>>>> simple:
> >>>>>>>        -mask_grid /path/to/gridded/data/file
> >>>>>>>
> >>>>>>> However, if you'd prefer the flexibility of defining a
polyline
> >> masking
> >>>>>>> region, using -mask_poly would work too:
> >>>>>>>        -mask_poly /path/to/polyline/mask/file
> >>>>>>>
> >>>>>>> To create a polyline mask, you simply create an ASCII file
> >> containing a
> >>>>>>> list of lat/lons that define the region of interest.  For
example,
> >>>> take a
> >>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
> >>>> specifies
> >>>>>>> the name for the polyline, and the remaining lines contain
lat/lon
> >>>> values
> >>>>>>> for the boundary points.  The last point is connected back
up to
> the
> >>>>>> first
> >>>>>>> point to complete the area.  The example is named "SWC" and
> contains
> >> 33
> >>>>>>> points, and there is no real maximum.
> >>>>>>>
> >>>>>>> I hope this helps.  Please let us know if you have other
questions.
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Julie
> >>>>>>>
> >>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hello Julie,
> >>>>>>>>
> >>>>>>>> I have further questions about Madis2nc use. I would like
to use
> the
> >>>>>>>> '-mask_grid string' option. However there are very limited
details
> >> on
> >>>>>>>> how define the polyline masking file in the user guide. I
should
> >> like
> >>>> to
> >>>>>>>> define the polyline masking file for Europe and especially
for
> >> France.
> >>>>>>>> Thank you in advance,
> >>>>>>>>
> >>>>>>>> Regards.
> >>>>>>>>
> >>>>>>>> Adrien
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>>>>>>>> According to our records, your request has been resolved.
If you
> >> have
> >>>>>> any
> >>>>>>>>> further questions or concerns, please respond to this
message.
> >>>>>>>> --
> >>>>>>>> Adrien Michel
> >>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>
> >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> 15
> >> |
> >>>>>> E:
> >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>
> >>>>>>>>
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> |
> >>>> E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Mon Oct 16 08:41:52 2017

Hello Julie,

How can I pass multiple netcdf point observation files to point-stat ?
I
didn't see any informations on the user_guide about it.

Thank you,

Adrien


Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> Hi Adrien.
>
> There’s no “need” to merge the files.   You can pass multiple netcdf
point
> observation files to point_stat and ensemble_stat.  However, if you
would
> like to merge the files, you could consider using the "ncrcat" tool:
>
> https://linux.die.net/man/1/ncrcat
>
> from NCO:
> http://nco.sourceforge.net/
>
> I hope that helps!
>
> Julie
>
> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hello Julie,
>>
>> I am running Madis2nc tool for hourly basis metar data. Actually I
would
>> like to merge these hourly data in daily file. Do you have
suggestion or
>> recommendation on how to do it ? Is there option for that in MET ?
>>
>>
>> Regards,
>>
>> Adrien
>>
>>
>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
>>>
>>> Julie
>>>
>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hi Julie,
>>>>
>>>> Thanks to the previous met_help ticket, now that worked perfectly
! I am
>>>> so grateful for your help, thank you. Now I will adapt this
method for
>>>> all my data.
>>>>
>>>> Another time, thank you. I'll definitely let you know if I have
others
>>>> questions.
>>>>
>>>> Best regards,
>>>>
>>>> Adrien
>>>>
>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>> Hi Adrien.
>>>>>
>>>>> I'm glad MET was able to read your CF compliant file.  Thank you
for
>>>>> uploading your data.
>>>>>
>>>>> When I run point_stat with your data and configuration file, I
see the
>>>>> following warning:
>>>>>
>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>> WARNING:
>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc" variable,
the
>> lead
>>>>> time does not match the requested lead time: (000000 != 020000)
>>>>> WARNING:
>>>>> WARNING:
>>>>> WARNING: process_fcst_climo_files() -> no fields matching
T_sfc(0,*,*)
>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>> WARNING:
>>>>>
>>>>> There is a specific way in the CF-convention of specifying the
>>>>> initialization time of the model.  You do so by defining a
variable
>> named
>>>>> "forecast_reference_time".  When that variable is not present,
MET sets
>>>> the
>>>>> forecast initialization time to the same value as the valid
time, which
>>>>> results in a lead time of 0.
>>>>>
>>>>> You need to add the "forecast_reference_time" variable to your
model
>>>>> files.  Take a look at this previous met_help ticket and see if
that
>>>> helps:
>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/002867.html
>>>>>
>>>>> Also, I see in your PointStatConfig file that you have defined
>>>> "lead_time"
>>>>> in the fcst dictionary.  That is not necessary and could cause
>> problems.
>>>>> MET determines the lead time by the time index of the time
dimension
>> that
>>>>> you specify in the "level" field:
>>>>>
>>>>>            level      = "(0,*,*)";
>>>>>
>>>>> I hope that helps.  Please let us know if you have any other
questions.
>>>>>
>>>>> Thanks,
>>>>> Julie
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hi Julie,
>>>>>>
>>>>>> Many thank, I have done as you suggested and MET seems to read
my CF
>>>>>> Compliant. However, I still have issues with the configuration
of
>>>>>> Point-Stat.
>>>>>>
>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>> - a forecast file (WRF file - CF compliance) - daily file for
>> 2013-01-01
>>>>>> I would also provide you :
>>>>>> - point observation file from Madis2nc - hourly file for
>>>>>> 2013-01-01_02:00:00
>>>>>> - Point-Stat configuration
>>>>>>
>>>>>> I'm grateful for you help.
>>>>>> Regards,
>>>>>>
>>>>>> Adrien Michel
>>>>>>
>>>>>>
>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>>>>> Hi Adrien.
>>>>>>>
>>>>>>> It is difficult to tell the problem with the file without
seeing it.
>>>>>>> However, I have something for you to try that might work.  MET
should
>>>> be
>>>>>>> able to read CF compliant files, and you have stated that your
NetCDF
>>>>>> file
>>>>>>> is CF Compliant.  MET tries to figure out the type of file,
but since
>>>> it
>>>>>> is
>>>>>>> having trouble, let's try explicitly telling the tools how to
process
>>>> the
>>>>>>> data by setting the following in your PointStat config file:
>>>>>>>
>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>
>>>>>>> This entry should be defined within the "fcst" dictionary.
For
>>>> example:
>>>>>>> fcst = {
>>>>>>> file_type = NETCDF_NCCF;
>>>>>>> ...
>>>>>>> }
>>>>>>>
>>>>>>> If that works, please let us know.  If that does not work,
please
>>>> upload
>>>>>>> your file to our ftp server using the following instructions
and let
>> us
>>>>>>> know once you have done that so that we can get the file and
take a
>>>> look.
>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Julie
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hi Julie.
>>>>>>>>
>>>>>>>>       I've done as you suggested and it ran without problem,
thank
>> you!
>>>>>>>> I come up with a another issue.. I'm trying to use Point-Stat
:
>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>
>>>>>>>> However, Point Stat seems to have issue to read my forecast
file
>> with
>>>>>>>> the following informations:
>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/PointStatConfig
>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>> new
>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>> ERROR  :
>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>> ERROR  :
>>>>>>>> I was wondering if you had any insight on what I could be
doing
>>>> wrong. I
>>>>>>>> appreciate any help you can give.
>>>>>>>> Thanks,
>>>>>>>>
>>>>>>>> Adrien Michel/
>>>>>>>>
>>>>>>>>
>>>>>>>> /
>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>>>>>> Hi Adrien.
>>>>>>>>>
>>>>>>>>> I see that you have a question about how to define a
polyline
>> masking
>>>>>>>>> file.  The -mask_grid option would take a named grid or a
gridded
>>>> data
>>>>>>>>> file, while the -mask_poly option would definite a polyline
masking
>>>>>> file.
>>>>>>>>> If you'd only like to keep the points falling inside your
model
>>>> domain,
>>>>>>>> and
>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid is
>> very
>>>>>>>>> simple:
>>>>>>>>>         -mask_grid /path/to/gridded/data/file
>>>>>>>>>
>>>>>>>>> However, if you'd prefer the flexibility of defining a
polyline
>>>> masking
>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>         -mask_poly /path/to/polyline/mask/file
>>>>>>>>>
>>>>>>>>> To create a polyline mask, you simply create an ASCII file
>>>> containing a
>>>>>>>>> list of lat/lons that define the region of interest.  For
example,
>>>>>> take a
>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
>>>>>> specifies
>>>>>>>>> the name for the polyline, and the remaining lines contain
lat/lon
>>>>>> values
>>>>>>>>> for the boundary points.  The last point is connected back
up to
>> the
>>>>>>>> first
>>>>>>>>> point to complete the area.  The example is named "SWC" and
>> contains
>>>> 33
>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>
>>>>>>>>> I hope this helps.  Please let us know if you have other
questions.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> Julie
>>>>>>>>>
>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
>>>>>> met_help at ucar.edu
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>
>>>>>>>>>> Hello Julie,
>>>>>>>>>>
>>>>>>>>>> I have further questions about Madis2nc use. I would like
to use
>> the
>>>>>>>>>> '-mask_grid string' option. However there are very limited
details
>>>> on
>>>>>>>>>> how define the polyline masking file in the user guide. I
should
>>>> like
>>>>>> to
>>>>>>>>>> define the polyline masking file for Europe and especially
for
>>>> France.
>>>>>>>>>> Thank you in advance,
>>>>>>>>>>
>>>>>>>>>> Regards.
>>>>>>>>>>
>>>>>>>>>> Adrien
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>>>>>>>>>> According to our records, your request has been resolved.
If you
>>>> have
>>>>>>>> any
>>>>>>>>>>> further questions or concerns, please respond to this
message.
>>>>>>>>>> --
>>>>>>>>>> Adrien Michel
>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>
>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
>> 15
>>>> |
>>>>>>>> E:
>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>> |
>>>>>> E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
>>>> E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
>> E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Mon Oct 16 09:02:56 2017

Hi Adrien.

When you run "point_stat" you can see the usage statement (see below).
You
can use the "-point_obs" option to specify additional point
observation
files:

  "-point_obs file" specifies additional NetCDF point observation
files to
be used (optional).

You can use this option multiple times.  So, if you have multiple
additional observation files you can add "-point_obs <obs_file_a>
-point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
point_stat.

I hope that helps.  Please let us know if you have any other
questions.

Julie


*** Model Evaluation Tools (METV6.0) ***

Usage: point_stat
        fcst_file
        obs_file
        config_file
        [-point_obs file]
        [-obs_valid_beg time]
        [-obs_valid_end time]
        [-outdir path]
        [-log file]
        [-v level]

        where   "fcst_file" is a gridded forecast file containing the
field(s) to be verified (required).
                "obs_file" is an observation file in NetCDF format
containing the verifying point observations (required).
                "config_file" is a PointStatConfig file containing the
desired configuration settings (required).
                "-point_obs file" specifies additional NetCDF point
observation files to be used (optional).
                "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]] sets the
beginning of the matching time window (optional).
                "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]] sets the
end
of the matching time window (optional).
                "-outdir path" overrides the default output directory
(.)
(optional).
                "-log file" outputs log messages to the specified file
(optional).
                "-v level" overrides the default level of logging (2)
(optional).


On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hello Julie,
>
> How can I pass multiple netcdf point observation files to point-stat
? I
> didn't see any informations on the user_guide about it.
>
> Thank you,
>
> Adrien
>
>
> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > There’s no “need” to merge the files.   You can pass multiple
netcdf
> point
> > observation files to point_stat and ensemble_stat.  However, if
you would
> > like to merge the files, you could consider using the "ncrcat"
tool:
> >
> > https://linux.die.net/man/1/ncrcat
> >
> > from NCO:
> > http://nco.sourceforge.net/
> >
> > I hope that helps!
> >
> > Julie
> >
> > On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hello Julie,
> >>
> >> I am running Madis2nc tool for hourly basis metar data. Actually
I would
> >> like to merge these hourly data in daily file. Do you have
suggestion or
> >> recommendation on how to do it ? Is there option for that in MET
?
> >>
> >>
> >> Regards,
> >>
> >> Adrien
> >>
> >>
> >> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> >>> I'm glad to hear it, Adrien!  Thank you for letting us know.
> >>>
> >>> Julie
> >>>
> >>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hi Julie,
> >>>>
> >>>> Thanks to the previous met_help ticket, now that worked
perfectly ! I
> am
> >>>> so grateful for your help, thank you. Now I will adapt this
method for
> >>>> all my data.
> >>>>
> >>>> Another time, thank you. I'll definitely let you know if I have
others
> >>>> questions.
> >>>>
> >>>> Best regards,
> >>>>
> >>>> Adrien
> >>>>
> >>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>>>> Hi Adrien.
> >>>>>
> >>>>> I'm glad MET was able to read your CF compliant file.  Thank
you for
> >>>>> uploading your data.
> >>>>>
> >>>>> When I run point_stat with your data and configuration file, I
see
> the
> >>>>> following warning:
> >>>>>
> >>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>>>> WARNING:
> >>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable, the
> >> lead
> >>>>> time does not match the requested lead time: (000000 !=
020000)
> >>>>> WARNING:
> >>>>> WARNING:
> >>>>> WARNING: process_fcst_climo_files() -> no fields matching
> T_sfc(0,*,*)
> >>>>> found in file: wrfpot_cf_2013-01-01.nc
> >>>>> WARNING:
> >>>>>
> >>>>> There is a specific way in the CF-convention of specifying the
> >>>>> initialization time of the model.  You do so by defining a
variable
> >> named
> >>>>> "forecast_reference_time".  When that variable is not present,
MET
> sets
> >>>> the
> >>>>> forecast initialization time to the same value as the valid
time,
> which
> >>>>> results in a lead time of 0.
> >>>>>
> >>>>> You need to add the "forecast_reference_time" variable to your
model
> >>>>> files.  Take a look at this previous met_help ticket and see
if that
> >>>> helps:
> >>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
> >>>>>
> >>>>> Also, I see in your PointStatConfig file that you have defined
> >>>> "lead_time"
> >>>>> in the fcst dictionary.  That is not necessary and could cause
> >> problems.
> >>>>> MET determines the lead time by the time index of the time
dimension
> >> that
> >>>>> you specify in the "level" field:
> >>>>>
> >>>>>            level      = "(0,*,*)";
> >>>>>
> >>>>> I hope that helps.  Please let us know if you have any other
> questions.
> >>>>>
> >>>>> Thanks,
> >>>>> Julie
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hi Julie,
> >>>>>>
> >>>>>> Many thank, I have done as you suggested and MET seems to
read my CF
> >>>>>> Compliant. However, I still have issues with the
configuration of
> >>>>>> Point-Stat.
> >>>>>>
> >>>>>> So I  uploaded my file (name file: michel_data)
> >>>>>> - a forecast file (WRF file - CF compliance) - daily file for
> >> 2013-01-01
> >>>>>> I would also provide you :
> >>>>>> - point observation file from Madis2nc - hourly file for
> >>>>>> 2013-01-01_02:00:00
> >>>>>> - Point-Stat configuration
> >>>>>>
> >>>>>> I'm grateful for you help.
> >>>>>> Regards,
> >>>>>>
> >>>>>> Adrien Michel
> >>>>>>
> >>>>>>
> >>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> >>>>>>> Hi Adrien.
> >>>>>>>
> >>>>>>> It is difficult to tell the problem with the file without
seeing
> it.
> >>>>>>> However, I have something for you to try that might work.
MET
> should
> >>>> be
> >>>>>>> able to read CF compliant files, and you have stated that
your
> NetCDF
> >>>>>> file
> >>>>>>> is CF Compliant.  MET tries to figure out the type of file,
but
> since
> >>>> it
> >>>>>> is
> >>>>>>> having trouble, let's try explicitly telling the tools how
to
> process
> >>>> the
> >>>>>>> data by setting the following in your PointStat config file:
> >>>>>>>
> >>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>
> >>>>>>> This entry should be defined within the "fcst" dictionary.
For
> >>>> example:
> >>>>>>> fcst = {
> >>>>>>> file_type = NETCDF_NCCF;
> >>>>>>> ...
> >>>>>>> }
> >>>>>>>
> >>>>>>> If that works, please let us know.  If that does not work,
please
> >>>> upload
> >>>>>>> your file to our ftp server using the following instructions
and
> let
> >> us
> >>>>>>> know once you have done that so that we can get the file and
take a
> >>>> look.
> >>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>>>
> >>>>>>> Thanks!
> >>>>>>>
> >>>>>>> Julie
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hi Julie.
> >>>>>>>>
> >>>>>>>>       I've done as you suggested and it ran without
problem, thank
> >> you!
> >>>>>>>> I come up with a another issue.. I'm trying to use Point-
Stat :
> >>>>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>>>> - a point observation file coming from Madis2nc
> >>>>>>>>
> >>>>>>>> However, Point Stat seems to have issue to read my forecast
file
> >> with
> >>>>>>>> the following informations:
> >>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
> >>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
> >> new
> >>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>> ERROR  :
> >>>>>>>>> ERROR  : Trouble reading forecast file
> >>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>>>>> ERROR  :
> >>>>>>>> I was wondering if you had any insight on what I could be
doing
> >>>> wrong. I
> >>>>>>>> appreciate any help you can give.
> >>>>>>>> Thanks,
> >>>>>>>>
> >>>>>>>> Adrien Michel/
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> /
> >>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>>>>>>>> Hi Adrien.
> >>>>>>>>>
> >>>>>>>>> I see that you have a question about how to define a
polyline
> >> masking
> >>>>>>>>> file.  The -mask_grid option would take a named grid or a
gridded
> >>>> data
> >>>>>>>>> file, while the -mask_poly option would definite a
polyline
> masking
> >>>>>> file.
> >>>>>>>>> If you'd only like to keep the points falling inside your
model
> >>>> domain,
> >>>>>>>> and
> >>>>>>>>> you have a gridded data file on that domain, using
-mask_grid is
> >> very
> >>>>>>>>> simple:
> >>>>>>>>>         -mask_grid /path/to/gridded/data/file
> >>>>>>>>>
> >>>>>>>>> However, if you'd prefer the flexibility of defining a
polyline
> >>>> masking
> >>>>>>>>> region, using -mask_poly would work too:
> >>>>>>>>>         -mask_poly /path/to/polyline/mask/file
> >>>>>>>>>
> >>>>>>>>> To create a polyline mask, you simply create an ASCII file
> >>>> containing a
> >>>>>>>>> list of lat/lons that define the region of interest.  For
> example,
> >>>>>> take a
> >>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
> >>>>>> specifies
> >>>>>>>>> the name for the polyline, and the remaining lines contain
> lat/lon
> >>>>>> values
> >>>>>>>>> for the boundary points.  The last point is connected back
up to
> >> the
> >>>>>>>> first
> >>>>>>>>> point to complete the area.  The example is named "SWC"
and
> >> contains
> >>>> 33
> >>>>>>>>> points, and there is no real maximum.
> >>>>>>>>>
> >>>>>>>>> I hope this helps.  Please let us know if you have other
> questions.
> >>>>>>>>>
> >>>>>>>>> Thanks,
> >>>>>>>>> Julie
> >>>>>>>>>
> >>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
> >>>>>> met_help at ucar.edu
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>>>
> >>>>>>>>>> Hello Julie,
> >>>>>>>>>>
> >>>>>>>>>> I have further questions about Madis2nc use. I would like
to use
> >> the
> >>>>>>>>>> '-mask_grid string' option. However there are very
limited
> details
> >>>> on
> >>>>>>>>>> how define the polyline masking file in the user guide. I
should
> >>>> like
> >>>>>> to
> >>>>>>>>>> define the polyline masking file for Europe and
especially for
> >>>> France.
> >>>>>>>>>> Thank you in advance,
> >>>>>>>>>>
> >>>>>>>>>> Regards.
> >>>>>>>>>>
> >>>>>>>>>> Adrien
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
> >>>>>>>>>>> According to our records, your request has been
resolved. If
> you
> >>>> have
> >>>>>>>> any
> >>>>>>>>>>> further questions or concerns, please respond to this
message.
> >>>>>>>>>> --
> >>>>>>>>>> Adrien Michel
> >>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>
> >>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> 95
> >> 15
> >>>> |
> >>>>>>>> E:
> >>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>> --
> >>>>>>>> Adrien Michel
> >>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>
> >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> 15
> >> |
> >>>>>> E:
> >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>
> >>>>>>>>
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> |
> >>>> E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
> E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Tue Oct 17 09:41:37 2017

Hi Julie,

Well thank you it helps me. So actually my command shell looks like
that:

point_stat \
met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
met-6.0/data/Metar_test/TT/20130101_0100.nc \
met-6.0/data/Test/PointStatConfig \
-point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
-point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
-outdir met-6.0/data/point_stat \
-v 5

I will use point-stat for 23 point observations files per day for
multiple years, is there a solution that will allow me to do it
faster/simply? I tried with "point_obs
met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
met-6.0/data/Metar_test/T" but it is not working.


I have another question about Point-Stat Configuration. For instance,
I
have used variables gives in the user_guide examples as bellow:

  field = [
       {
         name       = "TMP";
         level      = [ "Z2" ];
         cat_thresh = [ <=273.0 ];
     },
       {
     name       = "UGRD";
         level      = [ "Z10" ];
         cat_thresh = [ >=5.0 ];
     },
       {
     name       = "VGRD";
         level      = [ "Z10" ];
         cat_thresh = [ >=5.0 ];
     }
    ];


It is actually working, but I would like to evaluate additional
variables. Where I can find informations about the name of variables ?
Indeed, I can not read my file after pre-processing with Madis2nc.

Many thanks,

Regards.

Adrien

Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> Hi Adrien.
>
> When you run "point_stat" you can see the usage statement (see
below).  You
> can use the "-point_obs" option to specify additional point
observation
> files:
>
>    "-point_obs file" specifies additional NetCDF point observation
files to
> be used (optional).
>
> You can use this option multiple times.  So, if you have multiple
> additional observation files you can add "-point_obs <obs_file_a>
> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
point_stat.
>
> I hope that helps.  Please let us know if you have any other
questions.
>
> Julie
>
>
> *** Model Evaluation Tools (METV6.0) ***
>
> Usage: point_stat
>          fcst_file
>          obs_file
>          config_file
>          [-point_obs file]
>          [-obs_valid_beg time]
>          [-obs_valid_end time]
>          [-outdir path]
>          [-log file]
>          [-v level]
>
>          where   "fcst_file" is a gridded forecast file containing
the
> field(s) to be verified (required).
>                  "obs_file" is an observation file in NetCDF format
> containing the verifying point observations (required).
>                  "config_file" is a PointStatConfig file containing
the
> desired configuration settings (required).
>                  "-point_obs file" specifies additional NetCDF point
> observation files to be used (optional).
>                  "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]] sets
the
> beginning of the matching time window (optional).
>                  "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]] sets
the end
> of the matching time window (optional).
>                  "-outdir path" overrides the default output
directory (.)
> (optional).
>                  "-log file" outputs log messages to the specified
file
> (optional).
>                  "-v level" overrides the default level of logging
(2)
> (optional).
>
>
> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hello Julie,
>>
>> How can I pass multiple netcdf point observation files to point-
stat ? I
>> didn't see any informations on the user_guide about it.
>>
>> Thank you,
>>
>> Adrien
>>
>>
>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
>>> Hi Adrien.
>>>
>>> There’s no “need” to merge the files.   You can pass multiple
netcdf
>> point
>>> observation files to point_stat and ensemble_stat.  However, if
you would
>>> like to merge the files, you could consider using the "ncrcat"
tool:
>>>
>>> https://linux.die.net/man/1/ncrcat
>>>
>>> from NCO:
>>> http://nco.sourceforge.net/
>>>
>>> I hope that helps!
>>>
>>> Julie
>>>
>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hello Julie,
>>>>
>>>> I am running Madis2nc tool for hourly basis metar data. Actually
I would
>>>> like to merge these hourly data in daily file. Do you have
suggestion or
>>>> recommendation on how to do it ? Is there option for that in MET
?
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Adrien
>>>>
>>>>
>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
>>>>>
>>>>> Julie
>>>>>
>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hi Julie,
>>>>>>
>>>>>> Thanks to the previous met_help ticket, now that worked
perfectly ! I
>> am
>>>>>> so grateful for your help, thank you. Now I will adapt this
method for
>>>>>> all my data.
>>>>>>
>>>>>> Another time, thank you. I'll definitely let you know if I have
others
>>>>>> questions.
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Adrien
>>>>>>
>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>>>> Hi Adrien.
>>>>>>>
>>>>>>> I'm glad MET was able to read your CF compliant file.  Thank
you for
>>>>>>> uploading your data.
>>>>>>>
>>>>>>> When I run point_stat with your data and configuration file, I
see
>> the
>>>>>>> following warning:
>>>>>>>
>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>>>> WARNING:
>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable, the
>>>> lead
>>>>>>> time does not match the requested lead time: (000000 !=
020000)
>>>>>>> WARNING:
>>>>>>> WARNING:
>>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
>> T_sfc(0,*,*)
>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>>>> WARNING:
>>>>>>>
>>>>>>> There is a specific way in the CF-convention of specifying the
>>>>>>> initialization time of the model.  You do so by defining a
variable
>>>> named
>>>>>>> "forecast_reference_time".  When that variable is not present,
MET
>> sets
>>>>>> the
>>>>>>> forecast initialization time to the same value as the valid
time,
>> which
>>>>>>> results in a lead time of 0.
>>>>>>>
>>>>>>> You need to add the "forecast_reference_time" variable to your
model
>>>>>>> files.  Take a look at this previous met_help ticket and see
if that
>>>>>> helps:
>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
>>>>>>>
>>>>>>> Also, I see in your PointStatConfig file that you have defined
>>>>>> "lead_time"
>>>>>>> in the fcst dictionary.  That is not necessary and could cause
>>>> problems.
>>>>>>> MET determines the lead time by the time index of the time
dimension
>>>> that
>>>>>>> you specify in the "level" field:
>>>>>>>
>>>>>>>             level      = "(0,*,*)";
>>>>>>>
>>>>>>> I hope that helps.  Please let us know if you have any other
>> questions.
>>>>>>> Thanks,
>>>>>>> Julie
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hi Julie,
>>>>>>>>
>>>>>>>> Many thank, I have done as you suggested and MET seems to
read my CF
>>>>>>>> Compliant. However, I still have issues with the
configuration of
>>>>>>>> Point-Stat.
>>>>>>>>
>>>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>>>> - a forecast file (WRF file - CF compliance) - daily file for
>>>> 2013-01-01
>>>>>>>> I would also provide you :
>>>>>>>> - point observation file from Madis2nc - hourly file for
>>>>>>>> 2013-01-01_02:00:00
>>>>>>>> - Point-Stat configuration
>>>>>>>>
>>>>>>>> I'm grateful for you help.
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Adrien Michel
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>>>>>>> Hi Adrien.
>>>>>>>>>
>>>>>>>>> It is difficult to tell the problem with the file without
seeing
>> it.
>>>>>>>>> However, I have something for you to try that might work.
MET
>> should
>>>>>> be
>>>>>>>>> able to read CF compliant files, and you have stated that
your
>> NetCDF
>>>>>>>> file
>>>>>>>>> is CF Compliant.  MET tries to figure out the type of file,
but
>> since
>>>>>> it
>>>>>>>> is
>>>>>>>>> having trouble, let's try explicitly telling the tools how
to
>> process
>>>>>> the
>>>>>>>>> data by setting the following in your PointStat config file:
>>>>>>>>>
>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>
>>>>>>>>> This entry should be defined within the "fcst" dictionary.
For
>>>>>> example:
>>>>>>>>> fcst = {
>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>> ...
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> If that works, please let us know.  If that does not work,
please
>>>>>> upload
>>>>>>>>> your file to our ftp server using the following instructions
and
>> let
>>>> us
>>>>>>>>> know once you have done that so that we can get the file and
take a
>>>>>> look.
>>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> Julie
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
>>>>>> met_help at ucar.edu
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>
>>>>>>>>>> Hi Julie.
>>>>>>>>>>
>>>>>>>>>>        I've done as you suggested and it ran without
problem, thank
>>>> you!
>>>>>>>>>> I come up with a another issue.. I'm trying to use Point-
Stat :
>>>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>>>
>>>>>>>>>> However, Point Stat seems to have issue to read my forecast
file
>>>> with
>>>>>>>>>> the following informations:
>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
created
>>>> new
>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>> ERROR  :
>>>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>>>> ERROR  :
>>>>>>>>>> I was wondering if you had any insight on what I could be
doing
>>>>>> wrong. I
>>>>>>>>>> appreciate any help you can give.
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Adrien Michel/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /
>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>
>>>>>>>>>>> I see that you have a question about how to define a
polyline
>>>> masking
>>>>>>>>>>> file.  The -mask_grid option would take a named grid or a
gridded
>>>>>> data
>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
>> masking
>>>>>>>> file.
>>>>>>>>>>> If you'd only like to keep the points falling inside your
model
>>>>>> domain,
>>>>>>>>>> and
>>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid is
>>>> very
>>>>>>>>>>> simple:
>>>>>>>>>>>          -mask_grid /path/to/gridded/data/file
>>>>>>>>>>>
>>>>>>>>>>> However, if you'd prefer the flexibility of defining a
polyline
>>>>>> masking
>>>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>>>          -mask_poly /path/to/polyline/mask/file
>>>>>>>>>>>
>>>>>>>>>>> To create a polyline mask, you simply create an ASCII file
>>>>>> containing a
>>>>>>>>>>> list of lat/lons that define the region of interest.  For
>> example,
>>>>>>>> take a
>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of the
file
>>>>>>>> specifies
>>>>>>>>>>> the name for the polyline, and the remaining lines contain
>> lat/lon
>>>>>>>> values
>>>>>>>>>>> for the boundary points.  The last point is connected back
up to
>>>> the
>>>>>>>>>> first
>>>>>>>>>>> point to complete the area.  The example is named "SWC"
and
>>>> contains
>>>>>> 33
>>>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>>>
>>>>>>>>>>> I hope this helps.  Please let us know if you have other
>> questions.
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Julie
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
>>>>>>>> met_help at ucar.edu
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>>>
>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>
>>>>>>>>>>>> I have further questions about Madis2nc use. I would like
to use
>>>> the
>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
>> details
>>>>>> on
>>>>>>>>>>>> how define the polyline masking file in the user guide. I
should
>>>>>> like
>>>>>>>> to
>>>>>>>>>>>> define the polyline masking file for Europe and
especially for
>>>>>> France.
>>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>>>
>>>>>>>>>>>> Regards.
>>>>>>>>>>>>
>>>>>>>>>>>> Adrien
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>>> According to our records, your request has been
resolved. If
>> you
>>>>>> have
>>>>>>>>>> any
>>>>>>>>>>>>> further questions or concerns, please respond to this
message.
>>>>>>>>>>>> --
>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>
>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>> 95
>>>> 15
>>>>>> |
>>>>>>>>>> E:
>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Adrien Michel
>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>
>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
>> 15
>>>> |
>>>>>>>> E:
>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>> |
>>>>>> E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15 |
>>>> E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 |
>> E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Julie Prestopnik
Time: Tue Oct 17 14:03:23 2017

Hi Adrien.

With regard to processing multiple observation files for multiple
years in
point_stat in a faster/simpler way, I would like to speak to one of
our
main developers to find out more information.  I will get back to you
on
that.

With regard to getting more information about additional variables,
you
mentioned that you cannot read your file after processing with
Madis2nc.
You should be able to read your NetCDF data with a utility called
"ncdump".  Here is a link to more information about the "ncdump"
utility:
http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
utilities_guide.html#ncdump_guide

If you are unable to get and use the "ncdump" utility you are welcome
to
upload sample NetCDF files to our ftp site and I can dump the variable
information and pass it back to you.

You can upload your file(s) on our anonymous ftp site using these
instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp

I hope that helps.

Julie

On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi Julie,
>
> Well thank you it helps me. So actually my command shell looks like
that:
>
> point_stat \
> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
> met-6.0/data/Metar_test/TT/20130101_0100.nc \
> met-6.0/data/Test/PointStatConfig \
> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
> -outdir met-6.0/data/point_stat \
> -v 5
>
> I will use point-stat for 23 point observations files per day for
> multiple years, is there a solution that will allow me to do it
> faster/simply? I tried with "point_obs
> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
> met-6.0/data/Metar_test/T" but it is not working.
>
>
> I have another question about Point-Stat Configuration. For
instance, I
> have used variables gives in the user_guide examples as bellow:
>
>   field = [
>        {
>          name       = "TMP";
>          level      = [ "Z2" ];
>          cat_thresh = [ <=273.0 ];
>      },
>        {
>      name       = "UGRD";
>          level      = [ "Z10" ];
>          cat_thresh = [ >=5.0 ];
>      },
>        {
>      name       = "VGRD";
>          level      = [ "Z10" ];
>          cat_thresh = [ >=5.0 ];
>      }
>     ];
>
>
> It is actually working, but I would like to evaluate additional
> variables. Where I can find informations about the name of variables
?
> Indeed, I can not read my file after pre-processing with Madis2nc.
>
> Many thanks,
>
> Regards.
>
> Adrien
>
> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > When you run "point_stat" you can see the usage statement (see
below).
> You
> > can use the "-point_obs" option to specify additional point
observation
> > files:
> >
> >    "-point_obs file" specifies additional NetCDF point observation
files
> to
> > be used (optional).
> >
> > You can use this option multiple times.  So, if you have multiple
> > additional observation files you can add "-point_obs <obs_file_a>
> > -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
> point_stat.
> >
> > I hope that helps.  Please let us know if you have any other
questions.
> >
> > Julie
> >
> >
> > *** Model Evaluation Tools (METV6.0) ***
> >
> > Usage: point_stat
> >          fcst_file
> >          obs_file
> >          config_file
> >          [-point_obs file]
> >          [-obs_valid_beg time]
> >          [-obs_valid_end time]
> >          [-outdir path]
> >          [-log file]
> >          [-v level]
> >
> >          where   "fcst_file" is a gridded forecast file containing
the
> > field(s) to be verified (required).
> >                  "obs_file" is an observation file in NetCDF
format
> > containing the verifying point observations (required).
> >                  "config_file" is a PointStatConfig file
containing the
> > desired configuration settings (required).
> >                  "-point_obs file" specifies additional NetCDF
point
> > observation files to be used (optional).
> >                  "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]] sets
the
> > beginning of the matching time window (optional).
> >                  "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]] sets
the
> end
> > of the matching time window (optional).
> >                  "-outdir path" overrides the default output
directory
> (.)
> > (optional).
> >                  "-log file" outputs log messages to the specified
file
> > (optional).
> >                  "-v level" overrides the default level of logging
(2)
> > (optional).
> >
> >
> > On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hello Julie,
> >>
> >> How can I pass multiple netcdf point observation files to point-
stat ? I
> >> didn't see any informations on the user_guide about it.
> >>
> >> Thank you,
> >>
> >> Adrien
> >>
> >>
> >> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> There’s no “need” to merge the files.   You can pass multiple
netcdf
> >> point
> >>> observation files to point_stat and ensemble_stat.  However, if
you
> would
> >>> like to merge the files, you could consider using the "ncrcat"
tool:
> >>>
> >>> https://linux.die.net/man/1/ncrcat
> >>>
> >>> from NCO:
> >>> http://nco.sourceforge.net/
> >>>
> >>> I hope that helps!
> >>>
> >>> Julie
> >>>
> >>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hello Julie,
> >>>>
> >>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
> would
> >>>> like to merge these hourly data in daily file. Do you have
suggestion
> or
> >>>> recommendation on how to do it ? Is there option for that in
MET ?
> >>>>
> >>>>
> >>>> Regards,
> >>>>
> >>>> Adrien
> >>>>
> >>>>
> >>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> >>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
> >>>>>
> >>>>> Julie
> >>>>>
> >>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hi Julie,
> >>>>>>
> >>>>>> Thanks to the previous met_help ticket, now that worked
perfectly !
> I
> >> am
> >>>>>> so grateful for your help, thank you. Now I will adapt this
method
> for
> >>>>>> all my data.
> >>>>>>
> >>>>>> Another time, thank you. I'll definitely let you know if I
have
> others
> >>>>>> questions.
> >>>>>>
> >>>>>> Best regards,
> >>>>>>
> >>>>>> Adrien
> >>>>>>
> >>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>>>>>> Hi Adrien.
> >>>>>>>
> >>>>>>> I'm glad MET was able to read your CF compliant file.  Thank
you
> for
> >>>>>>> uploading your data.
> >>>>>>>
> >>>>>>> When I run point_stat with your data and configuration file,
I see
> >> the
> >>>>>>> following warning:
> >>>>>>>
> >>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>>>>>> WARNING:
> >>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable, the
> >>>> lead
> >>>>>>> time does not match the requested lead time: (000000 !=
020000)
> >>>>>>> WARNING:
> >>>>>>> WARNING:
> >>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
> >> T_sfc(0,*,*)
> >>>>>>> found in file: wrfpot_cf_2013-01-01.nc
> >>>>>>> WARNING:
> >>>>>>>
> >>>>>>> There is a specific way in the CF-convention of specifying
the
> >>>>>>> initialization time of the model.  You do so by defining a
variable
> >>>> named
> >>>>>>> "forecast_reference_time".  When that variable is not
present, MET
> >> sets
> >>>>>> the
> >>>>>>> forecast initialization time to the same value as the valid
time,
> >> which
> >>>>>>> results in a lead time of 0.
> >>>>>>>
> >>>>>>> You need to add the "forecast_reference_time" variable to
your
> model
> >>>>>>> files.  Take a look at this previous met_help ticket and see
if
> that
> >>>>>> helps:
> >>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
> >>>>>>>
> >>>>>>> Also, I see in your PointStatConfig file that you have
defined
> >>>>>> "lead_time"
> >>>>>>> in the fcst dictionary.  That is not necessary and could
cause
> >>>> problems.
> >>>>>>> MET determines the lead time by the time index of the time
> dimension
> >>>> that
> >>>>>>> you specify in the "level" field:
> >>>>>>>
> >>>>>>>             level      = "(0,*,*)";
> >>>>>>>
> >>>>>>> I hope that helps.  Please let us know if you have any other
> >> questions.
> >>>>>>> Thanks,
> >>>>>>> Julie
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hi Julie,
> >>>>>>>>
> >>>>>>>> Many thank, I have done as you suggested and MET seems to
read my
> CF
> >>>>>>>> Compliant. However, I still have issues with the
configuration of
> >>>>>>>> Point-Stat.
> >>>>>>>>
> >>>>>>>> So I  uploaded my file (name file: michel_data)
> >>>>>>>> - a forecast file (WRF file - CF compliance) - daily file
for
> >>>> 2013-01-01
> >>>>>>>> I would also provide you :
> >>>>>>>> - point observation file from Madis2nc - hourly file for
> >>>>>>>> 2013-01-01_02:00:00
> >>>>>>>> - Point-Stat configuration
> >>>>>>>>
> >>>>>>>> I'm grateful for you help.
> >>>>>>>> Regards,
> >>>>>>>>
> >>>>>>>> Adrien Michel
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> >>>>>>>>> Hi Adrien.
> >>>>>>>>>
> >>>>>>>>> It is difficult to tell the problem with the file without
seeing
> >> it.
> >>>>>>>>> However, I have something for you to try that might work.
MET
> >> should
> >>>>>> be
> >>>>>>>>> able to read CF compliant files, and you have stated that
your
> >> NetCDF
> >>>>>>>> file
> >>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file, but
> >> since
> >>>>>> it
> >>>>>>>> is
> >>>>>>>>> having trouble, let's try explicitly telling the tools how
to
> >> process
> >>>>>> the
> >>>>>>>>> data by setting the following in your PointStat config
file:
> >>>>>>>>>
> >>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>
> >>>>>>>>> This entry should be defined within the "fcst" dictionary.
For
> >>>>>> example:
> >>>>>>>>> fcst = {
> >>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>> ...
> >>>>>>>>> }
> >>>>>>>>>
> >>>>>>>>> If that works, please let us know.  If that does not work,
please
> >>>>>> upload
> >>>>>>>>> your file to our ftp server using the following
instructions and
> >> let
> >>>> us
> >>>>>>>>> know once you have done that so that we can get the file
and
> take a
> >>>>>> look.
> >>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>>>>>
> >>>>>>>>> Thanks!
> >>>>>>>>>
> >>>>>>>>> Julie
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
> >>>>>> met_help at ucar.edu
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>>>
> >>>>>>>>>> Hi Julie.
> >>>>>>>>>>
> >>>>>>>>>>        I've done as you suggested and it ran without
problem,
> thank
> >>>> you!
> >>>>>>>>>> I come up with a another issue.. I'm trying to use Point-
Stat :
> >>>>>>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>>>>>> - a point observation file coming from Madis2nc
> >>>>>>>>>>
> >>>>>>>>>> However, Point Stat seems to have issue to read my
forecast file
> >>>> with
> >>>>>>>>>> the following informations:
> >>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
> >>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
> created
> >>>> new
> >>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>> ERROR  :
> >>>>>>>>>>> ERROR  : Trouble reading forecast file
> >>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>>>>>>> ERROR  :
> >>>>>>>>>> I was wondering if you had any insight on what I could be
doing
> >>>>>> wrong. I
> >>>>>>>>>> appreciate any help you can give.
> >>>>>>>>>> Thanks,
> >>>>>>>>>>
> >>>>>>>>>> Adrien Michel/
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> /
> >>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
> >>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>
> >>>>>>>>>>> I see that you have a question about how to define a
polyline
> >>>> masking
> >>>>>>>>>>> file.  The -mask_grid option would take a named grid or
a
> gridded
> >>>>>> data
> >>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
> >> masking
> >>>>>>>> file.
> >>>>>>>>>>> If you'd only like to keep the points falling inside
your model
> >>>>>> domain,
> >>>>>>>>>> and
> >>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid
> is
> >>>> very
> >>>>>>>>>>> simple:
> >>>>>>>>>>>          -mask_grid /path/to/gridded/data/file
> >>>>>>>>>>>
> >>>>>>>>>>> However, if you'd prefer the flexibility of defining a
polyline
> >>>>>> masking
> >>>>>>>>>>> region, using -mask_poly would work too:
> >>>>>>>>>>>          -mask_poly /path/to/polyline/mask/file
> >>>>>>>>>>>
> >>>>>>>>>>> To create a polyline mask, you simply create an ASCII
file
> >>>>>> containing a
> >>>>>>>>>>> list of lat/lons that define the region of interest.
For
> >> example,
> >>>>>>>> take a
> >>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of
the file
> >>>>>>>> specifies
> >>>>>>>>>>> the name for the polyline, and the remaining lines
contain
> >> lat/lon
> >>>>>>>> values
> >>>>>>>>>>> for the boundary points.  The last point is connected
back up
> to
> >>>> the
> >>>>>>>>>> first
> >>>>>>>>>>> point to complete the area.  The example is named "SWC"
and
> >>>> contains
> >>>>>> 33
> >>>>>>>>>>> points, and there is no real maximum.
> >>>>>>>>>>>
> >>>>>>>>>>> I hope this helps.  Please let us know if you have other
> >> questions.
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> Julie
> >>>>>>>>>>>
> >>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
> >>>>>>>> met_help at ucar.edu
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello Julie,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I have further questions about Madis2nc use. I would
like to
> use
> >>>> the
> >>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
> >> details
> >>>>>> on
> >>>>>>>>>>>> how define the polyline masking file in the user guide.
I
> should
> >>>>>> like
> >>>>>>>> to
> >>>>>>>>>>>> define the polyline masking file for Europe and
especially for
> >>>>>> France.
> >>>>>>>>>>>> Thank you in advance,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Regards.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Adrien
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit
:
> >>>>>>>>>>>>> According to our records, your request has been
resolved. If
> >> you
> >>>>>> have
> >>>>>>>>>> any
> >>>>>>>>>>>>> further questions or concerns, please respond to this
> message.
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>
> >>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> >> 95
> >>>> 15
> >>>>>> |
> >>>>>>>>>> E:
> >>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Adrien Michel
> >>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>
> >>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> 95
> >> 15
> >>>> |
> >>>>>>>> E:
> >>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>> --
> >>>>>>>> Adrien Michel
> >>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>
> >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> 15
> >> |
> >>>>>> E:
> >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>
> >>>>>>>>
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> |
> >>>> E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> <+33%206%2095%2037%2095%2015> |
> >> E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16
> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> <+33%206%2095%2037%2095%2015> | E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
27 84
> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> <+33%206%2095%2037%2095%2015> | E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: John Halley Gotway
Time: Wed Oct 18 09:26:26 2017

Hi Adrien,

Julie asked me to take a look at this ticket.  The MET statistics
tools are
intended to be run once for each time "verification time".  You pass
to
them a forecast file, one or more observation files, and a
configuration
file to tell the tool what you'd like it to do.

But a lot of the details are dictated by your input data.  In the
example
you sent, you're passing this file to Point-Stat:
   met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc

How many output times does this file contain?

If you'd like, you could post this file to our anonymous ftp site, and
I
can take a closer look at it.

Just follow these directions:
   https://dtcenter.org/met/users/support/met_help.php#ftp

Thanks,
John

On Tue, Oct 17, 2017 at 2:03 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi Adrien.
>
> With regard to processing multiple observation files for multiple
years in
> point_stat in a faster/simpler way, I would like to speak to one of
our
> main developers to find out more information.  I will get back to
you on
> that.
>
> With regard to getting more information about additional variables,
you
> mentioned that you cannot read your file after processing with
Madis2nc.
> You should be able to read your NetCDF data with a utility called
> "ncdump".  Here is a link to more information about the "ncdump"
utility:
> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
> utilities_guide.html#ncdump_guide
>
> If you are unable to get and use the "ncdump" utility you are
welcome to
> upload sample NetCDF files to our ftp site and I can dump the
variable
> information and pass it back to you.
>
> You can upload your file(s) on our anonymous ftp site using these
> instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> I hope that helps.
>
> Julie
>
> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >
> > Hi Julie,
> >
> > Well thank you it helps me. So actually my command shell looks
like that:
> >
> > point_stat \
> > met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
> > met-6.0/data/Metar_test/TT/20130101_0100.nc \
> > met-6.0/data/Test/PointStatConfig \
> > -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
> > -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
> > -outdir met-6.0/data/point_stat \
> > -v 5
> >
> > I will use point-stat for 23 point observations files per day for
> > multiple years, is there a solution that will allow me to do it
> > faster/simply? I tried with "point_obs
> > met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
> > met-6.0/data/Metar_test/T" but it is not working.
> >
> >
> > I have another question about Point-Stat Configuration. For
instance, I
> > have used variables gives in the user_guide examples as bellow:
> >
> >   field = [
> >        {
> >          name       = "TMP";
> >          level      = [ "Z2" ];
> >          cat_thresh = [ <=273.0 ];
> >      },
> >        {
> >      name       = "UGRD";
> >          level      = [ "Z10" ];
> >          cat_thresh = [ >=5.0 ];
> >      },
> >        {
> >      name       = "VGRD";
> >          level      = [ "Z10" ];
> >          cat_thresh = [ >=5.0 ];
> >      }
> >     ];
> >
> >
> > It is actually working, but I would like to evaluate additional
> > variables. Where I can find informations about the name of
variables ?
> > Indeed, I can not read my file after pre-processing with Madis2nc.
> >
> > Many thanks,
> >
> > Regards.
> >
> > Adrien
> >
> > Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> > > Hi Adrien.
> > >
> > > When you run "point_stat" you can see the usage statement (see
below).
> > You
> > > can use the "-point_obs" option to specify additional point
observation
> > > files:
> > >
> > >    "-point_obs file" specifies additional NetCDF point
observation
> files
> > to
> > > be used (optional).
> > >
> > > You can use this option multiple times.  So, if you have
multiple
> > > additional observation files you can add "-point_obs
<obs_file_a>
> > > -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
> > point_stat.
> > >
> > > I hope that helps.  Please let us know if you have any other
questions.
> > >
> > > Julie
> > >
> > >
> > > *** Model Evaluation Tools (METV6.0) ***
> > >
> > > Usage: point_stat
> > >          fcst_file
> > >          obs_file
> > >          config_file
> > >          [-point_obs file]
> > >          [-obs_valid_beg time]
> > >          [-obs_valid_end time]
> > >          [-outdir path]
> > >          [-log file]
> > >          [-v level]
> > >
> > >          where   "fcst_file" is a gridded forecast file
containing the
> > > field(s) to be verified (required).
> > >                  "obs_file" is an observation file in NetCDF
format
> > > containing the verifying point observations (required).
> > >                  "config_file" is a PointStatConfig file
containing the
> > > desired configuration settings (required).
> > >                  "-point_obs file" specifies additional NetCDF
point
> > > observation files to be used (optional).
> > >                  "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]]
sets the
> > > beginning of the matching time window (optional).
> > >                  "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]]
sets the
> > end
> > > of the matching time window (optional).
> > >                  "-outdir path" overrides the default output
directory
> > (.)
> > > (optional).
> > >                  "-log file" outputs log messages to the
specified file
> > > (optional).
> > >                  "-v level" overrides the default level of
logging (2)
> > > (optional).
> > >
> > >
> > > On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
> met_help at ucar.edu
> > >
> > > wrote:
> > >
> > >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> > >>
> > >> Hello Julie,
> > >>
> > >> How can I pass multiple netcdf point observation files to
point-stat
> ? I
> > >> didn't see any informations on the user_guide about it.
> > >>
> > >> Thank you,
> > >>
> > >> Adrien
> > >>
> > >>
> > >> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> > >>> Hi Adrien.
> > >>>
> > >>> There’s no “need” to merge the files.   You can pass multiple
netcdf
> > >> point
> > >>> observation files to point_stat and ensemble_stat.  However,
if you
> > would
> > >>> like to merge the files, you could consider using the "ncrcat"
tool:
> > >>>
> > >>> https://linux.die.net/man/1/ncrcat
> > >>>
> > >>> from NCO:
> > >>> http://nco.sourceforge.net/
> > >>>
> > >>> I hope that helps!
> > >>>
> > >>> Julie
> > >>>
> > >>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
> > met_help at ucar.edu
> > >>>
> > >>> wrote:
> > >>>
> > >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> > >>>>
> > >>>> Hello Julie,
> > >>>>
> > >>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
> > would
> > >>>> like to merge these hourly data in daily file. Do you have
> suggestion
> > or
> > >>>> recommendation on how to do it ? Is there option for that in
MET ?
> > >>>>
> > >>>>
> > >>>> Regards,
> > >>>>
> > >>>> Adrien
> > >>>>
> > >>>>
> > >>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> > >>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
> > >>>>>
> > >>>>> Julie
> > >>>>>
> > >>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
> > >> met_help at ucar.edu
> > >>>>> wrote:
> > >>>>>
> > >>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> > >>>>>>
> > >>>>>> Hi Julie,
> > >>>>>>
> > >>>>>> Thanks to the previous met_help ticket, now that worked
perfectly
> !
> > I
> > >> am
> > >>>>>> so grateful for your help, thank you. Now I will adapt this
method
> > for
> > >>>>>> all my data.
> > >>>>>>
> > >>>>>> Another time, thank you. I'll definitely let you know if I
have
> > others
> > >>>>>> questions.
> > >>>>>>
> > >>>>>> Best regards,
> > >>>>>>
> > >>>>>> Adrien
> > >>>>>>
> > >>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> > >>>>>>> Hi Adrien.
> > >>>>>>>
> > >>>>>>> I'm glad MET was able to read your CF compliant file.
Thank you
> > for
> > >>>>>>> uploading your data.
> > >>>>>>>
> > >>>>>>> When I run point_stat with your data and configuration
file, I
> see
> > >> the
> > >>>>>>> following warning:
> > >>>>>>>
> > >>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> > >>>>>>> WARNING:
> > >>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable,
> the
> > >>>> lead
> > >>>>>>> time does not match the requested lead time: (000000 !=
020000)
> > >>>>>>> WARNING:
> > >>>>>>> WARNING:
> > >>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
> > >> T_sfc(0,*,*)
> > >>>>>>> found in file: wrfpot_cf_2013-01-01.nc
> > >>>>>>> WARNING:
> > >>>>>>>
> > >>>>>>> There is a specific way in the CF-convention of specifying
the
> > >>>>>>> initialization time of the model.  You do so by defining a
> variable
> > >>>> named
> > >>>>>>> "forecast_reference_time".  When that variable is not
present,
> MET
> > >> sets
> > >>>>>> the
> > >>>>>>> forecast initialization time to the same value as the
valid time,
> > >> which
> > >>>>>>> results in a lead time of 0.
> > >>>>>>>
> > >>>>>>> You need to add the "forecast_reference_time" variable to
your
> > model
> > >>>>>>> files.  Take a look at this previous met_help ticket and
see if
> > that
> > >>>>>> helps:
> > >>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
> > >>>>>>>
> > >>>>>>> Also, I see in your PointStatConfig file that you have
defined
> > >>>>>> "lead_time"
> > >>>>>>> in the fcst dictionary.  That is not necessary and could
cause
> > >>>> problems.
> > >>>>>>> MET determines the lead time by the time index of the time
> > dimension
> > >>>> that
> > >>>>>>> you specify in the "level" field:
> > >>>>>>>
> > >>>>>>>             level      = "(0,*,*)";
> > >>>>>>>
> > >>>>>>> I hope that helps.  Please let us know if you have any
other
> > >> questions.
> > >>>>>>> Thanks,
> > >>>>>>> Julie
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>>
> > >>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
> > >>>> met_help at ucar.edu
> > >>>>>>> wrote:
> > >>>>>>>
> > >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> > >>>>>>>>
> > >>>>>>>> Hi Julie,
> > >>>>>>>>
> > >>>>>>>> Many thank, I have done as you suggested and MET seems to
read
> my
> > CF
> > >>>>>>>> Compliant. However, I still have issues with the
configuration
> of
> > >>>>>>>> Point-Stat.
> > >>>>>>>>
> > >>>>>>>> So I  uploaded my file (name file: michel_data)
> > >>>>>>>> - a forecast file (WRF file - CF compliance) - daily file
for
> > >>>> 2013-01-01
> > >>>>>>>> I would also provide you :
> > >>>>>>>> - point observation file from Madis2nc - hourly file for
> > >>>>>>>> 2013-01-01_02:00:00
> > >>>>>>>> - Point-Stat configuration
> > >>>>>>>>
> > >>>>>>>> I'm grateful for you help.
> > >>>>>>>> Regards,
> > >>>>>>>>
> > >>>>>>>> Adrien Michel
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> > >>>>>>>>> Hi Adrien.
> > >>>>>>>>>
> > >>>>>>>>> It is difficult to tell the problem with the file
without
> seeing
> > >> it.
> > >>>>>>>>> However, I have something for you to try that might
work.  MET
> > >> should
> > >>>>>> be
> > >>>>>>>>> able to read CF compliant files, and you have stated
that your
> > >> NetCDF
> > >>>>>>>> file
> > >>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file, but
> > >> since
> > >>>>>> it
> > >>>>>>>> is
> > >>>>>>>>> having trouble, let's try explicitly telling the tools
how to
> > >> process
> > >>>>>> the
> > >>>>>>>>> data by setting the following in your PointStat config
file:
> > >>>>>>>>>
> > >>>>>>>>> file_type = NETCDF_NCCF;
> > >>>>>>>>>
> > >>>>>>>>> This entry should be defined within the "fcst"
dictionary.  For
> > >>>>>> example:
> > >>>>>>>>> fcst = {
> > >>>>>>>>> file_type = NETCDF_NCCF;
> > >>>>>>>>> ...
> > >>>>>>>>> }
> > >>>>>>>>>
> > >>>>>>>>> If that works, please let us know.  If that does not
work,
> please
> > >>>>>> upload
> > >>>>>>>>> your file to our ftp server using the following
instructions
> and
> > >> let
> > >>>> us
> > >>>>>>>>> know once you have done that so that we can get the file
and
> > take a
> > >>>>>> look.
> > >>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >>>>>>>>>
> > >>>>>>>>> Thanks!
> > >>>>>>>>>
> > >>>>>>>>> Julie
> > >>>>>>>>>
> > >>>>>>>>>
> > >>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
> > >>>>>> met_help at ucar.edu
> > >>>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> > >>>>>>>>>>
> > >>>>>>>>>> Hi Julie.
> > >>>>>>>>>>
> > >>>>>>>>>>        I've done as you suggested and it ran without
problem,
> > thank
> > >>>> you!
> > >>>>>>>>>> I come up with a another issue.. I'm trying to use
Point-Stat
> :
> > >>>>>>>>>> - a forecast file (WRF file - CF compliance)
> > >>>>>>>>>> - a point observation file coming from Madis2nc
> > >>>>>>>>>>
> > >>>>>>>>>> However, Point Stat seems to have issue to read my
forecast
> file
> > >>>> with
> > >>>>>>>>>> the following informations:
> > >>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> > >>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> > >>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> > >>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> > >>>>>>>>>>> DEBUG 1: Default Config File:
> > >>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
> > >>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
> > >>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file()
->
> > created
> > >>>> new
> > >>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> > >>>>>>>>>>> ERROR  :
> > >>>>>>>>>>> ERROR  : Trouble reading forecast file
> > >>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> > >>>>>>>>>>> ERROR  :
> > >>>>>>>>>> I was wondering if you had any insight on what I could
be
> doing
> > >>>>>> wrong. I
> > >>>>>>>>>> appreciate any help you can give.
> > >>>>>>>>>> Thanks,
> > >>>>>>>>>>
> > >>>>>>>>>> Adrien Michel/
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>>>> /
> > >>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit
:
> > >>>>>>>>>>> Hi Adrien.
> > >>>>>>>>>>>
> > >>>>>>>>>>> I see that you have a question about how to define a
polyline
> > >>>> masking
> > >>>>>>>>>>> file.  The -mask_grid option would take a named grid
or a
> > gridded
> > >>>>>> data
> > >>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
> > >> masking
> > >>>>>>>> file.
> > >>>>>>>>>>> If you'd only like to keep the points falling inside
your
> model
> > >>>>>> domain,
> > >>>>>>>>>> and
> > >>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid
> > is
> > >>>> very
> > >>>>>>>>>>> simple:
> > >>>>>>>>>>>          -mask_grid /path/to/gridded/data/file
> > >>>>>>>>>>>
> > >>>>>>>>>>> However, if you'd prefer the flexibility of defining a
> polyline
> > >>>>>> masking
> > >>>>>>>>>>> region, using -mask_poly would work too:
> > >>>>>>>>>>>          -mask_poly /path/to/polyline/mask/file
> > >>>>>>>>>>>
> > >>>>>>>>>>> To create a polyline mask, you simply create an ASCII
file
> > >>>>>> containing a
> > >>>>>>>>>>> list of lat/lons that define the region of interest.
For
> > >> example,
> > >>>>>>>> take a
> > >>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of
the
> file
> > >>>>>>>> specifies
> > >>>>>>>>>>> the name for the polyline, and the remaining lines
contain
> > >> lat/lon
> > >>>>>>>> values
> > >>>>>>>>>>> for the boundary points.  The last point is connected
back up
> > to
> > >>>> the
> > >>>>>>>>>> first
> > >>>>>>>>>>> point to complete the area.  The example is named
"SWC" and
> > >>>> contains
> > >>>>>> 33
> > >>>>>>>>>>> points, and there is no real maximum.
> > >>>>>>>>>>>
> > >>>>>>>>>>> I hope this helps.  Please let us know if you have
other
> > >> questions.
> > >>>>>>>>>>> Thanks,
> > >>>>>>>>>>> Julie
> > >>>>>>>>>>>
> > >>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<
> > >>>>>>>> met_help at ucar.edu
> > >>>>>>>>>>> wrote:
> > >>>>>>>>>>>
> > >>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81768
> > >
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Hello Julie,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I have further questions about Madis2nc use. I would
like to
> > use
> > >>>> the
> > >>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
> > >> details
> > >>>>>> on
> > >>>>>>>>>>>> how define the polyline masking file in the user
guide. I
> > should
> > >>>>>> like
> > >>>>>>>> to
> > >>>>>>>>>>>> define the polyline masking file for Europe and
especially
> for
> > >>>>>> France.
> > >>>>>>>>>>>> Thank you in advance,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Regards.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Adrien
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
> > >>>>>>>>>>>>> According to our records, your request has been
resolved.
> If
> > >> you
> > >>>>>> have
> > >>>>>>>>>> any
> > >>>>>>>>>>>>> further questions or concerns, please respond to
this
> > message.
> > >>>>>>>>>>>> --
> > >>>>>>>>>>>> Adrien Michel
> > >>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> > >>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
> 37
> > >> 95
> > >>>> 15
> > >>>>>> |
> > >>>>>>>>>> E:
> > >>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >>>>>>>>>>>> Website: http://www.atmoterra.com
> > >>>>>>>>>>>>
> > >>>>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> Adrien Michel
> > >>>>>>>>>> Environmental Consultant | Consultant Environnement
> > >>>>>>>>>>
> > >>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> > >>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> > 95
> > >> 15
> > >>>> |
> > >>>>>>>> E:
> > >>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >>>>>>>>>> Website: http://www.atmoterra.com
> > >>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>>> --
> > >>>>>>>> Adrien Michel
> > >>>>>>>> Environmental Consultant | Consultant Environnement
> > >>>>>>>>
> > >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > >>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> 95
> > 15
> > >> |
> > >>>>>> E:
> > >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >>>>>>>> Website: http://www.atmoterra.com
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>> --
> > >>>>>> Adrien Michel
> > >>>>>> Environmental Consultant | Consultant Environnement
> > >>>>>>
> > >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > >>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> 15
> > |
> > >>>> E:
> > >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >>>>>> Website: http://www.atmoterra.com
> > >>>>>>
> > >>>>>>
> > >>>> --
> > >>>> Adrien Michel
> > >>>> Environmental Consultant | Consultant Environnement
> > >>>>
> > >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > >>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> > <+33%206%2095%2037%2095%2015> |
> > >> E:
> > >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >>>> Website: http://www.atmoterra.com
> > >>>>
> > >>>>
> > >> --
> > >> Adrien Michel
> > >> Environmental Consultant | Consultant Environnement
> > >>
> > >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > >> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9
89 16
> > 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> > <+33%206%2095%2037%2095%2015> | E:
> > >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > >> Website: http://www.atmoterra.com
> > >>
> > >>
> >
> > --
> > Adrien Michel
> > Environmental Consultant | Consultant Environnement
> >
> > ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> > T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16 27
> 84
> > <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> > <+33%206%2095%2037%2095%2015> | E:
> > amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> > Website: http://www.atmoterra.com
> >
> >
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Tue Oct 31 03:31:20 2017

Hi John,

Thanks you for taking this ticket.

I upload my files with file name: amichel_data .You'll think some of
my
point-observations files, one wrf file and my Point-Stat
configuration.

At least, I would like to configure MET to verify :

- temperature

- wind

-rainfall

-cloud

- pressure

-...

Actually here are my two issues:

- verify wrf files with many hourly-point observations

- find names of variables (temperature, rainfal,cloud) after
pre-processing with madis2nc to configure point-stat


Thanks,

Adrien


Le 18/10/2017 à 17:26, John Halley Gotway via RT a écrit :
> Hi Adrien,
>
> Julie asked me to take a look at this ticket.  The MET statistics
tools are
> intended to be run once for each time "verification time".  You pass
to
> them a forecast file, one or more observation files, and a
configuration
> file to tell the tool what you'd like it to do.
>
> But a lot of the details are dictated by your input data.  In the
example
> you sent, you're passing this file to Point-Stat:
>     met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc
>
> How many output times does this file contain?
>
> If you'd like, you could post this file to our anonymous ftp site,
and I
> can take a closer look at it.
>
> Just follow these directions:
>     https://dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John
>
> On Tue, Oct 17, 2017 at 2:03 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hi Adrien.
>>
>> With regard to processing multiple observation files for multiple
years in
>> point_stat in a faster/simpler way, I would like to speak to one of
our
>> main developers to find out more information.  I will get back to
you on
>> that.
>>
>> With regard to getting more information about additional variables,
you
>> mentioned that you cannot read your file after processing with
Madis2nc.
>> You should be able to read your NetCDF data with a utility called
>> "ncdump".  Here is a link to more information about the "ncdump"
utility:
>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
>> utilities_guide.html#ncdump_guide
>>
>> If you are unable to get and use the "ncdump" utility you are
welcome to
>> upload sample NetCDF files to our ftp site and I can dump the
variable
>> information and pass it back to you.
>>
>> You can upload your file(s) on our anonymous ftp site using these
>> instructions:
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>
>> I hope that helps.
>>
>> Julie
>>
>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT
<met_help at ucar.edu>
>> wrote:
>>
>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>
>>> Hi Julie,
>>>
>>> Well thank you it helps me. So actually my command shell looks
like that:
>>>
>>> point_stat \
>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
>>> met-6.0/data/Test/PointStatConfig \
>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
>>> -outdir met-6.0/data/point_stat \
>>> -v 5
>>>
>>> I will use point-stat for 23 point observations files per day for
>>> multiple years, is there a solution that will allow me to do it
>>> faster/simply? I tried with "point_obs
>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
>>> met-6.0/data/Metar_test/T" but it is not working.
>>>
>>>
>>> I have another question about Point-Stat Configuration. For
instance, I
>>> have used variables gives in the user_guide examples as bellow:
>>>
>>>    field = [
>>>         {
>>>           name       = "TMP";
>>>           level      = [ "Z2" ];
>>>           cat_thresh = [ <=273.0 ];
>>>       },
>>>         {
>>>       name       = "UGRD";
>>>           level      = [ "Z10" ];
>>>           cat_thresh = [ >=5.0 ];
>>>       },
>>>         {
>>>       name       = "VGRD";
>>>           level      = [ "Z10" ];
>>>           cat_thresh = [ >=5.0 ];
>>>       }
>>>      ];
>>>
>>>
>>> It is actually working, but I would like to evaluate additional
>>> variables. Where I can find informations about the name of
variables ?
>>> Indeed, I can not read my file after pre-processing with Madis2nc.
>>>
>>> Many thanks,
>>>
>>> Regards.
>>>
>>> Adrien
>>>
>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
>>>> Hi Adrien.
>>>>
>>>> When you run "point_stat" you can see the usage statement (see
below).
>>> You
>>>> can use the "-point_obs" option to specify additional point
observation
>>>> files:
>>>>
>>>>     "-point_obs file" specifies additional NetCDF point
observation
>> files
>>> to
>>>> be used (optional).
>>>>
>>>> You can use this option multiple times.  So, if you have multiple
>>>> additional observation files you can add "-point_obs <obs_file_a>
>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
>>> point_stat.
>>>> I hope that helps.  Please let us know if you have any other
questions.
>>>>
>>>> Julie
>>>>
>>>>
>>>> *** Model Evaluation Tools (METV6.0) ***
>>>>
>>>> Usage: point_stat
>>>>           fcst_file
>>>>           obs_file
>>>>           config_file
>>>>           [-point_obs file]
>>>>           [-obs_valid_beg time]
>>>>           [-obs_valid_end time]
>>>>           [-outdir path]
>>>>           [-log file]
>>>>           [-v level]
>>>>
>>>>           where   "fcst_file" is a gridded forecast file
containing the
>>>> field(s) to be verified (required).
>>>>                   "obs_file" is an observation file in NetCDF
format
>>>> containing the verifying point observations (required).
>>>>                   "config_file" is a PointStatConfig file
containing the
>>>> desired configuration settings (required).
>>>>                   "-point_obs file" specifies additional NetCDF
point
>>>> observation files to be used (optional).
>>>>                   "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]]
sets the
>>>> beginning of the matching time window (optional).
>>>>                   "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]]
sets the
>>> end
>>>> of the matching time window (optional).
>>>>                   "-outdir path" overrides the default output
directory
>>> (.)
>>>> (optional).
>>>>                   "-log file" outputs log messages to the
specified file
>>>> (optional).
>>>>                   "-v level" overrides the default level of
logging (2)
>>>> (optional).
>>>>
>>>>
>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>> wrote:
>>>>
>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>
>>>>> Hello Julie,
>>>>>
>>>>> How can I pass multiple netcdf point observation files to point-
stat
>> ? I
>>>>> didn't see any informations on the user_guide about it.
>>>>>
>>>>> Thank you,
>>>>>
>>>>> Adrien
>>>>>
>>>>>
>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
>>>>>> Hi Adrien.
>>>>>>
>>>>>> There’s no “need” to merge the files.   You can pass multiple
netcdf
>>>>> point
>>>>>> observation files to point_stat and ensemble_stat.  However, if
you
>>> would
>>>>>> like to merge the files, you could consider using the "ncrcat"
tool:
>>>>>>
>>>>>> https://linux.die.net/man/1/ncrcat
>>>>>>
>>>>>> from NCO:
>>>>>> http://nco.sourceforge.net/
>>>>>>
>>>>>> I hope that helps!
>>>>>>
>>>>>> Julie
>>>>>>
>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
>>> met_help at ucar.edu
>>>>>> wrote:
>>>>>>
>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>
>>>>>>> Hello Julie,
>>>>>>>
>>>>>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
>>> would
>>>>>>> like to merge these hourly data in daily file. Do you have
>> suggestion
>>> or
>>>>>>> recommendation on how to do it ? Is there option for that in
MET ?
>>>>>>>
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Adrien
>>>>>>>
>>>>>>>
>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
>>>>>>>>
>>>>>>>> Julie
>>>>>>>>
>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
>>>>> met_help at ucar.edu
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>
>>>>>>>>> Hi Julie,
>>>>>>>>>
>>>>>>>>> Thanks to the previous met_help ticket, now that worked
perfectly
>> !
>>> I
>>>>> am
>>>>>>>>> so grateful for your help, thank you. Now I will adapt this
method
>>> for
>>>>>>>>> all my data.
>>>>>>>>>
>>>>>>>>> Another time, thank you. I'll definitely let you know if I
have
>>> others
>>>>>>>>> questions.
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>>
>>>>>>>>> Adrien
>>>>>>>>>
>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>>>>>>> Hi Adrien.
>>>>>>>>>>
>>>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank you
>>> for
>>>>>>>>>> uploading your data.
>>>>>>>>>>
>>>>>>>>>> When I run point_stat with your data and configuration
file, I
>> see
>>>>> the
>>>>>>>>>> following warning:
>>>>>>>>>>
>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>>>>>>> WARNING:
>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable,
>> the
>>>>>>> lead
>>>>>>>>>> time does not match the requested lead time: (000000 !=
020000)
>>>>>>>>>> WARNING:
>>>>>>>>>> WARNING:
>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
>>>>> T_sfc(0,*,*)
>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>>>>>>> WARNING:
>>>>>>>>>>
>>>>>>>>>> There is a specific way in the CF-convention of specifying
the
>>>>>>>>>> initialization time of the model.  You do so by defining a
>> variable
>>>>>>> named
>>>>>>>>>> "forecast_reference_time".  When that variable is not
present,
>> MET
>>>>> sets
>>>>>>>>> the
>>>>>>>>>> forecast initialization time to the same value as the valid
time,
>>>>> which
>>>>>>>>>> results in a lead time of 0.
>>>>>>>>>>
>>>>>>>>>> You need to add the "forecast_reference_time" variable to
your
>>> model
>>>>>>>>>> files.  Take a look at this previous met_help ticket and
see if
>>> that
>>>>>>>>> helps:
>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
>>>>>>>>>>
>>>>>>>>>> Also, I see in your PointStatConfig file that you have
defined
>>>>>>>>> "lead_time"
>>>>>>>>>> in the fcst dictionary.  That is not necessary and could
cause
>>>>>>> problems.
>>>>>>>>>> MET determines the lead time by the time index of the time
>>> dimension
>>>>>>> that
>>>>>>>>>> you specify in the "level" field:
>>>>>>>>>>
>>>>>>>>>>              level      = "(0,*,*)";
>>>>>>>>>>
>>>>>>>>>> I hope that helps.  Please let us know if you have any
other
>>>>> questions.
>>>>>>>>>> Thanks,
>>>>>>>>>> Julie
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
>>>>>>> met_help at ucar.edu
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>>
>>>>>>>>>>> Hi Julie,
>>>>>>>>>>>
>>>>>>>>>>> Many thank, I have done as you suggested and MET seems to
read
>> my
>>> CF
>>>>>>>>>>> Compliant. However, I still have issues with the
configuration
>> of
>>>>>>>>>>> Point-Stat.
>>>>>>>>>>>
>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily file
for
>>>>>>> 2013-01-01
>>>>>>>>>>> I would also provide you :
>>>>>>>>>>> - point observation file from Madis2nc - hourly file for
>>>>>>>>>>> 2013-01-01_02:00:00
>>>>>>>>>>> - Point-Stat configuration
>>>>>>>>>>>
>>>>>>>>>>> I'm grateful for you help.
>>>>>>>>>>> Regards,
>>>>>>>>>>>
>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>
>>>>>>>>>>>> It is difficult to tell the problem with the file without
>> seeing
>>>>> it.
>>>>>>>>>>>> However, I have something for you to try that might work.
MET
>>>>> should
>>>>>>>>> be
>>>>>>>>>>>> able to read CF compliant files, and you have stated that
your
>>>>> NetCDF
>>>>>>>>>>> file
>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file, but
>>>>> since
>>>>>>>>> it
>>>>>>>>>>> is
>>>>>>>>>>>> having trouble, let's try explicitly telling the tools
how to
>>>>> process
>>>>>>>>> the
>>>>>>>>>>>> data by setting the following in your PointStat config
file:
>>>>>>>>>>>>
>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>
>>>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.  For
>>>>>>>>> example:
>>>>>>>>>>>> fcst = {
>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>> ...
>>>>>>>>>>>> }
>>>>>>>>>>>>
>>>>>>>>>>>> If that works, please let us know.  If that does not
work,
>> please
>>>>>>>>> upload
>>>>>>>>>>>> your file to our ftp server using the following
instructions
>> and
>>>>> let
>>>>>>> us
>>>>>>>>>>>> know once you have done that so that we can get the file
and
>>> take a
>>>>>>>>> look.
>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>
>>>>>>>>>>>> Julie
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>>>>>>>>>>>>> Hi Julie.
>>>>>>>>>>>>>
>>>>>>>>>>>>>         I've done as you suggested and it ran without
problem,
>>> thank
>>>>>>> you!
>>>>>>>>>>>>> I come up with a another issue.. I'm trying to use
Point-Stat
>> :
>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>>>>>>
>>>>>>>>>>>>> However, Point Stat seems to have issue to read my
forecast
>> file
>>>>>>> with
>>>>>>>>>>>>> the following informations:
>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
>>>>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file()
->
>>> created
>>>>>>> new
>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>> I was wondering if you had any insight on what I could
be
>> doing
>>>>>>>>> wrong. I
>>>>>>>>>>>>> appreciate any help you can give.
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Adrien Michel/
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> /
>>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I see that you have a question about how to define a
polyline
>>>>>>> masking
>>>>>>>>>>>>>> file.  The -mask_grid option would take a named grid or
a
>>> gridded
>>>>>>>>> data
>>>>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
>>>>> masking
>>>>>>>>>>> file.
>>>>>>>>>>>>>> If you'd only like to keep the points falling inside
your
>> model
>>>>>>>>> domain,
>>>>>>>>>>>>> and
>>>>>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid
>>> is
>>>>>>> very
>>>>>>>>>>>>>> simple:
>>>>>>>>>>>>>>           -mask_grid /path/to/gridded/data/file
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> However, if you'd prefer the flexibility of defining a
>> polyline
>>>>>>>>> masking
>>>>>>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>>>>>>           -mask_poly /path/to/polyline/mask/file
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> To create a polyline mask, you simply create an ASCII
file
>>>>>>>>> containing a
>>>>>>>>>>>>>> list of lat/lons that define the region of interest.
For
>>>>> example,
>>>>>>>>>>> take a
>>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of
the
>> file
>>>>>>>>>>> specifies
>>>>>>>>>>>>>> the name for the polyline, and the remaining lines
contain
>>>>> lat/lon
>>>>>>>>>>> values
>>>>>>>>>>>>>> for the boundary points.  The last point is connected
back up
>>> to
>>>>>>> the
>>>>>>>>>>>>> first
>>>>>>>>>>>>>> point to complete the area.  The example is named "SWC"
and
>>>>>>> contains
>>>>>>>>> 33
>>>>>>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
>>>>> questions.
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
>> Ticket/Display.html?id=81768
>>>>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I have further questions about Madis2nc use. I would
like to
>>> use
>>>>>>> the
>>>>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
>>>>> details
>>>>>>>>> on
>>>>>>>>>>>>>>> how define the polyline masking file in the user
guide. I
>>> should
>>>>>>>>> like
>>>>>>>>>>> to
>>>>>>>>>>>>>>> define the polyline masking file for Europe and
especially
>> for
>>>>>>>>> France.
>>>>>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Regards.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Adrien
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit
:
>>>>>>>>>>>>>>>> According to our records, your request has been
resolved.
>> If
>>>>> you
>>>>>>>>> have
>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>> further questions or concerns, please respond to this
>>> message.
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
>> 37
>>>>> 95
>>>>>>> 15
>>>>>>>>> |
>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>
>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>>> 95
>>>>> 15
>>>>>>> |
>>>>>>>>>>> E:
>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Adrien Michel
>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>
>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37
>> 95
>>> 15
>>>>> |
>>>>>>>>> E:
>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Adrien Michel
>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>
>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
>> 15
>>> |
>>>>>>> E:
>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>
>>>>>>>>>
>>>>>>> --
>>>>>>> Adrien Michel
>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>
>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>>> <+33%206%2095%2037%2095%2015> |
>>>>> E:
>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>> Website: http://www.atmoterra.com
>>>>>>>
>>>>>>>
>>>>> --
>>>>> Adrien Michel
>>>>> Environmental Consultant | Consultant Environnement
>>>>>
>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9
89 16
>>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>> <+33%206%2095%2037%2095%2015> | E:
>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>> Website: http://www.atmoterra.com
>>>>>
>>>>>
>>> --
>>> Adrien Michel
>>> Environmental Consultant | Consultant Environnement
>>>
>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16 27
>> 84
>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>> <+33%206%2095%2037%2095%2015> | E:
>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>> Website: http://www.atmoterra.com
>>>
>>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Tue Nov 14 00:04:48 2017



Hi Julie,

Did you receive my last email ?

I send this following email to you co-worker John two weeks ago. Could
you help me with these isssues ?


I uploaded my files with file name: amichel_data .You'll find some of
my
point-observations files, one wrf file and my Point-Stat
configuration.

At least, I would like to configure MET to verify :

- temperature

- wind

-rainfall

-cloud

- pressure

-...

Actually here are my two issues:

- verify wrf files with many hourly-point observations

- find names of variables (temperature, rainfal,cloud) after
pre-processing with madis2nc to configure point-stat


Thanks,

Adrien

Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
> Hi Adrien.
>
> With regard to processing multiple observation files for multiple
years in
> point_stat in a faster/simpler way, I would like to speak to one of
our
> main developers to find out more information.  I will get back to
you on
> that.
>
> With regard to getting more information about additional variables,
you
> mentioned that you cannot read your file after processing with
Madis2nc.
> You should be able to read your NetCDF data with a utility called
> "ncdump".  Here is a link to more information about the "ncdump"
utility:
> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
> utilities_guide.html#ncdump_guide
>
> If you are unable to get and use the "ncdump" utility you are
welcome to
> upload sample NetCDF files to our ftp site and I can dump the
variable
> information and pass it back to you.
>
> You can upload your file(s) on our anonymous ftp site using these
> instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> I hope that helps.
>
> Julie
>
> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hi Julie,
>>
>> Well thank you it helps me. So actually my command shell looks like
that:
>>
>> point_stat \
>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
>> met-6.0/data/Test/PointStatConfig \
>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
>> -outdir met-6.0/data/point_stat \
>> -v 5
>>
>> I will use point-stat for 23 point observations files per day for
>> multiple years, is there a solution that will allow me to do it
>> faster/simply? I tried with "point_obs
>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
>> met-6.0/data/Metar_test/T" but it is not working.
>>
>>
>> I have another question about Point-Stat Configuration. For
instance, I
>> have used variables gives in the user_guide examples as bellow:
>>
>>    field = [
>>         {
>>           name       = "TMP";
>>           level      = [ "Z2" ];
>>           cat_thresh = [ <=273.0 ];
>>       },
>>         {
>>       name       = "UGRD";
>>           level      = [ "Z10" ];
>>           cat_thresh = [ >=5.0 ];
>>       },
>>         {
>>       name       = "VGRD";
>>           level      = [ "Z10" ];
>>           cat_thresh = [ >=5.0 ];
>>       }
>>      ];
>>
>>
>> It is actually working, but I would like to evaluate additional
>> variables. Where I can find informations about the name of
variables ?
>> Indeed, I can not read my file after pre-processing with Madis2nc.
>>
>> Many thanks,
>>
>> Regards.
>>
>> Adrien
>>
>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
>>> Hi Adrien.
>>>
>>> When you run "point_stat" you can see the usage statement (see
below).
>> You
>>> can use the "-point_obs" option to specify additional point
observation
>>> files:
>>>
>>>     "-point_obs file" specifies additional NetCDF point
observation files
>> to
>>> be used (optional).
>>>
>>> You can use this option multiple times.  So, if you have multiple
>>> additional observation files you can add "-point_obs <obs_file_a>
>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
>> point_stat.
>>> I hope that helps.  Please let us know if you have any other
questions.
>>>
>>> Julie
>>>
>>>
>>> *** Model Evaluation Tools (METV6.0) ***
>>>
>>> Usage: point_stat
>>>           fcst_file
>>>           obs_file
>>>           config_file
>>>           [-point_obs file]
>>>           [-obs_valid_beg time]
>>>           [-obs_valid_end time]
>>>           [-outdir path]
>>>           [-log file]
>>>           [-v level]
>>>
>>>           where   "fcst_file" is a gridded forecast file
containing the
>>> field(s) to be verified (required).
>>>                   "obs_file" is an observation file in NetCDF
format
>>> containing the verifying point observations (required).
>>>                   "config_file" is a PointStatConfig file
containing the
>>> desired configuration settings (required).
>>>                   "-point_obs file" specifies additional NetCDF
point
>>> observation files to be used (optional).
>>>                   "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]]
sets the
>>> beginning of the matching time window (optional).
>>>                   "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]]
sets the
>> end
>>> of the matching time window (optional).
>>>                   "-outdir path" overrides the default output
directory
>> (.)
>>> (optional).
>>>                   "-log file" outputs log messages to the
specified file
>>> (optional).
>>>                   "-v level" overrides the default level of
logging (2)
>>> (optional).
>>>
>>>
>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hello Julie,
>>>>
>>>> How can I pass multiple netcdf point observation files to point-
stat ? I
>>>> didn't see any informations on the user_guide about it.
>>>>
>>>> Thank you,
>>>>
>>>> Adrien
>>>>
>>>>
>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
>>>>> Hi Adrien.
>>>>>
>>>>> There’s no “need” to merge the files.   You can pass multiple
netcdf
>>>> point
>>>>> observation files to point_stat and ensemble_stat.  However, if
you
>> would
>>>>> like to merge the files, you could consider using the "ncrcat"
tool:
>>>>>
>>>>> https://linux.die.net/man/1/ncrcat
>>>>>
>>>>> from NCO:
>>>>> http://nco.sourceforge.net/
>>>>>
>>>>> I hope that helps!
>>>>>
>>>>> Julie
>>>>>
>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hello Julie,
>>>>>>
>>>>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
>> would
>>>>>> like to merge these hourly data in daily file. Do you have
suggestion
>> or
>>>>>> recommendation on how to do it ? Is there option for that in
MET ?
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Adrien
>>>>>>
>>>>>>
>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
>>>>>>>
>>>>>>> Julie
>>>>>>>
>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hi Julie,
>>>>>>>>
>>>>>>>> Thanks to the previous met_help ticket, now that worked
perfectly !
>> I
>>>> am
>>>>>>>> so grateful for your help, thank you. Now I will adapt this
method
>> for
>>>>>>>> all my data.
>>>>>>>>
>>>>>>>> Another time, thank you. I'll definitely let you know if I
have
>> others
>>>>>>>> questions.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>>
>>>>>>>> Adrien
>>>>>>>>
>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>>>>>> Hi Adrien.
>>>>>>>>>
>>>>>>>>> I'm glad MET was able to read your CF compliant file.  Thank
you
>> for
>>>>>>>>> uploading your data.
>>>>>>>>>
>>>>>>>>> When I run point_stat with your data and configuration file,
I see
>>>> the
>>>>>>>>> following warning:
>>>>>>>>>
>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>>>>>> WARNING:
>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable, the
>>>>>> lead
>>>>>>>>> time does not match the requested lead time: (000000 !=
020000)
>>>>>>>>> WARNING:
>>>>>>>>> WARNING:
>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
>>>> T_sfc(0,*,*)
>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>>>>>> WARNING:
>>>>>>>>>
>>>>>>>>> There is a specific way in the CF-convention of specifying
the
>>>>>>>>> initialization time of the model.  You do so by defining a
variable
>>>>>> named
>>>>>>>>> "forecast_reference_time".  When that variable is not
present, MET
>>>> sets
>>>>>>>> the
>>>>>>>>> forecast initialization time to the same value as the valid
time,
>>>> which
>>>>>>>>> results in a lead time of 0.
>>>>>>>>>
>>>>>>>>> You need to add the "forecast_reference_time" variable to
your
>> model
>>>>>>>>> files.  Take a look at this previous met_help ticket and see
if
>> that
>>>>>>>> helps:
>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
>>>>>>>>>
>>>>>>>>> Also, I see in your PointStatConfig file that you have
defined
>>>>>>>> "lead_time"
>>>>>>>>> in the fcst dictionary.  That is not necessary and could
cause
>>>>>> problems.
>>>>>>>>> MET determines the lead time by the time index of the time
>> dimension
>>>>>> that
>>>>>>>>> you specify in the "level" field:
>>>>>>>>>
>>>>>>>>>              level      = "(0,*,*)";
>>>>>>>>>
>>>>>>>>> I hope that helps.  Please let us know if you have any other
>>>> questions.
>>>>>>>>> Thanks,
>>>>>>>>> Julie
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
>>>>>> met_help at ucar.edu
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>
>>>>>>>>>> Hi Julie,
>>>>>>>>>>
>>>>>>>>>> Many thank, I have done as you suggested and MET seems to
read my
>> CF
>>>>>>>>>> Compliant. However, I still have issues with the
configuration of
>>>>>>>>>> Point-Stat.
>>>>>>>>>>
>>>>>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily file
for
>>>>>> 2013-01-01
>>>>>>>>>> I would also provide you :
>>>>>>>>>> - point observation file from Madis2nc - hourly file for
>>>>>>>>>> 2013-01-01_02:00:00
>>>>>>>>>> - Point-Stat configuration
>>>>>>>>>>
>>>>>>>>>> I'm grateful for you help.
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Adrien Michel
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>
>>>>>>>>>>> It is difficult to tell the problem with the file without
seeing
>>>> it.
>>>>>>>>>>> However, I have something for you to try that might work.
MET
>>>> should
>>>>>>>> be
>>>>>>>>>>> able to read CF compliant files, and you have stated that
your
>>>> NetCDF
>>>>>>>>>> file
>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file, but
>>>> since
>>>>>>>> it
>>>>>>>>>> is
>>>>>>>>>>> having trouble, let's try explicitly telling the tools how
to
>>>> process
>>>>>>>> the
>>>>>>>>>>> data by setting the following in your PointStat config
file:
>>>>>>>>>>>
>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>
>>>>>>>>>>> This entry should be defined within the "fcst" dictionary.
For
>>>>>>>> example:
>>>>>>>>>>> fcst = {
>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>> ...
>>>>>>>>>>> }
>>>>>>>>>>>
>>>>>>>>>>> If that works, please let us know.  If that does not work,
please
>>>>>>>> upload
>>>>>>>>>>> your file to our ftp server using the following
instructions and
>>>> let
>>>>>> us
>>>>>>>>>>> know once you have done that so that we can get the file
and
>> take a
>>>>>>>> look.
>>>>>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>>
>>>>>>>>>>> Julie
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
>>>>>>>> met_help at ucar.edu
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Julie.
>>>>>>>>>>>>
>>>>>>>>>>>>         I've done as you suggested and it ran without
problem,
>> thank
>>>>>> you!
>>>>>>>>>>>> I come up with a another issue.. I'm trying to use Point-
Stat :
>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>>>>>
>>>>>>>>>>>> However, Point Stat seems to have issue to read my
forecast file
>>>>>> with
>>>>>>>>>>>> the following informations:
>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
>>>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() ->
>> created
>>>>>> new
>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>> I was wondering if you had any insight on what I could be
doing
>>>>>>>> wrong. I
>>>>>>>>>>>> appreciate any help you can give.
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>
>>>>>>>>>>>> Adrien Michel/
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /
>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I see that you have a question about how to define a
polyline
>>>>>> masking
>>>>>>>>>>>>> file.  The -mask_grid option would take a named grid or
a
>> gridded
>>>>>>>> data
>>>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
>>>> masking
>>>>>>>>>> file.
>>>>>>>>>>>>> If you'd only like to keep the points falling inside
your model
>>>>>>>> domain,
>>>>>>>>>>>> and
>>>>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid
>> is
>>>>>> very
>>>>>>>>>>>>> simple:
>>>>>>>>>>>>>           -mask_grid /path/to/gridded/data/file
>>>>>>>>>>>>>
>>>>>>>>>>>>> However, if you'd prefer the flexibility of defining a
polyline
>>>>>>>> masking
>>>>>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>>>>>           -mask_poly /path/to/polyline/mask/file
>>>>>>>>>>>>>
>>>>>>>>>>>>> To create a polyline mask, you simply create an ASCII
file
>>>>>>>> containing a
>>>>>>>>>>>>> list of lat/lons that define the region of interest.
For
>>>> example,
>>>>>>>>>> take a
>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of
the file
>>>>>>>>>> specifies
>>>>>>>>>>>>> the name for the polyline, and the remaining lines
contain
>>>> lat/lon
>>>>>>>>>> values
>>>>>>>>>>>>> for the boundary points.  The last point is connected
back up
>> to
>>>>>> the
>>>>>>>>>>>> first
>>>>>>>>>>>>> point to complete the area.  The example is named "SWC"
and
>>>>>> contains
>>>>>>>> 33
>>>>>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I hope this helps.  Please let us know if you have other
>>>> questions.
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT <
>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>>>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I have further questions about Madis2nc use. I would
like to
>> use
>>>>>> the
>>>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
>>>> details
>>>>>>>> on
>>>>>>>>>>>>>> how define the polyline masking file in the user guide.
I
>> should
>>>>>>>> like
>>>>>>>>>> to
>>>>>>>>>>>>>> define the polyline masking file for Europe and
especially for
>>>>>>>> France.
>>>>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Regards.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Adrien
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a écrit
:
>>>>>>>>>>>>>>> According to our records, your request has been
resolved. If
>>>> you
>>>>>>>> have
>>>>>>>>>>>> any
>>>>>>>>>>>>>>> further questions or concerns, please respond to this
>> message.
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>>>> 95
>>>>>> 15
>>>>>>>> |
>>>>>>>>>>>> E:
>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>
>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>> 95
>>>> 15
>>>>>> |
>>>>>>>>>> E:
>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Adrien Michel
>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>
>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
>> 15
>>>> |
>>>>>>>> E:
>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>> |
>>>>>> E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>> <+33%206%2095%2037%2095%2015> |
>>>> E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16
>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>> <+33%206%2095%2037%2095%2015> | E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16 27 84
>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>> <+33%206%2095%2037%2095%2015> | E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: John Halley Gotway
Time: Tue Nov 14 13:08:55 2017

Adrien,

My apologies for the long delay in responding.  I went to go grab the
data
you posted to our ftp site, but unfortunately, it has already aged
off.

Any chance you could repost the data?

Sorry about that.

John


On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
>
>
> Hi Julie,
>
> Did you receive my last email ?
>
> I send this following email to you co-worker John two weeks ago.
Could
> you help me with these isssues ?
>
>
> I uploaded my files with file name: amichel_data .You'll find some
of my
> point-observations files, one wrf file and my Point-Stat
configuration.
>
> At least, I would like to configure MET to verify :
>
> - temperature
>
> - wind
>
> -rainfall
>
> -cloud
>
> - pressure
>
> -...
>
> Actually here are my two issues:
>
> - verify wrf files with many hourly-point observations
>
> - find names of variables (temperature, rainfal,cloud) after
> pre-processing with madis2nc to configure point-stat
>
>
> Thanks,
>
> Adrien
>
> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
> > Hi Adrien.
> >
> > With regard to processing multiple observation files for multiple
years
> in
> > point_stat in a faster/simpler way, I would like to speak to one
of our
> > main developers to find out more information.  I will get back to
you on
> > that.
> >
> > With regard to getting more information about additional
variables, you
> > mentioned that you cannot read your file after processing with
Madis2nc.
> > You should be able to read your NetCDF data with a utility called
> > "ncdump".  Here is a link to more information about the "ncdump"
utility:
> > http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
> > utilities_guide.html#ncdump_guide
> >
> > If you are unable to get and use the "ncdump" utility you are
welcome to
> > upload sample NetCDF files to our ftp site and I can dump the
variable
> > information and pass it back to you.
> >
> > You can upload your file(s) on our anonymous ftp site using these
> > instructions:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > I hope that helps.
> >
> > Julie
> >
> > On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hi Julie,
> >>
> >> Well thank you it helps me. So actually my command shell looks
like
> that:
> >>
> >> point_stat \
> >> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
> >> met-6.0/data/Metar_test/TT/20130101_0100.nc \
> >> met-6.0/data/Test/PointStatConfig \
> >> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
> >> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
> >> -outdir met-6.0/data/point_stat \
> >> -v 5
> >>
> >> I will use point-stat for 23 point observations files per day for
> >> multiple years, is there a solution that will allow me to do it
> >> faster/simply? I tried with "point_obs
> >> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
> >> met-6.0/data/Metar_test/T" but it is not working.
> >>
> >>
> >> I have another question about Point-Stat Configuration. For
instance, I
> >> have used variables gives in the user_guide examples as bellow:
> >>
> >>    field = [
> >>         {
> >>           name       = "TMP";
> >>           level      = [ "Z2" ];
> >>           cat_thresh = [ <=273.0 ];
> >>       },
> >>         {
> >>       name       = "UGRD";
> >>           level      = [ "Z10" ];
> >>           cat_thresh = [ >=5.0 ];
> >>       },
> >>         {
> >>       name       = "VGRD";
> >>           level      = [ "Z10" ];
> >>           cat_thresh = [ >=5.0 ];
> >>       }
> >>      ];
> >>
> >>
> >> It is actually working, but I would like to evaluate additional
> >> variables. Where I can find informations about the name of
variables ?
> >> Indeed, I can not read my file after pre-processing with
Madis2nc.
> >>
> >> Many thanks,
> >>
> >> Regards.
> >>
> >> Adrien
> >>
> >> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> When you run "point_stat" you can see the usage statement (see
below).
> >> You
> >>> can use the "-point_obs" option to specify additional point
observation
> >>> files:
> >>>
> >>>     "-point_obs file" specifies additional NetCDF point
observation
> files
> >> to
> >>> be used (optional).
> >>>
> >>> You can use this option multiple times.  So, if you have
multiple
> >>> additional observation files you can add "-point_obs
<obs_file_a>
> >>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
> >> point_stat.
> >>> I hope that helps.  Please let us know if you have any other
questions.
> >>>
> >>> Julie
> >>>
> >>>
> >>> *** Model Evaluation Tools (METV6.0) ***
> >>>
> >>> Usage: point_stat
> >>>           fcst_file
> >>>           obs_file
> >>>           config_file
> >>>           [-point_obs file]
> >>>           [-obs_valid_beg time]
> >>>           [-obs_valid_end time]
> >>>           [-outdir path]
> >>>           [-log file]
> >>>           [-v level]
> >>>
> >>>           where   "fcst_file" is a gridded forecast file
containing the
> >>> field(s) to be verified (required).
> >>>                   "obs_file" is an observation file in NetCDF
format
> >>> containing the verifying point observations (required).
> >>>                   "config_file" is a PointStatConfig file
containing
> the
> >>> desired configuration settings (required).
> >>>                   "-point_obs file" specifies additional NetCDF
point
> >>> observation files to be used (optional).
> >>>                   "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]]
sets the
> >>> beginning of the matching time window (optional).
> >>>                   "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]]
sets the
> >> end
> >>> of the matching time window (optional).
> >>>                   "-outdir path" overrides the default output
directory
> >> (.)
> >>> (optional).
> >>>                   "-log file" outputs log messages to the
specified
> file
> >>> (optional).
> >>>                   "-v level" overrides the default level of
logging (2)
> >>> (optional).
> >>>
> >>>
> >>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hello Julie,
> >>>>
> >>>> How can I pass multiple netcdf point observation files to
point-stat
> ? I
> >>>> didn't see any informations on the user_guide about it.
> >>>>
> >>>> Thank you,
> >>>>
> >>>> Adrien
> >>>>
> >>>>
> >>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> >>>>> Hi Adrien.
> >>>>>
> >>>>> There’s no “need” to merge the files.   You can pass multiple
netcdf
> >>>> point
> >>>>> observation files to point_stat and ensemble_stat.  However,
if you
> >> would
> >>>>> like to merge the files, you could consider using the "ncrcat"
tool:
> >>>>>
> >>>>> https://linux.die.net/man/1/ncrcat
> >>>>>
> >>>>> from NCO:
> >>>>> http://nco.sourceforge.net/
> >>>>>
> >>>>> I hope that helps!
> >>>>>
> >>>>> Julie
> >>>>>
> >>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hello Julie,
> >>>>>>
> >>>>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
> >> would
> >>>>>> like to merge these hourly data in daily file. Do you have
> suggestion
> >> or
> >>>>>> recommendation on how to do it ? Is there option for that in
MET ?
> >>>>>>
> >>>>>>
> >>>>>> Regards,
> >>>>>>
> >>>>>> Adrien
> >>>>>>
> >>>>>>
> >>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> >>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
> >>>>>>>
> >>>>>>> Julie
> >>>>>>>
> >>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hi Julie,
> >>>>>>>>
> >>>>>>>> Thanks to the previous met_help ticket, now that worked
perfectly
> !
> >> I
> >>>> am
> >>>>>>>> so grateful for your help, thank you. Now I will adapt this
method
> >> for
> >>>>>>>> all my data.
> >>>>>>>>
> >>>>>>>> Another time, thank you. I'll definitely let you know if I
have
> >> others
> >>>>>>>> questions.
> >>>>>>>>
> >>>>>>>> Best regards,
> >>>>>>>>
> >>>>>>>> Adrien
> >>>>>>>>
> >>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>>>>>>>> Hi Adrien.
> >>>>>>>>>
> >>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank you
> >> for
> >>>>>>>>> uploading your data.
> >>>>>>>>>
> >>>>>>>>> When I run point_stat with your data and configuration
file, I
> see
> >>>> the
> >>>>>>>>> following warning:
> >>>>>>>>>
> >>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>>>>>>>> WARNING:
> >>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable,
> the
> >>>>>> lead
> >>>>>>>>> time does not match the requested lead time: (000000 !=
020000)
> >>>>>>>>> WARNING:
> >>>>>>>>> WARNING:
> >>>>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
> >>>> T_sfc(0,*,*)
> >>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
> >>>>>>>>> WARNING:
> >>>>>>>>>
> >>>>>>>>> There is a specific way in the CF-convention of specifying
the
> >>>>>>>>> initialization time of the model.  You do so by defining a
> variable
> >>>>>> named
> >>>>>>>>> "forecast_reference_time".  When that variable is not
present,
> MET
> >>>> sets
> >>>>>>>> the
> >>>>>>>>> forecast initialization time to the same value as the
valid time,
> >>>> which
> >>>>>>>>> results in a lead time of 0.
> >>>>>>>>>
> >>>>>>>>> You need to add the "forecast_reference_time" variable to
your
> >> model
> >>>>>>>>> files.  Take a look at this previous met_help ticket and
see if
> >> that
> >>>>>>>> helps:
> >>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
> >>>>>>>>>
> >>>>>>>>> Also, I see in your PointStatConfig file that you have
defined
> >>>>>>>> "lead_time"
> >>>>>>>>> in the fcst dictionary.  That is not necessary and could
cause
> >>>>>> problems.
> >>>>>>>>> MET determines the lead time by the time index of the time
> >> dimension
> >>>>>> that
> >>>>>>>>> you specify in the "level" field:
> >>>>>>>>>
> >>>>>>>>>              level      = "(0,*,*)";
> >>>>>>>>>
> >>>>>>>>> I hope that helps.  Please let us know if you have any
other
> >>>> questions.
> >>>>>>>>> Thanks,
> >>>>>>>>> Julie
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
> >>>>>> met_help at ucar.edu
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>>>
> >>>>>>>>>> Hi Julie,
> >>>>>>>>>>
> >>>>>>>>>> Many thank, I have done as you suggested and MET seems to
read
> my
> >> CF
> >>>>>>>>>> Compliant. However, I still have issues with the
configuration
> of
> >>>>>>>>>> Point-Stat.
> >>>>>>>>>>
> >>>>>>>>>> So I  uploaded my file (name file: michel_data)
> >>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily file
for
> >>>>>> 2013-01-01
> >>>>>>>>>> I would also provide you :
> >>>>>>>>>> - point observation file from Madis2nc - hourly file for
> >>>>>>>>>> 2013-01-01_02:00:00
> >>>>>>>>>> - Point-Stat configuration
> >>>>>>>>>>
> >>>>>>>>>> I'm grateful for you help.
> >>>>>>>>>> Regards,
> >>>>>>>>>>
> >>>>>>>>>> Adrien Michel
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
> >>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>
> >>>>>>>>>>> It is difficult to tell the problem with the file
without
> seeing
> >>>> it.
> >>>>>>>>>>> However, I have something for you to try that might
work.  MET
> >>>> should
> >>>>>>>> be
> >>>>>>>>>>> able to read CF compliant files, and you have stated
that your
> >>>> NetCDF
> >>>>>>>>>> file
> >>>>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file, but
> >>>> since
> >>>>>>>> it
> >>>>>>>>>> is
> >>>>>>>>>>> having trouble, let's try explicitly telling the tools
how to
> >>>> process
> >>>>>>>> the
> >>>>>>>>>>> data by setting the following in your PointStat config
file:
> >>>>>>>>>>>
> >>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>
> >>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.  For
> >>>>>>>> example:
> >>>>>>>>>>> fcst = {
> >>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>> ...
> >>>>>>>>>>> }
> >>>>>>>>>>>
> >>>>>>>>>>> If that works, please let us know.  If that does not
work,
> please
> >>>>>>>> upload
> >>>>>>>>>>> your file to our ftp server using the following
instructions
> and
> >>>> let
> >>>>>> us
> >>>>>>>>>>> know once you have done that so that we can get the file
and
> >> take a
> >>>>>>>> look.
> >>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>>>>>>>
> >>>>>>>>>>> Thanks!
> >>>>>>>>>>>
> >>>>>>>>>>> Julie
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
> >>>>>>>> met_help at ucar.edu
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hi Julie.
> >>>>>>>>>>>>
> >>>>>>>>>>>>         I've done as you suggested and it ran without
problem,
> >> thank
> >>>>>> you!
> >>>>>>>>>>>> I come up with a another issue.. I'm trying to use
Point-Stat
> :
> >>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>>>>>>>> - a point observation file coming from Madis2nc
> >>>>>>>>>>>>
> >>>>>>>>>>>> However, Point Stat seems to have issue to read my
forecast
> file
> >>>>>> with
> >>>>>>>>>>>> the following informations:
> >>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
> >>>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file()
->
> >> created
> >>>>>> new
> >>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>>>> ERROR  :
> >>>>>>>>>>>>> ERROR  : Trouble reading forecast file
> >>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>>>>>>>>> ERROR  :
> >>>>>>>>>>>> I was wondering if you had any insight on what I could
be
> doing
> >>>>>>>> wrong. I
> >>>>>>>>>>>> appreciate any help you can give.
> >>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Adrien Michel/
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> /
> >>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit
:
> >>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I see that you have a question about how to define a
polyline
> >>>>>> masking
> >>>>>>>>>>>>> file.  The -mask_grid option would take a named grid
or a
> >> gridded
> >>>>>>>> data
> >>>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
> >>>> masking
> >>>>>>>>>> file.
> >>>>>>>>>>>>> If you'd only like to keep the points falling inside
your
> model
> >>>>>>>> domain,
> >>>>>>>>>>>> and
> >>>>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid
> >> is
> >>>>>> very
> >>>>>>>>>>>>> simple:
> >>>>>>>>>>>>>           -mask_grid /path/to/gridded/data/file
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> However, if you'd prefer the flexibility of defining a
> polyline
> >>>>>>>> masking
> >>>>>>>>>>>>> region, using -mask_poly would work too:
> >>>>>>>>>>>>>           -mask_poly /path/to/polyline/mask/file
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> To create a polyline mask, you simply create an ASCII
file
> >>>>>>>> containing a
> >>>>>>>>>>>>> list of lat/lons that define the region of interest.
For
> >>>> example,
> >>>>>>>>>> take a
> >>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of
the
> file
> >>>>>>>>>> specifies
> >>>>>>>>>>>>> the name for the polyline, and the remaining lines
contain
> >>>> lat/lon
> >>>>>>>>>> values
> >>>>>>>>>>>>> for the boundary points.  The last point is connected
back up
> >> to
> >>>>>> the
> >>>>>>>>>>>> first
> >>>>>>>>>>>>> point to complete the area.  The example is named
"SWC" and
> >>>>>> contains
> >>>>>>>> 33
> >>>>>>>>>>>>> points, and there is no real maximum.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
> >>>> questions.
> >>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<
> >>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Tic
> ket/Display.html?id=81768
> >>>>>>>>>>>>>> Hello Julie,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I have further questions about Madis2nc use. I would
like to
> >> use
> >>>>>> the
> >>>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
> >>>> details
> >>>>>>>> on
> >>>>>>>>>>>>>> how define the polyline masking file in the user
guide. I
> >> should
> >>>>>>>> like
> >>>>>>>>>> to
> >>>>>>>>>>>>>> define the polyline masking file for Europe and
especially
> for
> >>>>>>>> France.
> >>>>>>>>>>>>>> Thank you in advance,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Regards.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Adrien
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>> According to our records, your request has been
resolved.
> If
> >>>> you
> >>>>>>>> have
> >>>>>>>>>>>> any
> >>>>>>>>>>>>>>> further questions or concerns, please respond to
this
> >> message.
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
> 37
> >>>> 95
> >>>>>> 15
> >>>>>>>> |
> >>>>>>>>>>>> E:
> >>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>
> >>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> >> 95
> >>>> 15
> >>>>>> |
> >>>>>>>>>> E:
> >>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Adrien Michel
> >>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>
> >>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> 95
> >> 15
> >>>> |
> >>>>>>>> E:
> >>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>> --
> >>>>>>>> Adrien Michel
> >>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>
> >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> 15
> >> |
> >>>>>> E:
> >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>
> >>>>>>>>
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
> >> <+33%206%2095%2037%2095%2015> |
> >>>> E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
> >> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> <+33%206%2095%2037%2095%2015>
> >> <+33%206%2095%2037%2095%2015> | E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16 27 84
> <+33%209%2089%2016%2027%2084>
> >> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> <+33%206%2095%2037%2095%2015>
> >> <+33%206%2095%2037%2095%2015> | E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
27 84
> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> <+33%206%2095%2037%2095%2015> | E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Wed Nov 22 01:31:12 2017

Hi John,

No problem. I've repost the data on your ftp site at file name :
amichel_data

Regards,

Adrien


Le 14/11/2017 à 21:08, John Halley Gotway via RT a écrit :
> Adrien,
>
> My apologies for the long delay in responding.  I went to go grab
the data
> you posted to our ftp site, but unfortunately, it has already aged
off.
>
> Any chance you could repost the data?
>
> Sorry about that.
>
> John
>
>
> On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>>
>>
>> Hi Julie,
>>
>> Did you receive my last email ?
>>
>> I send this following email to you co-worker John two weeks ago.
Could
>> you help me with these isssues ?
>>
>>
>> I uploaded my files with file name: amichel_data .You'll find some
of my
>> point-observations files, one wrf file and my Point-Stat
configuration.
>>
>> At least, I would like to configure MET to verify :
>>
>> - temperature
>>
>> - wind
>>
>> -rainfall
>>
>> -cloud
>>
>> - pressure
>>
>> -...
>>
>> Actually here are my two issues:
>>
>> - verify wrf files with many hourly-point observations
>>
>> - find names of variables (temperature, rainfal,cloud) after
>> pre-processing with madis2nc to configure point-stat
>>
>>
>> Thanks,
>>
>> Adrien
>>
>> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>> Hi Adrien.
>>>
>>> With regard to processing multiple observation files for multiple
years
>> in
>>> point_stat in a faster/simpler way, I would like to speak to one
of our
>>> main developers to find out more information.  I will get back to
you on
>>> that.
>>>
>>> With regard to getting more information about additional
variables, you
>>> mentioned that you cannot read your file after processing with
Madis2nc.
>>> You should be able to read your NetCDF data with a utility called
>>> "ncdump".  Here is a link to more information about the "ncdump"
utility:
>>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
>>> utilities_guide.html#ncdump_guide
>>>
>>> If you are unable to get and use the "ncdump" utility you are
welcome to
>>> upload sample NetCDF files to our ftp site and I can dump the
variable
>>> information and pass it back to you.
>>>
>>> You can upload your file(s) on our anonymous ftp site using these
>>> instructions:
>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>
>>> I hope that helps.
>>>
>>> Julie
>>>
>>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hi Julie,
>>>>
>>>> Well thank you it helps me. So actually my command shell looks
like
>> that:
>>>> point_stat \
>>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
>>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
>>>> met-6.0/data/Test/PointStatConfig \
>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
>>>> -outdir met-6.0/data/point_stat \
>>>> -v 5
>>>>
>>>> I will use point-stat for 23 point observations files per day for
>>>> multiple years, is there a solution that will allow me to do it
>>>> faster/simply? I tried with "point_obs
>>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
>>>> met-6.0/data/Metar_test/T" but it is not working.
>>>>
>>>>
>>>> I have another question about Point-Stat Configuration. For
instance, I
>>>> have used variables gives in the user_guide examples as bellow:
>>>>
>>>>     field = [
>>>>          {
>>>>            name       = "TMP";
>>>>            level      = [ "Z2" ];
>>>>            cat_thresh = [ <=273.0 ];
>>>>        },
>>>>          {
>>>>        name       = "UGRD";
>>>>            level      = [ "Z10" ];
>>>>            cat_thresh = [ >=5.0 ];
>>>>        },
>>>>          {
>>>>        name       = "VGRD";
>>>>            level      = [ "Z10" ];
>>>>            cat_thresh = [ >=5.0 ];
>>>>        }
>>>>       ];
>>>>
>>>>
>>>> It is actually working, but I would like to evaluate additional
>>>> variables. Where I can find informations about the name of
variables ?
>>>> Indeed, I can not read my file after pre-processing with
Madis2nc.
>>>>
>>>> Many thanks,
>>>>
>>>> Regards.
>>>>
>>>> Adrien
>>>>
>>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
>>>>> Hi Adrien.
>>>>>
>>>>> When you run "point_stat" you can see the usage statement (see
below).
>>>> You
>>>>> can use the "-point_obs" option to specify additional point
observation
>>>>> files:
>>>>>
>>>>>      "-point_obs file" specifies additional NetCDF point
observation
>> files
>>>> to
>>>>> be used (optional).
>>>>>
>>>>> You can use this option multiple times.  So, if you have
multiple
>>>>> additional observation files you can add "-point_obs
<obs_file_a>
>>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call to
>>>> point_stat.
>>>>> I hope that helps.  Please let us know if you have any other
questions.
>>>>>
>>>>> Julie
>>>>>
>>>>>
>>>>> *** Model Evaluation Tools (METV6.0) ***
>>>>>
>>>>> Usage: point_stat
>>>>>            fcst_file
>>>>>            obs_file
>>>>>            config_file
>>>>>            [-point_obs file]
>>>>>            [-obs_valid_beg time]
>>>>>            [-obs_valid_end time]
>>>>>            [-outdir path]
>>>>>            [-log file]
>>>>>            [-v level]
>>>>>
>>>>>            where   "fcst_file" is a gridded forecast file
containing the
>>>>> field(s) to be verified (required).
>>>>>                    "obs_file" is an observation file in NetCDF
format
>>>>> containing the verifying point observations (required).
>>>>>                    "config_file" is a PointStatConfig file
containing
>> the
>>>>> desired configuration settings (required).
>>>>>                    "-point_obs file" specifies additional NetCDF
point
>>>>> observation files to be used (optional).
>>>>>                    "-obs_valid_beg time" in YYYYMMDD[_HH[MMSS]]
sets the
>>>>> beginning of the matching time window (optional).
>>>>>                    "-obs_valid_end time" in YYYYMMDD[_HH[MMSS]]
sets the
>>>> end
>>>>> of the matching time window (optional).
>>>>>                    "-outdir path" overrides the default output
directory
>>>> (.)
>>>>> (optional).
>>>>>                    "-log file" outputs log messages to the
specified
>> file
>>>>> (optional).
>>>>>                    "-v level" overrides the default level of
logging (2)
>>>>> (optional).
>>>>>
>>>>>
>>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hello Julie,
>>>>>>
>>>>>> How can I pass multiple netcdf point observation files to
point-stat
>> ? I
>>>>>> didn't see any informations on the user_guide about it.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>> Adrien
>>>>>>
>>>>>>
>>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
>>>>>>> Hi Adrien.
>>>>>>>
>>>>>>> There’s no “need” to merge the files.   You can pass multiple
netcdf
>>>>>> point
>>>>>>> observation files to point_stat and ensemble_stat.  However,
if you
>>>> would
>>>>>>> like to merge the files, you could consider using the "ncrcat"
tool:
>>>>>>>
>>>>>>> https://linux.die.net/man/1/ncrcat
>>>>>>>
>>>>>>> from NCO:
>>>>>>> http://nco.sourceforge.net/
>>>>>>>
>>>>>>> I hope that helps!
>>>>>>>
>>>>>>> Julie
>>>>>>>
>>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hello Julie,
>>>>>>>>
>>>>>>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
>>>> would
>>>>>>>> like to merge these hourly data in daily file. Do you have
>> suggestion
>>>> or
>>>>>>>> recommendation on how to do it ? Is there option for that in
MET ?
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Adrien
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us know.
>>>>>>>>>
>>>>>>>>> Julie
>>>>>>>>>
>>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
>>>>>> met_help at ucar.edu
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>
>>>>>>>>>> Hi Julie,
>>>>>>>>>>
>>>>>>>>>> Thanks to the previous met_help ticket, now that worked
perfectly
>> !
>>>> I
>>>>>> am
>>>>>>>>>> so grateful for your help, thank you. Now I will adapt this
method
>>>> for
>>>>>>>>>> all my data.
>>>>>>>>>>
>>>>>>>>>> Another time, thank you. I'll definitely let you know if I
have
>>>> others
>>>>>>>>>> questions.
>>>>>>>>>>
>>>>>>>>>> Best regards,
>>>>>>>>>>
>>>>>>>>>> Adrien
>>>>>>>>>>
>>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>
>>>>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank you
>>>> for
>>>>>>>>>>> uploading your data.
>>>>>>>>>>>
>>>>>>>>>>> When I run point_stat with your data and configuration
file, I
>> see
>>>>>> the
>>>>>>>>>>> following warning:
>>>>>>>>>>>
>>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>>>>>>>> WARNING:
>>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable,
>> the
>>>>>>>> lead
>>>>>>>>>>> time does not match the requested lead time: (000000 !=
020000)
>>>>>>>>>>> WARNING:
>>>>>>>>>>> WARNING:
>>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields matching
>>>>>> T_sfc(0,*,*)
>>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>>>>>>>> WARNING:
>>>>>>>>>>>
>>>>>>>>>>> There is a specific way in the CF-convention of specifying
the
>>>>>>>>>>> initialization time of the model.  You do so by defining a
>> variable
>>>>>>>> named
>>>>>>>>>>> "forecast_reference_time".  When that variable is not
present,
>> MET
>>>>>> sets
>>>>>>>>>> the
>>>>>>>>>>> forecast initialization time to the same value as the
valid time,
>>>>>> which
>>>>>>>>>>> results in a lead time of 0.
>>>>>>>>>>>
>>>>>>>>>>> You need to add the "forecast_reference_time" variable to
your
>>>> model
>>>>>>>>>>> files.  Take a look at this previous met_help ticket and
see if
>>>> that
>>>>>>>>>> helps:
>>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-
May/002867.html
>>>>>>>>>>>
>>>>>>>>>>> Also, I see in your PointStatConfig file that you have
defined
>>>>>>>>>> "lead_time"
>>>>>>>>>>> in the fcst dictionary.  That is not necessary and could
cause
>>>>>>>> problems.
>>>>>>>>>>> MET determines the lead time by the time index of the time
>>>> dimension
>>>>>>>> that
>>>>>>>>>>> you specify in the "level" field:
>>>>>>>>>>>
>>>>>>>>>>>               level      = "(0,*,*)";
>>>>>>>>>>>
>>>>>>>>>>> I hope that helps.  Please let us know if you have any
other
>>>>>> questions.
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Julie
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
>>>>>>>> met_help at ucar.edu
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Julie,
>>>>>>>>>>>>
>>>>>>>>>>>> Many thank, I have done as you suggested and MET seems to
read
>> my
>>>> CF
>>>>>>>>>>>> Compliant. However, I still have issues with the
configuration
>> of
>>>>>>>>>>>> Point-Stat.
>>>>>>>>>>>>
>>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily file
for
>>>>>>>> 2013-01-01
>>>>>>>>>>>> I would also provide you :
>>>>>>>>>>>> - point observation file from Madis2nc - hourly file for
>>>>>>>>>>>> 2013-01-01_02:00:00
>>>>>>>>>>>> - Point-Stat configuration
>>>>>>>>>>>>
>>>>>>>>>>>> I'm grateful for you help.
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>
>>>>>>>>>>>>> It is difficult to tell the problem with the file
without
>> seeing
>>>>>> it.
>>>>>>>>>>>>> However, I have something for you to try that might
work.  MET
>>>>>> should
>>>>>>>>>> be
>>>>>>>>>>>>> able to read CF compliant files, and you have stated
that your
>>>>>> NetCDF
>>>>>>>>>>>> file
>>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file, but
>>>>>> since
>>>>>>>>>> it
>>>>>>>>>>>> is
>>>>>>>>>>>>> having trouble, let's try explicitly telling the tools
how to
>>>>>> process
>>>>>>>>>> the
>>>>>>>>>>>>> data by setting the following in your PointStat config
file:
>>>>>>>>>>>>>
>>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>>
>>>>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.  For
>>>>>>>>>> example:
>>>>>>>>>>>>> fcst = {
>>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>> ...
>>>>>>>>>>>>> }
>>>>>>>>>>>>>
>>>>>>>>>>>>> If that works, please let us know.  If that does not
work,
>> please
>>>>>>>>>> upload
>>>>>>>>>>>>> your file to our ftp server using the following
instructions
>> and
>>>>>> let
>>>>>>>> us
>>>>>>>>>>>>> know once you have done that so that we can get the file
and
>>>> take a
>>>>>>>>>> look.
>>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>
>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT <
>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>>>>>>>>>>>>>> Hi Julie.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>          I've done as you suggested and it ran without
problem,
>>>> thank
>>>>>>>> you!
>>>>>>>>>>>>>> I come up with a another issue.. I'm trying to use
Point-Stat
>> :
>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> However, Point Stat seems to have issue to read my
forecast
>> file
>>>>>>>> with
>>>>>>>>>>>>>> the following informations:
>>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>>>>>>>>>> DEBUG 1: User Config File: met-
6.0/data/Test/PointStatConfig
>>>>>>>>>>>>>>> DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file()
->
>>>> created
>>>>>>>> new
>>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>> I was wondering if you had any insight on what I could
be
>> doing
>>>>>>>>>> wrong. I
>>>>>>>>>>>>>> appreciate any help you can give.
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Adrien Michel/
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> /
>>>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a écrit
:
>>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I see that you have a question about how to define a
polyline
>>>>>>>> masking
>>>>>>>>>>>>>>> file.  The -mask_grid option would take a named grid
or a
>>>> gridded
>>>>>>>>>> data
>>>>>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
>>>>>> masking
>>>>>>>>>>>> file.
>>>>>>>>>>>>>>> If you'd only like to keep the points falling inside
your
>> model
>>>>>>>>>> domain,
>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>> you have a gridded data file on that domain, using
-mask_grid
>>>> is
>>>>>>>> very
>>>>>>>>>>>>>>> simple:
>>>>>>>>>>>>>>>            -mask_grid /path/to/gridded/data/file
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> However, if you'd prefer the flexibility of defining a
>> polyline
>>>>>>>>>> masking
>>>>>>>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>>>>>>>            -mask_poly /path/to/polyline/mask/file
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> To create a polyline mask, you simply create an ASCII
file
>>>>>>>>>> containing a
>>>>>>>>>>>>>>> list of lat/lons that define the region of interest.
For
>>>>>> example,
>>>>>>>>>>>> take a
>>>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line of
the
>> file
>>>>>>>>>>>> specifies
>>>>>>>>>>>>>>> the name for the polyline, and the remaining lines
contain
>>>>>> lat/lon
>>>>>>>>>>>> values
>>>>>>>>>>>>>>> for the boundary points.  The last point is connected
back up
>>>> to
>>>>>>>> the
>>>>>>>>>>>>>> first
>>>>>>>>>>>>>>> point to complete the area.  The example is named
"SWC" and
>>>>>>>> contains
>>>>>>>>>> 33
>>>>>>>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
>>>>>> questions.
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via RT
<
>>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Tic
>> ket/Display.html?id=81768
>>>>>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I have further questions about Madis2nc use. I would
like to
>>>> use
>>>>>>>> the
>>>>>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
>>>>>> details
>>>>>>>>>> on
>>>>>>>>>>>>>>>> how define the polyline masking file in the user
guide. I
>>>> should
>>>>>>>>>> like
>>>>>>>>>>>> to
>>>>>>>>>>>>>>>> define the polyline masking file for Europe and
especially
>> for
>>>>>>>>>> France.
>>>>>>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Regards.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Adrien
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
>>>>>>>>>>>>>>>>> According to our records, your request has been
resolved.
>> If
>>>>>> you
>>>>>>>>>> have
>>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>>> further questions or concerns, please respond to
this
>>>> message.
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
>> 37
>>>>>> 95
>>>>>>>> 15
>>>>>>>>>> |
>>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>>>> 95
>>>>>> 15
>>>>>>>> |
>>>>>>>>>>>> E:
>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>
>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>> 95
>>>> 15
>>>>>> |
>>>>>>>>>> E:
>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Adrien Michel
>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>
>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
>> 15
>>>> |
>>>>>>>> E:
>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37
95 15
>>>> <+33%206%2095%2037%2095%2015> |
>>>>>> E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
>>>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>> <+33%206%2095%2037%2095%2015>
>>>> <+33%206%2095%2037%2095%2015> | E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16 27 84
>> <+33%209%2089%2016%2027%2084>
>>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>> <+33%206%2095%2037%2095%2015>
>>>> <+33%206%2095%2037%2095%2015> | E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16 27 84
>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>> <+33%206%2095%2037%2095%2015> | E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: John Halley Gotway
Time: Wed Nov 22 11:19:11 2017

Adrien,

OK, I pulled your data files and ran them through point_stat in met-
6.0.

I wrote the attached shell script (using the attached PointStatConfig2
file) to loop through the times and run point_stat once for each
output
time.

I noticed that...
- You have observations of dew point... so I switched "q_2m" to
"Td_2m" in
the config file.
- Your forecast_reference_time variable is set to a missing value
which
results in pretty weird forecast lead times.  It should instead be set
to a
value of 0.  I corrected that before running point_stat.

I ran my script like this:
./run_ps.sh >& run_ps.log

And I attached the output run_ps.log file.  That way you can see how
many
matched pairs I got:

Hope this helps get you going.

Thanks,
John

[johnhg at number5]% grep ", using" run_ps.log

DEBUG 2: Processing T_2m(1,*,*) versus TMP/Z2, for observation type
ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 156
pairs.

DEBUG 2: Processing Td_2m(1,*,*) versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
156
pairs.

DEBUG 2: Processing v_10m_gr(1,*,*) versus VGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
143
pairs.

DEBUG 2: Processing u_10m_gr(1,*,*) versus UGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
143
pairs.

DEBUG 2: Processing T_2m(2,*,*) versus TMP/Z2, for observation type
ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 170
pairs.

DEBUG 2: Processing Td_2m(2,*,*) versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
170
pairs.

DEBUG 2: Processing v_10m_gr(2,*,*) versus VGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
158
pairs.

DEBUG 2: Processing u_10m_gr(2,*,*) versus UGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
158
pairs.

DEBUG 2: Processing T_2m(3,*,*) versus TMP/Z2, for observation type
ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 307
pairs.

DEBUG 2: Processing Td_2m(3,*,*) versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
307
pairs.

DEBUG 2: Processing v_10m_gr(3,*,*) versus VGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
289
pairs.

DEBUG 2: Processing u_10m_gr(3,*,*) versus UGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
289
pairs.

DEBUG 2: Processing T_2m(4,*,*) versus TMP/Z2, for observation type
ADPSFC,
over region FULL, for interpolation method NEAREST(1), using 81 pairs.

DEBUG 2: Processing Td_2m(4,*,*) versus DPT/Z2, for observation type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
81
pairs.

DEBUG 2: Processing v_10m_gr(4,*,*) versus VGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
73
pairs.

DEBUG 2: Processing u_10m_gr(4,*,*) versus UGRD/Z10, for observation
type
ADPSFC, over region FULL, for interpolation method NEAREST(1), using
73
pairs.




On Wed, Nov 22, 2017 at 1:31 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> Hi John,
>
> No problem. I've repost the data on your ftp site at file name :
> amichel_data
>
> Regards,
>
> Adrien
>
>
> Le 14/11/2017 à 21:08, John Halley Gotway via RT a écrit :
> > Adrien,
> >
> > My apologies for the long delay in responding.  I went to go grab
the
> data
> > you posted to our ftp site, but unfortunately, it has already aged
off.
> >
> > Any chance you could repost the data?
> >
> > Sorry about that.
> >
> > John
> >
> >
> > On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >>
> >>
> >> Hi Julie,
> >>
> >> Did you receive my last email ?
> >>
> >> I send this following email to you co-worker John two weeks ago.
Could
> >> you help me with these isssues ?
> >>
> >>
> >> I uploaded my files with file name: amichel_data .You'll find
some of my
> >> point-observations files, one wrf file and my Point-Stat
configuration.
> >>
> >> At least, I would like to configure MET to verify :
> >>
> >> - temperature
> >>
> >> - wind
> >>
> >> -rainfall
> >>
> >> -cloud
> >>
> >> - pressure
> >>
> >> -...
> >>
> >> Actually here are my two issues:
> >>
> >> - verify wrf files with many hourly-point observations
> >>
> >> - find names of variables (temperature, rainfal,cloud) after
> >> pre-processing with madis2nc to configure point-stat
> >>
> >>
> >> Thanks,
> >>
> >> Adrien
> >>
> >> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>> Hi Adrien.
> >>>
> >>> With regard to processing multiple observation files for
multiple years
> >> in
> >>> point_stat in a faster/simpler way, I would like to speak to one
of our
> >>> main developers to find out more information.  I will get back
to you
> on
> >>> that.
> >>>
> >>> With regard to getting more information about additional
variables, you
> >>> mentioned that you cannot read your file after processing with
> Madis2nc.
> >>> You should be able to read your NetCDF data with a utility
called
> >>> "ncdump".  Here is a link to more information about the "ncdump"
> utility:
> >>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
> >>> utilities_guide.html#ncdump_guide
> >>>
> >>> If you are unable to get and use the "ncdump" utility you are
welcome
> to
> >>> upload sample NetCDF files to our ftp site and I can dump the
variable
> >>> information and pass it back to you.
> >>>
> >>> You can upload your file(s) on our anonymous ftp site using
these
> >>> instructions:
> >>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>
> >>> I hope that helps.
> >>>
> >>> Julie
> >>>
> >>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hi Julie,
> >>>>
> >>>> Well thank you it helps me. So actually my command shell looks
like
> >> that:
> >>>> point_stat \
> >>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
> >>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
> >>>> met-6.0/data/Test/PointStatConfig \
> >>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
> >>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
> >>>> -outdir met-6.0/data/point_stat \
> >>>> -v 5
> >>>>
> >>>> I will use point-stat for 23 point observations files per day
for
> >>>> multiple years, is there a solution that will allow me to do it
> >>>> faster/simply? I tried with "point_obs
> >>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
> >>>> met-6.0/data/Metar_test/T" but it is not working.
> >>>>
> >>>>
> >>>> I have another question about Point-Stat Configuration. For
instance,
> I
> >>>> have used variables gives in the user_guide examples as bellow:
> >>>>
> >>>>     field = [
> >>>>          {
> >>>>            name       = "TMP";
> >>>>            level      = [ "Z2" ];
> >>>>            cat_thresh = [ <=273.0 ];
> >>>>        },
> >>>>          {
> >>>>        name       = "UGRD";
> >>>>            level      = [ "Z10" ];
> >>>>            cat_thresh = [ >=5.0 ];
> >>>>        },
> >>>>          {
> >>>>        name       = "VGRD";
> >>>>            level      = [ "Z10" ];
> >>>>            cat_thresh = [ >=5.0 ];
> >>>>        }
> >>>>       ];
> >>>>
> >>>>
> >>>> It is actually working, but I would like to evaluate additional
> >>>> variables. Where I can find informations about the name of
variables ?
> >>>> Indeed, I can not read my file after pre-processing with
Madis2nc.
> >>>>
> >>>> Many thanks,
> >>>>
> >>>> Regards.
> >>>>
> >>>> Adrien
> >>>>
> >>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> >>>>> Hi Adrien.
> >>>>>
> >>>>> When you run "point_stat" you can see the usage statement (see
> below).
> >>>> You
> >>>>> can use the "-point_obs" option to specify additional point
> observation
> >>>>> files:
> >>>>>
> >>>>>      "-point_obs file" specifies additional NetCDF point
observation
> >> files
> >>>> to
> >>>>> be used (optional).
> >>>>>
> >>>>> You can use this option multiple times.  So, if you have
multiple
> >>>>> additional observation files you can add "-point_obs
<obs_file_a>
> >>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call
to
> >>>> point_stat.
> >>>>> I hope that helps.  Please let us know if you have any other
> questions.
> >>>>>
> >>>>> Julie
> >>>>>
> >>>>>
> >>>>> *** Model Evaluation Tools (METV6.0) ***
> >>>>>
> >>>>> Usage: point_stat
> >>>>>            fcst_file
> >>>>>            obs_file
> >>>>>            config_file
> >>>>>            [-point_obs file]
> >>>>>            [-obs_valid_beg time]
> >>>>>            [-obs_valid_end time]
> >>>>>            [-outdir path]
> >>>>>            [-log file]
> >>>>>            [-v level]
> >>>>>
> >>>>>            where   "fcst_file" is a gridded forecast file
containing
> the
> >>>>> field(s) to be verified (required).
> >>>>>                    "obs_file" is an observation file in NetCDF
format
> >>>>> containing the verifying point observations (required).
> >>>>>                    "config_file" is a PointStatConfig file
containing
> >> the
> >>>>> desired configuration settings (required).
> >>>>>                    "-point_obs file" specifies additional
NetCDF
> point
> >>>>> observation files to be used (optional).
> >>>>>                    "-obs_valid_beg time" in
YYYYMMDD[_HH[MMSS]] sets
> the
> >>>>> beginning of the matching time window (optional).
> >>>>>                    "-obs_valid_end time" in
YYYYMMDD[_HH[MMSS]] sets
> the
> >>>> end
> >>>>> of the matching time window (optional).
> >>>>>                    "-outdir path" overrides the default output
> directory
> >>>> (.)
> >>>>> (optional).
> >>>>>                    "-log file" outputs log messages to the
specified
> >> file
> >>>>> (optional).
> >>>>>                    "-v level" overrides the default level of
logging
> (2)
> >>>>> (optional).
> >>>>>
> >>>>>
> >>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hello Julie,
> >>>>>>
> >>>>>> How can I pass multiple netcdf point observation files to
point-stat
> >> ? I
> >>>>>> didn't see any informations on the user_guide about it.
> >>>>>>
> >>>>>> Thank you,
> >>>>>>
> >>>>>> Adrien
> >>>>>>
> >>>>>>
> >>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> >>>>>>> Hi Adrien.
> >>>>>>>
> >>>>>>> There’s no “need” to merge the files.   You can pass
multiple
> netcdf
> >>>>>> point
> >>>>>>> observation files to point_stat and ensemble_stat.  However,
if you
> >>>> would
> >>>>>>> like to merge the files, you could consider using the
"ncrcat"
> tool:
> >>>>>>>
> >>>>>>> https://linux.die.net/man/1/ncrcat
> >>>>>>>
> >>>>>>> from NCO:
> >>>>>>> http://nco.sourceforge.net/
> >>>>>>>
> >>>>>>> I hope that helps!
> >>>>>>>
> >>>>>>> Julie
> >>>>>>>
> >>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hello Julie,
> >>>>>>>>
> >>>>>>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
> >>>> would
> >>>>>>>> like to merge these hourly data in daily file. Do you have
> >> suggestion
> >>>> or
> >>>>>>>> recommendation on how to do it ? Is there option for that
in MET ?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Regards,
> >>>>>>>>
> >>>>>>>> Adrien
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> >>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us
know.
> >>>>>>>>>
> >>>>>>>>> Julie
> >>>>>>>>>
> >>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
> >>>>>> met_help at ucar.edu
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>>>
> >>>>>>>>>> Hi Julie,
> >>>>>>>>>>
> >>>>>>>>>> Thanks to the previous met_help ticket, now that worked
> perfectly
> >> !
> >>>> I
> >>>>>> am
> >>>>>>>>>> so grateful for your help, thank you. Now I will adapt
this
> method
> >>>> for
> >>>>>>>>>> all my data.
> >>>>>>>>>>
> >>>>>>>>>> Another time, thank you. I'll definitely let you know if
I have
> >>>> others
> >>>>>>>>>> questions.
> >>>>>>>>>>
> >>>>>>>>>> Best regards,
> >>>>>>>>>>
> >>>>>>>>>> Adrien
> >>>>>>>>>>
> >>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>
> >>>>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank
> you
> >>>> for
> >>>>>>>>>>> uploading your data.
> >>>>>>>>>>>
> >>>>>>>>>>> When I run point_stat with your data and configuration
file, I
> >> see
> >>>>>> the
> >>>>>>>>>>> following warning:
> >>>>>>>>>>>
> >>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>>>>>>>>>> WARNING:
> >>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable,
> >> the
> >>>>>>>> lead
> >>>>>>>>>>> time does not match the requested lead time: (000000 !=
020000)
> >>>>>>>>>>> WARNING:
> >>>>>>>>>>> WARNING:
> >>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields
matching
> >>>>>> T_sfc(0,*,*)
> >>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
> >>>>>>>>>>> WARNING:
> >>>>>>>>>>>
> >>>>>>>>>>> There is a specific way in the CF-convention of
specifying the
> >>>>>>>>>>> initialization time of the model.  You do so by defining
a
> >> variable
> >>>>>>>> named
> >>>>>>>>>>> "forecast_reference_time".  When that variable is not
present,
> >> MET
> >>>>>> sets
> >>>>>>>>>> the
> >>>>>>>>>>> forecast initialization time to the same value as the
valid
> time,
> >>>>>> which
> >>>>>>>>>>> results in a lead time of 0.
> >>>>>>>>>>>
> >>>>>>>>>>> You need to add the "forecast_reference_time" variable
to your
> >>>> model
> >>>>>>>>>>> files.  Take a look at this previous met_help ticket and
see if
> >>>> that
> >>>>>>>>>> helps:
> >>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/
> 002867.html
> >>>>>>>>>>>
> >>>>>>>>>>> Also, I see in your PointStatConfig file that you have
defined
> >>>>>>>>>> "lead_time"
> >>>>>>>>>>> in the fcst dictionary.  That is not necessary and could
cause
> >>>>>>>> problems.
> >>>>>>>>>>> MET determines the lead time by the time index of the
time
> >>>> dimension
> >>>>>>>> that
> >>>>>>>>>>> you specify in the "level" field:
> >>>>>>>>>>>
> >>>>>>>>>>>               level      = "(0,*,*)";
> >>>>>>>>>>>
> >>>>>>>>>>> I hope that helps.  Please let us know if you have any
other
> >>>>>> questions.
> >>>>>>>>>>> Thanks,
> >>>>>>>>>>> Julie
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
> >>>>>>>> met_help at ucar.edu
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hi Julie,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Many thank, I have done as you suggested and MET seems
to read
> >> my
> >>>> CF
> >>>>>>>>>>>> Compliant. However, I still have issues with the
configuration
> >> of
> >>>>>>>>>>>> Point-Stat.
> >>>>>>>>>>>>
> >>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
> >>>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily
file for
> >>>>>>>> 2013-01-01
> >>>>>>>>>>>> I would also provide you :
> >>>>>>>>>>>> - point observation file from Madis2nc - hourly file
for
> >>>>>>>>>>>> 2013-01-01_02:00:00
> >>>>>>>>>>>> - Point-Stat configuration
> >>>>>>>>>>>>
> >>>>>>>>>>>> I'm grateful for you help.
> >>>>>>>>>>>> Regards,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit
:
> >>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> It is difficult to tell the problem with the file
without
> >> seeing
> >>>>>> it.
> >>>>>>>>>>>>> However, I have something for you to try that might
work.
> MET
> >>>>>> should
> >>>>>>>>>> be
> >>>>>>>>>>>>> able to read CF compliant files, and you have stated
that
> your
> >>>>>> NetCDF
> >>>>>>>>>>>> file
> >>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file,
> but
> >>>>>> since
> >>>>>>>>>> it
> >>>>>>>>>>>> is
> >>>>>>>>>>>>> having trouble, let's try explicitly telling the tools
how to
> >>>>>> process
> >>>>>>>>>> the
> >>>>>>>>>>>>> data by setting the following in your PointStat config
file:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.
> For
> >>>>>>>>>> example:
> >>>>>>>>>>>>> fcst = {
> >>>>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>>> ...
> >>>>>>>>>>>>> }
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> If that works, please let us know.  If that does not
work,
> >> please
> >>>>>>>>>> upload
> >>>>>>>>>>>>> your file to our ftp server using the following
instructions
> >> and
> >>>>>> let
> >>>>>>>> us
> >>>>>>>>>>>>> know once you have done that so that we can get the
file and
> >>>> take a
> >>>>>>>>>> look.
> >>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
<
> >>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81768
> >>>>>>>>>>>>>> Hi Julie.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>          I've done as you suggested and it ran
without
> problem,
> >>>> thank
> >>>>>>>> you!
> >>>>>>>>>>>>>> I come up with a another issue.. I'm trying to use
> Point-Stat
> >> :
> >>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>>>>>>>>>> - a point observation file coming from Madis2nc
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> However, Point Stat seems to have issue to read my
forecast
> >> file
> >>>>>>>> with
> >>>>>>>>>>>>>> the following informations:
> >>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
> >>>>>>>>>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/
> PointStatConfig
> >>>>>>>>>>>>>>> DEBUG 4:
Met2dDataFileFactory::new_met_2d_data_file() ->
> >>>> created
> >>>>>>>> new
> >>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>>>>>> ERROR  :
> >>>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
> >>>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>>>>>>>>>>> ERROR  :
> >>>>>>>>>>>>>> I was wondering if you had any insight on what I
could be
> >> doing
> >>>>>>>>>> wrong. I
> >>>>>>>>>>>>>> appreciate any help you can give.
> >>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Adrien Michel/
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> /
> >>>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I see that you have a question about how to define a
> polyline
> >>>>>>>> masking
> >>>>>>>>>>>>>>> file.  The -mask_grid option would take a named grid
or a
> >>>> gridded
> >>>>>>>>>> data
> >>>>>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
> >>>>>> masking
> >>>>>>>>>>>> file.
> >>>>>>>>>>>>>>> If you'd only like to keep the points falling inside
your
> >> model
> >>>>>>>>>> domain,
> >>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>> you have a gridded data file on that domain, using
> -mask_grid
> >>>> is
> >>>>>>>> very
> >>>>>>>>>>>>>>> simple:
> >>>>>>>>>>>>>>>            -mask_grid /path/to/gridded/data/file
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> However, if you'd prefer the flexibility of defining
a
> >> polyline
> >>>>>>>>>> masking
> >>>>>>>>>>>>>>> region, using -mask_poly would work too:
> >>>>>>>>>>>>>>>            -mask_poly /path/to/polyline/mask/file
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> To create a polyline mask, you simply create an
ASCII file
> >>>>>>>>>> containing a
> >>>>>>>>>>>>>>> list of lat/lons that define the region of interest.
For
> >>>>>> example,
> >>>>>>>>>>>> take a
> >>>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line
of the
> >> file
> >>>>>>>>>>>> specifies
> >>>>>>>>>>>>>>> the name for the polyline, and the remaining lines
contain
> >>>>>> lat/lon
> >>>>>>>>>>>> values
> >>>>>>>>>>>>>>> for the boundary points.  The last point is
connected back
> up
> >>>> to
> >>>>>>>> the
> >>>>>>>>>>>>>> first
> >>>>>>>>>>>>>>> point to complete the area.  The example is named
"SWC" and
> >>>>>>>> contains
> >>>>>>>>>> 33
> >>>>>>>>>>>>>>> points, and there is no real maximum.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
> >>>>>> questions.
> >>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via
RT <
> >>>>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Tic
> >> ket/Display.html?id=81768
> >>>>>>>>>>>>>>>> Hello Julie,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I have further questions about Madis2nc use. I
would like
> to
> >>>> use
> >>>>>>>> the
> >>>>>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
> >>>>>> details
> >>>>>>>>>> on
> >>>>>>>>>>>>>>>> how define the polyline masking file in the user
guide. I
> >>>> should
> >>>>>>>>>> like
> >>>>>>>>>>>> to
> >>>>>>>>>>>>>>>> define the polyline masking file for Europe and
especially
> >> for
> >>>>>>>>>> France.
> >>>>>>>>>>>>>>>> Thank you in advance,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Regards.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Adrien
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>>>> According to our records, your request has been
resolved.
> >> If
> >>>>>> you
> >>>>>>>>>> have
> >>>>>>>>>>>>>> any
> >>>>>>>>>>>>>>>>> further questions or concerns, please respond to
this
> >>>> message.
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M:
+33 6
> 95
> >> 37
> >>>>>> 95
> >>>>>>>> 15
> >>>>>>>>>> |
> >>>>>>>>>>>>>> E:
> >>>>>>>>>>>>>>>> amichel at atmoterra.com
<mailto:amichel at atmoterra.com>
> >>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
> 37
> >>>> 95
> >>>>>> 15
> >>>>>>>> |
> >>>>>>>>>>>> E:
> >>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>
> >>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> >> 95
> >>>> 15
> >>>>>> |
> >>>>>>>>>> E:
> >>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Adrien Michel
> >>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>
> >>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> 95
> >> 15
> >>>> |
> >>>>>>>> E:
> >>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>> --
> >>>>>>>> Adrien Michel
> >>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>
> >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
> 15
> >>>> <+33%206%2095%2037%2095%2015> |
> >>>>>> E:
> >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>
> >>>>>>>>
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
> >> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
> >>>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> >> <+33%206%2095%2037%2095%2015>
> >>>> <+33%206%2095%2037%2095%2015> | E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
> >> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16 27 84
> >> <+33%209%2089%2016%2027%2084>
> >>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> >> <+33%206%2095%2037%2095%2015>
> >>>> <+33%206%2095%2037%2095%2015> | E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16 27
> 84
> >> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> >> <+33%206%2095%2037%2095%2015> | E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Tue Dec 05 03:58:19 2017

John,

I would like to thank you for you help, it seems to work better now!

Can I compute long-term statistics at individual sites (eg,
mean absolute error or RMS error for daily forecasts for a
month, a year...) with Stat-Analysis module ?


Regards,

Adrien


Le 22/11/2017 à 19:19, John Halley Gotway via RT a écrit :
> Adrien,
>
> OK, I pulled your data files and ran them through point_stat in met-
6.0.
>
> I wrote the attached shell script (using the attached
PointStatConfig2
> file) to loop through the times and run point_stat once for each
output
> time.
>
> I noticed that...
> - You have observations of dew point... so I switched "q_2m" to
"Td_2m" in
> the config file.
> - Your forecast_reference_time variable is set to a missing value
which
> results in pretty weird forecast lead times.  It should instead be
set to a
> value of 0.  I corrected that before running point_stat.
>
> I ran my script like this:
> ./run_ps.sh >& run_ps.log
>
> And I attached the output run_ps.log file.  That way you can see how
many
> matched pairs I got:
>
> Hope this helps get you going.
>
> Thanks,
> John
>
> [johnhg at number5]% grep ", using" run_ps.log
>
> DEBUG 2: Processing T_2m(1,*,*) versus TMP/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 156
pairs.
>
> DEBUG 2: Processing Td_2m(1,*,*) versus DPT/Z2, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
156
> pairs.
>
> DEBUG 2: Processing v_10m_gr(1,*,*) versus VGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
143
> pairs.
>
> DEBUG 2: Processing u_10m_gr(1,*,*) versus UGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
143
> pairs.
>
> DEBUG 2: Processing T_2m(2,*,*) versus TMP/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 170
pairs.
>
> DEBUG 2: Processing Td_2m(2,*,*) versus DPT/Z2, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
170
> pairs.
>
> DEBUG 2: Processing v_10m_gr(2,*,*) versus VGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
158
> pairs.
>
> DEBUG 2: Processing u_10m_gr(2,*,*) versus UGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
158
> pairs.
>
> DEBUG 2: Processing T_2m(3,*,*) versus TMP/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 307
pairs.
>
> DEBUG 2: Processing Td_2m(3,*,*) versus DPT/Z2, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
307
> pairs.
>
> DEBUG 2: Processing v_10m_gr(3,*,*) versus VGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
289
> pairs.
>
> DEBUG 2: Processing u_10m_gr(3,*,*) versus UGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
289
> pairs.
>
> DEBUG 2: Processing T_2m(4,*,*) versus TMP/Z2, for observation type
ADPSFC,
> over region FULL, for interpolation method NEAREST(1), using 81
pairs.
>
> DEBUG 2: Processing Td_2m(4,*,*) versus DPT/Z2, for observation type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
81
> pairs.
>
> DEBUG 2: Processing v_10m_gr(4,*,*) versus VGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
73
> pairs.
>
> DEBUG 2: Processing u_10m_gr(4,*,*) versus UGRD/Z10, for observation
type
> ADPSFC, over region FULL, for interpolation method NEAREST(1), using
73
> pairs.
>
>
>
>
> On Wed, Nov 22, 2017 at 1:31 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> Hi John,
>>
>> No problem. I've repost the data on your ftp site at file name :
>> amichel_data
>>
>> Regards,
>>
>> Adrien
>>
>>
>> Le 14/11/2017 à 21:08, John Halley Gotway via RT a écrit :
>>> Adrien,
>>>
>>> My apologies for the long delay in responding.  I went to go grab
the
>> data
>>> you posted to our ftp site, but unfortunately, it has already aged
off.
>>>
>>> Any chance you could repost the data?
>>>
>>> Sorry about that.
>>>
>>> John
>>>
>>>
>>> On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT <
>> met_help at ucar.edu>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>>
>>>>
>>>> Hi Julie,
>>>>
>>>> Did you receive my last email ?
>>>>
>>>> I send this following email to you co-worker John two weeks ago.
Could
>>>> you help me with these isssues ?
>>>>
>>>>
>>>> I uploaded my files with file name: amichel_data .You'll find
some of my
>>>> point-observations files, one wrf file and my Point-Stat
configuration.
>>>>
>>>> At least, I would like to configure MET to verify :
>>>>
>>>> - temperature
>>>>
>>>> - wind
>>>>
>>>> -rainfall
>>>>
>>>> -cloud
>>>>
>>>> - pressure
>>>>
>>>> -...
>>>>
>>>> Actually here are my two issues:
>>>>
>>>> - verify wrf files with many hourly-point observations
>>>>
>>>> - find names of variables (temperature, rainfal,cloud) after
>>>> pre-processing with madis2nc to configure point-stat
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Adrien
>>>>
>>>> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>> Hi Adrien.
>>>>>
>>>>> With regard to processing multiple observation files for
multiple years
>>>> in
>>>>> point_stat in a faster/simpler way, I would like to speak to one
of our
>>>>> main developers to find out more information.  I will get back
to you
>> on
>>>>> that.
>>>>>
>>>>> With regard to getting more information about additional
variables, you
>>>>> mentioned that you cannot read your file after processing with
>> Madis2nc.
>>>>> You should be able to read your NetCDF data with a utility
called
>>>>> "ncdump".  Here is a link to more information about the "ncdump"
>> utility:
>>>>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
>>>>> utilities_guide.html#ncdump_guide
>>>>>
>>>>> If you are unable to get and use the "ncdump" utility you are
welcome
>> to
>>>>> upload sample NetCDF files to our ftp site and I can dump the
variable
>>>>> information and pass it back to you.
>>>>>
>>>>> You can upload your file(s) on our anonymous ftp site using
these
>>>>> instructions:
>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>
>>>>> I hope that helps.
>>>>>
>>>>> Julie
>>>>>
>>>>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT <
>> met_help at ucar.edu
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>> Hi Julie,
>>>>>>
>>>>>> Well thank you it helps me. So actually my command shell looks
like
>>>> that:
>>>>>> point_stat \
>>>>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
>>>>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
>>>>>> met-6.0/data/Test/PointStatConfig \
>>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
>>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
>>>>>> -outdir met-6.0/data/point_stat \
>>>>>> -v 5
>>>>>>
>>>>>> I will use point-stat for 23 point observations files per day
for
>>>>>> multiple years, is there a solution that will allow me to do it
>>>>>> faster/simply? I tried with "point_obs
>>>>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
>>>>>> met-6.0/data/Metar_test/T" but it is not working.
>>>>>>
>>>>>>
>>>>>> I have another question about Point-Stat Configuration. For
instance,
>> I
>>>>>> have used variables gives in the user_guide examples as bellow:
>>>>>>
>>>>>>      field = [
>>>>>>           {
>>>>>>             name       = "TMP";
>>>>>>             level      = [ "Z2" ];
>>>>>>             cat_thresh = [ <=273.0 ];
>>>>>>         },
>>>>>>           {
>>>>>>         name       = "UGRD";
>>>>>>             level      = [ "Z10" ];
>>>>>>             cat_thresh = [ >=5.0 ];
>>>>>>         },
>>>>>>           {
>>>>>>         name       = "VGRD";
>>>>>>             level      = [ "Z10" ];
>>>>>>             cat_thresh = [ >=5.0 ];
>>>>>>         }
>>>>>>        ];
>>>>>>
>>>>>>
>>>>>> It is actually working, but I would like to evaluate additional
>>>>>> variables. Where I can find informations about the name of
variables ?
>>>>>> Indeed, I can not read my file after pre-processing with
Madis2nc.
>>>>>>
>>>>>> Many thanks,
>>>>>>
>>>>>> Regards.
>>>>>>
>>>>>> Adrien
>>>>>>
>>>>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
>>>>>>> Hi Adrien.
>>>>>>>
>>>>>>> When you run "point_stat" you can see the usage statement (see
>> below).
>>>>>> You
>>>>>>> can use the "-point_obs" option to specify additional point
>> observation
>>>>>>> files:
>>>>>>>
>>>>>>>       "-point_obs file" specifies additional NetCDF point
observation
>>>> files
>>>>>> to
>>>>>>> be used (optional).
>>>>>>>
>>>>>>> You can use this option multiple times.  So, if you have
multiple
>>>>>>> additional observation files you can add "-point_obs
<obs_file_a>
>>>>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your call
to
>>>>>> point_stat.
>>>>>>> I hope that helps.  Please let us know if you have any other
>> questions.
>>>>>>> Julie
>>>>>>>
>>>>>>>
>>>>>>> *** Model Evaluation Tools (METV6.0) ***
>>>>>>>
>>>>>>> Usage: point_stat
>>>>>>>             fcst_file
>>>>>>>             obs_file
>>>>>>>             config_file
>>>>>>>             [-point_obs file]
>>>>>>>             [-obs_valid_beg time]
>>>>>>>             [-obs_valid_end time]
>>>>>>>             [-outdir path]
>>>>>>>             [-log file]
>>>>>>>             [-v level]
>>>>>>>
>>>>>>>             where   "fcst_file" is a gridded forecast file
containing
>> the
>>>>>>> field(s) to be verified (required).
>>>>>>>                     "obs_file" is an observation file in
NetCDF format
>>>>>>> containing the verifying point observations (required).
>>>>>>>                     "config_file" is a PointStatConfig file
containing
>>>> the
>>>>>>> desired configuration settings (required).
>>>>>>>                     "-point_obs file" specifies additional
NetCDF
>> point
>>>>>>> observation files to be used (optional).
>>>>>>>                     "-obs_valid_beg time" in
YYYYMMDD[_HH[MMSS]] sets
>> the
>>>>>>> beginning of the matching time window (optional).
>>>>>>>                     "-obs_valid_end time" in
YYYYMMDD[_HH[MMSS]] sets
>> the
>>>>>> end
>>>>>>> of the matching time window (optional).
>>>>>>>                     "-outdir path" overrides the default
output
>> directory
>>>>>> (.)
>>>>>>> (optional).
>>>>>>>                     "-log file" outputs log messages to the
specified
>>>> file
>>>>>>> (optional).
>>>>>>>                     "-v level" overrides the default level of
logging
>> (2)
>>>>>>> (optional).
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hello Julie,
>>>>>>>>
>>>>>>>> How can I pass multiple netcdf point observation files to
point-stat
>>>> ? I
>>>>>>>> didn't see any informations on the user_guide about it.
>>>>>>>>
>>>>>>>> Thank you,
>>>>>>>>
>>>>>>>> Adrien
>>>>>>>>
>>>>>>>>
>>>>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
>>>>>>>>> Hi Adrien.
>>>>>>>>>
>>>>>>>>> There’s no “need” to merge the files.   You can pass
multiple
>> netcdf
>>>>>>>> point
>>>>>>>>> observation files to point_stat and ensemble_stat.  However,
if you
>>>>>> would
>>>>>>>>> like to merge the files, you could consider using the
"ncrcat"
>> tool:
>>>>>>>>> https://linux.die.net/man/1/ncrcat
>>>>>>>>>
>>>>>>>>> from NCO:
>>>>>>>>> http://nco.sourceforge.net/
>>>>>>>>>
>>>>>>>>> I hope that helps!
>>>>>>>>>
>>>>>>>>> Julie
>>>>>>>>>
>>>>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
>>>>>> met_help at ucar.edu
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>
>>>>>>>>>> Hello Julie,
>>>>>>>>>>
>>>>>>>>>> I am running Madis2nc tool for hourly basis metar data.
Actually I
>>>>>> would
>>>>>>>>>> like to merge these hourly data in daily file. Do you have
>>>> suggestion
>>>>>> or
>>>>>>>>>> recommendation on how to do it ? Is there option for that
in MET ?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Adrien
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>>>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us
know.
>>>>>>>>>>>
>>>>>>>>>>> Julie
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
>>>>>>>> met_help at ucar.edu
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>>>
>>>>>>>>>>>> Hi Julie,
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks to the previous met_help ticket, now that worked
>> perfectly
>>>> !
>>>>>> I
>>>>>>>> am
>>>>>>>>>>>> so grateful for your help, thank you. Now I will adapt
this
>> method
>>>>>> for
>>>>>>>>>>>> all my data.
>>>>>>>>>>>>
>>>>>>>>>>>> Another time, thank you. I'll definitely let you know if
I have
>>>>>> others
>>>>>>>>>>>> questions.
>>>>>>>>>>>>
>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Adrien
>>>>>>>>>>>>
>>>>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank
>> you
>>>>>> for
>>>>>>>>>>>>> uploading your data.
>>>>>>>>>>>>>
>>>>>>>>>>>>> When I run point_stat with your data and configuration
file, I
>>>> see
>>>>>>>> the
>>>>>>>>>>>>> following warning:
>>>>>>>>>>>>>
>>>>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
variable,
>>>> the
>>>>>>>>>> lead
>>>>>>>>>>>>> time does not match the requested lead time: (000000 !=
020000)
>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields
matching
>>>>>>>> T_sfc(0,*,*)
>>>>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>>
>>>>>>>>>>>>> There is a specific way in the CF-convention of
specifying the
>>>>>>>>>>>>> initialization time of the model.  You do so by defining
a
>>>> variable
>>>>>>>>>> named
>>>>>>>>>>>>> "forecast_reference_time".  When that variable is not
present,
>>>> MET
>>>>>>>> sets
>>>>>>>>>>>> the
>>>>>>>>>>>>> forecast initialization time to the same value as the
valid
>> time,
>>>>>>>> which
>>>>>>>>>>>>> results in a lead time of 0.
>>>>>>>>>>>>>
>>>>>>>>>>>>> You need to add the "forecast_reference_time" variable
to your
>>>>>> model
>>>>>>>>>>>>> files.  Take a look at this previous met_help ticket and
see if
>>>>>> that
>>>>>>>>>>>> helps:
>>>>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/
>> 002867.html
>>>>>>>>>>>>> Also, I see in your PointStatConfig file that you have
defined
>>>>>>>>>>>> "lead_time"
>>>>>>>>>>>>> in the fcst dictionary.  That is not necessary and could
cause
>>>>>>>>>> problems.
>>>>>>>>>>>>> MET determines the lead time by the time index of the
time
>>>>>> dimension
>>>>>>>>>> that
>>>>>>>>>>>>> you specify in the "level" field:
>>>>>>>>>>>>>
>>>>>>>>>>>>>                level      = "(0,*,*)";
>>>>>>>>>>>>>
>>>>>>>>>>>>> I hope that helps.  Please let us know if you have any
other
>>>>>>>> questions.
>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT <
>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>>>>>>>>>>>>>> Hi Julie,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Many thank, I have done as you suggested and MET seems
to read
>>>> my
>>>>>> CF
>>>>>>>>>>>>>> Compliant. However, I still have issues with the
configuration
>>>> of
>>>>>>>>>>>>>> Point-Stat.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily
file for
>>>>>>>>>> 2013-01-01
>>>>>>>>>>>>>> I would also provide you :
>>>>>>>>>>>>>> - point observation file from Madis2nc - hourly file
for
>>>>>>>>>>>>>> 2013-01-01_02:00:00
>>>>>>>>>>>>>> - Point-Stat configuration
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm grateful for you help.
>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a écrit
:
>>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> It is difficult to tell the problem with the file
without
>>>> seeing
>>>>>>>> it.
>>>>>>>>>>>>>>> However, I have something for you to try that might
work.
>> MET
>>>>>>>> should
>>>>>>>>>>>> be
>>>>>>>>>>>>>>> able to read CF compliant files, and you have stated
that
>> your
>>>>>>>> NetCDF
>>>>>>>>>>>>>> file
>>>>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type of
file,
>> but
>>>>>>>> since
>>>>>>>>>>>> it
>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>> having trouble, let's try explicitly telling the tools
how to
>>>>>>>> process
>>>>>>>>>>>> the
>>>>>>>>>>>>>>> data by setting the following in your PointStat config
file:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.
>> For
>>>>>>>>>>>> example:
>>>>>>>>>>>>>>> fcst = {
>>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> If that works, please let us know.  If that does not
work,
>>>> please
>>>>>>>>>>>> upload
>>>>>>>>>>>>>>> your file to our ftp server using the following
instructions
>>>> and
>>>>>>>> let
>>>>>>>>>> us
>>>>>>>>>>>>>>> know once you have done that so that we can get the
file and
>>>>>> take a
>>>>>>>>>>>> look.
>>>>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via RT
<
>>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
>> Ticket/Display.html?id=81768
>>>>>>>>>>>>>>>> Hi Julie.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>           I've done as you suggested and it ran
without
>> problem,
>>>>>> thank
>>>>>>>>>> you!
>>>>>>>>>>>>>>>> I come up with a another issue.. I'm trying to use
>> Point-Stat
>>>> :
>>>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>>>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> However, Point Stat seems to have issue to read my
forecast
>>>> file
>>>>>>>>>> with
>>>>>>>>>>>>>>>> the following informations:
>>>>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>>>>>> /usr/local/share/met/config/PointStatConfig_default
>>>>>>>>>>>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/
>> PointStatConfig
>>>>>>>>>>>>>>>>> DEBUG 4:
Met2dDataFileFactory::new_met_2d_data_file() ->
>>>>>> created
>>>>>>>>>> new
>>>>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>>>> I was wondering if you had any insight on what I
could be
>>>> doing
>>>>>>>>>>>> wrong. I
>>>>>>>>>>>>>>>> appreciate any help you can give.
>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Adrien Michel/
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> /
>>>>>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a
écrit :
>>>>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I see that you have a question about how to define a
>> polyline
>>>>>>>>>> masking
>>>>>>>>>>>>>>>>> file.  The -mask_grid option would take a named grid
or a
>>>>>> gridded
>>>>>>>>>>>> data
>>>>>>>>>>>>>>>>> file, while the -mask_poly option would definite a
polyline
>>>>>>>> masking
>>>>>>>>>>>>>> file.
>>>>>>>>>>>>>>>>> If you'd only like to keep the points falling inside
your
>>>> model
>>>>>>>>>>>> domain,
>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>> you have a gridded data file on that domain, using
>> -mask_grid
>>>>>> is
>>>>>>>>>> very
>>>>>>>>>>>>>>>>> simple:
>>>>>>>>>>>>>>>>>             -mask_grid /path/to/gridded/data/file
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> However, if you'd prefer the flexibility of defining
a
>>>> polyline
>>>>>>>>>>>> masking
>>>>>>>>>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>>>>>>>>>             -mask_poly /path/to/polyline/mask/file
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> To create a polyline mask, you simply create an
ASCII file
>>>>>>>>>>>> containing a
>>>>>>>>>>>>>>>>> list of lat/lons that define the region of interest.
For
>>>>>>>> example,
>>>>>>>>>>>>>> take a
>>>>>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first line
of the
>>>> file
>>>>>>>>>>>>>> specifies
>>>>>>>>>>>>>>>>> the name for the polyline, and the remaining lines
contain
>>>>>>>> lat/lon
>>>>>>>>>>>>>> values
>>>>>>>>>>>>>>>>> for the boundary points.  The last point is
connected back
>> up
>>>>>> to
>>>>>>>>>> the
>>>>>>>>>>>>>>>> first
>>>>>>>>>>>>>>>>> point to complete the area.  The example is named
"SWC" and
>>>>>>>>>> contains
>>>>>>>>>>>> 33
>>>>>>>>>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
>>>>>>>> questions.
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via
RT <
>>>>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Tic
>>>> ket/Display.html?id=81768
>>>>>>>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> I have further questions about Madis2nc use. I
would like
>> to
>>>>>> use
>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> '-mask_grid string' option. However there are very
limited
>>>>>>>> details
>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>> how define the polyline masking file in the user
guide. I
>>>>>> should
>>>>>>>>>>>> like
>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>> define the polyline masking file for Europe and
especially
>>>> for
>>>>>>>>>>>> France.
>>>>>>>>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Regards.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Adrien
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
>>>>>>>>>>>>>>>>>>> According to our records, your request has been
resolved.
>>>> If
>>>>>>>> you
>>>>>>>>>>>> have
>>>>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>>>>> further questions or concerns, please respond to
this
>>>>>> message.
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M:
+33 6
>> 95
>>>> 37
>>>>>>>> 95
>>>>>>>>>> 15
>>>>>>>>>>>> |
>>>>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>>>>> amichel at atmoterra.com
<mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
>> 37
>>>>>> 95
>>>>>>>> 15
>>>>>>>>>> |
>>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>>>> 95
>>>>>> 15
>>>>>>>> |
>>>>>>>>>>>> E:
>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>
>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>> 95
>>>> 15
>>>>>> |
>>>>>>>>>> E:
>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Adrien Michel
>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>
>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95
37 95
>> 15
>>>>>> <+33%206%2095%2037%2095%2015> |
>>>>>>>> E:
>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
>>>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
>>>>>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>>> <+33%206%2095%2037%2095%2015>
>>>>>> <+33%206%2095%2037%2095%2015> | E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
>>>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16 27 84
>>>> <+33%209%2089%2016%2027%2084>
>>>>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>>> <+33%206%2095%2037%2095%2015>
>>>>>> <+33%206%2095%2037%2095%2015> | E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9 89
16 27
>> 84
>>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>>> <+33%206%2095%2037%2095%2015> | E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: John Halley Gotway
Time: Fri Dec 08 15:00:58 2017

Adrien,

Yes, it is possible to do that with the STAT-Analysis tool.  However,
you'd
need to be writing the matched pair (MPR) line type from the Point-
Stat
tool.   Beware though that that creates pretty large output files.

But once you have that MPR output, you can run a STAT-Analysis job
that
looks like this:

stat_analysis -job aggregate_stat -line_type MPR -out_line_type CNT
-by SID
-lookin /directory/with/MPR/data

This job would do the following steps:
(1) Search recursively through the directory named
"/directory/with/MPR/data" for .stat output files.
(2) Read each .stat file, looking for MPR lines.
(3) Group the MPR lines together for each unique value of the SID
(i.e.
station id) column from the MPR line.
(4) For each unique SID value, use the matched pair data to compute
continuous statistics (CNT) output line type.

If you'd further like to subset results for different models and lead
times, all you'd need to add is this:
   -by MODEL,FCST_LEAD,SID

Hope that helps clarify.

Thanks,
John



On Tue, Dec 5, 2017 at 3:58 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> John,
>
> I would like to thank you for you help, it seems to work better now!
>
> Can I compute long-term statistics at individual sites (eg,
> mean absolute error or RMS error for daily forecasts for a
> month, a year...) with Stat-Analysis module ?
>
>
> Regards,
>
> Adrien
>
>
> Le 22/11/2017 à 19:19, John Halley Gotway via RT a écrit :
> > Adrien,
> >
> > OK, I pulled your data files and ran them through point_stat in
met-6.0.
> >
> > I wrote the attached shell script (using the attached
PointStatConfig2
> > file) to loop through the times and run point_stat once for each
output
> > time.
> >
> > I noticed that...
> > - You have observations of dew point... so I switched "q_2m" to
"Td_2m"
> in
> > the config file.
> > - Your forecast_reference_time variable is set to a missing value
which
> > results in pretty weird forecast lead times.  It should instead be
set
> to a
> > value of 0.  I corrected that before running point_stat.
> >
> > I ran my script like this:
> > ./run_ps.sh >& run_ps.log
> >
> > And I attached the output run_ps.log file.  That way you can see
how many
> > matched pairs I got:
> >
> > Hope this helps get you going.
> >
> > Thanks,
> > John
> >
> > [johnhg at number5]% grep ", using" run_ps.log
> >
> > DEBUG 2: Processing T_2m(1,*,*) versus TMP/Z2, for observation
type
> ADPSFC,
> > over region FULL, for interpolation method NEAREST(1), using 156
pairs.
> >
> > DEBUG 2: Processing Td_2m(1,*,*) versus DPT/Z2, for observation
type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 156
> > pairs.
> >
> > DEBUG 2: Processing v_10m_gr(1,*,*) versus VGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 143
> > pairs.
> >
> > DEBUG 2: Processing u_10m_gr(1,*,*) versus UGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 143
> > pairs.
> >
> > DEBUG 2: Processing T_2m(2,*,*) versus TMP/Z2, for observation
type
> ADPSFC,
> > over region FULL, for interpolation method NEAREST(1), using 170
pairs.
> >
> > DEBUG 2: Processing Td_2m(2,*,*) versus DPT/Z2, for observation
type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 170
> > pairs.
> >
> > DEBUG 2: Processing v_10m_gr(2,*,*) versus VGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 158
> > pairs.
> >
> > DEBUG 2: Processing u_10m_gr(2,*,*) versus UGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 158
> > pairs.
> >
> > DEBUG 2: Processing T_2m(3,*,*) versus TMP/Z2, for observation
type
> ADPSFC,
> > over region FULL, for interpolation method NEAREST(1), using 307
pairs.
> >
> > DEBUG 2: Processing Td_2m(3,*,*) versus DPT/Z2, for observation
type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 307
> > pairs.
> >
> > DEBUG 2: Processing v_10m_gr(3,*,*) versus VGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 289
> > pairs.
> >
> > DEBUG 2: Processing u_10m_gr(3,*,*) versus UGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 289
> > pairs.
> >
> > DEBUG 2: Processing T_2m(4,*,*) versus TMP/Z2, for observation
type
> ADPSFC,
> > over region FULL, for interpolation method NEAREST(1), using 81
pairs.
> >
> > DEBUG 2: Processing Td_2m(4,*,*) versus DPT/Z2, for observation
type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 81
> > pairs.
> >
> > DEBUG 2: Processing v_10m_gr(4,*,*) versus VGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 73
> > pairs.
> >
> > DEBUG 2: Processing u_10m_gr(4,*,*) versus UGRD/Z10, for
observation type
> > ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 73
> > pairs.
> >
> >
> >
> >
> > On Wed, Nov 22, 2017 at 1:31 AM, Adrien Michel via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> Hi John,
> >>
> >> No problem. I've repost the data on your ftp site at file name :
> >> amichel_data
> >>
> >> Regards,
> >>
> >> Adrien
> >>
> >>
> >> Le 14/11/2017 à 21:08, John Halley Gotway via RT a écrit :
> >>> Adrien,
> >>>
> >>> My apologies for the long delay in responding.  I went to go
grab the
> >> data
> >>> you posted to our ftp site, but unfortunately, it has already
aged off.
> >>>
> >>> Any chance you could repost the data?
> >>>
> >>> Sorry about that.
> >>>
> >>> John
> >>>
> >>>
> >>> On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT <
> >> met_help at ucar.edu>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>>
> >>>>
> >>>> Hi Julie,
> >>>>
> >>>> Did you receive my last email ?
> >>>>
> >>>> I send this following email to you co-worker John two weeks
ago. Could
> >>>> you help me with these isssues ?
> >>>>
> >>>>
> >>>> I uploaded my files with file name: amichel_data .You'll find
some of
> my
> >>>> point-observations files, one wrf file and my Point-Stat
> configuration.
> >>>>
> >>>> At least, I would like to configure MET to verify :
> >>>>
> >>>> - temperature
> >>>>
> >>>> - wind
> >>>>
> >>>> -rainfall
> >>>>
> >>>> -cloud
> >>>>
> >>>> - pressure
> >>>>
> >>>> -...
> >>>>
> >>>> Actually here are my two issues:
> >>>>
> >>>> - verify wrf files with many hourly-point observations
> >>>>
> >>>> - find names of variables (temperature, rainfal,cloud) after
> >>>> pre-processing with madis2nc to configure point-stat
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Adrien
> >>>>
> >>>> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>>>> Hi Adrien.
> >>>>>
> >>>>> With regard to processing multiple observation files for
multiple
> years
> >>>> in
> >>>>> point_stat in a faster/simpler way, I would like to speak to
one of
> our
> >>>>> main developers to find out more information.  I will get back
to you
> >> on
> >>>>> that.
> >>>>>
> >>>>> With regard to getting more information about additional
variables,
> you
> >>>>> mentioned that you cannot read your file after processing with
> >> Madis2nc.
> >>>>> You should be able to read your NetCDF data with a utility
called
> >>>>> "ncdump".  Here is a link to more information about the
"ncdump"
> >> utility:
> >>>>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
> >>>>> utilities_guide.html#ncdump_guide
> >>>>>
> >>>>> If you are unable to get and use the "ncdump" utility you are
welcome
> >> to
> >>>>> upload sample NetCDF files to our ftp site and I can dump the
> variable
> >>>>> information and pass it back to you.
> >>>>>
> >>>>> You can upload your file(s) on our anonymous ftp site using
these
> >>>>> instructions:
> >>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>
> >>>>> I hope that helps.
> >>>>>
> >>>>> Julie
> >>>>>
> >>>>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT <
> >> met_help at ucar.edu
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>> Hi Julie,
> >>>>>>
> >>>>>> Well thank you it helps me. So actually my command shell
looks like
> >>>> that:
> >>>>>> point_stat \
> >>>>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
> >>>>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
> >>>>>> met-6.0/data/Test/PointStatConfig \
> >>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
> >>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
> >>>>>> -outdir met-6.0/data/point_stat \
> >>>>>> -v 5
> >>>>>>
> >>>>>> I will use point-stat for 23 point observations files per day
for
> >>>>>> multiple years, is there a solution that will allow me to do
it
> >>>>>> faster/simply? I tried with "point_obs
> >>>>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
> >>>>>> met-6.0/data/Metar_test/T" but it is not working.
> >>>>>>
> >>>>>>
> >>>>>> I have another question about Point-Stat Configuration. For
> instance,
> >> I
> >>>>>> have used variables gives in the user_guide examples as
bellow:
> >>>>>>
> >>>>>>      field = [
> >>>>>>           {
> >>>>>>             name       = "TMP";
> >>>>>>             level      = [ "Z2" ];
> >>>>>>             cat_thresh = [ <=273.0 ];
> >>>>>>         },
> >>>>>>           {
> >>>>>>         name       = "UGRD";
> >>>>>>             level      = [ "Z10" ];
> >>>>>>             cat_thresh = [ >=5.0 ];
> >>>>>>         },
> >>>>>>           {
> >>>>>>         name       = "VGRD";
> >>>>>>             level      = [ "Z10" ];
> >>>>>>             cat_thresh = [ >=5.0 ];
> >>>>>>         }
> >>>>>>        ];
> >>>>>>
> >>>>>>
> >>>>>> It is actually working, but I would like to evaluate
additional
> >>>>>> variables. Where I can find informations about the name of
> variables ?
> >>>>>> Indeed, I can not read my file after pre-processing with
Madis2nc.
> >>>>>>
> >>>>>> Many thanks,
> >>>>>>
> >>>>>> Regards.
> >>>>>>
> >>>>>> Adrien
> >>>>>>
> >>>>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> >>>>>>> Hi Adrien.
> >>>>>>>
> >>>>>>> When you run "point_stat" you can see the usage statement
(see
> >> below).
> >>>>>> You
> >>>>>>> can use the "-point_obs" option to specify additional point
> >> observation
> >>>>>>> files:
> >>>>>>>
> >>>>>>>       "-point_obs file" specifies additional NetCDF point
> observation
> >>>> files
> >>>>>> to
> >>>>>>> be used (optional).
> >>>>>>>
> >>>>>>> You can use this option multiple times.  So, if you have
multiple
> >>>>>>> additional observation files you can add "-point_obs
<obs_file_a>
> >>>>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your
call to
> >>>>>> point_stat.
> >>>>>>> I hope that helps.  Please let us know if you have any other
> >> questions.
> >>>>>>> Julie
> >>>>>>>
> >>>>>>>
> >>>>>>> *** Model Evaluation Tools (METV6.0) ***
> >>>>>>>
> >>>>>>> Usage: point_stat
> >>>>>>>             fcst_file
> >>>>>>>             obs_file
> >>>>>>>             config_file
> >>>>>>>             [-point_obs file]
> >>>>>>>             [-obs_valid_beg time]
> >>>>>>>             [-obs_valid_end time]
> >>>>>>>             [-outdir path]
> >>>>>>>             [-log file]
> >>>>>>>             [-v level]
> >>>>>>>
> >>>>>>>             where   "fcst_file" is a gridded forecast file
> containing
> >> the
> >>>>>>> field(s) to be verified (required).
> >>>>>>>                     "obs_file" is an observation file in
NetCDF
> format
> >>>>>>> containing the verifying point observations (required).
> >>>>>>>                     "config_file" is a PointStatConfig file
> containing
> >>>> the
> >>>>>>> desired configuration settings (required).
> >>>>>>>                     "-point_obs file" specifies additional
NetCDF
> >> point
> >>>>>>> observation files to be used (optional).
> >>>>>>>                     "-obs_valid_beg time" in
YYYYMMDD[_HH[MMSS]]
> sets
> >> the
> >>>>>>> beginning of the matching time window (optional).
> >>>>>>>                     "-obs_valid_end time" in
YYYYMMDD[_HH[MMSS]]
> sets
> >> the
> >>>>>> end
> >>>>>>> of the matching time window (optional).
> >>>>>>>                     "-outdir path" overrides the default
output
> >> directory
> >>>>>> (.)
> >>>>>>> (optional).
> >>>>>>>                     "-log file" outputs log messages to the
> specified
> >>>> file
> >>>>>>> (optional).
> >>>>>>>                     "-v level" overrides the default level
of
> logging
> >> (2)
> >>>>>>> (optional).
> >>>>>>>
> >>>>>>>
> >>>>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hello Julie,
> >>>>>>>>
> >>>>>>>> How can I pass multiple netcdf point observation files to
> point-stat
> >>>> ? I
> >>>>>>>> didn't see any informations on the user_guide about it.
> >>>>>>>>
> >>>>>>>> Thank you,
> >>>>>>>>
> >>>>>>>> Adrien
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> >>>>>>>>> Hi Adrien.
> >>>>>>>>>
> >>>>>>>>> There’s no “need” to merge the files.   You can pass
multiple
> >> netcdf
> >>>>>>>> point
> >>>>>>>>> observation files to point_stat and ensemble_stat.
However, if
> you
> >>>>>> would
> >>>>>>>>> like to merge the files, you could consider using the
"ncrcat"
> >> tool:
> >>>>>>>>> https://linux.die.net/man/1/ncrcat
> >>>>>>>>>
> >>>>>>>>> from NCO:
> >>>>>>>>> http://nco.sourceforge.net/
> >>>>>>>>>
> >>>>>>>>> I hope that helps!
> >>>>>>>>>
> >>>>>>>>> Julie
> >>>>>>>>>
> >>>>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
> >>>>>> met_help at ucar.edu
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>>>
> >>>>>>>>>> Hello Julie,
> >>>>>>>>>>
> >>>>>>>>>> I am running Madis2nc tool for hourly basis metar data.
> Actually I
> >>>>>> would
> >>>>>>>>>> like to merge these hourly data in daily file. Do you
have
> >>>> suggestion
> >>>>>> or
> >>>>>>>>>> recommendation on how to do it ? Is there option for that
in
> MET ?
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Regards,
> >>>>>>>>>>
> >>>>>>>>>> Adrien
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
> >>>>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us
know.
> >>>>>>>>>>>
> >>>>>>>>>>> Julie
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
> >>>>>>>> met_help at ucar.edu
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hi Julie,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Thanks to the previous met_help ticket, now that worked
> >> perfectly
> >>>> !
> >>>>>> I
> >>>>>>>> am
> >>>>>>>>>>>> so grateful for your help, thank you. Now I will adapt
this
> >> method
> >>>>>> for
> >>>>>>>>>>>> all my data.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Another time, thank you. I'll definitely let you know
if I
> have
> >>>>>> others
> >>>>>>>>>>>> questions.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Best regards,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Adrien
> >>>>>>>>>>>>
> >>>>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit
:
> >>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank
> >> you
> >>>>>> for
> >>>>>>>>>>>>> uploading your data.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> When I run point_stat with your data and configuration
file,
> I
> >>>> see
> >>>>>>>> the
> >>>>>>>>>>>>> following warning:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
> variable,
> >>>> the
> >>>>>>>>>> lead
> >>>>>>>>>>>>> time does not match the requested lead time: (000000
!=
> 020000)
> >>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields
matching
> >>>>>>>> T_sfc(0,*,*)
> >>>>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
> >>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> There is a specific way in the CF-convention of
specifying
> the
> >>>>>>>>>>>>> initialization time of the model.  You do so by
defining a
> >>>> variable
> >>>>>>>>>> named
> >>>>>>>>>>>>> "forecast_reference_time".  When that variable is not
> present,
> >>>> MET
> >>>>>>>> sets
> >>>>>>>>>>>> the
> >>>>>>>>>>>>> forecast initialization time to the same value as the
valid
> >> time,
> >>>>>>>> which
> >>>>>>>>>>>>> results in a lead time of 0.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> You need to add the "forecast_reference_time" variable
to
> your
> >>>>>> model
> >>>>>>>>>>>>> files.  Take a look at this previous met_help ticket
and see
> if
> >>>>>> that
> >>>>>>>>>>>> helps:
> >>>>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/
> >> 002867.html
> >>>>>>>>>>>>> Also, I see in your PointStatConfig file that you have
> defined
> >>>>>>>>>>>> "lead_time"
> >>>>>>>>>>>>> in the fcst dictionary.  That is not necessary and
could
> cause
> >>>>>>>>>> problems.
> >>>>>>>>>>>>> MET determines the lead time by the time index of the
time
> >>>>>> dimension
> >>>>>>>>>> that
> >>>>>>>>>>>>> you specify in the "level" field:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>                level      = "(0,*,*)";
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> I hope that helps.  Please let us know if you have any
other
> >>>>>>>> questions.
> >>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT
<
> >>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81768
> >>>>>>>>>>>>>> Hi Julie,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Many thank, I have done as you suggested and MET
seems to
> read
> >>>> my
> >>>>>> CF
> >>>>>>>>>>>>>> Compliant. However, I still have issues with the
> configuration
> >>>> of
> >>>>>>>>>>>>>> Point-Stat.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
> >>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily
file
> for
> >>>>>>>>>> 2013-01-01
> >>>>>>>>>>>>>> I would also provide you :
> >>>>>>>>>>>>>> - point observation file from Madis2nc - hourly file
for
> >>>>>>>>>>>>>> 2013-01-01_02:00:00
> >>>>>>>>>>>>>> - Point-Stat configuration
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> I'm grateful for you help.
> >>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> It is difficult to tell the problem with the file
without
> >>>> seeing
> >>>>>>>> it.
> >>>>>>>>>>>>>>> However, I have something for you to try that might
work.
> >> MET
> >>>>>>>> should
> >>>>>>>>>>>> be
> >>>>>>>>>>>>>>> able to read CF compliant files, and you have stated
that
> >> your
> >>>>>>>> NetCDF
> >>>>>>>>>>>>>> file
> >>>>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type
of file,
> >> but
> >>>>>>>> since
> >>>>>>>>>>>> it
> >>>>>>>>>>>>>> is
> >>>>>>>>>>>>>>> having trouble, let's try explicitly telling the
tools how
> to
> >>>>>>>> process
> >>>>>>>>>>>> the
> >>>>>>>>>>>>>>> data by setting the following in your PointStat
config
> file:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.
> >> For
> >>>>>>>>>>>> example:
> >>>>>>>>>>>>>>> fcst = {
> >>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>>>>> ...
> >>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> If that works, please let us know.  If that does not
work,
> >>>> please
> >>>>>>>>>>>> upload
> >>>>>>>>>>>>>>> your file to our ftp server using the following
> instructions
> >>>> and
> >>>>>>>> let
> >>>>>>>>>> us
> >>>>>>>>>>>>>>> know once you have done that so that we can get the
file
> and
> >>>>>> take a
> >>>>>>>>>>>> look.
> >>>>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via
RT <
> >>>>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> >> Ticket/Display.html?id=81768
> >>>>>>>>>>>>>>>> Hi Julie.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>           I've done as you suggested and it ran
without
> >> problem,
> >>>>>> thank
> >>>>>>>>>> you!
> >>>>>>>>>>>>>>>> I come up with a another issue.. I'm trying to use
> >> Point-Stat
> >>>> :
> >>>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>>>>>>>>>>>> - a point observation file coming from Madis2nc
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> However, Point Stat seems to have issue to read my
> forecast
> >>>> file
> >>>>>>>>>> with
> >>>>>>>>>>>>>>>> the following informations:
> >>>>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>>>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>>>>>>>>
/usr/local/share/met/config/PointStatConfig_default
> >>>>>>>>>>>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/
> >> PointStatConfig
> >>>>>>>>>>>>>>>>> DEBUG 4:
Met2dDataFileFactory::new_met_2d_data_file() ->
> >>>>>> created
> >>>>>>>>>> new
> >>>>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>>>>>>>> ERROR  :
> >>>>>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
> >>>>>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
> >>>>>>>>>>>>>>>>> ERROR  :
> >>>>>>>>>>>>>>>> I was wondering if you had any insight on what I
could be
> >>>> doing
> >>>>>>>>>>>> wrong. I
> >>>>>>>>>>>>>>>> appreciate any help you can give.
> >>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Adrien Michel/
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> /
> >>>>>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> I see that you have a question about how to define
a
> >> polyline
> >>>>>>>>>> masking
> >>>>>>>>>>>>>>>>> file.  The -mask_grid option would take a named
grid or a
> >>>>>> gridded
> >>>>>>>>>>>> data
> >>>>>>>>>>>>>>>>> file, while the -mask_poly option would definite a
> polyline
> >>>>>>>> masking
> >>>>>>>>>>>>>> file.
> >>>>>>>>>>>>>>>>> If you'd only like to keep the points falling
inside your
> >>>> model
> >>>>>>>>>>>> domain,
> >>>>>>>>>>>>>>>> and
> >>>>>>>>>>>>>>>>> you have a gridded data file on that domain, using
> >> -mask_grid
> >>>>>> is
> >>>>>>>>>> very
> >>>>>>>>>>>>>>>>> simple:
> >>>>>>>>>>>>>>>>>             -mask_grid /path/to/gridded/data/file
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> However, if you'd prefer the flexibility of
defining a
> >>>> polyline
> >>>>>>>>>>>> masking
> >>>>>>>>>>>>>>>>> region, using -mask_poly would work too:
> >>>>>>>>>>>>>>>>>             -mask_poly /path/to/polyline/mask/file
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> To create a polyline mask, you simply create an
ASCII
> file
> >>>>>>>>>>>> containing a
> >>>>>>>>>>>>>>>>> list of lat/lons that define the region of
interest.  For
> >>>>>>>> example,
> >>>>>>>>>>>>>> take a
> >>>>>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first
line of
> the
> >>>> file
> >>>>>>>>>>>>>> specifies
> >>>>>>>>>>>>>>>>> the name for the polyline, and the remaining lines
> contain
> >>>>>>>> lat/lon
> >>>>>>>>>>>>>> values
> >>>>>>>>>>>>>>>>> for the boundary points.  The last point is
connected
> back
> >> up
> >>>>>> to
> >>>>>>>>>> the
> >>>>>>>>>>>>>>>> first
> >>>>>>>>>>>>>>>>> point to complete the area.  The example is named
"SWC"
> and
> >>>>>>>>>> contains
> >>>>>>>>>>>> 33
> >>>>>>>>>>>>>>>>> points, and there is no real maximum.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
> >>>>>>>> questions.
> >>>>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via
RT <
> >>>>>>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Tic
> >>>> ket/Display.html?id=81768
> >>>>>>>>>>>>>>>>>> Hello Julie,
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> I have further questions about Madis2nc use. I
would
> like
> >> to
> >>>>>> use
> >>>>>>>>>> the
> >>>>>>>>>>>>>>>>>> '-mask_grid string' option. However there are
very
> limited
> >>>>>>>> details
> >>>>>>>>>>>> on
> >>>>>>>>>>>>>>>>>> how define the polyline masking file in the user
guide.
> I
> >>>>>> should
> >>>>>>>>>>>> like
> >>>>>>>>>>>>>> to
> >>>>>>>>>>>>>>>>>> define the polyline masking file for Europe and
> especially
> >>>> for
> >>>>>>>>>>>> France.
> >>>>>>>>>>>>>>>>>> Thank you in advance,
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Regards.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Adrien
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>>>>>> According to our records, your request has been
> resolved.
> >>>> If
> >>>>>>>> you
> >>>>>>>>>>>> have
> >>>>>>>>>>>>>>>> any
> >>>>>>>>>>>>>>>>>>> further questions or concerns, please respond to
this
> >>>>>> message.
> >>>>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>>>>>> Environmental Consultant | Consultant
Environnement
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300
Nantes,
> FRANCE
> >>>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M:
+33 6
> >> 95
> >>>> 37
> >>>>>>>> 95
> >>>>>>>>>> 15
> >>>>>>>>>>>> |
> >>>>>>>>>>>>>>>> E:
> >>>>>>>>>>>>>>>>>> amichel at atmoterra.com
<mailto:amichel at atmoterra.com>
> >>>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> --
> >>>>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M:
+33 6
> 95
> >> 37
> >>>>>> 95
> >>>>>>>> 15
> >>>>>>>>>> |
> >>>>>>>>>>>>>> E:
> >>>>>>>>>>>>>>>> amichel at atmoterra.com
<mailto:amichel at atmoterra.com>
> >>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>> --
> >>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
> 37
> >>>> 95
> >>>>>> 15
> >>>>>>>> |
> >>>>>>>>>>>> E:
> >>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>>
> >>>>>>>>>>>> --
> >>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>>>
> >>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
> >>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> >> 95
> >>>> 15
> >>>>>> |
> >>>>>>>>>> E:
> >>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Adrien Michel
> >>>>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>>>
> >>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
> 95
> >> 15
> >>>>>> <+33%206%2095%2037%2095%2015> |
> >>>>>>>> E:
> >>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>> --
> >>>>>>>> Adrien Michel
> >>>>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>>>
> >>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
> >>>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
> >>>>>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> >>>> <+33%206%2095%2037%2095%2015>
> >>>>>> <+33%206%2095%2037%2095%2015> | E:
> >>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>>>> Website: http://www.atmoterra.com
> >>>>>>>>
> >>>>>>>>
> >>>>>> --
> >>>>>> Adrien Michel
> >>>>>> Environmental Consultant | Consultant Environnement
> >>>>>>
> >>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
> >>>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16 27 84
> >>>> <+33%209%2089%2016%2027%2084>
> >>>>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> >>>> <+33%206%2095%2037%2095%2015>
> >>>>>> <+33%206%2095%2037%2095%2015> | E:
> >>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>>>> Website: http://www.atmoterra.com
> >>>>>>
> >>>>>>
> >>>> --
> >>>> Adrien Michel
> >>>> Environmental Consultant | Consultant Environnement
> >>>>
> >>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9
89 16
> 27
> >> 84
> >>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
> >>>> <+33%206%2095%2037%2095%2015> | E:
> >>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >>>> Website: http://www.atmoterra.com
> >>>>
> >>>>
> >> --
> >> Adrien Michel
> >> Environmental Consultant | Consultant Environnement
> >>
> >> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> >> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 | E:
> >> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> >> Website: http://www.atmoterra.com
> >>
> >>
>
> --
> Adrien Michel
> Environmental Consultant | Consultant Environnement
>
> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
> Website: http://www.atmoterra.com
>
>

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Mon Dec 11 08:59:23 2017

John,

When running STAT-Analysis tool, I got :

[root at b71aa7ce1ca5 met]# stat_analysis -lookin
met-6.0/data/Stat/point_stat/point_stat -out
met-6.0/data/Stat/point_stat/test.stat -job aggregate_stat -line_type
MPR -out_line_type CNT -by EUR.poly \
DEBUG 1: Creating STAT-Analysis output file
"met-6.0/data/Stat/point_stat/test.stat"
DEBUG 2: Processing 23 STAT files.
DEBUG 2: STAT Lines read     = 24596
DEBUG 2: STAT Lines retained = 24228
DEBUG 2:
DEBUG 2: Processing Job 1: -job aggregate_stat -line_type MPR -by
EUR.POLY -out_line_type CNT -out_alpha 0.05000 -boot_interval 1
-boot_rep_prop 1.00000 -n_boot_rep 1000 -boot_rng mt19937 -boot_seed
''
-rank_corr_flag 1
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=18446744073364123226
ERROR  :
ERROR  : timestring_to_sec(const char *) -> can't parse time string
"3769600000"

It seems that FCST_LEAD is not recognize by STAT-Analysis Tool.
However
I tried to specifize it with the following command:

  stat_analysis \
-lookin met-6.0/data/Stat/point_stat/point_stat \ -out
met-6.0/data/Stat/point_stat/test.stat \
-job aggregate_stat -fcst_lead 20130101_020000 -line_type MPR
-out_line_type CNT -by EUR.poly
DEBUG 1: Creating STAT-Analysis output file
"met-6.0/data/Stat/point_stat/test.stat"
ERROR  :
ERROR  : timestring_to_sec(const char *) -> can't parse time string
"20130101_020000"
ERROR  :

You will find the MPR output file from Point-Stat in attachment.

Hope you could briefly check this issue,

Regards.

Adrien


Le 08/12/2017 à 23:00, John Halley Gotway via RT a écrit :
> Adrien,
>
> Yes, it is possible to do that with the STAT-Analysis tool.
However, you'd
> need to be writing the matched pair (MPR) line type from the Point-
Stat
> tool.   Beware though that that creates pretty large output files.
>
> But once you have that MPR output, you can run a STAT-Analysis job
that
> looks like this:
>
> stat_analysis -job aggregate_stat -line_type MPR -out_line_type CNT
-by SID
> -lookin /directory/with/MPR/data
>
> This job would do the following steps:
> (1) Search recursively through the directory named
> "/directory/with/MPR/data" for .stat output files.
> (2) Read each .stat file, looking for MPR lines.
> (3) Group the MPR lines together for each unique value of the SID
(i.e.
> station id) column from the MPR line.
> (4) For each unique SID value, use the matched pair data to compute
> continuous statistics (CNT) output line type.
>
> If you'd further like to subset results for different models and
lead
> times, all you'd need to add is this:
>     -by MODEL,FCST_LEAD,SID
>
> Hope that helps clarify.
>
> Thanks,
> John
>
>
>
> On Tue, Dec 5, 2017 at 3:58 AM, Adrien Michel via RT
<met_help at ucar.edu>
> wrote:
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>
>> John,
>>
>> I would like to thank you for you help, it seems to work better
now!
>>
>> Can I compute long-term statistics at individual sites (eg,
>> mean absolute error or RMS error for daily forecasts for a
>> month, a year...) with Stat-Analysis module ?
>>
>>
>> Regards,
>>
>> Adrien
>>
>>
>> Le 22/11/2017 à 19:19, John Halley Gotway via RT a écrit :
>>> Adrien,
>>>
>>> OK, I pulled your data files and ran them through point_stat in
met-6.0.
>>>
>>> I wrote the attached shell script (using the attached
PointStatConfig2
>>> file) to loop through the times and run point_stat once for each
output
>>> time.
>>>
>>> I noticed that...
>>> - You have observations of dew point... so I switched "q_2m" to
"Td_2m"
>> in
>>> the config file.
>>> - Your forecast_reference_time variable is set to a missing value
which
>>> results in pretty weird forecast lead times.  It should instead be
set
>> to a
>>> value of 0.  I corrected that before running point_stat.
>>>
>>> I ran my script like this:
>>> ./run_ps.sh >& run_ps.log
>>>
>>> And I attached the output run_ps.log file.  That way you can see
how many
>>> matched pairs I got:
>>>
>>> Hope this helps get you going.
>>>
>>> Thanks,
>>> John
>>>
>>> [johnhg at number5]% grep ", using" run_ps.log
>>>
>>> DEBUG 2: Processing T_2m(1,*,*) versus TMP/Z2, for observation
type
>> ADPSFC,
>>> over region FULL, for interpolation method NEAREST(1), using 156
pairs.
>>>
>>> DEBUG 2: Processing Td_2m(1,*,*) versus DPT/Z2, for observation
type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 156
>>> pairs.
>>>
>>> DEBUG 2: Processing v_10m_gr(1,*,*) versus VGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 143
>>> pairs.
>>>
>>> DEBUG 2: Processing u_10m_gr(1,*,*) versus UGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 143
>>> pairs.
>>>
>>> DEBUG 2: Processing T_2m(2,*,*) versus TMP/Z2, for observation
type
>> ADPSFC,
>>> over region FULL, for interpolation method NEAREST(1), using 170
pairs.
>>>
>>> DEBUG 2: Processing Td_2m(2,*,*) versus DPT/Z2, for observation
type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 170
>>> pairs.
>>>
>>> DEBUG 2: Processing v_10m_gr(2,*,*) versus VGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 158
>>> pairs.
>>>
>>> DEBUG 2: Processing u_10m_gr(2,*,*) versus UGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 158
>>> pairs.
>>>
>>> DEBUG 2: Processing T_2m(3,*,*) versus TMP/Z2, for observation
type
>> ADPSFC,
>>> over region FULL, for interpolation method NEAREST(1), using 307
pairs.
>>>
>>> DEBUG 2: Processing Td_2m(3,*,*) versus DPT/Z2, for observation
type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 307
>>> pairs.
>>>
>>> DEBUG 2: Processing v_10m_gr(3,*,*) versus VGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 289
>>> pairs.
>>>
>>> DEBUG 2: Processing u_10m_gr(3,*,*) versus UGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 289
>>> pairs.
>>>
>>> DEBUG 2: Processing T_2m(4,*,*) versus TMP/Z2, for observation
type
>> ADPSFC,
>>> over region FULL, for interpolation method NEAREST(1), using 81
pairs.
>>>
>>> DEBUG 2: Processing Td_2m(4,*,*) versus DPT/Z2, for observation
type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 81
>>> pairs.
>>>
>>> DEBUG 2: Processing v_10m_gr(4,*,*) versus VGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 73
>>> pairs.
>>>
>>> DEBUG 2: Processing u_10m_gr(4,*,*) versus UGRD/Z10, for
observation type
>>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 73
>>> pairs.
>>>
>>>
>>>
>>>
>>> On Wed, Nov 22, 2017 at 1:31 AM, Adrien Michel via RT
<met_help at ucar.edu
>>>
>>> wrote:
>>>
>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>
>>>> Hi John,
>>>>
>>>> No problem. I've repost the data on your ftp site at file name :
>>>> amichel_data
>>>>
>>>> Regards,
>>>>
>>>> Adrien
>>>>
>>>>
>>>> Le 14/11/2017 à 21:08, John Halley Gotway via RT a écrit :
>>>>> Adrien,
>>>>>
>>>>> My apologies for the long delay in responding.  I went to go
grab the
>>>> data
>>>>> you posted to our ftp site, but unfortunately, it has already
aged off.
>>>>>
>>>>> Any chance you could repost the data?
>>>>>
>>>>> Sorry about that.
>>>>>
>>>>> John
>>>>>
>>>>>
>>>>> On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu>
>>>>> wrote:
>>>>>
>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>
>>>>>>
>>>>>>
>>>>>> Hi Julie,
>>>>>>
>>>>>> Did you receive my last email ?
>>>>>>
>>>>>> I send this following email to you co-worker John two weeks
ago. Could
>>>>>> you help me with these isssues ?
>>>>>>
>>>>>>
>>>>>> I uploaded my files with file name: amichel_data .You'll find
some of
>> my
>>>>>> point-observations files, one wrf file and my Point-Stat
>> configuration.
>>>>>> At least, I would like to configure MET to verify :
>>>>>>
>>>>>> - temperature
>>>>>>
>>>>>> - wind
>>>>>>
>>>>>> -rainfall
>>>>>>
>>>>>> -cloud
>>>>>>
>>>>>> - pressure
>>>>>>
>>>>>> -...
>>>>>>
>>>>>> Actually here are my two issues:
>>>>>>
>>>>>> - verify wrf files with many hourly-point observations
>>>>>>
>>>>>> - find names of variables (temperature, rainfal,cloud) after
>>>>>> pre-processing with madis2nc to configure point-stat
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Adrien
>>>>>>
>>>>>> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
>>>>>>> Hi Adrien.
>>>>>>>
>>>>>>> With regard to processing multiple observation files for
multiple
>> years
>>>>>> in
>>>>>>> point_stat in a faster/simpler way, I would like to speak to
one of
>> our
>>>>>>> main developers to find out more information.  I will get back
to you
>>>> on
>>>>>>> that.
>>>>>>>
>>>>>>> With regard to getting more information about additional
variables,
>> you
>>>>>>> mentioned that you cannot read your file after processing with
>>>> Madis2nc.
>>>>>>> You should be able to read your NetCDF data with a utility
called
>>>>>>> "ncdump".  Here is a link to more information about the
"ncdump"
>>>> utility:
>>>>>>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
>>>>>>> utilities_guide.html#ncdump_guide
>>>>>>>
>>>>>>> If you are unable to get and use the "ncdump" utility you are
welcome
>>>> to
>>>>>>> upload sample NetCDF files to our ftp site and I can dump the
>> variable
>>>>>>> information and pass it back to you.
>>>>>>>
>>>>>>> You can upload your file(s) on our anonymous ftp site using
these
>>>>>>> instructions:
>>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>
>>>>>>> I hope that helps.
>>>>>>>
>>>>>>> Julie
>>>>>>>
>>>>>>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT <
>>>> met_help at ucar.edu
>>>>>>> wrote:
>>>>>>>
>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
>>>>>>>>
>>>>>>>> Hi Julie,
>>>>>>>>
>>>>>>>> Well thank you it helps me. So actually my command shell
looks like
>>>>>> that:
>>>>>>>> point_stat \
>>>>>>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
>>>>>>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
>>>>>>>> met-6.0/data/Test/PointStatConfig \
>>>>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
>>>>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
>>>>>>>> -outdir met-6.0/data/point_stat \
>>>>>>>> -v 5
>>>>>>>>
>>>>>>>> I will use point-stat for 23 point observations files per day
for
>>>>>>>> multiple years, is there a solution that will allow me to do
it
>>>>>>>> faster/simply? I tried with "point_obs
>>>>>>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
>>>>>>>> met-6.0/data/Metar_test/T" but it is not working.
>>>>>>>>
>>>>>>>>
>>>>>>>> I have another question about Point-Stat Configuration. For
>> instance,
>>>> I
>>>>>>>> have used variables gives in the user_guide examples as
bellow:
>>>>>>>>
>>>>>>>>       field = [
>>>>>>>>            {
>>>>>>>>              name       = "TMP";
>>>>>>>>              level      = [ "Z2" ];
>>>>>>>>              cat_thresh = [ <=273.0 ];
>>>>>>>>          },
>>>>>>>>            {
>>>>>>>>          name       = "UGRD";
>>>>>>>>              level      = [ "Z10" ];
>>>>>>>>              cat_thresh = [ >=5.0 ];
>>>>>>>>          },
>>>>>>>>            {
>>>>>>>>          name       = "VGRD";
>>>>>>>>              level      = [ "Z10" ];
>>>>>>>>              cat_thresh = [ >=5.0 ];
>>>>>>>>          }
>>>>>>>>         ];
>>>>>>>>
>>>>>>>>
>>>>>>>> It is actually working, but I would like to evaluate
additional
>>>>>>>> variables. Where I can find informations about the name of
>> variables ?
>>>>>>>> Indeed, I can not read my file after pre-processing with
Madis2nc.
>>>>>>>>
>>>>>>>> Many thanks,
>>>>>>>>
>>>>>>>> Regards.
>>>>>>>>
>>>>>>>> Adrien
>>>>>>>>
>>>>>>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
>>>>>>>>> Hi Adrien.
>>>>>>>>>
>>>>>>>>> When you run "point_stat" you can see the usage statement
(see
>>>> below).
>>>>>>>> You
>>>>>>>>> can use the "-point_obs" option to specify additional point
>>>> observation
>>>>>>>>> files:
>>>>>>>>>
>>>>>>>>>        "-point_obs file" specifies additional NetCDF point
>> observation
>>>>>> files
>>>>>>>> to
>>>>>>>>> be used (optional).
>>>>>>>>>
>>>>>>>>> You can use this option multiple times.  So, if you have
multiple
>>>>>>>>> additional observation files you can add "-point_obs
<obs_file_a>
>>>>>>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your
call to
>>>>>>>> point_stat.
>>>>>>>>> I hope that helps.  Please let us know if you have any other
>>>> questions.
>>>>>>>>> Julie
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> *** Model Evaluation Tools (METV6.0) ***
>>>>>>>>>
>>>>>>>>> Usage: point_stat
>>>>>>>>>              fcst_file
>>>>>>>>>              obs_file
>>>>>>>>>              config_file
>>>>>>>>>              [-point_obs file]
>>>>>>>>>              [-obs_valid_beg time]
>>>>>>>>>              [-obs_valid_end time]
>>>>>>>>>              [-outdir path]
>>>>>>>>>              [-log file]
>>>>>>>>>              [-v level]
>>>>>>>>>
>>>>>>>>>              where   "fcst_file" is a gridded forecast file
>> containing
>>>> the
>>>>>>>>> field(s) to be verified (required).
>>>>>>>>>                      "obs_file" is an observation file in
NetCDF
>> format
>>>>>>>>> containing the verifying point observations (required).
>>>>>>>>>                      "config_file" is a PointStatConfig file
>> containing
>>>>>> the
>>>>>>>>> desired configuration settings (required).
>>>>>>>>>                      "-point_obs file" specifies additional
NetCDF
>>>> point
>>>>>>>>> observation files to be used (optional).
>>>>>>>>>                      "-obs_valid_beg time" in
YYYYMMDD[_HH[MMSS]]
>> sets
>>>> the
>>>>>>>>> beginning of the matching time window (optional).
>>>>>>>>>                      "-obs_valid_end time" in
YYYYMMDD[_HH[MMSS]]
>> sets
>>>> the
>>>>>>>> end
>>>>>>>>> of the matching time window (optional).
>>>>>>>>>                      "-outdir path" overrides the default
output
>>>> directory
>>>>>>>> (.)
>>>>>>>>> (optional).
>>>>>>>>>                      "-log file" outputs log messages to the
>> specified
>>>>>> file
>>>>>>>>> (optional).
>>>>>>>>>                      "-v level" overrides the default level
of
>> logging
>>>> (2)
>>>>>>>>> (optional).
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
>>>>>> met_help at ucar.edu
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>
>>>>>>>>>> Hello Julie,
>>>>>>>>>>
>>>>>>>>>> How can I pass multiple netcdf point observation files to
>> point-stat
>>>>>> ? I
>>>>>>>>>> didn't see any informations on the user_guide about it.
>>>>>>>>>>
>>>>>>>>>> Thank you,
>>>>>>>>>>
>>>>>>>>>> Adrien
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>
>>>>>>>>>>> There’s no “need” to merge the files.   You can pass
multiple
>>>> netcdf
>>>>>>>>>> point
>>>>>>>>>>> observation files to point_stat and ensemble_stat.
However, if
>> you
>>>>>>>> would
>>>>>>>>>>> like to merge the files, you could consider using the
"ncrcat"
>>>> tool:
>>>>>>>>>>> https://linux.die.net/man/1/ncrcat
>>>>>>>>>>>
>>>>>>>>>>> from NCO:
>>>>>>>>>>> http://nco.sourceforge.net/
>>>>>>>>>>>
>>>>>>>>>>> I hope that helps!
>>>>>>>>>>>
>>>>>>>>>>> Julie
>>>>>>>>>>>
>>>>>>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
>>>>>>>> met_help at ucar.edu
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>>>>>>>>>>>>
>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>
>>>>>>>>>>>> I am running Madis2nc tool for hourly basis metar data.
>> Actually I
>>>>>>>> would
>>>>>>>>>>>> like to merge these hourly data in daily file. Do you
have
>>>>>> suggestion
>>>>>>>> or
>>>>>>>>>>>> recommendation on how to do it ? Is there option for that
in
>> MET ?
>>>>>>>>>>>>
>>>>>>>>>>>> Regards,
>>>>>>>>>>>>
>>>>>>>>>>>> Adrien
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit :
>>>>>>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us
know.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT <
>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>>>>>>>>>>>>>> Hi Julie,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks to the previous met_help ticket, now that worked
>>>> perfectly
>>>>>> !
>>>>>>>> I
>>>>>>>>>> am
>>>>>>>>>>>>>> so grateful for your help, thank you. Now I will adapt
this
>>>> method
>>>>>>>> for
>>>>>>>>>>>>>> all my data.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Another time, thank you. I'll definitely let you know
if I
>> have
>>>>>>>> others
>>>>>>>>>>>>>> questions.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Best regards,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Adrien
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a écrit
:
>>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I'm glad MET was able to read your CF compliant file.
Thank
>>>> you
>>>>>>>> for
>>>>>>>>>>>>>>> uploading your data.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> When I run point_stat with your data and configuration
file,
>> I
>>>>>> see
>>>>>>>>>> the
>>>>>>>>>>>>>>> following warning:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
>>>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for "T_sfc"
>> variable,
>>>>>> the
>>>>>>>>>>>> lead
>>>>>>>>>>>>>>> time does not match the requested lead time: (000000
!=
>> 020000)
>>>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields
matching
>>>>>>>>>> T_sfc(0,*,*)
>>>>>>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
>>>>>>>>>>>>>>> WARNING:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> There is a specific way in the CF-convention of
specifying
>> the
>>>>>>>>>>>>>>> initialization time of the model.  You do so by
defining a
>>>>>> variable
>>>>>>>>>>>> named
>>>>>>>>>>>>>>> "forecast_reference_time".  When that variable is not
>> present,
>>>>>> MET
>>>>>>>>>> sets
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>> forecast initialization time to the same value as the
valid
>>>> time,
>>>>>>>>>> which
>>>>>>>>>>>>>>> results in a lead time of 0.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> You need to add the "forecast_reference_time" variable
to
>> your
>>>>>>>> model
>>>>>>>>>>>>>>> files.  Take a look at this previous met_help ticket
and see
>> if
>>>>>>>> that
>>>>>>>>>>>>>> helps:
>>>>>>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/
>>>> 002867.html
>>>>>>>>>>>>>>> Also, I see in your PointStatConfig file that you have
>> defined
>>>>>>>>>>>>>> "lead_time"
>>>>>>>>>>>>>>> in the fcst dictionary.  That is not necessary and
could
>> cause
>>>>>>>>>>>> problems.
>>>>>>>>>>>>>>> MET determines the lead time by the time index of the
time
>>>>>>>> dimension
>>>>>>>>>>>> that
>>>>>>>>>>>>>>> you specify in the "level" field:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>                 level      = "(0,*,*)";
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I hope that helps.  Please let us know if you have any
other
>>>>>>>>>> questions.
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via RT
<
>>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
>> Ticket/Display.html?id=81768
>>>>>>>>>>>>>>>> Hi Julie,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Many thank, I have done as you suggested and MET
seems to
>> read
>>>>>> my
>>>>>>>> CF
>>>>>>>>>>>>>>>> Compliant. However, I still have issues with the
>> configuration
>>>>>> of
>>>>>>>>>>>>>>>> Point-Stat.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
>>>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance) - daily
file
>> for
>>>>>>>>>>>> 2013-01-01
>>>>>>>>>>>>>>>> I would also provide you :
>>>>>>>>>>>>>>>> - point observation file from Madis2nc - hourly file
for
>>>>>>>>>>>>>>>> 2013-01-01_02:00:00
>>>>>>>>>>>>>>>> - Point-Stat configuration
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> I'm grateful for you help.
>>>>>>>>>>>>>>>> Regards,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a
écrit :
>>>>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> It is difficult to tell the problem with the file
without
>>>>>> seeing
>>>>>>>>>> it.
>>>>>>>>>>>>>>>>> However, I have something for you to try that might
work.
>>>> MET
>>>>>>>>>> should
>>>>>>>>>>>>>> be
>>>>>>>>>>>>>>>>> able to read CF compliant files, and you have stated
that
>>>> your
>>>>>>>>>> NetCDF
>>>>>>>>>>>>>>>> file
>>>>>>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type
of file,
>>>> but
>>>>>>>>>> since
>>>>>>>>>>>>>> it
>>>>>>>>>>>>>>>> is
>>>>>>>>>>>>>>>>> having trouble, let's try explicitly telling the
tools how
>> to
>>>>>>>>>> process
>>>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>> data by setting the following in your PointStat
config
>> file:
>>>>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> This entry should be defined within the "fcst"
dictionary.
>>>> For
>>>>>>>>>>>>>> example:
>>>>>>>>>>>>>>>>> fcst = {
>>>>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
>>>>>>>>>>>>>>>>> ...
>>>>>>>>>>>>>>>>> }
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> If that works, please let us know.  If that does not
work,
>>>>>> please
>>>>>>>>>>>>>> upload
>>>>>>>>>>>>>>>>> your file to our ftp server using the following
>> instructions
>>>>>> and
>>>>>>>>>> let
>>>>>>>>>>>> us
>>>>>>>>>>>>>>>>> know once you have done that so that we can get the
file
>> and
>>>>>>>> take a
>>>>>>>>>>>>>> look.
>>>>>>>>>>>>>>>>>
http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via
RT <
>>>>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
>>>> Ticket/Display.html?id=81768
>>>>>>>>>>>>>>>>>> Hi Julie.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>            I've done as you suggested and it ran
without
>>>> problem,
>>>>>>>> thank
>>>>>>>>>>>> you!
>>>>>>>>>>>>>>>>>> I come up with a another issue.. I'm trying to use
>>>> Point-Stat
>>>>>> :
>>>>>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
>>>>>>>>>>>>>>>>>> - a point observation file coming from Madis2nc
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> However, Point Stat seems to have issue to read my
>> forecast
>>>>>> file
>>>>>>>>>>>> with
>>>>>>>>>>>>>>>>>> the following informations:
>>>>>>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
>>>>>>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
>>>>>>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
>>>>>>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
>>>>>>>>>>>>>>>>>>> DEBUG 1: Default Config File:
>>>>>>>>>>>>>>>>>>>
/usr/local/share/met/config/PointStatConfig_default
>>>>>>>>>>>>>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/
>>>> PointStatConfig
>>>>>>>>>>>>>>>>>>> DEBUG 4:
Met2dDataFileFactory::new_met_2d_data_file() ->
>>>>>>>> created
>>>>>>>>>>>> new
>>>>>>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
>>>>>>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>>>>>>> ERROR  : Trouble reading forecast file
>>>>>>>>>>>>>>>>>>> "met-6.0/data/WRF_cf/wrfpost_output.nc"
>>>>>>>>>>>>>>>>>>> ERROR  :
>>>>>>>>>>>>>>>>>> I was wondering if you had any insight on what I
could be
>>>>>> doing
>>>>>>>>>>>>>> wrong. I
>>>>>>>>>>>>>>>>>> appreciate any help you can give.
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Adrien Michel/
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> /
>>>>>>>>>>>>>>>>>> Le 11/09/2017 à 21:13, Julie Prestopnik via RT a
écrit :
>>>>>>>>>>>>>>>>>>> Hi Adrien.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I see that you have a question about how to define
a
>>>> polyline
>>>>>>>>>>>> masking
>>>>>>>>>>>>>>>>>>> file.  The -mask_grid option would take a named
grid or a
>>>>>>>> gridded
>>>>>>>>>>>>>> data
>>>>>>>>>>>>>>>>>>> file, while the -mask_poly option would definite a
>> polyline
>>>>>>>>>> masking
>>>>>>>>>>>>>>>> file.
>>>>>>>>>>>>>>>>>>> If you'd only like to keep the points falling
inside your
>>>>>> model
>>>>>>>>>>>>>> domain,
>>>>>>>>>>>>>>>>>> and
>>>>>>>>>>>>>>>>>>> you have a gridded data file on that domain, using
>>>> -mask_grid
>>>>>>>> is
>>>>>>>>>>>> very
>>>>>>>>>>>>>>>>>>> simple:
>>>>>>>>>>>>>>>>>>>              -mask_grid /path/to/gridded/data/file
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> However, if you'd prefer the flexibility of
defining a
>>>>>> polyline
>>>>>>>>>>>>>> masking
>>>>>>>>>>>>>>>>>>> region, using -mask_poly would work too:
>>>>>>>>>>>>>>>>>>>              -mask_poly
/path/to/polyline/mask/file
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> To create a polyline mask, you simply create an
ASCII
>> file
>>>>>>>>>>>>>> containing a
>>>>>>>>>>>>>>>>>>> list of lat/lons that define the region of
interest.  For
>>>>>>>>>> example,
>>>>>>>>>>>>>>>> take a
>>>>>>>>>>>>>>>>>>> look in met-6.0/data/poly/SWC.poly.  The first
line of
>> the
>>>>>> file
>>>>>>>>>>>>>>>> specifies
>>>>>>>>>>>>>>>>>>> the name for the polyline, and the remaining lines
>> contain
>>>>>>>>>> lat/lon
>>>>>>>>>>>>>>>> values
>>>>>>>>>>>>>>>>>>> for the boundary points.  The last point is
connected
>> back
>>>> up
>>>>>>>> to
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>> first
>>>>>>>>>>>>>>>>>>> point to complete the area.  The example is named
"SWC"
>> and
>>>>>>>>>>>> contains
>>>>>>>>>>>>>> 33
>>>>>>>>>>>>>>>>>>> points, and there is no real maximum.
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I hope this helps.  Please let us know if you have
other
>>>>>>>>>> questions.
>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>> Julie
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Mon, Sep 11, 2017 at 2:55 AM, Adrien Michel via
RT <
>>>>>>>>>>>>>>>> met_help at ucar.edu
>>>>>>>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/Tic
>>>>>> ket/Display.html?id=81768
>>>>>>>>>>>>>>>>>>>> Hello Julie,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> I have further questions about Madis2nc use. I
would
>> like
>>>> to
>>>>>>>> use
>>>>>>>>>>>> the
>>>>>>>>>>>>>>>>>>>> '-mask_grid string' option. However there are
very
>> limited
>>>>>>>>>> details
>>>>>>>>>>>>>> on
>>>>>>>>>>>>>>>>>>>> how define the polyline masking file in the user
guide.
>> I
>>>>>>>> should
>>>>>>>>>>>>>> like
>>>>>>>>>>>>>>>> to
>>>>>>>>>>>>>>>>>>>> define the polyline masking file for Europe and
>> especially
>>>>>> for
>>>>>>>>>>>>>> France.
>>>>>>>>>>>>>>>>>>>> Thank you in advance,
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Regards.
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Adrien
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Le 30/08/2017 à 16:45, Julie Prestopnik via RT a
écrit :
>>>>>>>>>>>>>>>>>>>>> According to our records, your request has been
>> resolved.
>>>>>> If
>>>>>>>>>> you
>>>>>>>>>>>>>> have
>>>>>>>>>>>>>>>>>> any
>>>>>>>>>>>>>>>>>>>>> further questions or concerns, please respond to
this
>>>>>>>> message.
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>>>>>> Environmental Consultant | Consultant
Environnement
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300
Nantes,
>> FRANCE
>>>>>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M:
+33 6
>>>> 95
>>>>>> 37
>>>>>>>>>> 95
>>>>>>>>>>>> 15
>>>>>>>>>>>>>> |
>>>>>>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>>>>>>> amichel at atmoterra.com
<mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M:
+33 6
>> 95
>>>> 37
>>>>>>>> 95
>>>>>>>>>> 15
>>>>>>>>>>>> |
>>>>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>>>>> amichel at atmoterra.com
<mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33
6 95
>> 37
>>>>>> 95
>>>>>>>> 15
>>>>>>>>>> |
>>>>>>>>>>>>>> E:
>>>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>> --
>>>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes,
FRANCE
>>>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>>>> 95
>>>>>> 15
>>>>>>>> |
>>>>>>>>>>>> E:
>>>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Adrien Michel
>>>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>>>
>>>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6
95 37
>> 95
>>>> 15
>>>>>>>> <+33%206%2095%2037%2095%2015> |
>>>>>>>>>> E:
>>>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Adrien Michel
>>>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>>>
>>>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
>>>>>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16
>>>>>>>> 27 84 <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>>>>> <+33%206%2095%2037%2095%2015>
>>>>>>>> <+33%206%2095%2037%2095%2015> | E:
>>>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> --
>>>>>>>> Adrien Michel
>>>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>>>
>>>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084>
>>>>>> <+33%209%2084%2016%2027%2084> | F : +33 9 89 16 27 84
>>>>>> <+33%209%2089%2016%2027%2084>
>>>>>>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>>>>> <+33%206%2095%2037%2095%2015>
>>>>>>>> <+33%206%2095%2037%2095%2015> | E:
>>>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>>>> Website: http://www.atmoterra.com
>>>>>>>>
>>>>>>>>
>>>>>> --
>>>>>> Adrien Michel
>>>>>> Environmental Consultant | Consultant Environnement
>>>>>>
>>>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>>>> T: +33 9 84 16 27 84 <+33%209%2084%2016%2027%2084> | F : +33 9
89 16
>> 27
>>>> 84
>>>>>> <+33%209%2089%2016%2027%2084> | M: +33 6 95 37 95 15
>>>>>> <+33%206%2095%2037%2095%2015> | E:
>>>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>>>> Website: http://www.atmoterra.com
>>>>>>
>>>>>>
>>>> --
>>>> Adrien Michel
>>>> Environmental Consultant | Consultant Environnement
>>>>
>>>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>>>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95
15 | E:
>>>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>>>> Website: http://www.atmoterra.com
>>>>
>>>>
>> --
>> Adrien Michel
>> Environmental Consultant | Consultant Environnement
>>
>> ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
>> T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15
| E:
>> amichel at atmoterra.com <mailto:amichel at atmoterra.com>
>> Website: http://www.atmoterra.com
>>
>>

--
Adrien Michel
Environmental Consultant | Consultant Environnement

ATMOTERRA | 80 Impasse des Nympheas, 44300 Nantes, FRANCE
T: +33 9 84 16 27 84 | F : +33 9 89 16 27 84 | M: +33 6 95 37 95 15 |
E:
amichel at atmoterra.com <mailto:amichel at atmoterra.com>
Website: http://www.atmoterra.com

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: Adrien Michel
Time: Mon Dec 11 08:59:23 2017

VERSION MODEL DESC FCST_LEAD  FCST_VALID_BEG  FCST_VALID_END  OBS_LEAD
OBS_VALID_BEG   OBS_VALID_END   FCST_VAR FCST_LEV OBS_VAR OBS_LEV
OBTYPE VX_MASK INTERP_MTHD INTERP_PNTS FCST_THRESH OBS_THRESH
COV_THRESH ALPHA LINE_TYPE TOTAL INDEX OBS_SID OBS_LAT OBS_LON OBS_LVL
OBS_ELV FCST       OBS          CLIMO OBS_QC
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_224600 20130101_224600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     1    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     2    ETNG   50.97    6.05      NA      NA
4.36328  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     3    LSZA   46       8.97      NA      NA
-1.85754  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     4    LSGG   46.25    6.13      NA      NA
4.55493  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     5    LSZB   46.92    7.5       NA      NA
1.6477   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     6    LSZH   47.48    8.53      NA      NA
5.04276  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     7    LSMS   46.22    7.32      NA      NA
-6.74448  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     8    EDDS   48.68    9.22      NA      NA
3.53265  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     9    EDDF   50.05    8.6       NA      NA
1.01947  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    10    EDDK   50.87    7.17      NA      NA
0.19745  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    11    EDDL   51.28    6.78      NA      NA
3.59576  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    12    EDDR   49.22    7.12      NA      NA
0.35608  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    13    LSGC   47.08    6.79      NA      NA
1.92441  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    14    LSZG   47.18    7.42      NA      NA
2.88284  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    15    LSZR   47.48    9.56      NA      NA
-0.47995  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    16    EGGD   51.38   -2.72      NA      NA
7.35941  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    17    EGKK   51.15    0.18      NA      NA
4.19781  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    18    EGFF   51.4    -3.35      NA      NA
8.50964  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    19    EGLC   51.5     0.5       NA      NA
3.38104  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    20    EGLL   51.48   -0.45      NA      NA
1.64105  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    21    ELLX   49.62    6.22      NA      NA
-0.1965   275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    22    EBCI   50.47    4.45      NA      NA
2.0636   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    23    EBLG   50.65    5.45      NA      NA
2.64941  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    24    EBBR   50.9     4.53      NA      NA
2.40012  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    25    EBOS   51.2     2.87      NA      NA
8.02753  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    26    EBAW   51.2     4.47      NA      NA
2.83295  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    27    EDFH   49.95    7.27      NA      NA
0.69312  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    28    LIMJ   44.42    8.85      NA      NA
3.23224  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    29    LIMF   45.22    7.65      NA      NA
1.11459  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    30    LIML   45.43    9.28      NA      NA
2.51675  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    31    LIMC   45.62    8.73      NA      NA
2.63919  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    32    LIME   45.67    9.7       NA      NA
-0.2908   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    33    EHWO   51.45    4.33      NA      NA
3.20996  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    34    EHEH   51.45    5.42      NA      NA
2.25879  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    35    LSMM   46.75    8.12      NA      NA
-2.4776   274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    36    LSMP   46.82    6.95      NA      NA
2.0499   277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    37    LSMA   46.95    8.28      NA      NA
-0.62122  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    38    LSME   47.1     8.3       NA      NA
1.03479  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    39    LSMD   47.4     8.65      NA      NA
6.21149  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    40    EHBK   50.92    5.78      NA      NA
2.7587   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    41    EGDL   51.5    -1.98      NA      NA
2.80792  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    42    EDFE   49.97    8.63      NA      NA
0.69226  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    43    ETOU   50.05    8.33      NA      NA
0.87079  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    44    EHFS   51.44    3.6       NA      NA
5.8168   280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    45    EGLL   51.48   -0.45      NA      NA
1.64105  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    46    EDNY   47.67    9.52      NA      NA
1.07993  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    47    ETAR   49.43    7.6       NA      NA
4.09204  271.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    48    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    49    LFOA   47.05    2.63      NA      NA
1.26373  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    50    LFPV   48.77    2.2       NA      NA
2.1185   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    51    LFPC   49.25    2.52      NA      NA
3.21728  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    52    LFKS   41.92    9.4       NA      NA
13.01678  283.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    53    LFMC   43.38    6.38      NA      NA
5.73798  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    54    LFMY   43.6     5.1       NA      NA
5.09045  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    55    LFBY   43.68   -1.07      NA      NA
9.42578  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    56    LFBM   43.92    0.5       NA      NA
3.78406  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    57    LFMO   44.13    4.83      NA      NA
4.64536  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    58    LFBC   44.53   -1.13      NA      NA
11.31186  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    59    LFBG   45.67    0.32      NA      NA
6.18601  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    60    LFOJ   47.98    1.75      NA      NA
2.68362  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    61    LFOC   48.05    1.38      NA      NA
2.44937  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    62    LFRL   48.28   -4.43      NA      NA
10.61566  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    63    LFRJ   48.52   -4.15      NA      NA
10.44489  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    64    LFOE   49.02    1.22      NA      NA
4.04462  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    65    LFYR   47.32    1.68      NA      NA
3.12106  272.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    66    LFSX   47.78    6.35      NA      NA
0.69504  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    67    LFSO   48.58    5.97      NA      NA
0.77591  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    68    LFSI   48.63    4.9       NA      NA
1.13251  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    69    LFKF   41.5     9.1       NA      NA
8.14899  282.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    70    LFKJ   41.92    8.8       NA      NA
4.57492  283.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    71    LFKB   42.55    9.48      NA      NA
13.32861  282.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    72    LFMP   42.73    2.87      NA      NA
6.50674  282.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    73    LFMV   43.9     4.9       NA      NA
5.27692  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    74    LFLC   45.78    3.17      NA      NA
4.83771  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    75    LFSL   48.78    5.48      NA      NA
0.79895  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    76    LFMN   43.65    7.2       NA      NA
3.43759  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    77    LFLL   45.73    5.08      NA      NA
4.71973  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    78    LFRS   47.17   -1.6       NA      NA
3.81808  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    79    LFRB   48.45   -4.42      NA      NA
10.52704  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    80    LFPO   48.73    2.4       NA      NA
3.25757  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    81    LFPG   49.02    2.53      NA      NA
2.08469  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    82    LFQQ   50.57    3.1       NA      NA
3.39609  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    83    LFBT   43.18    0         NA      NA
4.38315  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    84    LFBP   43.38    0.42      NA      NA
4.22983  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    85    LFBZ   43.47   -1.53      NA      NA
11.78625  284.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    86    LFBO   43.63    1.37      NA      NA
4.88312  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    87    LFBD   44.83   -0.7       NA      NA
6.51163  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    88    LFLB   45.65    5.88      NA      NA
1.59085  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    89    LFBL   45.87    1.18      NA      NA
2.22867  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    90    LFBH   46.15   -1.15      NA      NA
5.27902  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    91    LFBI   46.58    0.32      NA      NA
3.28415  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    92    LFLX   46.85    1.72      NA      NA
3.14825  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    93    LFMU   43.32    3.35      NA      NA
5.18292  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    94    LFMT   43.58    3.97      NA      NA
4.87408  282.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    95    LFCR   44.4     2.48      NA      NA
0.58368  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    96    LFLS   45.37    5.33      NA      NA
2.94717  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    97    LFLY   45.72    4.95      NA      NA
4.71973  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    98    LFLP   45.92    6.08      NA      NA
0.33578  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    99    LFOK   48.78    4.18      NA      NA
4.54672  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   100    LFPB   48.97    2.45      NA      NA
2.08014  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   101    LFJL   48.98    6.25      NA      NA
2.39975  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   102    LFOP   49.38    1.18      NA      NA
5.39545  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   103    LFOB   49.47    2.12      NA      NA
3.85172  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   104    LFOH   49.52    0.07      NA      NA
8.9884   281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   105    LFTW   43.75    4.42      NA      NA
5.38785  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   106    LFBU   45.72    0.22      NA      NA
4.46726  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   107    LFLN   46.42    4.02      NA      NA
0.10043  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   108    LFSD   47.27    5.08      NA      NA
3.40884  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   109    LFRH   47.77   -3.45      NA      NA
5.89777  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   110    LFRQ   47.97   -4.17      NA      NA
10.60959  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   111    LFRT   48.53   -2.85      NA      NA
8.55756  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   112    LFPM   48.62    2.68      NA      NA
2.69507  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   113    LFPT   49.1     2.03      NA      NA
2.92871  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   114    LFAQ   49.97    2.7       NA      NA
3.19467  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   115    LFAT   50.52    1.62      NA      NA
6.86621  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   116    LFMD   43.55    6.95      NA      NA
7.35828  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   117    LFBA   44.18    0.6       NA      NA
4.65518  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   118    LFBE   44.82    0.52      NA      NA
6.41602  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   119    LFMH   45.53    4.3       NA      NA
1.6619   278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   120    LFGJ   47.04    5.44      NA      NA
1.8291   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   121    LFOT   47.45    0.72      NA      NA
4.82355  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   122    LFJR   47.57    0.3       NA      NA
2.01965  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   123    LFPN   48.77    1.1       NA      NA
5.04892  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   124    LFRK   49.18    0.45      NA      NA
8.28967  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   125    LFRG   49.37    0.15      NA      NA
9.02295  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   126    LFRC   49.65   -1.47      NA      NA
9.16122  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   127    LFTH   43.1     6.15      NA      NA
5.05337  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   128    LFMK   43.22    2.32      NA      NA
3.9733   281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   129    LFMI   43.52    4.93      NA      NA
4.49127  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   130    LFRZ   47.32   -2.17      NA      NA
6.19135  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   131    LFSB   47.6     7.52      NA      NA
0.4057   278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   132    LFRN   48.07   -1.73      NA      NA
7.07306  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   133    LFST   48.55    7.63      NA      NA
1.79922  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   134    LFRD   48.58   -2.07      NA      NA
9.78226  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   135    LFRO   48.75   -3.47      NA      NA
10.29303  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   136    LFML   43.45    5.23      NA      NA
4.54486  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   137    LIPO   45.4    10.32      NA      NA
4.26025  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   138    LIMP   44.82   10.29      NA      NA
3.11761  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   139    LEBL   41.28    2.07      NA      NA
6.9787   280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   140    LEZG   41.67   -1.02      NA      NA
4.44064  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   141    LEGE   41.9     2.77      NA      NA
3.50839  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   142    LEPP   42.77   -1.63      NA      NA
4.10703  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   143    EGWU   51.55   -0.42      NA      NA
1.83923  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230500 20130101_230500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   144    LFML   43.45    5.23      NA      NA
4.54486  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   145    EGDY   51      -2.63      NA      NA
5.11035  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   146    EGVP   51.15   -1.57      NA      NA
2.15424  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   147    EGDM   51.17   -1.75      NA      NA
2.09531  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   148    EGVO   51.23    0.95      NA      NA
2.89365  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   149    EGDX   51.39   -3.45      NA      NA
8.6481   280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   150    LEVT   42.88   -2.72      NA      NA
5.25473  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   151    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   152    EBFN   51.08    2.65      NA      NA
8.12592  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   153    LIMP   44.82   10.29      NA      NA
3.11761  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   154    LIPO   45.4    10.32      NA      NA
4.26025  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   155    LIMK   45.03    7.73      NA      NA
0.86166  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   156    LIMJ   44.42    8.85      NA      NA
3.23224  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   157    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   158    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   159    LIMH   45.93    7.7       NA      NA
-2.86731  262.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   160    LFHP   45.08    3.77      NA      NA
0.32205  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   161    LFRI   46.7    -1.38      NA      NA
4.19858  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   162    LIMU   43.95    8.17      NA      NA
8.04858  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   163    EDNY   47.67    9.52      NA      NA
1.07993  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   164    LELO   42.45   -2.33      NA      NA
5.51547  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   165    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   166    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   167    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   168    LELO   42.45   -2.33      NA      NA
5.51547  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   169    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   170    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   171    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   172    LEBL   41.28    2.07      NA      NA
6.9787   280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   173    LEZG   41.67   -1.02      NA      NA
4.44064  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   174    LEGE   41.9     2.77      NA      NA
3.50839  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   175    LEVT   42.88   -2.72      NA      NA
5.25473  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   176    LEGE   41.9     2.77      NA      NA
3.50839  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   177    LFHP   45.08    3.77      NA      NA
0.32205  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   178    LFRI   46.7    -1.38      NA      NA
4.19858  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   179    EDNY   47.67    9.52      NA      NA
1.07993  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   180    LELO   42.45   -2.33      NA      NA
5.51547  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   181    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   182    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   183    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   184    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   185    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231200 20130101_231200 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   186    EHWO   51.45    4.33      NA      NA
3.20996  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231700 20130101_231700 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   187    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231800 20130101_231800 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   188    EHWO   51.45    4.33      NA      NA
3.20996  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233300 20130101_233300 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   189    ETAD   49.98    6.7       NA      NA
0.6319   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   190    LEGE   41.9     2.77      NA      NA
3.50839  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234000 20130101_234000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   191    EDNY   47.67    9.52      NA      NA
1.07993  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233600 20130101_233600 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   192    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   193    EDNY   47.67    9.52      NA      NA
1.07993  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234000 20130101_234000 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   194    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   195    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   196    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 T_2m     23,*,*   TMP     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   197    EHWO   51.45    4.33      NA      NA
3.20996  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_224600 20130101_224600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     1    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     2    ETNG   50.97    6.05      NA      NA
1.61347  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     3    LSZA   46       8.97      NA      NA
-2.84972  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     4    LSGG   46.25    6.13      NA      NA
3.09479  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     5    LSZB   46.92    7.5       NA      NA
2.14763  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     6    LSZH   47.48    8.53      NA      NA
4.17667  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     7    LSMS   46.22    7.32      NA      NA
-7.60956  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     8    EDDS   48.68    9.22      NA      NA
3.34943  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197     9    EDDF   50.05    8.6       NA      NA
0.33038  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    10    EDDK   50.87    7.17      NA      NA
-0.42702  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    11    EDDL   51.28    6.78      NA      NA
1.66734  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    12    EDDR   49.22    7.12      NA      NA
-0.4723   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    13    LSGC   47.08    6.79      NA      NA
1.7333   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    14    LSZG   47.18    7.42      NA      NA
2.76338  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    15    LSZR   47.48    9.56      NA      NA
-1.0613   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    16    EGGD   51.38   -2.72      NA      NA
4.84113  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    17    EGKK   51.15    0.18      NA      NA
1.75548  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    18    EGFF   51.4    -3.35      NA      NA
5.35034  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    19    EGLC   51.5     0.5       NA      NA
1.72404  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    20    EGLL   51.48   -0.45      NA      NA
-0.010198 275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    21    ELLX   49.62    6.22      NA      NA
-1.10799  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    22    EBCI   50.47    4.45      NA      NA
0.63118  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    23    EBLG   50.65    5.45      NA      NA
0.91882  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    24    EBBR   50.9     4.53      NA      NA
0.97939  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    25    EBOS   51.2     2.87      NA      NA
4.67042  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    26    EBAW   51.2     4.47      NA      NA
1.54655  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    27    EDFH   49.95    7.27      NA      NA
-0.37768  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    28    LIMJ   44.42    8.85      NA      NA
3.06054  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    29    LIMF   45.22    7.65      NA      NA
0.69119  272.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    30    LIML   45.43    9.28      NA      NA
1.82837  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    31    LIMC   45.62    8.73      NA      NA
1.80848  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    32    LIME   45.67    9.7       NA      NA
-0.66458  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    33    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    34    EHEH   51.45    5.42      NA      NA
0.80409  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    35    LSMM   46.75    8.12      NA      NA
-2.8311   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    36    LSMP   46.82    6.95      NA      NA
2.70547  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    37    LSMA   46.95    8.28      NA      NA
-0.92249  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    38    LSME   47.1     8.3       NA      NA
1.33549  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    39    LSMD   47.4     8.65      NA      NA
4.61514  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    40    EHBK   50.92    5.78      NA      NA
1.24129  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    41    EGDL   51.5    -1.98      NA      NA
1.18268  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    42    EDFE   49.97    8.63      NA      NA
-0.19396  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    43    ETOU   50.05    8.33      NA      NA
0.6036   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    44    EHFS   51.44    3.6       NA      NA
3.29281  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    45    EGLL   51.48   -0.45      NA      NA
-0.010198 275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    46    EDNY   47.67    9.52      NA      NA
0.61651  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    47    ETAR   49.43    7.6       NA      NA
1.13711  271.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    48    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    49    LFOA   47.05    2.63      NA      NA
0.87854  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    50    LFPV   48.77    2.2       NA      NA
1.30893  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    51    LFPC   49.25    2.52      NA      NA
1.60276  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    52    LFKS   41.92    9.4       NA      NA
8.2463   279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    53    LFMC   43.38    6.38      NA      NA
2.34985  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    54    LFMY   43.6     5.1       NA      NA
3.71766  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    55    LFBY   43.68   -1.07      NA      NA
7.27221  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    56    LFBM   43.92    0.5       NA      NA
3.07951  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    57    LFMO   44.13    4.83      NA      NA
3.11265  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    58    LFBC   44.53   -1.13      NA      NA
6.75109  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    59    LFBG   45.67    0.32      NA      NA
4.71258  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    60    LFOJ   47.98    1.75      NA      NA
2.02594  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    61    LFOC   48.05    1.38      NA      NA
1.44828  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    62    LFRL   48.28   -4.43      NA      NA
5.50082  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    63    LFRJ   48.52   -4.15      NA      NA
5.6938   277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    64    LFOE   49.02    1.22      NA      NA
2.12303  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    65    LFYR   47.32    1.68      NA      NA
2.33619  272.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    66    LFSX   47.78    6.35      NA      NA
0.47697  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    67    LFSO   48.58    5.97      NA      NA
0.26081  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    68    LFSI   48.63    4.9       NA      NA
0.38731  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    69    LFKF   41.5     9.1       NA      NA
6.73693  281.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    70    LFKJ   41.92    8.8       NA      NA
4.24289  282.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    71    LFKB   42.55    9.48      NA      NA
8.34687  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    72    LFMP   42.73    2.87      NA      NA
4.40448  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    73    LFMV   43.9     4.9       NA      NA
3.42267  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    74    LFLC   45.78    3.17      NA      NA
3.099    274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    75    LFSL   48.78    5.48      NA      NA
0.1109   273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    76    LFMN   43.65    7.2       NA      NA
1.42297  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    77    LFLL   45.73    5.08      NA      NA
3.72951  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    78    LFRS   47.17   -1.6       NA      NA
2.16396  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    79    LFRB   48.45   -4.42      NA      NA
5.52476  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    80    LFPO   48.73    2.4       NA      NA
2.21964  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    81    LFPG   49.02    2.53      NA      NA
1.07293  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    82    LFQQ   50.57    3.1       NA      NA
1.83835  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    83    LFBT   43.18    0         NA      NA
3.62629  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    84    LFBP   43.38    0.42      NA      NA
3.82028  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    85    LFBZ   43.47   -1.53      NA      NA
7.89758  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    86    LFBO   43.63    1.37      NA      NA
4.26515  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    87    LFBD   44.83   -0.7       NA      NA
4.458    279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    88    LFLB   45.65    5.88      NA      NA
1.47451  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    89    LFBL   45.87    1.18      NA      NA
0.99282  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    90    LFBH   46.15   -1.15      NA      NA
3.28088  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    91    LFBI   46.58    0.32      NA      NA
2.30343  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    92    LFLX   46.85    1.72      NA      NA
2.41914  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    93    LFMU   43.32    3.35      NA      NA
2.47948  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    94    LFMT   43.58    3.97      NA      NA
2.67432  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    95    LFCR   44.4     2.48      NA      NA
-0.58928  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    96    LFLS   45.37    5.33      NA      NA
2.14454  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    97    LFLY   45.72    4.95      NA      NA
3.72951  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    98    LFLP   45.92    6.08      NA      NA
0.19915  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197    99    LFOK   48.78    4.18      NA      NA
3.34524  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   100    LFPB   48.97    2.45      NA      NA
1.1297   275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   101    LFJL   48.98    6.25      NA      NA
0.836    273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   102    LFOP   49.38    1.18      NA      NA
3.13707  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   103    LFOB   49.47    2.12      NA      NA
1.90788  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   104    LFOH   49.52    0.07      NA      NA
5.20596  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   105    LFTW   43.75    4.42      NA      NA
4.23472  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   106    LFBU   45.72    0.22      NA      NA
3.19677  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   107    LFLN   46.42    4.02      NA      NA
-0.54745  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   108    LFSD   47.27    5.08      NA      NA
2.31099  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   109    LFRH   47.77   -3.45      NA      NA
3.42161  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   110    LFRQ   47.97   -4.17      NA      NA
5.65145  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   111    LFRT   48.53   -2.85      NA      NA
4.78904  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   112    LFPM   48.62    2.68      NA      NA
1.53436  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   113    LFPT   49.1     2.03      NA      NA
1.26136  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   114    LFAQ   49.97    2.7       NA      NA
1.41709  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   115    LFAT   50.52    1.62      NA      NA
4.48908  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   116    LFMD   43.55    6.95      NA      NA
2.96492  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   117    LFBA   44.18    0.6       NA      NA
2.68291  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   118    LFBE   44.82    0.52      NA      NA
5.28029  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   119    LFMH   45.53    4.3       NA      NA
0.83441  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   120    LFGJ   47.04    5.44      NA      NA
0.66112  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   121    LFOT   47.45    0.72      NA      NA
4.14936  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   122    LFJR   47.57    0.3       NA      NA
1.21799  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   123    LFPN   48.77    1.1       NA      NA
2.82529  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   124    LFRK   49.18    0.45      NA      NA
3.5084   274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   125    LFRG   49.37    0.15      NA      NA
5.15157  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   126    LFRC   49.65   -1.47      NA      NA
5.6202   276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   127    LFTH   43.1     6.15      NA      NA
3.82258  280.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   128    LFMK   43.22    2.32      NA      NA
3.52746  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   129    LFMI   43.52    4.93      NA      NA
3.471    279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   130    LFRZ   47.32   -2.17      NA      NA
3.96955  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   131    LFSB   47.6     7.52      NA      NA
0.24343  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   132    LFRN   48.07   -1.73      NA      NA
4.47119  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   133    LFST   48.55    7.63      NA      NA
1.59347  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   134    LFRD   48.58   -2.07      NA      NA
5.76285  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   135    LFRO   48.75   -3.47      NA      NA
5.91549  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   136    LFML   43.45    5.23      NA      NA
2.84111  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   137    LIPO   45.4    10.32      NA      NA
1.20791  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   138    LIMP   44.82   10.29      NA      NA
1.78639  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   139    LEBL   41.28    2.07      NA      NA
4.53882  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   140    LEZG   41.67   -1.02      NA      NA
3.45801  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   141    LEGE   41.9     2.77      NA      NA
-1.45494  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   142    LEPP   42.77   -1.63      NA      NA
3.21128  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   143    EGWU   51.55   -0.42      NA      NA
0.20578  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230500 20130101_230500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   144    LFML   43.45    5.23      NA      NA
2.84111  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   145    EGDY   51      -2.63      NA      NA
3.71031  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   146    EGVP   51.15   -1.57      NA      NA
0.97171  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   147    EGDM   51.17   -1.75      NA      NA
0.50225  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   148    EGVO   51.23    0.95      NA      NA
1.31332  274.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   149    EGDX   51.39   -3.45      NA      NA
5.41658  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   150    LEVT   42.88   -2.72      NA      NA
5.05263  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   151    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   152    EBFN   51.08    2.65      NA      NA
5.05218  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   153    LIMP   44.82   10.29      NA      NA
1.78639  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   154    LIPO   45.4    10.32      NA      NA
1.20791  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   155    LIMK   45.03    7.73      NA      NA
0.58427  275.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   156    LIMJ   44.42    8.85      NA      NA
3.06054  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   157    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   158    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   159    LIMH   45.93    7.7       NA      NA
-4.57078  261.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   160    LFHP   45.08    3.77      NA      NA
0.11593  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   161    LFRI   46.7    -1.38      NA      NA
2.22978  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   162    LIMU   43.95    8.17      NA      NA
5.68887  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   163    EDNY   47.67    9.52      NA      NA
0.61651  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   164    LELO   42.45   -2.33      NA      NA
4.02773  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   165    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   166    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   167    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   168    LELO   42.45   -2.33      NA      NA
4.02773  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   169    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   170    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   171    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   172    LEBL   41.28    2.07      NA      NA
4.53882  278.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   173    LEZG   41.67   -1.02      NA      NA
3.45801  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   174    LEGE   41.9     2.77      NA      NA
-1.45494  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   175    LEVT   42.88   -2.72      NA      NA
5.05263  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   176    LEGE   41.9     2.77      NA      NA
-1.45494  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   177    LFHP   45.08    3.77      NA      NA
0.11593  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   178    LFRI   46.7    -1.38      NA      NA
2.22978  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   179    EDNY   47.67    9.52      NA      NA
0.61651  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   180    LELO   42.45   -2.33      NA      NA
4.02773  279.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   181    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   182    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   183    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   184    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   185    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231200 20130101_231200 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   186    EHWO   51.45    4.33      NA      NA
1.35231  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231700 20130101_231700 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   187    EHWO   51.45    4.33      NA      NA
1.35231  277.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231800 20130101_231800 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   188    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233300 20130101_233300 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   189    ETAD   49.98    6.7       NA      NA
-0.78521  273.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   190    LEGE   41.9     2.77      NA      NA
-1.45494  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234000 20130101_234000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   191    EDNY   47.67    9.52      NA      NA
0.61651  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233600 20130101_233600 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   192    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   193    EDNY   47.67    9.52      NA      NA
0.61651  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234000 20130101_234000 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   194    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   195    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   196    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 Td_2m    23,*,*   DPT     Z2
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         197   197    EHWO   51.45    4.33      NA      NA
1.35231  276.14999       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_224600 20130101_224600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     1    ETAD   49.98    6.7       NA      NA
2.33382    0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     2    ETNG   50.97    6.05      NA      NA
1.54526    2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     3    LSGG   46.25    6.13      NA      NA
-0.91552    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     4    LSZH   47.48    8.53      NA      NA
4.35449    1.23165       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     5    EDDS   48.68    9.22      NA      NA
-1.08928    1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     6    EDDF   50.05    8.6       NA      NA
-0.49813    2.4171        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     7    EDDK   50.87    7.17      NA      NA
1.31041    2.64543       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     8    EDDL   51.28    6.78      NA      NA
2.14819    3.1527        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     9    EDDR   49.22    7.12      NA      NA
1.37468    0.44666       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    10    LSZG   47.18    7.42      NA      NA
-0.68321    2.31475       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    11    LSZR   47.48    9.56      NA      NA
3.11749    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    12    EGGD   51.38   -2.72      NA      NA
-3.64931    8.5052e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    13    EGKK   51.15    0.18      NA      NA
0.17757    1.0557        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    14    EGFF   51.4    -3.35      NA      NA
-5.47126   -1.80056       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    15    EGLC   51.5     0.5       NA      NA
-1.15883    2.31475       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    16    EGLL   51.48   -0.45      NA      NA
-0.9338     0.89332       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    17    ELLX   49.62    6.22      NA      NA
2.09969   -0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    18    EBCI   50.47    4.45      NA      NA
2.39592    2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    19    EBLG   50.65    5.45      NA      NA
3.26705    2.97611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    20    EBBR   50.9     4.53      NA      NA
2.78664    2.97611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    21    EBOS   51.2     2.87      NA      NA
-2.95286   -1.42932       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    22    EBAW   51.2     4.47      NA      NA
1.28204    2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    23    EDFH   49.95    7.27      NA      NA
0.58566    5.6701e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    24    LIMJ   44.42    8.85      NA      NA
1.44439   -2.97611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    25    LIMF   45.22    7.65      NA      NA
-1.86753   -1.45026       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    26    LIML   45.43    9.28      NA      NA
-0.59572    1.33657       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    27    LIMC   45.62    8.73      NA      NA
-0.90607    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    28    LIME   45.67    9.7       NA      NA
-1.09236    1.65339       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    29    EHWO   51.45    4.33      NA      NA
0.071588   2.315         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    30    EHEH   51.45    5.42      NA      NA
1.22371    2.64543       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    31    LSMM   46.75    8.12      NA      NA
-0.13795    0.52785       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    32    LSMP   46.82    6.95      NA      NA
-0.061659   2.4171        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    33    LSMA   46.95    8.28      NA      NA
0.45106    0.99204       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    34    LSME   47.1     8.3       NA      NA
2.38525    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    35    EHBK   50.92    5.78      NA      NA
2.64934    3.63746       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    36    EGDL   51.5    -1.98      NA      NA
-1.70525    1.4076        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    37    EDFE   49.97    8.63      NA      NA
-0.76672    1.78209       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    38    ETOU   50.05    8.33      NA      NA
1.43071    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    39    EHFS   51.44    3.6       NA      NA
-1.84363   -2.46331       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    40    EGLL   51.48   -0.45      NA      NA
-0.9338     0.89332       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    41    EDNY   47.67    9.52      NA      NA
2.93308    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    42    ETAR   49.43    7.6       NA      NA
0.16161    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    43    ETAD   49.98    6.7       NA      NA
2.33382    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    44    LFOA   47.05    2.63      NA      NA
-0.76243    1.18226       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    45    LFPV   48.77    2.2       NA      NA
-0.053262   5.6701e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    46    LFPC   49.25    2.52      NA      NA
-1.24488    2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    47    LFKS   41.92    9.4       NA      NA
7.71576   -0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    48    LFMY   43.6     5.1       NA      NA
-4.19443   -1.78209       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    49    LFBY   43.68   -1.07      NA      NA
-2.78545   -0.99204       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    50    LFBM   43.92    0.5       NA      NA
-0.98732    3.7801e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    51    LFMO   44.13    4.83      NA      NA
-8.67615   -0.78817       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    52    LFBC   44.53   -1.13      NA      NA
-7.1365    -0.17866       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    53    LFBG   45.67    0.32      NA      NA
-2.21884    1.89e-16      NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    54    LFOJ   47.98    1.75      NA      NA
0.2996     0.53599       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    55    LFOC   48.05    1.38      NA      NA
-1.25706   -0.71466       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    56    LFRL   48.28   -4.43      NA      NA
-6.29954   -2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    57    LFRJ   48.52   -4.15      NA      NA
-5.85538   -1.65339       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    58    LFOE   49.02    1.22      NA      NA
-1.05426    1.23165       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    59    LFYR   47.32    1.68      NA      NA
-1.13966    0.96684       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    60    LFSI   48.63    4.9       NA      NA
0.10534    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    61    LFKF   41.5     9.1       NA      NA
1.0822     0.25722       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    62    LFKJ   41.92    8.8       NA      NA
4.62073   -2.75861       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    63    LFKB   42.55    9.48      NA      NA
8.40143    0.78817       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    64    LFMP   42.73    2.87      NA      NA
-4.24639   -1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    65    LFLC   45.78    3.17      NA      NA
-1.85314    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    66    LFSL   48.78    5.48      NA      NA
0.392      0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    67    LFMN   43.65    7.2       NA      NA
0.60411   -3.86736       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    68    LFLL   45.73    5.08      NA      NA
-4.22342   -0.52785       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    69    LFRS   47.17   -1.6       NA      NA
-2.2027    -1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    70    LFRB   48.45   -4.42      NA      NA
-5.59415   -0.7038        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    71    LFPO   48.73    2.4       NA      NA
0.33303    1.0557        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    72    LFPG   49.02    2.53      NA      NA
0.57581    1.23165       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    73    LFQQ   50.57    3.1       NA      NA
0.12661    0.53599       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    74    LFBT   43.18    0         NA      NA
0.24697    1.4076        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    75    LFBZ   43.47   -1.53      NA      NA
-7.90844   -3.1527        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    76    LFBO   43.63    1.37      NA      NA
-1.64086   -0.80399       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    77    LFBD   44.83   -0.7       NA      NA
-3.09422   -1.65339       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    78    LFBL   45.87    1.18      NA      NA
-0.94731   -1.65339       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    79    LFBH   46.15   -1.15      NA      NA
-3.56173   -4.45522       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    80    LFBI   46.58    0.32      NA      NA
-1.46173   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    81    LFLX   46.85    1.72      NA      NA
-1.912      0.53599       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    82    LFMU   43.32    3.35      NA      NA
-5.94436   -1.23165       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    83    LFMT   43.58    3.97      NA      NA
-5.55726   -0.89332       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    84    LFCR   44.4     2.48      NA      NA
-4.19424   -4.33496       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    85    LFLS   45.37    5.33      NA      NA
-2.02076    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    86    LFLY   45.72    4.95      NA      NA
-4.22342   -1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    87    LFLP   45.92    6.08      NA      NA
-1.47249    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    88    LFOK   48.78    4.18      NA      NA
0.3304     2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    89    LFPB   48.97    2.45      NA      NA
1.01666    1.0557        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    90    LFJL   48.98    6.25      NA      NA
-0.32321    2.31475       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    91    LFOP   49.38    1.18      NA      NA
-1.55751    0.87975       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    92    LFOB   49.47    2.12      NA      NA
-1.35935    0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    93    LFOH   49.52    0.07      NA      NA
-5.67636   -4.6295        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    94    LFTW   43.75    4.42      NA      NA
-5.03786   -2.4171        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    95    LFBU   45.72    0.22      NA      NA
-1.91272    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    96    LFLN   46.42    4.02      NA      NA
-0.94824   -2.31475       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    97    LFRH   47.77   -3.45      NA      NA
-3.33801   -1.02889       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    98    LFRQ   47.97   -4.17      NA      NA
-6.3373    -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    99    LFRT   48.53   -2.85      NA      NA
-4.72173    4.7251e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   100    LFPM   48.62    2.68      NA      NA
0.29355    0.87975       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   101    LFPT   49.1     2.03      NA      NA
-1.64485    3.7801e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   102    LFAQ   49.97    2.7       NA      NA
-1.11135    4.7251e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   103    LFAT   50.52    1.62      NA      NA
-3.11349   -2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   104    LFBA   44.18    0.6       NA      NA
-2.49507   -0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   105    LFBE   44.82    0.52      NA      NA
-1.41833   -0.3519        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   106    LFMH   45.53    4.3       NA      NA
-3.67488   -1.57635       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   107    LFGJ   47.04    5.44      NA      NA
0.027556   0.3519        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   108    LFOT   47.45    0.72      NA      NA
-1.92298   -0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   109    LFJR   47.57    0.3       NA      NA
-0.10992   -0.17866       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   110    LFPN   48.77    1.1       NA      NA
-1.56738    0.53599       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   111    LFRK   49.18    0.45      NA      NA
-2.81129    0.71466       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   112    LFRG   49.37    0.15      NA      NA
-5.71597   -2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   113    LFRC   49.65   -1.47      NA      NA
-5.93706   -2.82944       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   114    LFTH   43.1     6.15      NA      NA
-2.5968    -0.52785       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   115    LFMK   43.22    2.32      NA      NA
-5.52263   -2.1114        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   116    LFMI   43.52    4.93      NA      NA
-3.67166   -2.53314       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   117    LFRZ   47.32   -2.17      NA      NA
-3.63789   -1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   118    LFSB   47.6     7.52      NA      NA
-3.83272    0.62533       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   119    LFRN   48.07   -1.73      NA      NA
-1.92644   -1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   120    LFST   48.55    7.63      NA      NA
-0.2753     1.18226       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   121    LFRD   48.58   -2.07      NA      NA
-6.86027   -4.8342        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   122    LFRO   48.75   -3.47      NA      NA
-5.65959   -2.31475       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   123    LFML   43.45    5.23      NA      NA
-3.11217    0.78817       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   124    LIPO   45.4    10.32      NA      NA
-0.83053   -1.78209       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   125    LIMP   44.82   10.29      NA      NA
-0.083796  -0.7038        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   126    LEBL   41.28    2.07      NA      NA
-1.20437   -3.94087       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   127    LEZG   41.67   -1.02      NA      NA
-1.97274   -2.28735       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   128    LEPP   42.77   -1.63      NA      NA
-5.55388   -0.52785       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   129    EGWU   51.55   -0.42      NA      NA
-0.97976    0.53599       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230500 20130101_230500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   130    LFML   43.45    5.23      NA      NA
-3.11217    0.78817       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   131    EGDY   51      -2.63      NA      NA
-3.63064    0.7038        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   132    EGVP   51.15   -1.57      NA      NA
-0.32448    8.5052e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   133    EGDM   51.17   -1.75      NA      NA
-0.62678   -0.98266       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   134    EGVO   51.23    0.95      NA      NA
-0.097672   0.89332       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   135    EGDX   51.39   -3.45      NA      NA
-5.12874   -1.58355       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   136    ETAD   49.98    6.7       NA      NA
2.33382    0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   137    EBFN   51.08    2.65      NA      NA
-2.89626   -2.1114        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   138    LIMP   44.82   10.29      NA      NA
-0.083796  -0.7038        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   139    LIPO   45.4    10.32      NA      NA
-0.83053   -1.78209       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   140    LIMK   45.03    7.73      NA      NA
-0.94782   -0.51444       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   141    LIMJ   44.42    8.85      NA      NA
1.44439   -2.97611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   142    EHWO   51.45    4.33      NA      NA
0.071588   1.7595        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   143    ETAD   49.98    6.7       NA      NA
2.33382    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   144    LIMH   45.93    7.7       NA      NA
0.44683   -3.63746       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   145    LFHP   45.08    3.77      NA      NA
-3.13193   -1.65339       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   146    LFRI   46.7    -1.38      NA      NA
-2.92873   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   147    LIMU   43.95    8.17      NA      NA
-10.90485   -4.11556       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   148    EDNY   47.67    9.52      NA      NA
2.93308    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   149    LELO   42.45   -2.33      NA      NA
-3.51353   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   150    ETAD   49.98    6.7       NA      NA
2.33382    0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   151    EHWO   51.45    4.33      NA      NA
0.071588   1.7595        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   152    ETAD   49.98    6.7       NA      NA
2.33382    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   153    LELO   42.45   -2.33      NA      NA
-3.51353   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   154    ETAD   49.98    6.7       NA      NA
2.33382    0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   155    EHWO   51.45    4.33      NA      NA
0.071588   1.7595        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   156    ETAD   49.98    6.7       NA      NA
2.33382    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   157    LEBL   41.28    2.07      NA      NA
-1.20437   -4.90074       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   158    LEZG   41.67   -1.02      NA      NA
-1.97274   -2.28735       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   159    LEGE   41.9     2.77      NA      NA
0.88022    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   160    LEVT   42.88   -2.72      NA      NA
-4.92606   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   161    LEGE   41.9     2.77      NA      NA
0.88022   -0.17595       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   162    LFHP   45.08    3.77      NA      NA
-3.13193   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   163    LFRI   46.7    -1.38      NA      NA
-2.92873   -1.65339       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   164    EDNY   47.67    9.52      NA      NA
2.93308    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   165    LELO   42.45   -2.33      NA      NA
-3.51353   -1.28611       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   166    ETAD   49.98    6.7       NA      NA
2.33382    0.35733       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   167    EHWO   51.45    4.33      NA      NA
0.071588   1.7595        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   168    ETAD   49.98    6.7       NA      NA
2.33382    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   169    EHWO   51.45    4.33      NA      NA
0.071588   1.7595        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   170    ETAD   49.98    6.7       NA      NA
2.33382    0.268         NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231200 20130101_231200 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   171    EHWO   51.45    4.33      NA      NA
0.071588   0.98266       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231700 20130101_231700 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   172    EHWO   51.45    4.33      NA      NA
0.071588   0.98266       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231800 20130101_231800 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   173    EHWO   51.45    4.33      NA      NA
0.071588   0.98266       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233300 20130101_233300 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   174    ETAD   49.98    6.7       NA      NA
2.33382    4.7251e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   175    LEGE   41.9     2.77      NA      NA
0.88022   -0.17595       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233600 20130101_233600 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   176    EHWO   51.45    4.33      NA      NA
0.071588   1.80056       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   177    EDNY   47.67    9.52      NA      NA
2.93308    0.78817       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234000 20130101_234000 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   178    EHWO   51.45    4.33      NA      NA
0.071588   1.80056       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   179    EHWO   51.45    4.33      NA      NA
0.071588   1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   180    EHWO   51.45    4.33      NA      NA
0.071588   1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 v_10m_gr 23,*,*   VGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   181    EHWO   51.45    4.33      NA      NA
0.071588   1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_224600 20130101_224600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     1    ETAD   49.98    6.7       NA      NA
2.65219    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     2    ETNG   50.97    6.05      NA      NA
3.63658    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     3    LSGG   46.25    6.13      NA      NA
0.36703    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     4    LSZH   47.48    8.53      NA      NA
8.90743    3.38394       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     5    EDDS   48.68    9.22      NA      NA
4.28982    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     6    EDDF   50.05    8.6       NA      NA
4.07867    0.87975       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     7    EDDK   50.87    7.17      NA      NA
4.7976     3.1527        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     8    EDDL   51.28    6.78      NA      NA
3.19715    2.64543       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181     9    EDDR   49.22    7.12      NA      NA
3.21813    2.53314       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    10    LSZG   47.18    7.42      NA      NA
3.89582    2.75861       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    11    LSZR   47.48    9.56      NA      NA
4.94351   -1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    12    EGGD   51.38   -2.72      NA      NA
5.5195     4.63          NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    13    EGKK   51.15    0.18      NA      NA
3.46097    2.90052       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    14    EGFF   51.4    -3.35      NA      NA
6.91111    3.11865       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    15    EGLC   51.5     0.5       NA      NA
5.3882     2.75861       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    16    EGLL   51.48   -0.45      NA      NA
3.44341    5.06629       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    17    ELLX   49.62    6.22      NA      NA
2.71957    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    18    EBCI   50.47    4.45      NA      NA
4.29527    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    19    EBLG   50.65    5.45      NA      NA
4.68132    3.54679       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    20    EBBR   50.9     4.53      NA      NA
4.7245     3.54679       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    21    EBOS   51.2     2.87      NA      NA
9.80061    8.10606       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    22    EBAW   51.2     4.47      NA      NA
3.96651    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    23    EDFH   49.95    7.27      NA      NA
4.69158    3.08667       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    24    LIMJ   44.42    8.85      NA      NA
1.87684   -3.54679       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    25    LIMF   45.22    7.65      NA      NA
-0.86538    0.52785       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    26    LIML   45.43    9.28      NA      NA
-0.85073    0.77167       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    27    LIMC   45.62    8.73      NA      NA
-0.13324    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    28    LIME   45.67    9.7       NA      NA
0.71221   -1.97044       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    29    EHWO   51.45    4.33      NA      NA
3.86542    4.0097        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    30    EHEH   51.45    5.42      NA      NA
3.41655    3.1527        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    31    LSMM   46.75    8.12      NA      NA
5.79168   -1.45026       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    32    LSMP   46.82    6.95      NA      NA
2.68771    0.87975       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    33    LSMA   46.95    8.28      NA      NA
5.12933    1.18226       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    34    LSME   47.1     8.3       NA      NA
3.91572    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    35    EHBK   50.92    5.78      NA      NA
5.0744     4.33496       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    36    EGDL   51.5    -1.98      NA      NA
3.60346    3.86736       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    37    EDFE   49.97    8.63      NA      NA
3.91755    1.02889       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    38    ETOU   50.05    8.33      NA      NA
3.54847    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    39    EHFS   51.44    3.6       NA      NA
6.35973    6.76788       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    40    EGLL   51.48   -0.45      NA      NA
3.44341    5.06629       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    41    EDNY   47.67    9.52      NA      NA
3.89332    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    42    ETAR   49.43    7.6       NA      NA
3.44725    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225800 20130101_225800 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    43    ETAD   49.98    6.7       NA      NA
2.65219    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    44    LFOA   47.05    2.63      NA      NA
3.23982    0.99204       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    45    LFPV   48.77    2.2       NA      NA
3.56398    3.08667       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    46    LFPC   49.25    2.52      NA      NA
4.08225    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    47    LFKS   41.92    9.4       NA      NA
1.05323    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    48    LFMY   43.6     5.1       NA      NA
2.24005    1.02889       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    49    LFBY   43.68   -1.07      NA      NA
1.96735    1.18226       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    50    LFBM   43.92    0.5       NA      NA
3.01228    2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    51    LFMO   44.13    4.83      NA      NA
-0.2338     0.66136       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    52    LFBC   44.53   -1.13      NA      NA
4.92912    1.01326       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    53    LFBG   45.67    0.32      NA      NA
2.19116    1.02889       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    54    LFOJ   47.98    1.75      NA      NA
3.91198    3.03977       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    55    LFOC   48.05    1.38      NA      NA
3.7214     4.05303       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    56    LFRL   48.28   -4.43      NA      NA
4.67997    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    57    LFRJ   48.52   -4.15      NA      NA
5.14489    1.97044       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    58    LFOE   49.02    1.22      NA      NA
3.66905    3.38394       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    59    LFYR   47.32    1.68      NA      NA
3.4624     0.3519        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    60    LFSI   48.63    4.9       NA      NA
3.20082    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    61    LFKF   41.5     9.1       NA      NA
1.31688   -0.44552       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    62    LFKJ   41.92    8.8       NA      NA
0.23173   -2.31475       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    63    LFKB   42.55    9.48      NA      NA
-0.2402     0.66136       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    64    LFMP   42.73    2.87      NA      NA
5.4705     2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    65    LFLC   45.78    3.17      NA      NA
2.79168    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    66    LFSL   48.78    5.48      NA      NA
3.75184    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    67    LFMN   43.65    7.2       NA      NA
-1.61174    1.4076        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    68    LFLL   45.73    5.08      NA      NA
3.69975    1.45026       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    69    LFRS   47.17   -1.6       NA      NA
2.95345    2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    70    LFRB   48.45   -4.42      NA      NA
4.73347    1.93368       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    71    LFPO   48.73    2.4       NA      NA
3.59158    2.90052       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    72    LFPG   49.02    2.53      NA      NA
3.46016    3.38394       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    73    LFQQ   50.57    3.1       NA      NA
5.39796    3.03977       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    74    LFBT   43.18    0         NA      NA
2.87581    3.86736       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    75    LFBZ   43.47   -1.53      NA      NA
3.27872    2.64543       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    76    LFBO   43.63    1.37      NA      NA
3.10434    4.55966       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    77    LFBD   44.83   -0.7       NA      NA
2.45938    1.97044       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    78    LFBL   45.87    1.18      NA      NA
2.34915    1.97044       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    79    LFBH   46.15   -1.15      NA      NA
1.15561    2.57222       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    80    LFBI   46.58    0.32      NA      NA
2.80228    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    81    LFLX   46.85    1.72      NA      NA
3.92733    3.03977       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    82    LFMU   43.32    3.35      NA      NA
4.31889    3.38394       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    83    LFMT   43.58    3.97      NA      NA
0.041453   5.06629       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    84    LFCR   44.4     2.48      NA      NA
1.64438    3.63746       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    85    LFLS   45.37    5.33      NA      NA
2.53252    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    86    LFLY   45.72    4.95      NA      NA
3.69975    2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    87    LFLP   45.92    6.08      NA      NA
3.92655    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    88    LFOK   48.78    4.18      NA      NA
3.94802    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    89    LFPB   48.97    2.45      NA      NA
3.18888    2.90052       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    90    LFJL   48.98    6.25      NA      NA
3.59364    2.75861       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    91    LFOP   49.38    1.18      NA      NA
4.29951    2.4171        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    92    LFOB   49.47    2.12      NA      NA
4.9686     2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    93    LFOH   49.52    0.07      NA      NA
7.63277    5.51722       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    94    LFTW   43.75    4.42      NA      NA
0.012358  -0.87975       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    95    LFBU   45.72    0.22      NA      NA
1.75433    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    96    LFLN   46.42    4.02      NA      NA
2.62635    2.75861       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    97    LFRH   47.77   -3.45      NA      NA
1.98075    1.78209       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    98    LFRQ   47.97   -4.17      NA      NA
3.89973    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181    99    LFRT   48.53   -2.85      NA      NA
3.84143    2.57222       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   100    LFPM   48.62    2.68      NA      NA
3.40711    2.4171        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   101    LFPT   49.1     2.03      NA      NA
4.47798    2.05778       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   102    LFAQ   49.97    2.7       NA      NA
5.04602    2.57222       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   103    LFAT   50.52    1.62      NA      NA
9.61716    3.56418       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   104    LFBA   44.18    0.6       NA      NA
1.5579     1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   105    LFBE   44.82    0.52      NA      NA
1.36994    0.96684       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   106    LFMH   45.53    4.3       NA      NA
4.18547    1.32271       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   107    LFGJ   47.04    5.44      NA      NA
2.17728    0.96684       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   108    LFOT   47.45    0.72      NA      NA
4.81278    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   109    LFJR   47.57    0.3       NA      NA
2.12466    1.01326       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   110    LFPN   48.77    1.1       NA      NA
4.41002    3.03977       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   111    LFRK   49.18    0.45      NA      NA
3.98432    4.05303       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   112    LFRG   49.37    0.15      NA      NA
7.20196    1.54333       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   113    LFRC   49.65   -1.47      NA      NA
7.59266    4.90074       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   114    LFTH   43.1     6.15      NA      NA
3.83163    1.45026       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   115    LFMK   43.22    2.32      NA      NA
2.97297    5.80104       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   116    LFMI   43.52    4.93      NA      NA
0.95978    0.44666       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   117    LFRZ   47.32   -2.17      NA      NA
2.45514    2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   118    LFSB   47.6     7.52      NA      NA
4.08702    3.5464        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   119    LFRN   48.07   -1.73      NA      NA
2.87211    3.7801e-16    NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   120    LFST   48.55    7.63      NA      NA
4.58805    0.99204       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   121    LFRD   48.58   -2.07      NA      NA
5.36415    1.7595        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   122    LFRO   48.75   -3.47      NA      NA
5.77534    2.75861       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   123    LFML   43.45    5.23      NA      NA
1.77075   -0.66136       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   124    LIPO   45.4    10.32      NA      NA
-2.97105   -1.02889       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   125    LIMP   44.82   10.29      NA      NA
-2.53345    1.93368       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   126    LEBL   41.28    2.07      NA      NA
1.63392    3.30679       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   127    LEZG   41.67   -1.02      NA      NA
4.43623    6.28446       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   128    LEPP   42.77   -1.63      NA      NA
3.68771    1.45026       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   129    EGWU   51.55   -0.42      NA      NA
3.68573    3.03977       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230500 20130101_230500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   130    LFML   43.45    5.23      NA      NA
1.77075   -0.66136       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   131    EGDY   51      -2.63      NA      NA
5.60555    1.93368       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   132    EGVP   51.15   -1.57      NA      NA
3.96444    4.63          NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   133    EGDM   51.17   -1.75      NA      NA
3.45198    5.57292       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   134    EGVO   51.23    0.95      NA      NA
4.611      5.06629       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   135    EGDX   51.39   -3.45      NA      NA
7.13522    4.35078       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   136    ETAD   49.98    6.7       NA      NA
2.65219    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   137    EBFN   51.08    2.65      NA      NA
10.32952    5.80104       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   138    LIMP   44.82   10.29      NA      NA
-2.53345    1.93368       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   139    LIPO   45.4    10.32      NA      NA
-2.97105   -1.02889       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   140    LIMK   45.03    7.73      NA      NA
0.61572   -0.89104       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225000 20130101_225000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   141    LIMJ   44.42    8.85      NA      NA
1.87684   -3.54679       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   142    EHWO   51.45    4.33      NA      NA
3.86542    4.8342        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   143    ETAD   49.98    6.7       NA      NA
2.65219    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   144    LIMH   45.93    7.7       NA      NA
-0.071803  -4.33496       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   145    LFHP   45.08    3.77      NA      NA
2.84253    1.97044       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   146    LFRI   46.7    -1.38      NA      NA
2.05884    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   147    LIMU   43.95    8.17      NA      NA
3.19459    1.008e-15     NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   148    EDNY   47.67    9.52      NA      NA
3.89332    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   149    LELO   42.45   -2.33      NA      NA
2.72891    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   150    ETAD   49.98    6.7       NA      NA
2.65219    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   151    EHWO   51.45    4.33      NA      NA
3.86542    4.8342        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   152    ETAD   49.98    6.7       NA      NA
2.65219    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   153    LELO   42.45   -2.33      NA      NA
2.72891    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   154    ETAD   49.98    6.7       NA      NA
2.65219    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   155    EHWO   51.45    4.33      NA      NA
3.86542    4.8342        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   156    ETAD   49.98    6.7       NA      NA
2.65219    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   157    LEBL   41.28    2.07      NA      NA
1.63392    2.82944       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   158    LEZG   41.67   -1.02      NA      NA
4.43623    6.28446       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   159    LEGE   41.9     2.77      NA      NA
1.65222    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   160    LEVT   42.88   -2.72      NA      NA
1.00845    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   161    LEGE   41.9     2.77      NA      NA
1.65222    0.48342       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   162    LFHP   45.08    3.77      NA      NA
2.84253    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233000 20130101_233000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   163    LFRI   46.7    -1.38      NA      NA
2.05884    1.97044       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_225500 20130101_225500 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   164    EDNY   47.67    9.52      NA      NA
3.89332    0             NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230000 20130101_230000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   165    LELO   42.45   -2.33      NA      NA
2.72891    2.22761       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230300 20130101_230300 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   166    ETAD   49.98    6.7       NA      NA
2.65219    2.02652       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   167    EHWO   51.45    4.33      NA      NA
3.86542    4.8342        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   168    ETAD   49.98    6.7       NA      NA
2.65219    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_230600 20130101_230600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   169    EHWO   51.45    4.33      NA      NA
3.86542    4.8342        NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231400 20130101_231400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   170    ETAD   49.98    6.7       NA      NA
2.65219    1.51989       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231200 20130101_231200 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   171    EHWO   51.45    4.33      NA      NA
3.86542    5.57292       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231700 20130101_231700 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   172    EHWO   51.45    4.33      NA      NA
3.86542    5.57292       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_231800 20130101_231800 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   173    EHWO   51.45    4.33      NA      NA
3.86542    5.57292       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233300 20130101_233300 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   174    ETAD   49.98    6.7       NA      NA
2.65219    2.57222       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   175    LEGE   41.9     2.77      NA      NA
1.65222    0.48342       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_233600 20130101_233600 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   176    EHWO   51.45    4.33      NA      NA
3.86542    3.11865       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234100 20130101_234100 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   177    EDNY   47.67    9.52      NA      NA
3.89332   -0.66136       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234000 20130101_234000 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   178    EHWO   51.45    4.33      NA      NA
3.86542    3.11865       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   179    EHWO   51.45    4.33      NA      NA
3.86542    2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   180    EHWO   51.45    4.33      NA      NA
3.86542    2.67313       NA      S
V6.0    WRF   NA   3769670000 20130101_230000 20130101_230000 000000
20130101_234400 20130101_234400 u_10m_gr 23,*,*   UGRD    Z10
ADPSFC FULL    NEAREST     1           NA          NA         NA
NA    MPR         181   181    EHWO   51.45    4.33      NA      NA
3.86542    2.67313       NA      S

------------------------------------------------
Subject: Met_v6 - Issues using Point Stat
From: John Halley Gotway
Time: Mon Dec 11 09:29:58 2017

Michel,

I see you're having some issues with the STAT-Analysis tool.  Thanks
for
sending your sample data.  I grabbed it, reran your job, and
replicated the
behavior you describe.

The error you're getting is actually coming from the command line
switch
(-fcst_lead 20130101_020000) that you specified.  STAT-Analysis is
expecting that setting to be in HHMMSS format (for hours, minutes, and
seconds) instead of the YYYYMMDD_HHMMSS format you specified.

Let's take a step back and clarify what STAT-Analysis is doing.

(1) You use the "-lookin path" option one or more times to to tell
STAT-Analysis what files and/or directories to read.  If the "path" is
a
filename, it reads that file regardless of the suffix.  If the "path"
is a
directory, it searches that directory *recursively* looking for files
that
end in ".stat".  So basically, you use "-lookin" to tell STAT-Analysis
the
input data it should read.

(2) Next, the "-job" option specifies the type of analysis you want to
perform on that input data.  You are using "-job aggregate_stat" which
makes sense for this data.  The other job types are described in the
MET
User's Guide.

(3) You can specify filtering criteria.  All of the .stat output lines
have
the first 22 header columns in common.  The is a job filtering switch
for
each of those header columns.  For example, "-model" filters the
"MODEL"
header column.  And in your case, "-fcst_lead" filters the "FCST_LEAD"
header column.  Let's look at the FCST_LEAD column in the data you
sent to
me:

   cat point_stat_3769670000L_20130101_230000V_mpr.txt | awk '{print
$4}' |
sort -u
   FCST_LEAD
   3769670000

It is set to a constant value of 3769670000.  Remember, this is
supposed to
be in the format HHMMSS.  So in this case, the hours are 376967,
minutes
are 00, and seconds are 00.   Doing the math, this would be a lead
time of
about 43 years!  And when I run STAT-Analysis using "-fcst_lead
3769670000", it can't parse that timestring either!

ERROR  : timestring_to_sec(const char *) -> can't parse time string
"3769670000"

I strongly suspect that there is a problem in how point_stat is
computing
the FCST_LEAD column.  So we should step back to point_stat to see how
that
value is being created.

To test though, I replaced that value of 3769670000 with 120000:

   cat point_stat_3769670000L_20130101_230000V_mpr.txt | \
   sed 's/3769670000/120000/g' > \
   point_stat_3769670000L_20130101_230000V_PATCH_mpr.txt

And then I reran stat_analysis like this:

/usr/local/met-6.0/bin/stat_analysis \
-lookin point_stat_3769670000L_20130101_230000V_PATCH_mpr.txt \
-job aggregate_stat -line_type MPR -out_line_type CNT \
-by FCST_VAR,OBS_SID \
-out_stat stat_analysis_CNT_by_OBS_SID.txt

And I've attached the resulting output file.  So once we get the
FCST_LEAD
values working correctly, this analysis should work.

One last point, I see that you specified: -by EUR.poly
And I assume that you want to only process the MPR lines that fall
inside
EUR.poly.  The "-by" option is used to specify the name of header
columns
to be used when defining case information.  EUR.poly is not a header
column
name.  Instead, you'd use "-mask_poly EUR.poly".

Please look in the User's Guide for more details on this:
https://dtcenter.org/met/users/docs/overview.php

Thanks,
John

On Mon, Dec 11, 2017 at 8:59 AM, Adrien Michel via RT
<met_help at ucar.edu>
wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
>
> John,
>
> When running STAT-Analysis tool, I got :
>
> [root at b71aa7ce1ca5 met]# stat_analysis -lookin
> met-6.0/data/Stat/point_stat/point_stat -out
> met-6.0/data/Stat/point_stat/test.stat -job aggregate_stat
-line_type
> MPR -out_line_type CNT -by EUR.poly \
> DEBUG 1: Creating STAT-Analysis output file
> "met-6.0/data/Stat/point_stat/test.stat"
> DEBUG 2: Processing 23 STAT files.
> DEBUG 2: STAT Lines read     = 24596
> DEBUG 2: STAT Lines retained = 24228
> DEBUG 2:
> DEBUG 2: Processing Job 1: -job aggregate_stat -line_type MPR -by
> EUR.POLY -out_line_type CNT -out_alpha 0.05000 -boot_interval 1
> -boot_rep_prop 1.00000 -n_boot_rep 1000 -boot_rng mt19937 -boot_seed
''
> -rank_corr_flag 1
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=18446744073364123226
> ERROR  :
> ERROR  : timestring_to_sec(const char *) -> can't parse time string
> "3769600000"
>
> It seems that FCST_LEAD is not recognize by STAT-Analysis Tool.
However
> I tried to specifize it with the following command:
>
>   stat_analysis \
> -lookin met-6.0/data/Stat/point_stat/point_stat \ -out
> met-6.0/data/Stat/point_stat/test.stat \
> -job aggregate_stat -fcst_lead 20130101_020000 -line_type MPR
> -out_line_type CNT -by EUR.poly
> DEBUG 1: Creating STAT-Analysis output file
> "met-6.0/data/Stat/point_stat/test.stat"
> ERROR  :
> ERROR  : timestring_to_sec(const char *) -> can't parse time string
> "20130101_020000"
> ERROR  :
>
> You will find the MPR output file from Point-Stat in attachment.
>
> Hope you could briefly check this issue,
>
> Regards.
>
> Adrien
>
>
> Le 08/12/2017 à 23:00, John Halley Gotway via RT a écrit :
> > Adrien,
> >
> > Yes, it is possible to do that with the STAT-Analysis tool.
However,
> you'd
> > need to be writing the matched pair (MPR) line type from the
Point-Stat
> > tool.   Beware though that that creates pretty large output files.
> >
> > But once you have that MPR output, you can run a STAT-Analysis job
that
> > looks like this:
> >
> > stat_analysis -job aggregate_stat -line_type MPR -out_line_type
CNT -by
> SID
> > -lookin /directory/with/MPR/data
> >
> > This job would do the following steps:
> > (1) Search recursively through the directory named
> > "/directory/with/MPR/data" for .stat output files.
> > (2) Read each .stat file, looking for MPR lines.
> > (3) Group the MPR lines together for each unique value of the SID
(i.e.
> > station id) column from the MPR line.
> > (4) For each unique SID value, use the matched pair data to
compute
> > continuous statistics (CNT) output line type.
> >
> > If you'd further like to subset results for different models and
lead
> > times, all you'd need to add is this:
> >     -by MODEL,FCST_LEAD,SID
> >
> > Hope that helps clarify.
> >
> > Thanks,
> > John
> >
> >
> >
> > On Tue, Dec 5, 2017 at 3:58 AM, Adrien Michel via RT
<met_help at ucar.edu>
> > wrote:
> >
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>
> >> John,
> >>
> >> I would like to thank you for you help, it seems to work better
now!
> >>
> >> Can I compute long-term statistics at individual sites (eg,
> >> mean absolute error or RMS error for daily forecasts for a
> >> month, a year...) with Stat-Analysis module ?
> >>
> >>
> >> Regards,
> >>
> >> Adrien
> >>
> >>
> >> Le 22/11/2017 à 19:19, John Halley Gotway via RT a écrit :
> >>> Adrien,
> >>>
> >>> OK, I pulled your data files and ran them through point_stat in
> met-6.0.
> >>>
> >>> I wrote the attached shell script (using the attached
PointStatConfig2
> >>> file) to loop through the times and run point_stat once for each
output
> >>> time.
> >>>
> >>> I noticed that...
> >>> - You have observations of dew point... so I switched "q_2m" to
"Td_2m"
> >> in
> >>> the config file.
> >>> - Your forecast_reference_time variable is set to a missing
value which
> >>> results in pretty weird forecast lead times.  It should instead
be set
> >> to a
> >>> value of 0.  I corrected that before running point_stat.
> >>>
> >>> I ran my script like this:
> >>> ./run_ps.sh >& run_ps.log
> >>>
> >>> And I attached the output run_ps.log file.  That way you can see
how
> many
> >>> matched pairs I got:
> >>>
> >>> Hope this helps get you going.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>> [johnhg at number5]% grep ", using" run_ps.log
> >>>
> >>> DEBUG 2: Processing T_2m(1,*,*) versus TMP/Z2, for observation
type
> >> ADPSFC,
> >>> over region FULL, for interpolation method NEAREST(1), using 156
pairs.
> >>>
> >>> DEBUG 2: Processing Td_2m(1,*,*) versus DPT/Z2, for observation
type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 156
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing v_10m_gr(1,*,*) versus VGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 143
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing u_10m_gr(1,*,*) versus UGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 143
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing T_2m(2,*,*) versus TMP/Z2, for observation
type
> >> ADPSFC,
> >>> over region FULL, for interpolation method NEAREST(1), using 170
pairs.
> >>>
> >>> DEBUG 2: Processing Td_2m(2,*,*) versus DPT/Z2, for observation
type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 170
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing v_10m_gr(2,*,*) versus VGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 158
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing u_10m_gr(2,*,*) versus UGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 158
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing T_2m(3,*,*) versus TMP/Z2, for observation
type
> >> ADPSFC,
> >>> over region FULL, for interpolation method NEAREST(1), using 307
pairs.
> >>>
> >>> DEBUG 2: Processing Td_2m(3,*,*) versus DPT/Z2, for observation
type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 307
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing v_10m_gr(3,*,*) versus VGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 289
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing u_10m_gr(3,*,*) versus UGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using
> 289
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing T_2m(4,*,*) versus TMP/Z2, for observation
type
> >> ADPSFC,
> >>> over region FULL, for interpolation method NEAREST(1), using 81
pairs.
> >>>
> >>> DEBUG 2: Processing Td_2m(4,*,*) versus DPT/Z2, for observation
type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 81
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing v_10m_gr(4,*,*) versus VGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 73
> >>> pairs.
> >>>
> >>> DEBUG 2: Processing u_10m_gr(4,*,*) versus UGRD/Z10, for
observation
> type
> >>> ADPSFC, over region FULL, for interpolation method NEAREST(1),
using 73
> >>> pairs.
> >>>
> >>>
> >>>
> >>>
> >>> On Wed, Nov 22, 2017 at 1:31 AM, Adrien Michel via RT <
> met_help at ucar.edu
> >>>
> >>> wrote:
> >>>
> >>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>
> >>>> Hi John,
> >>>>
> >>>> No problem. I've repost the data on your ftp site at file name
:
> >>>> amichel_data
> >>>>
> >>>> Regards,
> >>>>
> >>>> Adrien
> >>>>
> >>>>
> >>>> Le 14/11/2017 à 21:08, John Halley Gotway via RT a écrit :
> >>>>> Adrien,
> >>>>>
> >>>>> My apologies for the long delay in responding.  I went to go
grab the
> >>>> data
> >>>>> you posted to our ftp site, but unfortunately, it has already
aged
> off.
> >>>>>
> >>>>> Any chance you could repost the data?
> >>>>>
> >>>>> Sorry about that.
> >>>>>
> >>>>> John
> >>>>>
> >>>>>
> >>>>> On Tue, Nov 14, 2017 at 12:04 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu>
> >>>>> wrote:
> >>>>>
> >>>>>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> Hi Julie,
> >>>>>>
> >>>>>> Did you receive my last email ?
> >>>>>>
> >>>>>> I send this following email to you co-worker John two weeks
ago.
> Could
> >>>>>> you help me with these isssues ?
> >>>>>>
> >>>>>>
> >>>>>> I uploaded my files with file name: amichel_data .You'll find
some
> of
> >> my
> >>>>>> point-observations files, one wrf file and my Point-Stat
> >> configuration.
> >>>>>> At least, I would like to configure MET to verify :
> >>>>>>
> >>>>>> - temperature
> >>>>>>
> >>>>>> - wind
> >>>>>>
> >>>>>> -rainfall
> >>>>>>
> >>>>>> -cloud
> >>>>>>
> >>>>>> - pressure
> >>>>>>
> >>>>>> -...
> >>>>>>
> >>>>>> Actually here are my two issues:
> >>>>>>
> >>>>>> - verify wrf files with many hourly-point observations
> >>>>>>
> >>>>>> - find names of variables (temperature, rainfal,cloud) after
> >>>>>> pre-processing with madis2nc to configure point-stat
> >>>>>>
> >>>>>>
> >>>>>> Thanks,
> >>>>>>
> >>>>>> Adrien
> >>>>>>
> >>>>>> Le 17/10/2017 à 22:03, Julie Prestopnik via RT a écrit :
> >>>>>>> Hi Adrien.
> >>>>>>>
> >>>>>>> With regard to processing multiple observation files for
multiple
> >> years
> >>>>>> in
> >>>>>>> point_stat in a faster/simpler way, I would like to speak to
one of
> >> our
> >>>>>>> main developers to find out more information.  I will get
back to
> you
> >>>> on
> >>>>>>> that.
> >>>>>>>
> >>>>>>> With regard to getting more information about additional
variables,
> >> you
> >>>>>>> mentioned that you cannot read your file after processing
with
> >>>> Madis2nc.
> >>>>>>> You should be able to read your NetCDF data with a utility
called
> >>>>>>> "ncdump".  Here is a link to more information about the
"ncdump"
> >>>> utility:
> >>>>>>> http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_
> >>>>>>> utilities_guide.html#ncdump_guide
> >>>>>>>
> >>>>>>> If you are unable to get and use the "ncdump" utility you
are
> welcome
> >>>> to
> >>>>>>> upload sample NetCDF files to our ftp site and I can dump
the
> >> variable
> >>>>>>> information and pass it back to you.
> >>>>>>>
> >>>>>>> You can upload your file(s) on our anonymous ftp site using
these
> >>>>>>> instructions:
> >>>>>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >>>>>>>
> >>>>>>> I hope that helps.
> >>>>>>>
> >>>>>>> Julie
> >>>>>>>
> >>>>>>> On Tue, Oct 17, 2017 at 9:41 AM, Adrien Michel via RT <
> >>>> met_help at ucar.edu
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>
> >>>>>>>> Hi Julie,
> >>>>>>>>
> >>>>>>>> Well thank you it helps me. So actually my command shell
looks
> like
> >>>>>> that:
> >>>>>>>> point_stat \
> >>>>>>>> met-6.0/data/WRF_cf/wrfpost_d_2013-01-01.nc \
> >>>>>>>> met-6.0/data/Metar_test/TT/20130101_0100.nc \
> >>>>>>>> met-6.0/data/Test/PointStatConfig \
> >>>>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0200.nc \
> >>>>>>>> -point_obs met-6.0/data/Metar_test/T/20130101_0300.nc \
> >>>>>>>> -outdir met-6.0/data/point_stat \
> >>>>>>>> -v 5
> >>>>>>>>
> >>>>>>>> I will use point-stat for 23 point observations files per
day for
> >>>>>>>> multiple years, is there a solution that will allow me to
do it
> >>>>>>>> faster/simply? I tried with "point_obs
> >>>>>>>> met-6.0/data/Metar_test/T/20130101_****.nc" and "point_obs
> >>>>>>>> met-6.0/data/Metar_test/T" but it is not working.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> I have another question about Point-Stat Configuration. For
> >> instance,
> >>>> I
> >>>>>>>> have used variables gives in the user_guide examples as
bellow:
> >>>>>>>>
> >>>>>>>>       field = [
> >>>>>>>>            {
> >>>>>>>>              name       = "TMP";
> >>>>>>>>              level      = [ "Z2" ];
> >>>>>>>>              cat_thresh = [ <=273.0 ];
> >>>>>>>>          },
> >>>>>>>>            {
> >>>>>>>>          name       = "UGRD";
> >>>>>>>>              level      = [ "Z10" ];
> >>>>>>>>              cat_thresh = [ >=5.0 ];
> >>>>>>>>          },
> >>>>>>>>            {
> >>>>>>>>          name       = "VGRD";
> >>>>>>>>              level      = [ "Z10" ];
> >>>>>>>>              cat_thresh = [ >=5.0 ];
> >>>>>>>>          }
> >>>>>>>>         ];
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> It is actually working, but I would like to evaluate
additional
> >>>>>>>> variables. Where I can find informations about the name of
> >> variables ?
> >>>>>>>> Indeed, I can not read my file after pre-processing with
Madis2nc.
> >>>>>>>>
> >>>>>>>> Many thanks,
> >>>>>>>>
> >>>>>>>> Regards.
> >>>>>>>>
> >>>>>>>> Adrien
> >>>>>>>>
> >>>>>>>> Le 16/10/2017 à 17:02, Julie Prestopnik via RT a écrit :
> >>>>>>>>> Hi Adrien.
> >>>>>>>>>
> >>>>>>>>> When you run "point_stat" you can see the usage statement
(see
> >>>> below).
> >>>>>>>> You
> >>>>>>>>> can use the "-point_obs" option to specify additional
point
> >>>> observation
> >>>>>>>>> files:
> >>>>>>>>>
> >>>>>>>>>        "-point_obs file" specifies additional NetCDF point
> >> observation
> >>>>>> files
> >>>>>>>> to
> >>>>>>>>> be used (optional).
> >>>>>>>>>
> >>>>>>>>> You can use this option multiple times.  So, if you have
multiple
> >>>>>>>>> additional observation files you can add "-point_obs
<obs_file_a>
> >>>>>>>>> -point_obs <obs_file_b> -point_obs <obs_file_c>" to your
call to
> >>>>>>>> point_stat.
> >>>>>>>>> I hope that helps.  Please let us know if you have any
other
> >>>> questions.
> >>>>>>>>> Julie
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> *** Model Evaluation Tools (METV6.0) ***
> >>>>>>>>>
> >>>>>>>>> Usage: point_stat
> >>>>>>>>>              fcst_file
> >>>>>>>>>              obs_file
> >>>>>>>>>              config_file
> >>>>>>>>>              [-point_obs file]
> >>>>>>>>>              [-obs_valid_beg time]
> >>>>>>>>>              [-obs_valid_end time]
> >>>>>>>>>              [-outdir path]
> >>>>>>>>>              [-log file]
> >>>>>>>>>              [-v level]
> >>>>>>>>>
> >>>>>>>>>              where   "fcst_file" is a gridded forecast
file
> >> containing
> >>>> the
> >>>>>>>>> field(s) to be verified (required).
> >>>>>>>>>                      "obs_file" is an observation file in
NetCDF
> >> format
> >>>>>>>>> containing the verifying point observations (required).
> >>>>>>>>>                      "config_file" is a PointStatConfig
file
> >> containing
> >>>>>> the
> >>>>>>>>> desired configuration settings (required).
> >>>>>>>>>                      "-point_obs file" specifies
additional
> NetCDF
> >>>> point
> >>>>>>>>> observation files to be used (optional).
> >>>>>>>>>                      "-obs_valid_beg time" in
YYYYMMDD[_HH[MMSS]]
> >> sets
> >>>> the
> >>>>>>>>> beginning of the matching time window (optional).
> >>>>>>>>>                      "-obs_valid_end time" in
YYYYMMDD[_HH[MMSS]]
> >> sets
> >>>> the
> >>>>>>>> end
> >>>>>>>>> of the matching time window (optional).
> >>>>>>>>>                      "-outdir path" overrides the default
output
> >>>> directory
> >>>>>>>> (.)
> >>>>>>>>> (optional).
> >>>>>>>>>                      "-log file" outputs log messages to
the
> >> specified
> >>>>>> file
> >>>>>>>>> (optional).
> >>>>>>>>>                      "-v level" overrides the default
level of
> >> logging
> >>>> (2)
> >>>>>>>>> (optional).
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> On Mon, Oct 16, 2017 at 8:41 AM, Adrien Michel via RT <
> >>>>>> met_help at ucar.edu
> >>>>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768 >
> >>>>>>>>>>
> >>>>>>>>>> Hello Julie,
> >>>>>>>>>>
> >>>>>>>>>> How can I pass multiple netcdf point observation files to
> >> point-stat
> >>>>>> ? I
> >>>>>>>>>> didn't see any informations on the user_guide about it.
> >>>>>>>>>>
> >>>>>>>>>> Thank you,
> >>>>>>>>>>
> >>>>>>>>>> Adrien
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> Le 13/10/2017 à 17:20, Julie Prestopnik via RT a écrit :
> >>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>
> >>>>>>>>>>> There’s no “need” to merge the files.   You can pass
multiple
> >>>> netcdf
> >>>>>>>>>> point
> >>>>>>>>>>> observation files to point_stat and ensemble_stat.
However, if
> >> you
> >>>>>>>> would
> >>>>>>>>>>> like to merge the files, you could consider using the
"ncrcat"
> >>>> tool:
> >>>>>>>>>>> https://linux.die.net/man/1/ncrcat
> >>>>>>>>>>>
> >>>>>>>>>>> from NCO:
> >>>>>>>>>>> http://nco.sourceforge.net/
> >>>>>>>>>>>
> >>>>>>>>>>> I hope that helps!
> >>>>>>>>>>>
> >>>>>>>>>>> Julie
> >>>>>>>>>>>
> >>>>>>>>>>> On Fri, Oct 13, 2017 at 1:17 AM, Adrien Michel via RT <
> >>>>>>>> met_help at ucar.edu
> >>>>>>>>>>> wrote:
> >>>>>>>>>>>
> >>>>>>>>>>>> <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81768
> >
> >>>>>>>>>>>>
> >>>>>>>>>>>> Hello Julie,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I am running Madis2nc tool for hourly basis metar data.
> >> Actually I
> >>>>>>>> would
> >>>>>>>>>>>> like to merge these hourly data in daily file. Do you
have
> >>>>>> suggestion
> >>>>>>>> or
> >>>>>>>>>>>> recommendation on how to do it ? Is there option for
that in
> >> MET ?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Regards,
> >>>>>>>>>>>>
> >>>>>>>>>>>> Adrien
> >>>>>>>>>>>>
> >>>>>>>>>>>>
> >>>>>>>>>>>> Le 15/09/2017 à 18:20, Julie Prestopnik via RT a écrit
:
> >>>>>>>>>>>>> I'm glad to hear it, Adrien!  Thank you for letting us
know.
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>
> >>>>>>>>>>>>> On Fri, Sep 15, 2017 at 8:42 AM, Adrien Michel via RT
<
> >>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>
> >>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81768
> >>>>>>>>>>>>>> Hi Julie,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Thanks to the previous met_help ticket, now that
worked
> >>>> perfectly
> >>>>>> !
> >>>>>>>> I
> >>>>>>>>>> am
> >>>>>>>>>>>>>> so grateful for your help, thank you. Now I will
adapt this
> >>>> method
> >>>>>>>> for
> >>>>>>>>>>>>>> all my data.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Another time, thank you. I'll definitely let you know
if I
> >> have
> >>>>>>>> others
> >>>>>>>>>>>>>> questions.
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Best regards,
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Adrien
> >>>>>>>>>>>>>>
> >>>>>>>>>>>>>> Le 13/09/2017 à 22:03, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I'm glad MET was able to read your CF compliant
file.
> Thank
> >>>> you
> >>>>>>>> for
> >>>>>>>>>>>>>>> uploading your data.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> When I run point_stat with your data and
configuration
> file,
> >> I
> >>>>>> see
> >>>>>>>>>> the
> >>>>>>>>>>>>>>> following warning:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> DEBUG 2: Reading data for T_sfc(0,*,*).
> >>>>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>>>> WARNING: MetNcCFDataFile::data_plane() -> for
"T_sfc"
> >> variable,
> >>>>>> the
> >>>>>>>>>>>> lead
> >>>>>>>>>>>>>>> time does not match the requested lead time: (000000
!=
> >> 020000)
> >>>>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>>>> WARNING: process_fcst_climo_files() -> no fields
matching
> >>>>>>>>>> T_sfc(0,*,*)
> >>>>>>>>>>>>>>> found in file: wrfpot_cf_2013-01-01.nc
> >>>>>>>>>>>>>>> WARNING:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> There is a specific way in the CF-convention of
specifying
> >> the
> >>>>>>>>>>>>>>> initialization time of the model.  You do so by
defining a
> >>>>>> variable
> >>>>>>>>>>>> named
> >>>>>>>>>>>>>>> "forecast_reference_time".  When that variable is
not
> >> present,
> >>>>>> MET
> >>>>>>>>>> sets
> >>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>> forecast initialization time to the same value as
the valid
> >>>> time,
> >>>>>>>>>> which
> >>>>>>>>>>>>>>> results in a lead time of 0.
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> You need to add the "forecast_reference_time"
variable to
> >> your
> >>>>>>>> model
> >>>>>>>>>>>>>>> files.  Take a look at this previous met_help ticket
and
> see
> >> if
> >>>>>>>> that
> >>>>>>>>>>>>>> helps:
> >>>>>>>>>>>>>>> http://mailman.ucar.edu/pipermail/met_help/2017-May/
> >>>> 002867.html
> >>>>>>>>>>>>>>> Also, I see in your PointStatConfig file that you
have
> >> defined
> >>>>>>>>>>>>>> "lead_time"
> >>>>>>>>>>>>>>> in the fcst dictionary.  That is not necessary and
could
> >> cause
> >>>>>>>>>>>> problems.
> >>>>>>>>>>>>>>> MET determines the lead time by the time index of
the time
> >>>>>>>> dimension
> >>>>>>>>>>>> that
> >>>>>>>>>>>>>>> you specify in the "level" field:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>                 level      = "(0,*,*)";
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> I hope that helps.  Please let us know if you have
any
> other
> >>>>>>>>>> questions.
> >>>>>>>>>>>>>>> Thanks,
> >>>>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> On Wed, Sep 13, 2017 at 9:57 AM, Adrien Michel via
RT <
> >>>>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> >> Ticket/Display.html?id=81768
> >>>>>>>>>>>>>>>> Hi Julie,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Many thank, I have done as you suggested and MET
seems to
> >> read
> >>>>>> my
> >>>>>>>> CF
> >>>>>>>>>>>>>>>> Compliant. However, I still have issues with the
> >> configuration
> >>>>>> of
> >>>>>>>>>>>>>>>> Point-Stat.
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> So I  uploaded my file (name file: michel_data)
> >>>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance) -
daily file
> >> for
> >>>>>>>>>>>> 2013-01-01
> >>>>>>>>>>>>>>>> I would also provide you :
> >>>>>>>>>>>>>>>> - point observation file from Madis2nc - hourly
file for
> >>>>>>>>>>>>>>>> 2013-01-01_02:00:00
> >>>>>>>>>>>>>>>> - Point-Stat configuration
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> I'm grateful for you help.
> >>>>>>>>>>>>>>>> Regards,
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Adrien Michel
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>> Le 12/09/2017 à 19:09, Julie Prestopnik via RT a
écrit :
> >>>>>>>>>>>>>>>>> Hi Adrien.
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> It is difficult to tell the problem with the file
without
> >>>>>> seeing
> >>>>>>>>>> it.
> >>>>>>>>>>>>>>>>> However, I have something for you to try that
might work.
> >>>> MET
> >>>>>>>>>> should
> >>>>>>>>>>>>>> be
> >>>>>>>>>>>>>>>>> able to read CF compliant files, and you have
stated that
> >>>> your
> >>>>>>>>>> NetCDF
> >>>>>>>>>>>>>>>> file
> >>>>>>>>>>>>>>>>> is CF Compliant.  MET tries to figure out the type
of
> file,
> >>>> but
> >>>>>>>>>> since
> >>>>>>>>>>>>>> it
> >>>>>>>>>>>>>>>> is
> >>>>>>>>>>>>>>>>> having trouble, let's try explicitly telling the
tools
> how
> >> to
> >>>>>>>>>> process
> >>>>>>>>>>>>>> the
> >>>>>>>>>>>>>>>>> data by setting the following in your PointStat
config
> >> file:
> >>>>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> This entry should be defined within the "fcst"
> dictionary.
> >>>> For
> >>>>>>>>>>>>>> example:
> >>>>>>>>>>>>>>>>> fcst = {
> >>>>>>>>>>>>>>>>> file_type = NETCDF_NCCF;
> >>>>>>>>>>>>>>>>> ...
> >>>>>>>>>>>>>>>>> }
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> If that works, please let us know.  If that does
not
> work,
> >>>>>> please
> >>>>>>>>>>>>>> upload
> >>>>>>>>>>>>>>>>> your file to our ftp server using the following
> >> instructions
> >>>>>> and
> >>>>>>>>>> let
> >>>>>>>>>>>> us
> >>>>>>>>>>>>>>>>> know once you have done that so that we can get
the file
> >> and
> >>>>>>>> take a
> >>>>>>>>>>>>>> look.
> >>>>>>>>>>>>>>>>> http://www.dtcenter.org/met/
> users/support/met_help.php#ftp
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Thanks!
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> Julie
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>> On Tue, Sep 12, 2017 at 7:01 AM, Adrien Michel via
RT <
> >>>>>>>>>>>>>> met_help at ucar.edu
> >>>>>>>>>>>>>>>>> wrote:
> >>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> <URL: https://rt.rap.ucar.edu/rt/
> >>>> Ticket/Display.html?id=81768
> >>>>>>>>>>>>>>>>>> Hi Julie.
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>>            I've done as you suggested and it ran
without
> >>>> problem,
> >>>>>>>> thank
> >>>>>>>>>>>> you!
> >>>>>>>>>>>>>>>>>> I come up with a another issue.. I'm trying to
use
> >>>> Point-Stat
> >>>>>> :
> >>>>>>>>>>>>>>>>>> - a forecast file (WRF file - CF compliance)
> >>>>>>>>>>>>>>>>>> - a point observation file coming from Madis2nc
> >>>>>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>>>> However, Point Stat seems to have issue to read
my
> >> forecast
> >>>>>> file
> >>>>>>>>>>>> with
> >>>>>>>>>>>>>>>>>> the following informations:
> >>>>>>>>>>>>>>>>>>> point_stat met-6.0/data/WRF_cf/wrfpost_output.nc
> >>>>>>>>>>>>>>>>>>> met-6.0/data/Madis2nc_test/20130101_0200.nc
> >>>>>>>>>>>>>>>>>>> met-6.0/data/Test/PointStatConfig -outdir
> >>>>>>>>>>>>>>>>>>> /met-6.0/data/Point_Stat_Test -v 5
> >>>>>>>>>>>>>>>>>>> DEBUG 1: Default Config File:
> >>>>>>>>>>>>>>>>>>>
/usr/local/share/met/config/PointStatConfig_default
> >>>>>>>>>>>>>>>>>>> DEBUG 1: User Config File: met-6.0/data/Test/
> >>>> PointStatConfig
> >>>>>>>>>>>>>>>>>>> DEBUG 4:
Met2dDataFileFactory::new_met_2d_data_file()
> ->
> >>>>>>>> created
> >>>>>>>>>>>> new
> >>>>>>>>>>>>>>>>>>> Met2dDataFile object of type "FileType_None".
> >>>>>>>>>>>>>