[Met_help] [rt.rap.ucar.edu #51610] History for Averaged files: unexpected time range indicator of 113
Paul Oldenburg via RT
met_help at ucar.edu
Tue Nov 22 08:42:08 MST 2011
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Dear MET Help,
I am trying to compare monthly averages of climate variables between WRF
model output and some NARR monthly data in GRIBv1 format.
I obtained the WRF monthly averages by using UPP to convert the WRF netCDF
files (.nc) to GRIBv1 files for every 3-hour interval. (This was a lot of
files, and awkward to deal with!) I used copygb to convert all of them to
the NARR observation grid (grid 221).
Then I used cdo to merge the files appropriate for each month and compute
the monthly averages.
The NARR provides GRIB files for every 3-hour interval, which would again be
enormous. They also provide monthly averages as GRIBv1 files. But if I try
to process these in MET, I get the following:
-----
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=1243007566
Forecast File: sharc/d01_2004_mon_cp/monmean.grib
Observation File: narr/mon2004/narrmon-a_221_20040101_0000_000.grb
Configuration File: config/GridStatConfig_WRFvsNARR
ERROR: read_pds() -> unexpected time range indicator of 113.
-----
This "time range indicator" is described here:
http://www.nco.ncep.noaa.gov/pmb/docs/on388/table5.html
to mean the average of N forecasts. Which is exactly right; that's what I
want to compare. Why does MET reject this data? What is the appropriate
way to compare monthly averages with MET? Any help would be very
appreciated. Thanks,
__
Michael Biggs
Undergraduate Student Research Assistant
Waterloo Atmosphere-land Interactions Research Group (WatAIR)
University of Waterloo
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #51610] Averaged files: unexpected time range indicator of 113
From: Paul Oldenburg
Time: Mon Nov 21 09:35:02 2011
Michael,
Can you please put a sample of both your model data and NARR obs data
in grib format onto our FTP site, using the
following instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
I will take a look and try to figure out if I can get grid_stat to run
on your data. It is possible that MET was not
designed to handle climate data like that you are trying to use, but
the individual who is more knowledgeable in these
matters than I is out this week. If you have any other questions,
please let me know.
Thanks,
Paul
On 11/21/2011 02:29 AM, Michael Biggs via RT wrote:
>
> Mon Nov 21 02:29:41 2011: Request 51610 was acted upon.
> Transaction: Ticket created by met_help at doubleplum.net
> Queue: met_help
> Subject: Averaged files: unexpected time range indicator of 113
> Owner: Nobody
> Requestors: met_help at doubleplum.net
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=51610 >
>
>
> Dear MET Help,
>
> I am trying to compare monthly averages of climate variables between
WRF
> model output and some NARR monthly data in GRIBv1 format.
>
> I obtained the WRF monthly averages by using UPP to convert the WRF
netCDF
> files (.nc) to GRIBv1 files for every 3-hour interval. (This was a
lot of
> files, and awkward to deal with!) I used copygb to convert all of
them to
> the NARR observation grid (grid 221).
> Then I used cdo to merge the files appropriate for each month and
compute
> the monthly averages.
>
> The NARR provides GRIB files for every 3-hour interval, which would
again be
> enormous. They also provide monthly averages as GRIBv1 files. But
if I try
> to process these in MET, I get the following:
>
> -----
> GSL_RNG_TYPE=mt19937
> GSL_RNG_SEED=1243007566
> Forecast File: sharc/d01_2004_mon_cp/monmean.grib
> Observation File: narr/mon2004/narrmon-a_221_20040101_0000_000.grb
> Configuration File: config/GridStatConfig_WRFvsNARR
>
>
> ERROR: read_pds() -> unexpected time range indicator of 113.
> -----
>
> This "time range indicator" is described here:
> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table5.html
>
> to mean the average of N forecasts. Which is exactly right; that's
what I
> want to compare. Why does MET reject this data? What is the
appropriate
> way to compare monthly averages with MET? Any help would be very
> appreciated. Thanks,
>
> __
> Michael Biggs
> Undergraduate Student Research Assistant
> Waterloo Atmosphere-land Interactions Research Group (WatAIR)
> University of Waterloo
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #51610] Averaged files: unexpected time range indicator of 113
From: Michael Biggs
Time: Mon Nov 21 10:00:51 2011
Thanks Paul.
I have put the files into the incoming/irap/met_help/biggs_data
directory.
__
Michael Biggs
On Mon, 21 Nov 2011, Paul Oldenburg via RT wrote:
> Michael,
>
> Can you please put a sample of both your model data and NARR obs
data in grib format onto our FTP site, using the
> following instructions:
>
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> I will take a look and try to figure out if I can get grid_stat to
run on your data. It is possible that MET was not
> designed to handle climate data like that you are trying to use, but
the individual who is more knowledgeable in these
> matters than I is out this week. If you have any other questions,
please let me know.
>
> Thanks,
>
> Paul
>
>
> On 11/21/2011 02:29 AM, Michael Biggs via RT wrote:
>>
>> Mon Nov 21 02:29:41 2011: Request 51610 was acted upon.
>> Transaction: Ticket created by met_help at doubleplum.net
>> Queue: met_help
>> Subject: Averaged files: unexpected time range indicator of
113
>> Owner: Nobody
>> Requestors: met_help at doubleplum.net
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=51610 >
>>
>>
>> Dear MET Help,
>>
>> I am trying to compare monthly averages of climate variables
between WRF
>> model output and some NARR monthly data in GRIBv1 format.
>>
>> I obtained the WRF monthly averages by using UPP to convert the WRF
netCDF
>> files (.nc) to GRIBv1 files for every 3-hour interval. (This was a
lot of
>> files, and awkward to deal with!) I used copygb to convert all of
them to
>> the NARR observation grid (grid 221).
>> Then I used cdo to merge the files appropriate for each month and
compute
>> the monthly averages.
>>
>> The NARR provides GRIB files for every 3-hour interval, which would
again be
>> enormous. They also provide monthly averages as GRIBv1 files. But
if I try
>> to process these in MET, I get the following:
>>
>> -----
>> GSL_RNG_TYPE=mt19937
>> GSL_RNG_SEED=1243007566
>> Forecast File: sharc/d01_2004_mon_cp/monmean.grib
>> Observation File: narr/mon2004/narrmon-a_221_20040101_0000_000.grb
>> Configuration File: config/GridStatConfig_WRFvsNARR
>>
>>
>> ERROR: read_pds() -> unexpected time range indicator of 113.
>> -----
>>
>> This "time range indicator" is described here:
>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table5.html
>>
>> to mean the average of N forecasts. Which is exactly right; that's
what I
>> want to compare. Why does MET reject this data? What is the
appropriate
>> way to compare monthly averages with MET? Any help would be very
>> appreciated. Thanks,
>>
>> __
>> Michael Biggs
>> Undergraduate Student Research Assistant
>> Waterloo Atmosphere-land Interactions Research Group (WatAIR)
>> University of Waterloo
>
>
>
------------------------------------------------
Subject: Averaged files: unexpected time range indicator of 113
From: Paul Oldenburg
Time: Mon Nov 21 11:21:48 2011
Michael,
I think that you may have to add a small patch to your version of MET
in order to get your data to run through
grid_stat. I performed a small test on 500mb HGT with a patched
version and put the input and output files into a
tarball on the FTP site:
/incoming/irap/met_help/biggs_data/climo_test.tar.gz. I attached
three plots that I created
using IDV (http://www.unidata.ucar.edu/software/idv/) of data in the
grid_stat NetCDF output file, showing the fcst, obs
and difference for HGT/P500.
The patch that I applied is as follows (assuming you have METv3.0.1).
Add the following line to the file
[MET_BASE]/lib/vx_met_util/read_grib.cc after line 1072:
case 113:
After that change, the code in that neighborhood should look like
this:
case 3: // Average
case 113:
valid_ut = (unixtime) (init_ut + pds_ptr-
>p2*sec_per_fcst_unit);
accum = 0;
break;
Then, save read_grib.cc and rebuild by running make at the top-level
directory of MET. I get the following warning when
I run the patched grid_stat on your data, but I'll leave it to you to
align (in time) the model data and obs data that
you want to compare:
***WARNING***: process_scores() -> Forecast and observation valid
times do not match 20040131_210000 != 20040101_030000
for HGT/P500 versus HGT/P500.
Please let me know if you have any questions.
Thanks,
Paul
On 11/21/2011 10:00 AM, Michael Biggs via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=51610 >
>
> Thanks Paul.
>
> I have put the files into the incoming/irap/met_help/biggs_data
directory.
>
> __
> Michael Biggs
>
>
> On Mon, 21 Nov 2011, Paul Oldenburg via RT wrote:
>> Michael,
>>
>> Can you please put a sample of both your model data and NARR obs
data in grib format onto our FTP site, using the
>> following instructions:
>>
>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>
>> I will take a look and try to figure out if I can get grid_stat to
run on your data. It is possible that MET was not
>> designed to handle climate data like that you are trying to use,
but the individual who is more knowledgeable in these
>> matters than I is out this week. If you have any other questions,
please let me know.
>>
>> Thanks,
>>
>> Paul
>>
>>
>> On 11/21/2011 02:29 AM, Michael Biggs via RT wrote:
>>>
>>> Mon Nov 21 02:29:41 2011: Request 51610 was acted upon.
>>> Transaction: Ticket created by met_help at doubleplum.net
>>> Queue: met_help
>>> Subject: Averaged files: unexpected time range indicator of
113
>>> Owner: Nobody
>>> Requestors: met_help at doubleplum.net
>>> Status: new
>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=51610 >
>>>
>>>
>>> Dear MET Help,
>>>
>>> I am trying to compare monthly averages of climate variables
between WRF
>>> model output and some NARR monthly data in GRIBv1 format.
>>>
>>> I obtained the WRF monthly averages by using UPP to convert the
WRF netCDF
>>> files (.nc) to GRIBv1 files for every 3-hour interval. (This was
a lot of
>>> files, and awkward to deal with!) I used copygb to convert all of
them to
>>> the NARR observation grid (grid 221).
>>> Then I used cdo to merge the files appropriate for each month and
compute
>>> the monthly averages.
>>>
>>> The NARR provides GRIB files for every 3-hour interval, which
would again be
>>> enormous. They also provide monthly averages as GRIBv1 files.
But if I try
>>> to process these in MET, I get the following:
>>>
>>> -----
>>> GSL_RNG_TYPE=mt19937
>>> GSL_RNG_SEED=1243007566
>>> Forecast File: sharc/d01_2004_mon_cp/monmean.grib
>>> Observation File: narr/mon2004/narrmon-a_221_20040101_0000_000.grb
>>> Configuration File: config/GridStatConfig_WRFvsNARR
>>>
>>>
>>> ERROR: read_pds() -> unexpected time range indicator of 113.
>>> -----
>>>
>>> This "time range indicator" is described here:
>>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table5.html
>>>
>>> to mean the average of N forecasts. Which is exactly right;
that's what I
>>> want to compare. Why does MET reject this data? What is the
appropriate
>>> way to compare monthly averages with MET? Any help would be very
>>> appreciated. Thanks,
>>>
>>> __
>>> Michael Biggs
>>> Undergraduate Student Research Assistant
>>> Waterloo Atmosphere-land Interactions Research Group (WatAIR)
>>> University of Waterloo
>>
>>
>>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #51610] Averaged files: unexpected time range indicator of 113
From: Michael Biggs
Time: Tue Nov 22 00:10:07 2011
Thanks very much Paul. The patch seems to be working great.
__
Michael Biggs
On Mon, 21 Nov 2011, Paul Oldenburg via RT wrote:
> Michael,
>
> I think that you may have to add a small patch to your version of
MET in order to get your data to run through
> grid_stat. I performed a small test on 500mb HGT with a patched
version and put the input and output files into a
> tarball on the FTP site:
/incoming/irap/met_help/biggs_data/climo_test.tar.gz. I attached
three plots that I created
> using IDV (http://www.unidata.ucar.edu/software/idv/) of data in the
grid_stat NetCDF output file, showing the fcst, obs
> and difference for HGT/P500.
>
> The patch that I applied is as follows (assuming you have
METv3.0.1). Add the following line to the file
> [MET_BASE]/lib/vx_met_util/read_grib.cc after line 1072:
>
> case 113:
>
> After that change, the code in that neighborhood should look like
this:
>
> case 3: // Average
> case 113:
> valid_ut = (unixtime) (init_ut + pds_ptr-
>p2*sec_per_fcst_unit);
> accum = 0;
> break;
>
> Then, save read_grib.cc and rebuild by running make at the top-level
directory of MET. I get the following warning when
> I run the patched grid_stat on your data, but I'll leave it to you
to align (in time) the model data and obs data that
> you want to compare:
>
> ***WARNING***: process_scores() -> Forecast and observation valid
times do not match 20040131_210000 != 20040101_030000
> for HGT/P500 versus HGT/P500.
>
> Please let me know if you have any questions.
>
> Thanks,
>
> Paul
>
>
> On 11/21/2011 10:00 AM, Michael Biggs via RT wrote:
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=51610 >
>>
>> Thanks Paul.
>>
>> I have put the files into the incoming/irap/met_help/biggs_data
directory.
>>
>> __
>> Michael Biggs
>>
>>
>> On Mon, 21 Nov 2011, Paul Oldenburg via RT wrote:
>>> Michael,
>>>
>>> Can you please put a sample of both your model data and NARR obs
data in grib format onto our FTP site, using the
>>> following instructions:
>>>
>>> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>>>
>>> I will take a look and try to figure out if I can get grid_stat to
run on your data. It is possible that MET was not
>>> designed to handle climate data like that you are trying to use,
but the individual who is more knowledgeable in these
>>> matters than I is out this week. If you have any other questions,
please let me know.
>>>
>>> Thanks,
>>>
>>> Paul
>>>
>>>
>>> On 11/21/2011 02:29 AM, Michael Biggs via RT wrote:
>>>>
>>>> Mon Nov 21 02:29:41 2011: Request 51610 was acted upon.
>>>> Transaction: Ticket created by met_help at doubleplum.net
>>>> Queue: met_help
>>>> Subject: Averaged files: unexpected time range indicator of
113
>>>> Owner: Nobody
>>>> Requestors: met_help at doubleplum.net
>>>> Status: new
>>>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=51610 >
>>>>
>>>>
>>>> Dear MET Help,
>>>>
>>>> I am trying to compare monthly averages of climate variables
between WRF
>>>> model output and some NARR monthly data in GRIBv1 format.
>>>>
>>>> I obtained the WRF monthly averages by using UPP to convert the
WRF netCDF
>>>> files (.nc) to GRIBv1 files for every 3-hour interval. (This was
a lot of
>>>> files, and awkward to deal with!) I used copygb to convert all
of them to
>>>> the NARR observation grid (grid 221).
>>>> Then I used cdo to merge the files appropriate for each month and
compute
>>>> the monthly averages.
>>>>
>>>> The NARR provides GRIB files for every 3-hour interval, which
would again be
>>>> enormous. They also provide monthly averages as GRIBv1 files.
But if I try
>>>> to process these in MET, I get the following:
>>>>
>>>> -----
>>>> GSL_RNG_TYPE=mt19937
>>>> GSL_RNG_SEED=1243007566
>>>> Forecast File: sharc/d01_2004_mon_cp/monmean.grib
>>>> Observation File: narr/mon2004/narrmon-
a_221_20040101_0000_000.grb
>>>> Configuration File: config/GridStatConfig_WRFvsNARR
>>>>
>>>>
>>>> ERROR: read_pds() -> unexpected time range indicator of 113.
>>>> -----
>>>>
>>>> This "time range indicator" is described here:
>>>> http://www.nco.ncep.noaa.gov/pmb/docs/on388/table5.html
>>>>
>>>> to mean the average of N forecasts. Which is exactly right;
that's what I
>>>> want to compare. Why does MET reject this data? What is the
appropriate
>>>> way to compare monthly averages with MET? Any help would be very
>>>> appreciated. Thanks,
>>>>
>>>> __
>>>> Michael Biggs
>>>> Undergraduate Student Research Assistant
>>>> Waterloo Atmosphere-land Interactions Research Group (WatAIR)
>>>> University of Waterloo
>>>
>>>
>>>
>
>
>
------------------------------------------------
More information about the Met_help
mailing list