[Met_help] [rt.rap.ucar.edu #56988] History for Running point_stat with NCAR ds337 ncdf files
John Halley Gotway via RT
met_help at ucar.edu
Tue Jun 26 10:52:03 MDT 2012
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I have recently upgraded to v3.1 of MET and am running point_stat for
the first time on two separate machines - one locally, with the other
being NASA Ames' Pleiades. I am trying to use the netcdf PrepBufr obs
files obtained from NCAR's dss337, however, all attempts to run
point_stat terminate with this error:
DEBUG 1: Default Config File:
/u/jmhender/NWP/WRF-MET/METv3.1/data/config/PointStatConfig_default
DEBUG 1: User Config File:
PointStatConfig_V3.1-SLC-case03.20120614.13.47.57.UTC
DEBUG 1: Forecast File:
/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib
DEBUG 1: Climatology File: none
DEBUG 1: Observation File:
/nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090101.nc
DEBUG 1: Observation File:
/nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090102.nc
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for TMP/P200.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "TMP/P200" in GRIB record 81 of GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
matching VarInfo "TMP/P200" in GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 4: parse_sid_mask() -> parsing station ID mask file "(nul)"
DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
DEBUG 2: For TMP/P200 found 1 forecast levels and 0 climatology levels.
DEBUG 2:
...
DEBUG 3: Rotating U and V wind components from grid-relative to
earth-relative.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
matching VarInfo "32/Z010" in GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Reading V-wind records.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match for
VarInfo "32/Z010" in GRIB record 294 of GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have V-wind record, reading
U-wind record.
DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact match for
VarInfo "32/Z010" in GRIB record 293 of GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 3: Rotating U and V wind components from grid-relative to
earth-relative.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
matching VarInfo "32/Z010" in GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 3: Deriving wind speed from U and V wind components.
DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB records
matching VarInfo "32/Z010" in GRIB file
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
DEBUG 2: For 32/Z010 found 1 forecast levels and 0 climatology levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Searching 2979273 observations from 85274 messages.
ERROR :
ERROR : process_obs_file() -> can't read the header array record for
header number 85274
ERROR :
I was wondering if this perhaps is something related to my build of
METv3.1, the way I am calling point_stat, or perhaps a bug in the ncdf
files. Note that the test script provided with METv3.1 seems to work
just fine.
Any help would be much appreciated.
Thanks.
John Henderson
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56988] Running point_stat with NCAR ds337 ncdf files
From: John Halley Gotway
Time: Thu Jun 14 10:36:24 2012
John,
Very good question. Can you please clarify one thing for me?
Are you retrieving the PrepBufr files themselves from this ds337 link:
http://rda.ucar.edu/datasets/ds337.0
And then running them through the PB2NC tool to pre-process them?
Or are you using the subset request form at this link:
http://rda.ucar.edu/datasets/ds337.0/forms/337_subset.php
And using that data as input into Point-Stat directly?
I need to figure out which avenue needs debugging.
Thanks,
John
On 06/14/2012 09:59 AM, jhenders at aer.com via RT wrote:
>
> Thu Jun 14 09:59:39 2012: Request 56988 was acted upon.
> Transaction: Ticket created by jhenders at aer.com
> Queue: met_help
> Subject: Running point_stat with NCAR ds337 ncdf files
> Owner: Nobody
> Requestors: jhenders at aer.com
> Status: new
> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56988>
>
>
> Hello,
>
> I have recently upgraded to v3.1 of MET and am running point_stat
for
> the first time on two separate machines - one locally, with the
other
> being NASA Ames' Pleiades. I am trying to use the netcdf PrepBufr
obs
> files obtained from NCAR's dss337, however, all attempts to run
> point_stat terminate with this error:
>
> DEBUG 1: Default Config File:
> /u/jmhender/NWP/WRF-MET/METv3.1/data/config/PointStatConfig_default
> DEBUG 1: User Config File:
> PointStatConfig_V3.1-SLC-case03.20120614.13.47.57.UTC
> DEBUG 1: Forecast File:
> /nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib
> DEBUG 1: Climatology File: none
> DEBUG 1: Observation File:
> /nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090101.nc
> DEBUG 1: Observation File:
> /nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090102.nc
> DEBUG 2:
> DEBUG 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Reading data for TMP/P200.
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> VarInfo "TMP/P200" in GRIB record 81 of GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> matching VarInfo "TMP/P200" in GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 4: parse_sid_mask() -> parsing station ID mask file "(nul)"
> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
> DEBUG 2: For TMP/P200 found 1 forecast levels and 0 climatology
levels.
> DEBUG 2:
>
> ...
>
> DEBUG 3: Rotating U and V wind components from grid-relative to
> earth-relative.
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> matching VarInfo "32/Z010" in GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Reading V-wind
records.
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range match
for
> VarInfo "32/Z010" in GRIB record 294 of GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have V-wind record,
reading
> U-wind record.
> DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact match
for
> VarInfo "32/Z010" in GRIB record 293 of GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 3: Rotating U and V wind components from grid-relative to
> earth-relative.
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> matching VarInfo "32/Z010" in GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 3: Deriving wind speed from U and V wind components.
> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
> matching VarInfo "32/Z010" in GRIB file
>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
> DEBUG 2: For 32/Z010 found 1 forecast levels and 0 climatology
levels.
> DEBUG 2:
> DEBUG 2:
>
--------------------------------------------------------------------------------
> DEBUG 2:
> DEBUG 2: Searching 2979273 observations from 85274 messages.
> ERROR :
> ERROR : process_obs_file() -> can't read the header array record
for
> header number 85274
> ERROR :
>
> I was wondering if this perhaps is something related to my build of
> METv3.1, the way I am calling point_stat, or perhaps a bug in the
ncdf
> files. Note that the test script provided with METv3.1 seems to work
> just fine.
>
> Any help would be much appreciated.
>
> Thanks.
>
> John Henderson
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56988] Running point_stat with NCAR ds337 ncdf files
From: jhenders at aer.com
Time: Thu Jun 14 12:12:22 2012
Hello again John,
Thanks again for your prompt response. The quick answer is that I have
tried both ways.
Originally I retrieved the netcdf files directly from
http://rda.ucar.edu/dsszone/ds337.0/index.html?g=5.
Having this new archive of netcdf files at NCAR was a welcome
discovery,
except that they are global files and point_stat took 3 h on NASA's
Pleiades before failing with the error I provided.
To test further, I then requested netcdf files for a geographical
subregion via
http://rda.ucar.edu/datasets/ds337.0/forms/337_subset.php.
That again fails (much faster) with the same error.
I should note that I have only used point_stat with netcdf obs files
from 20090901 and 20090902. The error shows up on both a local linux
cluster as well as on Pleiades.
In the past hour I have retrieved a PrepBufr file from NCAR and run
pb2nc on Pleiades. I then provide that ncdf file to point_stat. I was
able to get past the error, though (for unknown reasons) I am not
finding any successful matches.
This suggests a problem with the ncdf files at NCAR.
Thanks.
John
On 6/14/12 12:36 PM, John Halley Gotway via RT wrote:
> John,
>
> Very good question. Can you please clarify one thing for me?
>
> Are you retrieving the PrepBufr files themselves from this ds337
link:
> http://rda.ucar.edu/datasets/ds337.0
> And then running them through the PB2NC tool to pre-process them?
>
> Or are you using the subset request form at this link:
> http://rda.ucar.edu/datasets/ds337.0/forms/337_subset.php
> And using that data as input into Point-Stat directly?
>
> I need to figure out which avenue needs debugging.
>
> Thanks,
> John
>
> On 06/14/2012 09:59 AM, jhenders at aer.com via RT wrote:
>> Thu Jun 14 09:59:39 2012: Request 56988 was acted upon.
>> Transaction: Ticket created by jhenders at aer.com
>> Queue: met_help
>> Subject: Running point_stat with NCAR ds337 ncdf files
>> Owner: Nobody
>> Requestors: jhenders at aer.com
>> Status: new
>> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56988>
>>
>>
>> Hello,
>>
>> I have recently upgraded to v3.1 of MET and am running point_stat
for
>> the first time on two separate machines - one locally, with the
other
>> being NASA Ames' Pleiades. I am trying to use the netcdf PrepBufr
obs
>> files obtained from NCAR's dss337, however, all attempts to run
>> point_stat terminate with this error:
>>
>> DEBUG 1: Default Config File:
>> /u/jmhender/NWP/WRF-MET/METv3.1/data/config/PointStatConfig_default
>> DEBUG 1: User Config File:
>> PointStatConfig_V3.1-SLC-case03.20120614.13.47.57.UTC
>> DEBUG 1: Forecast File:
>> /nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib
>> DEBUG 1: Climatology File: none
>> DEBUG 1: Observation File:
>> /nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090101.nc
>> DEBUG 1: Observation File:
>> /nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090102.nc
>> DEBUG 2:
>> DEBUG 2:
>>
--------------------------------------------------------------------------------
>> DEBUG 2:
>> DEBUG 2: Reading data for TMP/P200.
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match for
>> VarInfo "TMP/P200" in GRIB record 81 of GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>> matching VarInfo "TMP/P200" in GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 4: parse_sid_mask() -> parsing station ID mask file
"(nul)"
>> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
>> DEBUG 2: For TMP/P200 found 1 forecast levels and 0 climatology
levels.
>> DEBUG 2:
>>
>> ...
>>
>> DEBUG 3: Rotating U and V wind components from grid-relative to
>> earth-relative.
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>> matching VarInfo "32/Z010" in GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Reading V-wind
records.
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match for
>> VarInfo "32/Z010" in GRIB record 294 of GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have V-wind record,
reading
>> U-wind record.
>> DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact
match for
>> VarInfo "32/Z010" in GRIB record 293 of GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 3: Rotating U and V wind components from grid-relative to
>> earth-relative.
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>> matching VarInfo "32/Z010" in GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 3: Deriving wind speed from U and V wind components.
>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>> matching VarInfo "32/Z010" in GRIB file
>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>> DEBUG 2: For 32/Z010 found 1 forecast levels and 0 climatology
levels.
>> DEBUG 2:
>> DEBUG 2:
>>
--------------------------------------------------------------------------------
>> DEBUG 2:
>> DEBUG 2: Searching 2979273 observations from 85274 messages.
>> ERROR :
>> ERROR : process_obs_file() -> can't read the header array record
for
>> header number 85274
>> ERROR :
>>
>> I was wondering if this perhaps is something related to my build of
>> METv3.1, the way I am calling point_stat, or perhaps a bug in the
ncdf
>> files. Note that the test script provided with METv3.1 seems to
work
>> just fine.
>>
>> Any help would be much appreciated.
>>
>> Thanks.
>>
>> John Henderson
>>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56988] Running point_stat with NCAR ds337 ncdf files
From: John Halley Gotway
Time: Thu Jun 14 12:47:59 2012
John,
I tried to replicate the error you're seeing but was not immediately
able to do so. I went to the page you sent:
http://rda.ucar.edu/dsszone/ds337.0/index.html?g=5
And retrieved some data:
netcdf.gdas.2009010100.nc
netcdf.gdas.2009010106.nc
When I run point_stat against it, it runs fine. I tried using both
the originally released METv3.1 and the version with the latest set of
patches applied. I'm not able to produce the error using either.
Here are some questions:
- Am I looking at the right dates? In your message you say 20090901
and 20090902, but in the command you sent it's 20090101 and 20090102.
I tested with January, 2009 data, but should I be looking
September 2009 data instead?
- I'm not sure where exactly you got this file:
/nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090101.nc
On ds337.0, the file names are "netcdf.gdas.YYYYMMDDHH.nc" - but yours
is missing the "HH". How did you get a single file for the entire
day?
You mentioned getting 0 matched pairs, and not knowing why. Please
try running Point-Stat with "-v 3", that'll dump out more verbose
output and give you more detailed information for each
verification task. Something like the following:
DEBUG 2: Processing VGRD/Z10 versus VGRD/Z10, for observation type
ADPSFC, over region DTC165, for interpolation method UW_MEAN(1), using
9998 pairs.
DEBUG 3: Number of matched pairs = 9998
DEBUG 3: Observations processed = 2920139
DEBUG 3: Rejected: GRIB code = 2322261
DEBUG 3: Rejected: valid time = 0
DEBUG 3: Rejected: bad obs value = 0
DEBUG 3: Rejected: off the grid = 486827
DEBUG 3: Rejected: level mismatch = 61549
DEBUG 3: Rejected: message type = 5863
DEBUG 3: Rejected: masking region = 33641
DEBUG 3: Rejected: bad fcst value = 0
That way you can tell why the observation are not be used in each
verification task.
Lastly, I think a very possible scenario is that those NetCDF files in
ds337.0 were generated using an earlier version of the PB2NC tool, and
the Point-Stat tool is not handling them well. But if
that really is the case, then I should be able to reproduce the error
here.
If you'd like, you could bundle up a model file, NetCDF point
observation file, and Point-Stat config file that demonstrate the
error and post them to our ftp site. I could grab them, reproduce the
error here, and then figure out what's going wrong. Here's
instructions for posting to our ftp site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John
On 06/14/2012 12:12 PM, jhenders at aer.com via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56988 >
>
> Hello again John,
>
> Thanks again for your prompt response. The quick answer is that I
have
> tried both ways.
>
> Originally I retrieved the netcdf files directly from
> http://rda.ucar.edu/dsszone/ds337.0/index.html?g=5.
>
> Having this new archive of netcdf files at NCAR was a welcome
discovery,
> except that they are global files and point_stat took 3 h on NASA's
> Pleiades before failing with the error I provided.
>
> To test further, I then requested netcdf files for a geographical
> subregion via
http://rda.ucar.edu/datasets/ds337.0/forms/337_subset.php.
> That again fails (much faster) with the same error.
>
> I should note that I have only used point_stat with netcdf obs files
> from 20090901 and 20090902. The error shows up on both a local linux
> cluster as well as on Pleiades.
>
> In the past hour I have retrieved a PrepBufr file from NCAR and run
> pb2nc on Pleiades. I then provide that ncdf file to point_stat. I
was
> able to get past the error, though (for unknown reasons) I am not
> finding any successful matches.
>
> This suggests a problem with the ncdf files at NCAR.
>
> Thanks.
>
> John
>
>
> On 6/14/12 12:36 PM, John Halley Gotway via RT wrote:
>> John,
>>
>> Very good question. Can you please clarify one thing for me?
>>
>> Are you retrieving the PrepBufr files themselves from this ds337
link:
>> http://rda.ucar.edu/datasets/ds337.0
>> And then running them through the PB2NC tool to pre-process them?
>>
>> Or are you using the subset request form at this link:
>> http://rda.ucar.edu/datasets/ds337.0/forms/337_subset.php
>> And using that data as input into Point-Stat directly?
>>
>> I need to figure out which avenue needs debugging.
>>
>> Thanks,
>> John
>>
>> On 06/14/2012 09:59 AM, jhenders at aer.com via RT wrote:
>>> Thu Jun 14 09:59:39 2012: Request 56988 was acted upon.
>>> Transaction: Ticket created by jhenders at aer.com
>>> Queue: met_help
>>> Subject: Running point_stat with NCAR ds337 ncdf files
>>> Owner: Nobody
>>> Requestors: jhenders at aer.com
>>> Status: new
>>> Ticket<URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56988>
>>>
>>>
>>> Hello,
>>>
>>> I have recently upgraded to v3.1 of MET and am running point_stat
for
>>> the first time on two separate machines - one locally, with the
other
>>> being NASA Ames' Pleiades. I am trying to use the netcdf PrepBufr
obs
>>> files obtained from NCAR's dss337, however, all attempts to run
>>> point_stat terminate with this error:
>>>
>>> DEBUG 1: Default Config File:
>>> /u/jmhender/NWP/WRF-
MET/METv3.1/data/config/PointStatConfig_default
>>> DEBUG 1: User Config File:
>>> PointStatConfig_V3.1-SLC-case03.20120614.13.47.57.UTC
>>> DEBUG 1: Forecast File:
>>> /nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib
>>> DEBUG 1: Climatology File: none
>>> DEBUG 1: Observation File:
>>> /nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090101.nc
>>> DEBUG 1: Observation File:
>>> /nobackupp6/jmhender/p1652/obs/netcdf.gdas.20090102.nc
>>> DEBUG 2:
>>> DEBUG 2:
>>>
--------------------------------------------------------------------------------
>>> DEBUG 2:
>>> DEBUG 2: Reading data for TMP/P200.
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match for
>>> VarInfo "TMP/P200" in GRIB record 81 of GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>>> matching VarInfo "TMP/P200" in GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 4: parse_sid_mask() -> parsing station ID mask file
"(nul)"
>>> DEBUG 4: parse_grid_mask() -> parsing grid mask "FULL"
>>> DEBUG 2: For TMP/P200 found 1 forecast levels and 0 climatology
levels.
>>> DEBUG 2:
>>>
>>> ...
>>>
>>> DEBUG 3: Rotating U and V wind components from grid-relative to
>>> earth-relative.
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>>> matching VarInfo "32/Z010" in GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Reading V-wind
records.
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found range
match for
>>> VarInfo "32/Z010" in GRIB record 294 of GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 3: MetGrib1DataFile::rotate_winds() -> Have V-wind record,
reading
>>> U-wind record.
>>> DEBUG 3: MetGrib1DataFile::data_plane_scalar() -> Found exact
match for
>>> VarInfo "32/Z010" in GRIB record 293 of GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 3: Rotating U and V wind components from grid-relative to
>>> earth-relative.
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>>> matching VarInfo "32/Z010" in GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 3: Deriving wind speed from U and V wind components.
>>> DEBUG 3: MetGrib1DataFile::data_plane_array() -> Found 1 GRIB
records
>>> matching VarInfo "32/Z010" in GRIB file
>>>
"/nobackupp6/jmhender/p1652/grib/2009010100/d2_2009010100_3000.grib".
>>> DEBUG 2: For 32/Z010 found 1 forecast levels and 0 climatology
levels.
>>> DEBUG 2:
>>> DEBUG 2:
>>>
--------------------------------------------------------------------------------
>>> DEBUG 2:
>>> DEBUG 2: Searching 2979273 observations from 85274 messages.
>>> ERROR :
>>> ERROR : process_obs_file() -> can't read the header array
record for
>>> header number 85274
>>> ERROR :
>>>
>>> I was wondering if this perhaps is something related to my build
of
>>> METv3.1, the way I am calling point_stat, or perhaps a bug in the
ncdf
>>> files. Note that the test script provided with METv3.1 seems to
work
>>> just fine.
>>>
>>> Any help would be much appreciated.
>>>
>>> Thanks.
>>>
>>> John Henderson
>>>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56988] Running point_stat with NCAR ds337 ncdf files
From: jhenders at aer.com
Time: Thu Jun 14 13:17:55 2012
John,
Thank you for trying to reproduce. I now suspect that the problem lies
in my use of an nco tool to join the four six-hourly ncdf files from
NCAR into one daily file (correct date is 20090101 - sorry). That
explains the naming convention you mention below. Perhaps I'm issuing
that incorrectly or otherwise that is not an appropriate tool to use.
I
used the nco tool to limit the number of files that I had to provide
at
the command line.
I will let you know the results of a rerun soon.
Thanks.
John
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56988] Running point_stat with NCAR ds337 ncdf files
From: John Halley Gotway
Time: Thu Jun 14 13:42:56 2012
John,
Yes, that does sound like the likely culprit.
John
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56988 >
>
> John,
>
> Thank you for trying to reproduce. I now suspect that the problem
lies
> in my use of an nco tool to join the four six-hourly ncdf files from
> NCAR into one daily file (correct date is 20090101 - sorry). That
> explains the naming convention you mention below. Perhaps I'm
issuing
> that incorrectly or otherwise that is not an appropriate tool to
use. I
> used the nco tool to limit the number of files that I had to provide
at
> the command line.
>
> I will let you know the results of a rerun soon.
>
> Thanks.
>
> John
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #56988] Running point_stat with NCAR ds337 ncdf files
From: jhenders at aer.com
Time: Thu Jun 14 13:46:18 2012
John,
Earlier I believe I had confirmed that the number of obs in the
combined
file equalled the sum of those in the individual files. Something may
still be awry, of course. As I mentioned earlier, I will report on
subsequent tests when they finish.
Thanks again.
Regards,
John
On 6/14/12 3:42 PM, John Halley Gotway via RT wrote:
> John,
>
> Yes, that does sound like the likely culprit.
>
> John
>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=56988>
>>
>> John,
>>
>> Thank you for trying to reproduce. I now suspect that the problem
lies
>> in my use of an nco tool to join the four six-hourly ncdf files
from
>> NCAR into one daily file (correct date is 20090101 - sorry). That
>> explains the naming convention you mention below. Perhaps I'm
issuing
>> that incorrectly or otherwise that is not an appropriate tool to
use. I
>> used the nco tool to limit the number of files that I had to
provide at
>> the command line.
>>
>> I will let you know the results of a rerun soon.
>>
>> Thanks.
>>
>> John
>>
>>
>
>
------------------------------------------------
More information about the Met_help
mailing list