[Met_help] [rt.rap.ucar.edu #46965] History for Problem with Point-Stat (UNCLASSIFIED)
RAL HelpDesk {for John Halley Gotway}
met_help at ucar.edu
Mon May 23 11:41:08 MDT 2011
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Classification: UNCLASSIFIED
Caveats: NONE
I have run into a problem while trying to run Point-Stat on NAM data
received from the CISL archive data site.
I am running METV3.0 and am trying to use the optional argument -fcst_lead
because the NAM file contains all forecast lead times in one large file.
When I run Point-Stat, it has the following error:
timestring_to_sec(const char *) -> can't parse time string "20090326_000000"
I've attached the script I use to run Point-Stat, the log file which show
the error, and a sample of the 2GB NAM file.
I can't figure out what is needed to resolve this and wondered if you could
help me out.
Thanks.
R/
John
Mr John W. Raby, Meteorologist
U.S. Army Research Laboratory
White Sands Missile Range, NM 88002
(575) 678-2004 DSN 258-2004
FAX (575) 678-1230 DSN 258-1230
Email: john.raby at us.army.mil
Classification: UNCLASSIFIED
Caveats: NONE
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #46965] Problem with Point-Stat (UNCLASSIFIED)
From: John Halley Gotway
Time: Fri May 20 21:58:09 2011
John,
If you look closely at the usage statement for Point-Stat, I think
you'll
discover the problem. You're using the "-fcst_lead" command line
argument
when I'm guessing you intend to be using the "-fcst_valid" command
line
argument. The former is used to specify a particular lead time in
HHMMSS
format while the latter is used to specify the valid time in
YYYYMMDD_HHMMSS. I'm guessing that's really what you're trying to do.
Hope that helps.
John Halley Gotway
met_help at ucar.edu
>
> Fri May 20 07:09:09 2011: Request 46965 was acted upon.
> Transaction: Ticket created by john.raby at us.army.mil
> Queue: met_help
> Subject: Problem with Point-Stat (UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.raby at us.army.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=46965 >
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I have run into a problem while trying to run Point-Stat on NAM data
> received from the CISL archive data site.
>
> I am running METV3.0 and am trying to use the optional argument
-fcst_lead
> because the NAM file contains all forecast lead times in one large
file.
>
> When I run Point-Stat, it has the following error:
>
> timestring_to_sec(const char *) -> can't parse time string
> "20090326_000000"
>
> I've attached the script I use to run Point-Stat, the log file which
show
> the error, and a sample of the 2GB NAM file.
>
> I can't figure out what is needed to resolve this and wondered if
you
> could
> help me out.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.raby at us.army.mil
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
>
------------------------------------------------
Subject: Problem with Point-Stat (UNCLASSIFIED)
From: Raby, John
Time: Mon May 23 11:33:39 2011
Classification: UNCLASSIFIED
Caveats: NONE
John -
Based on your response, I ran another test but decided to keep the
-fcst_lead and correct the problem where it was apparently rejecting
the YYYYMMDD (my Start_Date variable). I omitted the YYYYMMDD and just
specified the HH only and I believe it worked. At least it's moved
ahead to other problems I have with the fcst_fields and fcst_thresh,
but I think I know how to fix those.
Actually, I prefer the fcst_lead since I don’t have to specify the
YYYYMMDD which, in terms of valid times, would need to be incremented
by one day as the valid time crossed over into the next date. With
lead time, all you have to do us tell it the desired lead times which
correspond to the valid times you want.
By the way, the User's Guide for METV3.0 shows that the -fcst_lead
argument does use the YYYYMMDD. Is this a typo?
Thanks.
John
-----Original Message-----
From: RAL HelpDesk {for John Halley Gotway} [mailto:met_help at ucar.edu]
Sent: Friday, May 20, 2011 9:58 PM
To: Raby, John (Civ, ARL/CISD)
Cc: Brown, Bob (Civ, ARL/CISD)
Subject: Re: [rt.rap.ucar.edu #46965] Problem with Point-Stat
(UNCLASSIFIED)
John,
If you look closely at the usage statement for Point-Stat, I think
you'll discover the problem. You're using the "-fcst_lead" command
line argument when I'm guessing you intend to be using the "-
fcst_valid" command line argument. The former is used to specify a
particular lead time in HHMMSS format while the latter is used to
specify the valid time in YYYYMMDD_HHMMSS. I'm guessing that's really
what you're trying to do.
Hope that helps.
John Halley Gotway
met_help at ucar.edu
>
> Fri May 20 07:09:09 2011: Request 46965 was acted upon.
> Transaction: Ticket created by john.raby at us.army.mil
> Queue: met_help
> Subject: Problem with Point-Stat (UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.raby at us.army.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=46965
> >
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> I have run into a problem while trying to run Point-Stat on NAM data
> received from the CISL archive data site.
>
> I am running METV3.0 and am trying to use the optional argument
> -fcst_lead because the NAM file contains all forecast lead times in
one large file.
>
> When I run Point-Stat, it has the following error:
>
> timestring_to_sec(const char *) -> can't parse time string
> "20090326_000000"
>
> I've attached the script I use to run Point-Stat, the log file which
> show the error, and a sample of the 2GB NAM file.
>
> I can't figure out what is needed to resolve this and wondered if
you
> could help me out.
>
> Thanks.
>
> R/
> John
>
> Mr John W. Raby, Meteorologist
> U.S. Army Research Laboratory
> White Sands Missile Range, NM 88002
> (575) 678-2004 DSN 258-2004
> FAX (575) 678-1230 DSN 258-1230
> Email: john.raby at us.army.mil
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #46965] Problem with Point-Stat (UNCLASSIFIED)
From: John Halley Gotway
Time: Mon May 23 11:40:44 2011
John,
Yes, that is a typo. Thanks for finding it! I'll make sure it gets
corrected in the next version.
I'll go ahead and resolve this ticket. But if more issues arise, feel
free to write us at met_help at ucar.edu.
Thanks,
John
On 05/23/2011 11:33 AM, RAL HelpDesk {for Raby, John} wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=46965 >
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> John -
>
> Based on your response, I ran another test but decided to keep the
-fcst_lead and correct the problem where it was apparently rejecting
the YYYYMMDD (my Start_Date variable). I omitted the YYYYMMDD and just
specified the HH only and I believe it worked. At least it's moved
ahead to other problems I have with the fcst_fields and fcst_thresh,
but I think I know how to fix those.
>
> Actually, I prefer the fcst_lead since I don’t have to specify the
YYYYMMDD which, in terms of valid times, would need to be incremented
by one day as the valid time crossed over into the next date. With
lead time, all you have to do us tell it the desired lead times which
correspond to the valid times you want.
>
> By the way, the User's Guide for METV3.0 shows that the -fcst_lead
argument does use the YYYYMMDD. Is this a typo?
>
> Thanks.
>
> John
>
>
>
>
> -----Original Message-----
> From: RAL HelpDesk {for John Halley Gotway}
[mailto:met_help at ucar.edu]
> Sent: Friday, May 20, 2011 9:58 PM
> To: Raby, John (Civ, ARL/CISD)
> Cc: Brown, Bob (Civ, ARL/CISD)
> Subject: Re: [rt.rap.ucar.edu #46965] Problem with Point-Stat
(UNCLASSIFIED)
>
> John,
>
> If you look closely at the usage statement for Point-Stat, I think
you'll discover the problem. You're using the "-fcst_lead" command
line argument when I'm guessing you intend to be using the "-
fcst_valid" command line argument. The former is used to specify a
particular lead time in HHMMSS format while the latter is used to
specify the valid time in YYYYMMDD_HHMMSS. I'm guessing that's really
what you're trying to do.
>
> Hope that helps.
>
> John Halley Gotway
> met_help at ucar.edu
>
>>
>> Fri May 20 07:09:09 2011: Request 46965 was acted upon.
>> Transaction: Ticket created by john.raby at us.army.mil
>> Queue: met_help
>> Subject: Problem with Point-Stat (UNCLASSIFIED)
>> Owner: Nobody
>> Requestors: john.raby at us.army.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=46965
>>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> I have run into a problem while trying to run Point-Stat on NAM
data
>> received from the CISL archive data site.
>>
>> I am running METV3.0 and am trying to use the optional argument
>> -fcst_lead because the NAM file contains all forecast lead times in
one large file.
>>
>> When I run Point-Stat, it has the following error:
>>
>> timestring_to_sec(const char *) -> can't parse time string
>> "20090326_000000"
>>
>> I've attached the script I use to run Point-Stat, the log file
which
>> show the error, and a sample of the 2GB NAM file.
>>
>> I can't figure out what is needed to resolve this and wondered if
you
>> could help me out.
>>
>> Thanks.
>>
>> R/
>> John
>>
>> Mr John W. Raby, Meteorologist
>> U.S. Army Research Laboratory
>> White Sands Missile Range, NM 88002
>> (575) 678-2004 DSN 258-2004
>> FAX (575) 678-1230 DSN 258-1230
>> Email: john.raby at us.army.mil
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>>
>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
------------------------------------------------
More information about the Met_help
mailing list