[Met_help] [rt.rap.ucar.edu #56590] History for Point-Stat error (UNCLASSIFIED)
Paul Oldenburg via RT
met_help at ucar.edu
Mon Jun 11 09:05:55 MDT 2012
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Classification: UNCLASSIFIED
Caveats: NONE
Request assistance to debug the following error:
Ran V3.1 point-stat and received an error statement with words to the effect
"Can't process vector winds. Each UGRD observation must be followed by a
VGRD observation".
I checked the observations an all have GRIB codes 33 and 34 data. We have
been trying to use profiler and vadwind observations to augment ADPUPA data.
Are there any known problems when encountering UGRD and VGRD observations
when the values are both 0? (calm)
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.w.raby2.civ at mail.mil
Classification: UNCLASSIFIED
Caveats: NONE
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error (UNCLASSIFIED)
From: Paul Oldenburg
Time: Wed May 23 15:57:24 2012
John,
I'm not able to find a place in the code that produces that exact
error message. Can you please copy and paste the
entire point_stat output into an email for me? When you want to
generate vl1l2 output lines, you must specify the UGRD
and VGRD fields at a particular level consecutively:
obs_field[] = [ "UGRD/Z10", "VGRD/Z10" ];
I suspect that this is the cause of the problem, but I'm not sure.
Please let me know if you have any questions.
Thanks,
Paul
On 05/23/2012 03:40 PM, Raby, John W USA CIV via RT wrote:
>
> Wed May 23 15:40:50 2012: Request 56590 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: Point-Stat error (UNCLASSIFIED)
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Request assistance to debug the following error:
>
> Ran V3.1 point-stat and received an error statement with words to
the effect
> "Can't process vector winds. Each UGRD observation must be followed
by a
> VGRD observation".
> I checked the observations an all have GRIB codes 33 and 34 data. We
have
> been trying to use profiler and vadwind observations to augment
ADPUPA data.
>
>
> Are there any known problems when encountering UGRD and VGRD
observations
> when the values are both 0? (calm)
>
>
>
>
> 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.w.raby2.civ at mail.mil
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error (UNCLASSIFIED)
From: John Halley Gotway
Time: Thu May 24 07:22:41 2012
John and Paul,
Let me jump in on this one. By convention, when computing VL1L2 or
VAL1L2 lines, Point-Stat expects to see in the observations U/V pairs
grouped together. When it encounters U at a given location at
500mb, it expects that the next observation will be V at the same
location at 500mb. Since the U/V information gets paired together
when computing those vector lines, we chose this convention to
simplify the processing.
John, you have 2 choices. First, if you turn *OFF* the VL1L2 and
VAL1L2 output lines in the config file, this error should go away.
Second, change the order how U and V observations are stored.
How did you acquire these observations? Are these really just
additional message types from a PrepBufr file or did they come from
some other source?
Thanks,
John Halley Gotway
On 05/23/2012 03:57 PM, Paul Oldenburg via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>
> John,
>
> I'm not able to find a place in the code that produces that exact
error message. Can you please copy and paste the
> entire point_stat output into an email for me? When you want to
generate vl1l2 output lines, you must specify the UGRD
> and VGRD fields at a particular level consecutively:
>
> obs_field[] = [ "UGRD/Z10", "VGRD/Z10" ];
>
> I suspect that this is the cause of the problem, but I'm not sure.
Please let me know if you have any questions.
>
> Thanks,
>
> Paul
>
>
> On 05/23/2012 03:40 PM, Raby, John W USA CIV via RT wrote:
>>
>> Wed May 23 15:40:50 2012: Request 56590 was acted upon.
>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>> Queue: met_help
>> Subject: Point-Stat error (UNCLASSIFIED)
>> Owner: Nobody
>> Requestors: john.w.raby2.civ at mail.mil
>> Status: new
>> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Request assistance to debug the following error:
>>
>> Ran V3.1 point-stat and received an error statement with words to
the effect
>> "Can't process vector winds. Each UGRD observation must be followed
by a
>> VGRD observation".
>> I checked the observations an all have GRIB codes 33 and 34 data.
We have
>> been trying to use profiler and vadwind observations to augment
ADPUPA data.
>>
>>
>> Are there any known problems when encountering UGRD and VGRD
observations
>> when the values are both 0? (calm)
>>
>>
>>
>>
>> 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.w.raby2.civ at mail.mil
>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #56590] Point-Stat error (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Thu May 24 08:32:58 2012
John and Paul -
Thanks for both of your quick responses.
My colleague, Jeff Passner will have to respond on the exact data he
used when he encountered the error. I had run into this same error
back on 9 MAY, but I wrote it off because I was doing some testing of
my scripts and was running Point-Stat on a WRF forecast from a domain
in UT using observations from a domain near LA in CA. I believed that
the error was because Point-Stat was not able to read the data from
the mismatch in domain locations. I postponed further investigation
until I could get a WRF run over the same CA domain.
I am collecting the PrepBUFR and MADIS mesonet data to run Point-Stat
on the same domain in the LA area he is working with. For PrepBUFR I
specify the message types ADPSFC, ADPUPA, ANYAIR and PROFLR. For the
MADIS data, I use only the ADPSFC message type. I do know that Jeff is
trying to use the same plus VADWND and SFCSHP, but I'm not sure from
which source he acquires his data.
I have spot checked the .nc files produced by PB2NC and ASCII2NC and
they show the UGRD and VGRD data (GRIB codes 33,34) in the usual
sequence I have always seen, an example of which is as follows:
4, 7, 988, 212.1846, 212,
4, 33, 988, 212.1846, -2.8,
4, 34, 988, 212.1846, 5.1,
4, 32, 988, 212.1846, 5.818075,
4, 7, 980.6, 275.2394, 275,
4, 33, 980.6, 275.2394, -3,
4, 34, 980.6, 275.2394, 4.8,
4, 32, 980.6, 275.2394, 5.660389,
4, 7, 973.4, 337.2934, 337,
4, 33, 973.4, 337.2934, -3.1,
4, 34, 973.4, 337.2934, 4.6,
4, 32, 973.4, 337.2934, 5.547071,
4, 7, 966.1, 400.3482, 400,
4, 33, 966.1, 400.3482, -3.1,
4, 34, 966.1, 400.3482, 4.3,
4, 32, 966.1, 400.3482, 5.300943,
4, 7, 959, 462.4022, 462,
I believe this data is from a profiler and is PrepBUFR data.
An example of the MADIS data (ADPSFC only) follows:
176, 2, 985.59, 220, 101140,
176, 7, 985.59, 220, 220,
176, 11, 985.59, 220, 288.15,
176, 17, 985.59, 220, 285.1,
176, 32, 985.59, 220, 2.2352,
176, 33, 985.59, 220, -1.761362,
176, 34, 985.59, 220, 1.376126,
176, 52, 985.59, 220, 82,
177, 7, -9999, 244, 244,
177, 11, -9999, 244, 290.3722,
177, 17, -9999, 244, 274.7722,
177, 32, -9999, 244, 0,
177, 33, -9999, 244, 0,
177, 34, -9999, 244, 0,
177, 52, -9999, 244, 35,
178, 2, 940.572, 619, 101240,
178, 7, 940.572, 619, 619,
Both data sources seem to provide the UGRD and VGRD data in the right
sequence (paired together, one line following the other)
R/
John
________________________________________
From: John Halley Gotway via RT [met_help at ucar.edu]
Sent: Thursday, May 24, 2012 7:22 AM
To: Raby, John W CIV (US)
Cc: Passner, Jeffrey E CIV (US)
Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error (UNCLASSIFIED)
John and Paul,
Let me jump in on this one. By convention, when computing VL1L2 or
VAL1L2 lines, Point-Stat expects to see in the observations U/V pairs
grouped together. When it encounters U at a given location at
500mb, it expects that the next observation will be V at the same
location at 500mb. Since the U/V information gets paired together
when computing those vector lines, we chose this convention to
simplify the processing.
John, you have 2 choices. First, if you turn *OFF* the VL1L2 and
VAL1L2 output lines in the config file, this error should go away.
Second, change the order how U and V observations are stored.
How did you acquire these observations? Are these really just
additional message types from a PrepBufr file or did they come from
some other source?
Thanks,
John Halley Gotway
On 05/23/2012 03:57 PM, Paul Oldenburg via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>
> John,
>
> I'm not able to find a place in the code that produces that exact
error message. Can you please copy and paste the
> entire point_stat output into an email for me? When you want to
generate vl1l2 output lines, you must specify the UGRD
> and VGRD fields at a particular level consecutively:
>
> obs_field[] = [ "UGRD/Z10", "VGRD/Z10" ];
>
> I suspect that this is the cause of the problem, but I'm not sure.
Please let me know if you have any questions.
>
> Thanks,
>
> Paul
>
>
> On 05/23/2012 03:40 PM, Raby, John W USA CIV via RT wrote:
>>
>> Wed May 23 15:40:50 2012: Request 56590 was acted upon.
>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>> Queue: met_help
>> Subject: Point-Stat error (UNCLASSIFIED)
>> Owner: Nobody
>> Requestors: john.w.raby2.civ at mail.mil
>> Status: new
>> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Request assistance to debug the following error:
>>
>> Ran V3.1 point-stat and received an error statement with words to
the effect
>> "Can't process vector winds. Each UGRD observation must be followed
by a
>> VGRD observation".
>> I checked the observations an all have GRIB codes 33 and 34 data.
We have
>> been trying to use profiler and vadwind observations to augment
ADPUPA data.
>>
>>
>> Are there any known problems when encountering UGRD and VGRD
observations
>> when the values are both 0? (calm)
>>
>>
>>
>>
>> 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.w.raby2.civ at mail.mil
>>
>>
>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error (UNCLASSIFIED)
From: John Halley Gotway
Time: Thu May 24 08:45:15 2012
John,
Yeah, the NetCDF point obs you referenced do seem to have the U/V obs
in the expected order. Probably the quickest way to get to the bottom
of this would be for you to send us a small test case that
demonstrates the error. If we can reproduce it here, we can let you
know where it's coming from.
John
On 05/24/2012 08:32 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>
> John and Paul -
>
> Thanks for both of your quick responses.
>
> My colleague, Jeff Passner will have to respond on the exact data he
used when he encountered the error. I had run into this same error
back on 9 MAY, but I wrote it off because I was doing some testing of
my scripts and was running Point-Stat on a WRF forecast from a domain
in UT using observations from a domain near LA in CA. I believed that
the error was because Point-Stat was not able to read the data from
the mismatch in domain locations. I postponed further investigation
until I could get a WRF run over the same CA domain.
>
> I am collecting the PrepBUFR and MADIS mesonet data to run Point-
Stat on the same domain in the LA area he is working with. For
PrepBUFR I specify the message types ADPSFC, ADPUPA, ANYAIR and
PROFLR. For the MADIS data, I use only the ADPSFC message type. I do
know that Jeff is trying to use the same plus VADWND and SFCSHP, but
I'm not sure from which source he acquires his data.
>
> I have spot checked the .nc files produced by PB2NC and ASCII2NC and
they show the UGRD and VGRD data (GRIB codes 33,34) in the usual
sequence I have always seen, an example of which is as follows:
>
> 4, 7, 988, 212.1846, 212,
> 4, 33, 988, 212.1846, -2.8,
> 4, 34, 988, 212.1846, 5.1,
> 4, 32, 988, 212.1846, 5.818075,
> 4, 7, 980.6, 275.2394, 275,
> 4, 33, 980.6, 275.2394, -3,
> 4, 34, 980.6, 275.2394, 4.8,
> 4, 32, 980.6, 275.2394, 5.660389,
> 4, 7, 973.4, 337.2934, 337,
> 4, 33, 973.4, 337.2934, -3.1,
> 4, 34, 973.4, 337.2934, 4.6,
> 4, 32, 973.4, 337.2934, 5.547071,
> 4, 7, 966.1, 400.3482, 400,
> 4, 33, 966.1, 400.3482, -3.1,
> 4, 34, 966.1, 400.3482, 4.3,
> 4, 32, 966.1, 400.3482, 5.300943,
> 4, 7, 959, 462.4022, 462,
>
> I believe this data is from a profiler and is PrepBUFR data.
>
> An example of the MADIS data (ADPSFC only) follows:
>
> 176, 2, 985.59, 220, 101140,
> 176, 7, 985.59, 220, 220,
> 176, 11, 985.59, 220, 288.15,
> 176, 17, 985.59, 220, 285.1,
> 176, 32, 985.59, 220, 2.2352,
> 176, 33, 985.59, 220, -1.761362,
> 176, 34, 985.59, 220, 1.376126,
> 176, 52, 985.59, 220, 82,
> 177, 7, -9999, 244, 244,
> 177, 11, -9999, 244, 290.3722,
> 177, 17, -9999, 244, 274.7722,
> 177, 32, -9999, 244, 0,
> 177, 33, -9999, 244, 0,
> 177, 34, -9999, 244, 0,
> 177, 52, -9999, 244, 35,
> 178, 2, 940.572, 619, 101240,
> 178, 7, 940.572, 619, 619,
>
> Both data sources seem to provide the UGRD and VGRD data in the
right sequence (paired together, one line following the other)
>
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Thursday, May 24, 2012 7:22 AM
> To: Raby, John W CIV (US)
> Cc: Passner, Jeffrey E CIV (US)
> Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error
(UNCLASSIFIED)
>
> John and Paul,
>
> Let me jump in on this one. By convention, when computing VL1L2 or
VAL1L2 lines, Point-Stat expects to see in the observations U/V pairs
grouped together. When it encounters U at a given location at
> 500mb, it expects that the next observation will be V at the same
location at 500mb. Since the U/V information gets paired together
when computing those vector lines, we chose this convention to
> simplify the processing.
>
> John, you have 2 choices. First, if you turn *OFF* the VL1L2 and
VAL1L2 output lines in the config file, this error should go away.
Second, change the order how U and V observations are stored.
>
> How did you acquire these observations? Are these really just
additional message types from a PrepBufr file or did they come from
some other source?
>
> Thanks,
> John Halley Gotway
>
> On 05/23/2012 03:57 PM, Paul Oldenburg via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>>
>> John,
>>
>> I'm not able to find a place in the code that produces that exact
error message. Can you please copy and paste the
>> entire point_stat output into an email for me? When you want to
generate vl1l2 output lines, you must specify the UGRD
>> and VGRD fields at a particular level consecutively:
>>
>> obs_field[] = [ "UGRD/Z10", "VGRD/Z10" ];
>>
>> I suspect that this is the cause of the problem, but I'm not sure.
Please let me know if you have any questions.
>>
>> Thanks,
>>
>> Paul
>>
>>
>> On 05/23/2012 03:40 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> Wed May 23 15:40:50 2012: Request 56590 was acted upon.
>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>> Queue: met_help
>>> Subject: Point-Stat error (UNCLASSIFIED)
>>> Owner: Nobody
>>> Requestors: john.w.raby2.civ at mail.mil
>>> Status: new
>>> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> Request assistance to debug the following error:
>>>
>>> Ran V3.1 point-stat and received an error statement with words to
the effect
>>> "Can't process vector winds. Each UGRD observation must be
followed by a
>>> VGRD observation".
>>> I checked the observations an all have GRIB codes 33 and 34 data.
We have
>>> been trying to use profiler and vadwind observations to augment
ADPUPA data.
>>>
>>>
>>> Are there any known problems when encountering UGRD and VGRD
observations
>>> when the values are both 0? (calm)
>>>
>>>
>>>
>>>
>>> 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.w.raby2.civ at mail.mil
>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>
>
------------------------------------------------
Subject: Point-Stat error (UNCLASSIFIED)
From: Raby, John W USA CIV
Time: Thu May 24 09:12:35 2012
Classification: UNCLASSIFIED
Caveats: NONE
John -
OK. I will have Jeff send you some test data. Are the following
instructions
from a previous debug session OK to use for sending the data?
Ultimately, I think it'll be easiest if you just send me some sample
data to
play with. Please execute the following commands and send me this
test data:
tar -cvzf before.tar.gz
MET_PointStat/results_m1o1_P2/*/point_stat_m1o1_P2_110000L*.stat
tar -cvzf after.tar.gz
MET_PointStat/results_m1o1_T3/*/point_stat_m1o1_T3_110000L*.stat
And then you can follow the instructions here for posting the
"before.tar.gz"
and "after.tar.gz" files to our anonymous FTP site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Thursday, May 24, 2012 8:45 AM
To: Raby, John W CIV (US)
Cc: Passner, Jeffrey E CIV (US)
Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error (UNCLASSIFIED)
John,
Yeah, the NetCDF point obs you referenced do seem to have the U/V obs
in the
expected order. Probably the quickest way to get to the bottom of
this would
be for you to send us a small test case that demonstrates the error.
If we
can reproduce it here, we can let you know where it's coming from.
John
On 05/24/2012 08:32 AM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>
> John and Paul -
>
> Thanks for both of your quick responses.
>
> My colleague, Jeff Passner will have to respond on the exact data he
used
> when he encountered the error. I had run into this same error back
on 9 MAY,
> but I wrote it off because I was doing some testing of my scripts
and was
> running Point-Stat on a WRF forecast from a domain in UT using
observations
> from a domain near LA in CA. I believed that the error was because
> Point-Stat was not able to read the data from the mismatch in domain
> locations. I postponed further investigation until I could get a WRF
run
> over the same CA domain.
>
> I am collecting the PrepBUFR and MADIS mesonet data to run Point-
Stat on the
> same domain in the LA area he is working with. For PrepBUFR I
specify the
> message types ADPSFC, ADPUPA, ANYAIR and PROFLR. For the MADIS data,
I use
> only the ADPSFC message type. I do know that Jeff is trying to use
the same
> plus VADWND and SFCSHP, but I'm not sure from which source he
acquires his
> data.
>
> I have spot checked the .nc files produced by PB2NC and ASCII2NC and
they
> show the UGRD and VGRD data (GRIB codes 33,34) in the usual sequence
I have
> always seen, an example of which is as follows:
>
> 4, 7, 988, 212.1846, 212,
> 4, 33, 988, 212.1846, -2.8,
> 4, 34, 988, 212.1846, 5.1,
> 4, 32, 988, 212.1846, 5.818075,
> 4, 7, 980.6, 275.2394, 275,
> 4, 33, 980.6, 275.2394, -3,
> 4, 34, 980.6, 275.2394, 4.8,
> 4, 32, 980.6, 275.2394, 5.660389,
> 4, 7, 973.4, 337.2934, 337,
> 4, 33, 973.4, 337.2934, -3.1,
> 4, 34, 973.4, 337.2934, 4.6,
> 4, 32, 973.4, 337.2934, 5.547071,
> 4, 7, 966.1, 400.3482, 400,
> 4, 33, 966.1, 400.3482, -3.1,
> 4, 34, 966.1, 400.3482, 4.3,
> 4, 32, 966.1, 400.3482, 5.300943,
> 4, 7, 959, 462.4022, 462,
>
> I believe this data is from a profiler and is PrepBUFR data.
>
> An example of the MADIS data (ADPSFC only) follows:
>
> 176, 2, 985.59, 220, 101140,
> 176, 7, 985.59, 220, 220,
> 176, 11, 985.59, 220, 288.15,
> 176, 17, 985.59, 220, 285.1,
> 176, 32, 985.59, 220, 2.2352,
> 176, 33, 985.59, 220, -1.761362,
> 176, 34, 985.59, 220, 1.376126,
> 176, 52, 985.59, 220, 82,
> 177, 7, -9999, 244, 244,
> 177, 11, -9999, 244, 290.3722,
> 177, 17, -9999, 244, 274.7722,
> 177, 32, -9999, 244, 0,
> 177, 33, -9999, 244, 0,
> 177, 34, -9999, 244, 0,
> 177, 52, -9999, 244, 35,
> 178, 2, 940.572, 619, 101240,
> 178, 7, 940.572, 619, 619,
>
> Both data sources seem to provide the UGRD and VGRD data in the
right
> sequence (paired together, one line following the other)
>
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Thursday, May 24, 2012 7:22 AM
> To: Raby, John W CIV (US)
> Cc: Passner, Jeffrey E CIV (US)
> Subject: Re: [rt.rap.ucar.edu #56590] Point-Stat error
(UNCLASSIFIED)
>
> John and Paul,
>
> Let me jump in on this one. By convention, when computing VL1L2 or
> VAL1L2 lines, Point-Stat expects to see in the observations U/V
pairs
> grouped together. When it encounters U at a given location at
500mb, it
> expects that the next observation will be V at the same location at
500mb.
> Since the U/V information gets paired together when computing those
vector
> lines, we chose this convention to simplify the processing.
>
> John, you have 2 choices. First, if you turn *OFF* the VL1L2 and
VAL1L2
> output lines in the config file, this error should go away. Second,
change
> the order how U and V observations are stored.
>
> How did you acquire these observations? Are these really just
additional
> message types from a PrepBufr file or did they come from some other
source?
>
> Thanks,
> John Halley Gotway
>
> On 05/23/2012 03:57 PM, Paul Oldenburg via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>>
>> John,
>>
>> I'm not able to find a place in the code that produces that exact
>> error message. Can you please copy and paste the entire point_stat
>> output into an email for me? When you want to generate vl1l2
output lines,
>> you must specify the UGRD and VGRD fields at a particular level
>> consecutively:
>>
>> obs_field[] = [ "UGRD/Z10", "VGRD/Z10" ];
>>
>> I suspect that this is the cause of the problem, but I'm not sure.
Please
>> let me know if you have any questions.
>>
>> Thanks,
>>
>> Paul
>>
>>
>> On 05/23/2012 03:40 PM, Raby, John W USA CIV via RT wrote:
>>>
>>> Wed May 23 15:40:50 2012: Request 56590 was acted upon.
>>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>>> Queue: met_help
>>> Subject: Point-Stat error (UNCLASSIFIED)
>>> Owner: Nobody
>>> Requestors: john.w.raby2.civ at mail.mil
>>> Status: new
>>> Ticket<URL:
>>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56590>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>> Request assistance to debug the following error:
>>>
>>> Ran V3.1 point-stat and received an error statement with words to
>>> the effect "Can't process vector winds. Each UGRD observation must
>>> be followed by a VGRD observation".
>>> I checked the observations an all have GRIB codes 33 and 34 data.
We
>>> have been trying to use profiler and vadwind observations to
augment
>>> ADPUPA data.
>>>
>>>
>>> Are there any known problems when encountering UGRD and VGRD
>>> observations when the values are both 0? (calm)
>>>
>>>
>>>
>>>
>>> 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.w.raby2.civ at mail.mil
>>>
>>>
>>>
>>> Classification: UNCLASSIFIED
>>> Caveats: NONE
>>>
>>>
>>>
>>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
More information about the Met_help
mailing list