[Met_help] [rt.rap.ucar.edu #71239] History for ascii2nc issue
John Halley Gotway via RT
met_help at ucar.edu
Mon Apr 13 14:09:09 MDT 2015
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I am trying to process data with ascii2nc and am running to the following problem.
The original input contains measurements with station codes that are alphanumeric e.g. A3138. I thought I can make ascii2nc work if I convert
letters to numbers (e.g. A-> 9) but that does not work. I don’t want to eliminate the measurements for alphanumeric stations.
The MET version I have has been patched and if possible would like avoid upgrading.
Can you help?
Thanks,
Mariusz
Model Evaluation Tools METv4.0 (June 25, 2012)
DEBUG 1: Creating NetCDF Observation file: wgn_sfc.nc
DEBUG 1: Reading ASCII Observation file: wgn_sfc.txt
DEBUG 2: Processing 4093 observations.
ERROR :
ERROR : timestring_to_sec(const char *) -> can't parse time string "963.9"
ERROR :
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: ascii2nc issue
From: Julie Prestopnik
Time: Fri Mar 27 09:58:54 2015
Hi Mariusz.
Based on the error you're getting:
timestring_to_sec(const char *) -> can't parse time string "963.9"
It looks like MET is having a hard time reading the value 963.9 which
is in
the eighth column of your file.
Column 8 of the input ascii data should contain the "level"
information,
described in the ascii2nc usage statement as:
"Level" is the pressure level (hPa) or accumulation interval
(HH[MMSS])
For precipitation variables, like APCP in GRIB code 61, it's expecting
to
see a timestring in HH[MMSS] format to indicate the accumulation
interval.
If the data values are accumulated precipitation, just indicate the
time
over which it is accumulated in HH or HHMMSS format.
Please let us know if you have any questions.
Thanks,
Julie
On Thu, Mar 26, 2015 at 1:26 PM, Mariusz Pagowski via RT
<met_help at ucar.edu>
wrote:
>
> Thu Mar 26 13:26:38 2015: Request 71239 was acted upon.
> Transaction: Ticket created by Mariusz.Pagowski at noaa.gov
> Queue: met_help
> Subject: ascii2nc issue
> Owner: Nobody
> Requestors: Mariusz.Pagowski at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
>
>
> Hello,
> I am trying to process data with ascii2nc and am running to the
following
> problem.
> The original input contains measurements with station codes that are
> alphanumeric e.g. A3138. I thought I can make ascii2nc work if I
convert
> letters to numbers (e.g. A-> 9) but that does not work. I don’t want
to
> eliminate the measurements for alphanumeric stations.
> The MET version I have has been patched and if possible would like
avoid
> upgrading.
> Can you help?
> Thanks,
> Mariusz
>
> Model Evaluation Tools METv4.0 (June 25, 2012)
>
> DEBUG 1: Creating NetCDF Observation file: wgn_sfc.nc
> DEBUG 1: Reading ASCII Observation file: wgn_sfc.txt
> DEBUG 2: Processing 4093 observations.
> ERROR :
> ERROR : timestring_to_sec(const char *) -> can't parse time string
"963.9"
> ERROR :
>
>
>
>
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #71239] ascii2nc issue
From: Mariusz Pagowski
Time: Fri Mar 27 10:21:40 2015
Thanks Julie,
Could you clarify what the line should look like for e.g. 10 mm precip
accumulated after 6 hours for time of measurement 20150327_000000 ?
I am little unclear about the units and conversion factor.
Mariusz
> On Mar 27, 2015, at 9:58 AM, Julie Prestopnik via RT
<met_help at ucar.edu> wrote:
>
> Hi Mariusz.
>
> Based on the error you're getting:
>
> timestring_to_sec(const char *) -> can't parse time string "963.9"
>
> It looks like MET is having a hard time reading the value 963.9
which is in
> the eighth column of your file.
>
> Column 8 of the input ascii data should contain the "level"
information,
> described in the ascii2nc usage statement as:
> "Level" is the pressure level (hPa) or accumulation interval
(HH[MMSS])
>
> For precipitation variables, like APCP in GRIB code 61, it's
expecting to
> see a timestring in HH[MMSS] format to indicate the accumulation
interval.
> If the data values are accumulated precipitation, just indicate the
time
> over which it is accumulated in HH or HHMMSS format.
>
> Please let us know if you have any questions.
>
> Thanks,
> Julie
>
> On Thu, Mar 26, 2015 at 1:26 PM, Mariusz Pagowski via RT
<met_help at ucar.edu>
> wrote:
>
>>
>> Thu Mar 26 13:26:38 2015: Request 71239 was acted upon.
>> Transaction: Ticket created by Mariusz.Pagowski at noaa.gov
>> Queue: met_help
>> Subject: ascii2nc issue
>> Owner: Nobody
>> Requestors: Mariusz.Pagowski at noaa.gov
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
>>
>>
>> Hello,
>> I am trying to process data with ascii2nc and am running to the
following
>> problem.
>> The original input contains measurements with station codes that
are
>> alphanumeric e.g. A3138. I thought I can make ascii2nc work if I
convert
>> letters to numbers (e.g. A-> 9) but that does not work. I don’t
want to
>> eliminate the measurements for alphanumeric stations.
>> The MET version I have has been patched and if possible would like
avoid
>> upgrading.
>> Can you help?
>> Thanks,
>> Mariusz
>>
>> Model Evaluation Tools METv4.0 (June 25, 2012)
>>
>> DEBUG 1: Creating NetCDF Observation file: wgn_sfc.nc
>> DEBUG 1: Reading ASCII Observation file: wgn_sfc.txt
>> DEBUG 2: Processing 4093 observations.
>> ERROR :
>> ERROR : timestring_to_sec(const char *) -> can't parse time string
"963.9"
>> ERROR :
>>
>>
>>
>>
>>
>>
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
------------------------------------------------
Subject: ascii2nc issue
From: Julie Prestopnik
Time: Fri Mar 27 10:32:58 2015
Here is what the 11 columns would like:
ADPSFC 80001 20150327_000000 12.58 -81.72 1.0 61 6 -9999 -9999 10
In the example above, I set height and qc string to the missing value
of
-9999. The units of the observation value depend on the grib code.
In
this case they are millimeters.
I hope this helps clarify. Please let us know if you have any
questions.
Thanks,
Julie
On Fri, Mar 27, 2015 at 10:21 AM, Mariusz Pagowski via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
>
> Thanks Julie,
> Could you clarify what the line should look like for e.g. 10 mm
precip
> accumulated after 6 hours for time of measurement 20150327_000000 ?
> I am little unclear about the units and conversion factor.
> Mariusz
>
> > On Mar 27, 2015, at 9:58 AM, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
> >
> > Hi Mariusz.
> >
> > Based on the error you're getting:
> >
> > timestring_to_sec(const char *) -> can't parse time string "963.9"
> >
> > It looks like MET is having a hard time reading the value 963.9
which is
> in
> > the eighth column of your file.
> >
> > Column 8 of the input ascii data should contain the "level"
information,
> > described in the ascii2nc usage statement as:
> > "Level" is the pressure level (hPa) or accumulation interval
(HH[MMSS])
> >
> > For precipitation variables, like APCP in GRIB code 61, it's
expecting to
> > see a timestring in HH[MMSS] format to indicate the accumulation
> interval.
> > If the data values are accumulated precipitation, just indicate
the time
> > over which it is accumulated in HH or HHMMSS format.
> >
> > Please let us know if you have any questions.
> >
> > Thanks,
> > Julie
> >
> > On Thu, Mar 26, 2015 at 1:26 PM, Mariusz Pagowski via RT <
> met_help at ucar.edu>
> > wrote:
> >
> >>
> >> Thu Mar 26 13:26:38 2015: Request 71239 was acted upon.
> >> Transaction: Ticket created by Mariusz.Pagowski at noaa.gov
> >> Queue: met_help
> >> Subject: ascii2nc issue
> >> Owner: Nobody
> >> Requestors: Mariusz.Pagowski at noaa.gov
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
> >>
> >>
> >> Hello,
> >> I am trying to process data with ascii2nc and am running to the
> following
> >> problem.
> >> The original input contains measurements with station codes that
are
> >> alphanumeric e.g. A3138. I thought I can make ascii2nc work if I
convert
> >> letters to numbers (e.g. A-> 9) but that does not work. I don’t
want to
> >> eliminate the measurements for alphanumeric stations.
> >> The MET version I have has been patched and if possible would
like avoid
> >> upgrading.
> >> Can you help?
> >> Thanks,
> >> Mariusz
> >>
> >> Model Evaluation Tools METv4.0 (June 25, 2012)
> >>
> >> DEBUG 1: Creating NetCDF Observation file: wgn_sfc.nc
> >> DEBUG 1: Reading ASCII Observation file: wgn_sfc.txt
> >> DEBUG 2: Processing 4093 observations.
> >> ERROR :
> >> ERROR : timestring_to_sec(const char *) -> can't parse time
string
> "963.9"
> >> ERROR :
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
>
>
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #71239] ascii2nc issue
From: Mariusz Pagowski
Time: Fri Mar 27 11:09:08 2015
Your kindness is paying off for me but maybe not for you: I have a
follow-up question.
there is no elevation and/or pressure data for a sfc station. If I
enter -9999. in these places can e.g. temperature still be included
in the verification using point_stat, and how would results differ if
elevation/pressure were known for this station.
Thanks,
Mariusz
> On Mar 27, 2015, at 10:32 AM, Julie Prestopnik via RT
<met_help at ucar.edu> wrote:
>
> Here is what the 11 columns would like:
> ADPSFC 80001 20150327_000000 12.58 -81.72 1.0 61 6 -9999 -9999 10
>
> In the example above, I set height and qc string to the missing
value of
> -9999. The units of the observation value depend on the grib code.
In
> this case they are millimeters.
>
> I hope this helps clarify. Please let us know if you have any
questions.
>
> Thanks,
> Julie
>
> On Fri, Mar 27, 2015 at 10:21 AM, Mariusz Pagowski via RT
<met_help at ucar.edu
>> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
>>
>> Thanks Julie,
>> Could you clarify what the line should look like for e.g. 10 mm
precip
>> accumulated after 6 hours for time of measurement 20150327_000000 ?
>> I am little unclear about the units and conversion factor.
>> Mariusz
>>
>>> On Mar 27, 2015, at 9:58 AM, Julie Prestopnik via RT
<met_help at ucar.edu>
>> wrote:
>>>
>>> Hi Mariusz.
>>>
>>> Based on the error you're getting:
>>>
>>> timestring_to_sec(const char *) -> can't parse time string "963.9"
>>>
>>> It looks like MET is having a hard time reading the value 963.9
which is
>> in
>>> the eighth column of your file.
>>>
>>> Column 8 of the input ascii data should contain the "level"
information,
>>> described in the ascii2nc usage statement as:
>>> "Level" is the pressure level (hPa) or accumulation interval
(HH[MMSS])
>>>
>>> For precipitation variables, like APCP in GRIB code 61, it's
expecting to
>>> see a timestring in HH[MMSS] format to indicate the accumulation
>> interval.
>>> If the data values are accumulated precipitation, just indicate
the time
>>> over which it is accumulated in HH or HHMMSS format.
>>>
>>> Please let us know if you have any questions.
>>>
>>> Thanks,
>>> Julie
>>>
>>> On Thu, Mar 26, 2015 at 1:26 PM, Mariusz Pagowski via RT <
>> met_help at ucar.edu>
>>> wrote:
>>>
>>>>
>>>> Thu Mar 26 13:26:38 2015: Request 71239 was acted upon.
>>>> Transaction: Ticket created by Mariusz.Pagowski at noaa.gov
>>>> Queue: met_help
>>>> Subject: ascii2nc issue
>>>> Owner: Nobody
>>>> Requestors: Mariusz.Pagowski at noaa.gov
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
>>>>
>>>>
>>>> Hello,
>>>> I am trying to process data with ascii2nc and am running to the
>> following
>>>> problem.
>>>> The original input contains measurements with station codes that
are
>>>> alphanumeric e.g. A3138. I thought I can make ascii2nc work if I
convert
>>>> letters to numbers (e.g. A-> 9) but that does not work. I don’t
want to
>>>> eliminate the measurements for alphanumeric stations.
>>>> The MET version I have has been patched and if possible would
like avoid
>>>> upgrading.
>>>> Can you help?
>>>> Thanks,
>>>> Mariusz
>>>>
>>>> Model Evaluation Tools METv4.0 (June 25, 2012)
>>>>
>>>> DEBUG 1: Creating NetCDF Observation file: wgn_sfc.nc
>>>> DEBUG 1: Reading ASCII Observation file: wgn_sfc.txt
>>>> DEBUG 2: Processing 4093 observations.
>>>> ERROR :
>>>> ERROR : timestring_to_sec(const char *) -> can't parse time
string
>> "963.9"
>>>> ERROR :
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Julie Prestopnik
>>> National Center for Atmospheric Research
>>> Research Applications Laboratory
>>> Phone: 303.497.8399
>>> Email: jpresto at ucar.edu
>>>
>>
>>
>>
>>
>
>
> --
> Julie Prestopnik
> National Center for Atmospheric Research
> Research Applications Laboratory
> Phone: 303.497.8399
> Email: jpresto at ucar.edu
>
------------------------------------------------
Subject: ascii2nc issue
From: Julie Prestopnik
Time: Fri Mar 27 12:30:47 2015
Mariusz,
We're happy to answer any questions you have. If it is really surface
observation, as opposed to a sounding, the elevation/pressure doesn't
matter. In point_stat, the surface observations are treated as a
special
message type that causes point observations to be used for
verification at
the surface regardless of elevation and/or pressure levels. So, yes,
temperature can be included in the verification using point_stat, and
the
results would no differ if elevation/pressure were known (for land
based
and water based surface observations).
I hope this helps.
Julie
On Fri, Mar 27, 2015 at 11:09 AM, Mariusz Pagowski via RT
<met_help at ucar.edu
> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
>
> Your kindness is paying off for me but maybe not for you: I have a
> follow-up question.
> there is no elevation and/or pressure data for a sfc station. If I
enter
> -9999. in these places can e.g. temperature still be included
> in the verification using point_stat, and how would results differ
if
> elevation/pressure were known for this station.
> Thanks,
> Mariusz
>
> > On Mar 27, 2015, at 10:32 AM, Julie Prestopnik via RT
<met_help at ucar.edu>
> wrote:
> >
> > Here is what the 11 columns would like:
> > ADPSFC 80001 20150327_000000 12.58 -81.72 1.0 61 6 -9999 -9999 10
> >
> > In the example above, I set height and qc string to the missing
value of
> > -9999. The units of the observation value depend on the grib
code. In
> > this case they are millimeters.
> >
> > I hope this helps clarify. Please let us know if you have any
questions.
> >
> > Thanks,
> > Julie
> >
> > On Fri, Mar 27, 2015 at 10:21 AM, Mariusz Pagowski via RT <
> met_help at ucar.edu
> >> wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239 >
> >>
> >> Thanks Julie,
> >> Could you clarify what the line should look like for e.g. 10 mm
precip
> >> accumulated after 6 hours for time of measurement 20150327_000000
?
> >> I am little unclear about the units and conversion factor.
> >> Mariusz
> >>
> >>> On Mar 27, 2015, at 9:58 AM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> >> wrote:
> >>>
> >>> Hi Mariusz.
> >>>
> >>> Based on the error you're getting:
> >>>
> >>> timestring_to_sec(const char *) -> can't parse time string
"963.9"
> >>>
> >>> It looks like MET is having a hard time reading the value 963.9
which
> is
> >> in
> >>> the eighth column of your file.
> >>>
> >>> Column 8 of the input ascii data should contain the "level"
> information,
> >>> described in the ascii2nc usage statement as:
> >>> "Level" is the pressure level (hPa) or accumulation interval
(HH[MMSS])
> >>>
> >>> For precipitation variables, like APCP in GRIB code 61, it's
expecting
> to
> >>> see a timestring in HH[MMSS] format to indicate the accumulation
> >> interval.
> >>> If the data values are accumulated precipitation, just indicate
the
> time
> >>> over which it is accumulated in HH or HHMMSS format.
> >>>
> >>> Please let us know if you have any questions.
> >>>
> >>> Thanks,
> >>> Julie
> >>>
> >>> On Thu, Mar 26, 2015 at 1:26 PM, Mariusz Pagowski via RT <
> >> met_help at ucar.edu>
> >>> wrote:
> >>>
> >>>>
> >>>> Thu Mar 26 13:26:38 2015: Request 71239 was acted upon.
> >>>> Transaction: Ticket created by Mariusz.Pagowski at noaa.gov
> >>>> Queue: met_help
> >>>> Subject: ascii2nc issue
> >>>> Owner: Nobody
> >>>> Requestors: Mariusz.Pagowski at noaa.gov
> >>>> Status: new
> >>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=71239
> >
> >>>>
> >>>>
> >>>> Hello,
> >>>> I am trying to process data with ascii2nc and am running to the
> >> following
> >>>> problem.
> >>>> The original input contains measurements with station codes
that are
> >>>> alphanumeric e.g. A3138. I thought I can make ascii2nc work if
I
> convert
> >>>> letters to numbers (e.g. A-> 9) but that does not work. I don’t
want
> to
> >>>> eliminate the measurements for alphanumeric stations.
> >>>> The MET version I have has been patched and if possible would
like
> avoid
> >>>> upgrading.
> >>>> Can you help?
> >>>> Thanks,
> >>>> Mariusz
> >>>>
> >>>> Model Evaluation Tools METv4.0 (June 25, 2012)
> >>>>
> >>>> DEBUG 1: Creating NetCDF Observation file: wgn_sfc.nc
> >>>> DEBUG 1: Reading ASCII Observation file: wgn_sfc.txt
> >>>> DEBUG 2: Processing 4093 observations.
> >>>> ERROR :
> >>>> ERROR : timestring_to_sec(const char *) -> can't parse time
string
> >> "963.9"
> >>>> ERROR :
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Julie Prestopnik
> >>> National Center for Atmospheric Research
> >>> Research Applications Laboratory
> >>> Phone: 303.497.8399
> >>> Email: jpresto at ucar.edu
> >>>
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Julie Prestopnik
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > Phone: 303.497.8399
> > Email: jpresto at ucar.edu
> >
>
>
>
>
--
Julie Prestopnik
National Center for Atmospheric Research
Research Applications Laboratory
Phone: 303.497.8399
Email: jpresto at ucar.edu
------------------------------------------------
More information about the Met_help
mailing list