[Met_help] [rt.rap.ucar.edu #94808] History for regrid_data_plane help
John Halley Gotway via RT
met_help at ucar.edu
Mon Apr 27 17:34:47 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
My name is Michael Pletcher and I'm currently having an issue with MET's
regrid_data_plane tool. I'm using RAP initializations as my input file, and
the program is able to debug fully, but I'm getting the warning:
WARNING:
WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2 matching
records for "UGRD/R163.1":
WARNING: record 163 field 1: ipdtmpl[15] = 2, 2, 2, 0, 105, 0, 0, 1, 0,
100, 0, 85000, 255, 0, 0
WARNING: record 163 field 2: ipdtmpl[15] = 2, 3, 2, 0, 105, 0, 0, 1, 0,
100, 0, 85000, 255, 0, 0
WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
"GRIB2_ipdtmpl_val" config file options to select one.
WARNING:
DEBUG 2: Range of input data (name="UGRD"; level="R163.1";) is -15.2235 to
17.044.
DEBUG 2: Range of regridded data (name="UGRD"; level="R163.1";) is -12.9074
to 17.044.
Here, I'm attempting to regrid the 850 mb u component of wind, but
obviously there's no negative values of wind. I'm assuming that I'm getting
this warning because the range should be from 0 to xx.xxxx, but here it is
negative. Forgive me if this is not how I should be understanding it, but
should the range of the regridded data be 0 to 29.9514? I came up with this
by adding 12.9074 to 17.044.
Please let me know if you need anymore information.
Thanks,
Michael
--
Michael Pletcher
B.S. Candidate, Atmospheric & Oceanic Science / GIS Minor
University of Maryland, College Park Class of 2020
mpletch1 at terpmail.umd.edu|443-857-1127
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: regrid_data_plane help
From: John Halley Gotway
Time: Wed Apr 01 20:25:14 2020
Michael,
I'd strongly advise against setting level = "R163";
That tells MET to use data from GRIB record number 163 regardless of
what
the record number actually contains. Since you called it UGRD, MET
calls
it UGRD in the output. But the actual data is whatever happens to be
in
record number 163. We only use the record number when all else
fails...
and usually just for testing.
Instead, please try setting: *'name="UGRD"; level="P850";'*
That tells MET to search through the GRIB records looking for one with
a
pressure level value of 850.
Does that produce any better results?
Thanks,
John Halley Gotway
On Wed, Apr 1, 2020 at 8:08 PM Michael Pletcher via RT
<met_help at ucar.edu>
wrote:
>
> Wed Apr 01 20:08:37 2020: Request 94808 was acted upon.
> Transaction: Ticket created by mpletch1 at terpmail.umd.edu
> Queue: met_help
> Subject: regrid_data_plane help
> Owner: Nobody
> Requestors: mpletch1 at terpmail.umd.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94808 >
>
>
> Hello,
>
> My name is Michael Pletcher and I'm currently having an issue with
MET's
> regrid_data_plane tool. I'm using RAP initializations as my input
file, and
> the program is able to debug fully, but I'm getting the warning:
>
> WARNING:
> WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> records for "UGRD/R163.1":
> WARNING: record 163 field 1: ipdtmpl[15] = 2, 2, 2, 0, 105, 0, 0, 1,
0,
> 100, 0, 85000, 255, 0, 0
> WARNING: record 163 field 2: ipdtmpl[15] = 2, 3, 2, 0, 105, 0, 0, 1,
0,
> 100, 0, 85000, 255, 0, 0
> WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> "GRIB2_ipdtmpl_val" config file options to select one.
> WARNING:
> DEBUG 2: Range of input data (name="UGRD"; level="R163.1";) is
-15.2235 to
> 17.044.
> DEBUG 2: Range of regridded data (name="UGRD"; level="R163.1";) is
-12.9074
> to 17.044.
>
> Here, I'm attempting to regrid the 850 mb u component of wind, but
> obviously there's no negative values of wind. I'm assuming that I'm
getting
> this warning because the range should be from 0 to xx.xxxx, but here
it is
> negative. Forgive me if this is not how I should be understanding
it, but
> should the range of the regridded data be 0 to 29.9514? I came up
with this
> by adding 12.9074 to 17.044.
>
> Please let me know if you need anymore information.
>
> Thanks,
> Michael
> --
> Michael Pletcher
> B.S. Candidate, Atmospheric & Oceanic Science / GIS Minor
> University of Maryland, College Park Class of 2020
> mpletch1 at terpmail.umd.edu|443-857-1127
>
>
------------------------------------------------
Subject: regrid_data_plane help
From: Michael Pletcher
Time: Wed Apr 01 20:35:10 2020
John,
Thank you for the reply. After making those changes, I'm no longer
receiving any warnings, however, I am still getting the same values as
I
did before which are
DEBUG 2: Range of input data (name="UGRD"; level="P850";) is -15.2235
to
17.044.
DEBUG 2: Range of regridded data (name="UGRD"; level="P850";) is
-12.9074
to 17.044.
For context, I'm using Python to call the command as you can see
below.
import subprocess
output =
subprocess.call('/homes/metogra/mpletch1/ResearchProject/met/bin/regrid_data_plane
~/ResearchProject/grb2/rap_130_20180629_0000_000.grb2 \'latlon 701 301
20
-130 0.1 0.1 \' rap_test_ugrd.nc -field \'name="UGRD";
level="P850";\'',shell=True)
Let me know if there's anything you see that I could change.
Thanks,
Michael
On Wed, Apr 1, 2020 at 10:25 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Michael,
>
> I'd strongly advise against setting level = "R163";
>
> That tells MET to use data from GRIB record number 163 regardless of
what
> the record number actually contains. Since you called it UGRD, MET
calls
> it UGRD in the output. But the actual data is whatever happens to
be in
> record number 163. We only use the record number when all else
fails...
> and usually just for testing.
>
> Instead, please try setting: *'name="UGRD"; level="P850";'*
>
> That tells MET to search through the GRIB records looking for one
with a
> pressure level value of 850.
>
> Does that produce any better results?
>
> Thanks,
> John Halley Gotway
>
> On Wed, Apr 1, 2020 at 8:08 PM Michael Pletcher via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Wed Apr 01 20:08:37 2020: Request 94808 was acted upon.
> > Transaction: Ticket created by mpletch1 at terpmail.umd.edu
> > Queue: met_help
> > Subject: regrid_data_plane help
> > Owner: Nobody
> > Requestors: mpletch1 at terpmail.umd.edu
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94808 >
> >
> >
> > Hello,
> >
> > My name is Michael Pletcher and I'm currently having an issue with
MET's
> > regrid_data_plane tool. I'm using RAP initializations as my input
file,
> and
> > the program is able to debug fully, but I'm getting the warning:
> >
> > WARNING:
> > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
matching
> > records for "UGRD/R163.1":
> > WARNING: record 163 field 1: ipdtmpl[15] = 2, 2, 2, 0, 105, 0, 0,
1, 0,
> > 100, 0, 85000, 255, 0, 0
> > WARNING: record 163 field 2: ipdtmpl[15] = 2, 3, 2, 0, 105, 0, 0,
1, 0,
> > 100, 0, 85000, 255, 0, 0
> > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > "GRIB2_ipdtmpl_val" config file options to select one.
> > WARNING:
> > DEBUG 2: Range of input data (name="UGRD"; level="R163.1";) is
-15.2235
> to
> > 17.044.
> > DEBUG 2: Range of regridded data (name="UGRD"; level="R163.1";) is
> -12.9074
> > to 17.044.
> >
> > Here, I'm attempting to regrid the 850 mb u component of wind, but
> > obviously there's no negative values of wind. I'm assuming that
I'm
> getting
> > this warning because the range should be from 0 to xx.xxxx, but
here it
> is
> > negative. Forgive me if this is not how I should be understanding
it, but
> > should the range of the regridded data be 0 to 29.9514? I came up
with
> this
> > by adding 12.9074 to 17.044.
> >
> > Please let me know if you need anymore information.
> >
> > Thanks,
> > Michael
> > --
> > Michael Pletcher
> > B.S. Candidate, Atmospheric & Oceanic Science / GIS Minor
> > University of Maryland, College Park Class of 2020
> > mpletch1 at terpmail.umd.edu|443-857-1127
> >
> >
>
>
--
Michael Pletcher
B.S. Candidate, Atmospheric & Oceanic Science / GIS Minor
University of Maryland, College Park Class of 2020
mpletch1 at terpmail.umd.edu|443-857-1127
------------------------------------------------
Subject: regrid_data_plane help
From: John Halley Gotway
Time: Wed Apr 01 21:49:27 2020
Michael,
I think it’s very normal for the U and V wind component values to have
values in the range of (-15, 17). U > 0 indicates winds blowing from
west
to east while U < 0 indicates the opposite. The wind components can
be
positive/negative, but the wind speed should be strictly positive.
I always recommend that people run MET’s plot_data_plane tool to
visualize
their data to make sure its what they expect.
subprocess.call('/homes/metogra/mpletch1/ResearchProject/
met/bin/plot_data_plane
~/ResearchProject/grb2/rap_130
_20180629_0000_000.grb2
rap_test_ugrd.ps ‘field \'name="UGRD";
<http://rap_test_ugrd.nc>level="P850";\'',shell=True)
And then look at the resulting PostScript image file. If you’re still
unsure, you can double-check by plotting the data some other way...
like
Unidata’s IDV tool or using python.
Thanks,
John
On Wed, Apr 1, 2020 at 8:35 PM Michael Pletcher via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94808 >
>
> John,
>
> Thank you for the reply. After making those changes, I'm no longer
> receiving any warnings, however, I am still getting the same values
as I
> did before which are
>
> DEBUG 2: Range of input data (name="UGRD"; level="P850";) is
-15.2235 to
> 17.044.
> DEBUG 2: Range of regridded data (name="UGRD"; level="P850";) is
-12.9074
> to 17.044.
>
> For context, I'm using Python to call the command as you can see
below.
>
> import subprocess
>
> output =
>
>
subprocess.call('/homes/metogra/mpletch1/ResearchProject/met/bin/regrid_data_plane
> ~/ResearchProject/grb2/rap_130_20180629_0000_000.grb2 \'latlon 701
301 20
> -130 0.1 0.1 \' rap_test_ugrd.nc -field \'name="UGRD";
> level="P850";\'',shell=True)
>
> Let me know if there's anything you see that I could change.
>
> Thanks,
> Michael
>
> On Wed, Apr 1, 2020 at 10:25 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Michael,
> >
> > I'd strongly advise against setting level = "R163";
> >
> > That tells MET to use data from GRIB record number 163 regardless
of what
> > the record number actually contains. Since you called it UGRD,
MET calls
> > it UGRD in the output. But the actual data is whatever happens to
be in
> > record number 163. We only use the record number when all else
fails...
> > and usually just for testing.
> >
> > Instead, please try setting: *'name="UGRD"; level="P850";'*
> >
> > That tells MET to search through the GRIB records looking for one
with a
> > pressure level value of 850.
> >
> > Does that produce any better results?
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Wed, Apr 1, 2020 at 8:08 PM Michael Pletcher via RT <
> met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Wed Apr 01 20:08:37 2020: Request 94808 was acted upon.
> > > Transaction: Ticket created by mpletch1 at terpmail.umd.edu
> > > Queue: met_help
> > > Subject: regrid_data_plane help
> > > Owner: Nobody
> > > Requestors: mpletch1 at terpmail.umd.edu
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94808
> >
> > >
> > >
> > > Hello,
> > >
> > > My name is Michael Pletcher and I'm currently having an issue
with
> MET's
> > > regrid_data_plane tool. I'm using RAP initializations as my
input file,
> > and
> > > the program is able to debug fully, but I'm getting the warning:
> > >
> > > WARNING:
> > > WARNING: MetGrib2DataFile::data_plane() -> Using the first of 2
> matching
> > > records for "UGRD/R163.1":
> > > WARNING: record 163 field 1: ipdtmpl[15] = 2, 2, 2, 0, 105, 0,
0, 1, 0,
> > > 100, 0, 85000, 255, 0, 0
> > > WARNING: record 163 field 2: ipdtmpl[15] = 2, 3, 2, 0, 105, 0,
0, 1, 0,
> > > 100, 0, 85000, 255, 0, 0
> > > WARNING: Try setting the 0-based "GRIB2_ipdtmpl_index" and
> > > "GRIB2_ipdtmpl_val" config file options to select one.
> > > WARNING:
> > > DEBUG 2: Range of input data (name="UGRD"; level="R163.1";) is
-15.2235
> > to
> > > 17.044.
> > > DEBUG 2: Range of regridded data (name="UGRD"; level="R163.1";)
is
> > -12.9074
> > > to 17.044.
> > >
> > > Here, I'm attempting to regrid the 850 mb u component of wind,
but
> > > obviously there's no negative values of wind. I'm assuming that
I'm
> > getting
> > > this warning because the range should be from 0 to xx.xxxx, but
here it
> > is
> > > negative. Forgive me if this is not how I should be
understanding it,
> but
> > > should the range of the regridded data be 0 to 29.9514? I came
up with
> > this
> > > by adding 12.9074 to 17.044.
> > >
> > > Please let me know if you need anymore information.
> > >
> > > Thanks,
> > > Michael
> > > --
> > > Michael Pletcher
> > > B.S. Candidate, Atmospheric & Oceanic Science / GIS Minor
> > > University of Maryland, College Park Class of 2020
> > > mpletch1 at terpmail.umd.edu|443-857-1127
> > >
> > >
> >
> >
>
> --
> Michael Pletcher
> B.S. Candidate, Atmospheric & Oceanic Science / GIS Minor
> University of Maryland, College Park Class of 2020
> mpletch1 at terpmail.umd.edu|443-857-1127
>
>
------------------------------------------------
More information about the Met_help
mailing list