[Met_help] [rt.rap.ucar.edu #96092] History for Regrid Data Plane Issue
John Halley Gotway via RT
met_help at ucar.edu
Mon Aug 3 10:41:03 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Met Help:
I am trying to use the regrid_data_plane command and am getting the
following error:
/opt/MET6/met6.0/bin/regrid_data_plane pr_bcp06m_2020071006f006.grib2
urma_pr_2p5km_qpe06_2020073000.grib2 pr_data_1p25km.nc -field 'name="APCP";
level="R1";'
DEBUG 1: Reading data file: ../pr_bcp06m_2020071006f006.grib2
DEBUG 2: Input grid: Projection: Mercator Nx: 157 Ny: 109 Lat_LL_radians:
0.2738 Lon_LL_radians: 1.2238 Lat_UR_radians: 0.3585 Lon_UR_radians: 1.0950
Mx: 1211.1301 My: 1212.1858 Bx: 1482.2112 By: -336.1759
ERROR :
ERROR : MetGrib2DataFile::read_grib2_record_list() -> accum valid time
unexpectedly set for record 1 field 1
ERROR :
DEBUG 1: Input File: ../urma_pr_2p5km_qpe06_2020073000.grib2
DEBUG 1: Mask File: pr_data_1p25km.nc
ERROR :
ERROR : MetGrib2DataFile::read_grib2_record_list() -> accum valid time
unexpectedly set for record 1 field 1
ERROR :
I've attached both grib2 files listed in the command. We cannot figure out
what is wrong with the urma_pr_2p5km_qpe grib2 file that would cause this
error. We use similar files for CONUS URMA in other processes and do not
encounter the error. Do you have any suggestions on what to try?
Thanks,
Ben
--
Benjamin Albright, Phd.
Meteorological Developer
Systems Research Group, Inc. at NOAA/NWS/Weather Prediction Center
Work email: benjamin.albright at noaa.gov
Work phone: 301-683-1474
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Regrid Data Plane Issue
From: John Halley Gotway
Time: Mon Aug 03 10:15:16 2020
Hi Ben,
I see you're having an issue running regrid_data_plane on GRIB2 inputs
using MET version 6.0. I can tell you that when I run your command
using
the most recent released version of MET (version 9.0), it all works
fine
and produces the attached plot:
*regrid_data_plane pr_bcp06m_2020071006f006.grib2
urma_pr_2p5km_qpe06_2020073000.grib2 pr_data_1p25km.nc
<http://pr_data_1p25km.nc> -field 'name="APCP"; level="Z0";'*
*plot_data_plane pr_data_1p25km.nc <http://pr_data_1p25km.nc>
pr_data_1p25km.ps <http://pr_data_1p25km.ps> 'name="APCP_00_Z0";
level="(*,*)";'*
So a couple of points. MET version 6.0 was released in 2017, and I'm
sure
that the issue you're seeing was found/fixed sometime in the last 3
years.
The best solution would be upgrading to the latest version of MET...
or
wait until later this week when we should be releasing MET version
9.1.
But to your question, what's the issue with the input datasets? I
really
don't think it's a problem with the URMA input. Instead, it's an issue
with
the pr_bcp06m_2020071006f006.grib2 file... as seen by running wgrib2
on
both of those files:
*wgrib2 urma_pr_2p5km_qpe06_2020073000.grib2
1:0:d=2020072918:APCP:surface:0-6 hour acc fcst:*
*wgrib2 pr_bcp06m_2020071006f006.grib2 1:0:d=2020071006:APCP:surface -
surface:Code Table 4.11=255:*
I'm guessing that MET version 6.0 is expecting the APCP record to
define an
accumulation interval. In the case of URMA, that's 0 to 6 hours. For
the
pr_bcp06m data, it's not listed. To find the precise set of bytes that
are
problematic, you'd need to pour over the GRIB2 documentation:
https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/
Hope that helps.
Thanks,
John Halley Gotway
On Mon, Aug 3, 2020 at 9:24 AM Benjamin Albright - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> Mon Aug 03 09:24:01 2020: Request 96092 was acted upon.
> Transaction: Ticket created by benjamin.albright at noaa.gov
> Queue: met_help
> Subject: Regrid Data Plane Issue
> Owner: Nobody
> Requestors: benjamin.albright at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96092 >
>
>
> Met Help:
>
> I am trying to use the regrid_data_plane command and am getting the
> following error:
>
> /opt/MET6/met6.0/bin/regrid_data_plane
pr_bcp06m_2020071006f006.grib2
> urma_pr_2p5km_qpe06_2020073000.grib2 pr_data_1p25km.nc -field
> 'name="APCP";
> level="R1";'
>
> DEBUG 1: Reading data file: ../pr_bcp06m_2020071006f006.grib2
> DEBUG 2: Input grid: Projection: Mercator Nx: 157 Ny: 109
Lat_LL_radians:
> 0.2738 Lon_LL_radians: 1.2238 Lat_UR_radians: 0.3585 Lon_UR_radians:
1.0950
> Mx: 1211.1301 My: 1212.1858 Bx: 1482.2112 By: -336.1759
> ERROR :
> ERROR : MetGrib2DataFile::read_grib2_record_list() -> accum valid
time
> unexpectedly set for record 1 field 1
> ERROR :
> DEBUG 1: Input File: ../urma_pr_2p5km_qpe06_2020073000.grib2
> DEBUG 1: Mask File: pr_data_1p25km.nc
> ERROR :
> ERROR : MetGrib2DataFile::read_grib2_record_list() -> accum valid
time
> unexpectedly set for record 1 field 1
> ERROR :
>
> I've attached both grib2 files listed in the command. We cannot
figure out
> what is wrong with the urma_pr_2p5km_qpe grib2 file that would cause
this
> error. We use similar files for CONUS URMA in other processes and do
not
> encounter the error. Do you have any suggestions on what to try?
>
> Thanks,
> Ben
>
> --
> Benjamin Albright, Phd.
> Meteorological Developer
> Systems Research Group, Inc. at NOAA/NWS/Weather Prediction Center
> Work email: benjamin.albright at noaa.gov
> Work phone: 301-683-1474
>
>
------------------------------------------------
Subject: Regrid Data Plane Issue
From: Benjamin Albright - NOAA Affiliate
Time: Mon Aug 03 10:37:59 2020
Thanks for the quick response John. I did link the script to a newer
version of MET (9.0) and it also worked for me. Appreciate the help!
Ben
On Mon, Aug 3, 2020 at 12:15 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Hi Ben,
>
> I see you're having an issue running regrid_data_plane on GRIB2
inputs
> using MET version 6.0. I can tell you that when I run your command
using
> the most recent released version of MET (version 9.0), it all works
fine
> and produces the attached plot:
>
>
> *regrid_data_plane pr_bcp06m_2020071006f006.grib2
> urma_pr_2p5km_qpe06_2020073000.grib2 pr_data_1p25km.nc
> <http://pr_data_1p25km.nc> -field 'name="APCP"; level="Z0";'*
> *plot_data_plane pr_data_1p25km.nc <http://pr_data_1p25km.nc>
> pr_data_1p25km.ps <http://pr_data_1p25km.ps> 'name="APCP_00_Z0";
> level="(*,*)";'*
>
> So a couple of points. MET version 6.0 was released in 2017, and I'm
sure
> that the issue you're seeing was found/fixed sometime in the last 3
years.
> The best solution would be upgrading to the latest version of MET...
or
> wait until later this week when we should be releasing MET version
9.1.
>
> But to your question, what's the issue with the input datasets? I
really
> don't think it's a problem with the URMA input. Instead, it's an
issue with
> the pr_bcp06m_2020071006f006.grib2 file... as seen by running wgrib2
on
> both of those files:
>
>
>
> *wgrib2 urma_pr_2p5km_qpe06_2020073000.grib2
> 1:0:d=2020072918:APCP:surface:0-6 hour acc fcst:*
>
> *wgrib2 pr_bcp06m_2020071006f006.grib2 1:0:d=2020071006:APCP:surface
-
> surface:Code Table 4.11=255:*
>
> I'm guessing that MET version 6.0 is expecting the APCP record to
define an
> accumulation interval. In the case of URMA, that's 0 to 6 hours. For
the
> pr_bcp06m data, it's not listed. To find the precise set of bytes
that are
> problematic, you'd need to pour over the GRIB2 documentation:
> https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/
>
> Hope that helps.
>
> Thanks,
> John Halley Gotway
>
> On Mon, Aug 3, 2020 at 9:24 AM Benjamin Albright - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Mon Aug 03 09:24:01 2020: Request 96092 was acted upon.
> > Transaction: Ticket created by benjamin.albright at noaa.gov
> > Queue: met_help
> > Subject: Regrid Data Plane Issue
> > Owner: Nobody
> > Requestors: benjamin.albright at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=96092 >
> >
> >
> > Met Help:
> >
> > I am trying to use the regrid_data_plane command and am getting
the
> > following error:
> >
> > /opt/MET6/met6.0/bin/regrid_data_plane
pr_bcp06m_2020071006f006.grib2
> > urma_pr_2p5km_qpe06_2020073000.grib2 pr_data_1p25km.nc -field
> > 'name="APCP";
> > level="R1";'
> >
> > DEBUG 1: Reading data file: ../pr_bcp06m_2020071006f006.grib2
> > DEBUG 2: Input grid: Projection: Mercator Nx: 157 Ny: 109
Lat_LL_radians:
> > 0.2738 Lon_LL_radians: 1.2238 Lat_UR_radians: 0.3585
Lon_UR_radians:
> 1.0950
> > Mx: 1211.1301 My: 1212.1858 Bx: 1482.2112 By: -336.1759
> > ERROR :
> > ERROR : MetGrib2DataFile::read_grib2_record_list() -> accum valid
time
> > unexpectedly set for record 1 field 1
> > ERROR :
> > DEBUG 1: Input File: ../urma_pr_2p5km_qpe06_2020073000.grib2
> > DEBUG 1: Mask File: pr_data_1p25km.nc
> > ERROR :
> > ERROR : MetGrib2DataFile::read_grib2_record_list() -> accum valid
time
> > unexpectedly set for record 1 field 1
> > ERROR :
> >
> > I've attached both grib2 files listed in the command. We cannot
figure
> out
> > what is wrong with the urma_pr_2p5km_qpe grib2 file that would
cause this
> > error. We use similar files for CONUS URMA in other processes and
do not
> > encounter the error. Do you have any suggestions on what to try?
> >
> > Thanks,
> > Ben
> >
> > --
> > Benjamin Albright, Phd.
> > Meteorological Developer
> > Systems Research Group, Inc. at NOAA/NWS/Weather Prediction Center
> > Work email: benjamin.albright at noaa.gov
> > Work phone: 301-683-1474
> >
> >
>
>
--
Benjamin Albright, Phd.
Meteorological Developer
Systems Research Group, Inc. at NOAA/NWS/Weather Prediction Center
Work email: benjamin.albright at noaa.gov
Work phone: 301-683-1474
------------------------------------------------
More information about the Met_help
mailing list