[Met_help] [rt.rap.ucar.edu #81768] History for Met_v6 - Issues using Point Stat
Julie Prestopnik via RT
met_help at ucar.edu
Mon Sep 18 08:40:52 MDT 2017
----------------------------------------------------------------
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
>
>
------------------------------------------------
More information about the Met_help
mailing list