[Met_help] [rt.rap.ucar.edu #90553] History for

Tue Jul 9 11:41:30 MDT 2019

----------------------------------------------------------------
  Initial Request
----------------------------------------------------------------

Hi,

I am trying to use plot_data_plane to check a file that I would like to
later run through grid stat. It produces a strange plot, and I think
something is wrong. Also, it complains that it finds VIS twice in the file,
but wgrib2 shows it only once. Any idea what is going on?

Files are on /scratch/tressa

Thanks,

Tressa

plot_data_plane 20190401_000000.grb2 /scratch/tressa/testplot1.ps
'name="VIS";level="R001";' -v 4

DEBUG 1: Reading user-defined grib2 MET_GRIB_TABLES file:
/home/tressa/grib2_local.txt

DEBUG 1: Opening data file: 20190401_000000.grb2

DEBUG 4: Met2dDataFileFactory::new_met_2d_data_file() -> created new
Met2dDataFile object of type "FileType_Gb2".

DEBUG 4: Switching the GRIB2 radius of the earth value of 6371.23 km to
6371.2 km for internal consistency.

DEBUG 4:

DEBUG 4: Latitude/Longitude Grid Data:

DEBUG 4:      lat_ll: 30

DEBUG 4:      lon_ll: -143.517

DEBUG 4:   delta_lat: 0.081237

DEBUG 4:   delta_lon: 0.020309

DEBUG 4:        Nlat: 739

DEBUG 4:        Nlon: 7575

DEBUG 4:

DEBUG 4: VarInfoFactory::new_var_info() -> created new VarInfo object of
type "FileType_Gb2".

DEBUG 3:

DEBUG 3: Multiple GRIB2 table entries match lookup criteria (parm_name =
VIS):

DEBUG 3:   parm_name: VIS, index_a = 0, grib2_mtab = 1, grib2_cntr = 0,
grib2_ltab = 0, index_b = 19, index_c = 0

DEBUG 3:   parm_name: VIS, index_a = 0, grib2_mtab = 14, grib2_cntr = 57,
grib2_ltab = 0, index_b = 19, index_c = 0

DEBUG 3: Using the first match found:   parm_name: VIS, index_a = 0,
grib2_mtab = 1, grib2_cntr = 0, grib2_ltab = 0, index_b = 19, index_c = 0

DEBUG 3:

WARNING:

WARNING: MetGrib2DataFile::data_plane() - Multiple matching records found
for 'VIS/R1' - 1, 1 - using 1

WARNING:

DEBUG 3: MetGrib2DataFile::data_plane() - Found exact match for 'VIS/R1' in
GRIB2 record 1 field 1 of GRIB2 file '20190401_000000.grb2'

DEBUG 4:

DEBUG 4: Data plane information:

DEBUG 4:       plane min: 0

DEBUG 4:       plane max: 24.997

DEBUG 4:       scan mode: 64

DEBUG 4:      valid time: 20190401_020000

DEBUG 4:       lead time: 020000

DEBUG 4:       init time: 20190401_000000

DEBUG 4:     bitmap flag: 0

DEBUG 4: DEBUG 1: Creating postscript file: /scratch/tressa/testplot1.ps

DEBUG 4: draw_map() -> Plotting map data file:
/usr/local/met-8.0/share/met/map/country_data

DEBUG 4: draw_map() -> Plotting map data file:
/usr/local/met-8.0/share/met/map/usa_state_data

DEBUG 4: draw_map() -> Plotting map data file:
/usr/local/met-8.0/share/met/map/major_lakes_data

redoubt:/d1/ceiling/alaska/raw/rap_reproj_cal_242/grib2/calibrated/20190401>
wgrib2 20190401_000000.grb2

1.1:0:d=2019040100:CEIL:local level type 215 0.1:2 hour fcst:

1.2:0:d=2019040100:VIS:surface:2 hour fcst:

----------------------------------------------------------------
  Complete Ticket History
----------------------------------------------------------------

Subject: 
From: John Halley Gotway
Time: Tue Jun 11 12:26:56 2019

Tressa,

I see you're having trouble with plot_data_plane on this GRIB2 file.
This
is actually pretty interesting.  The GRIB2 file format allows for each
record to contain multiple "fields".  However in practice, we've never
seen
that.  In all the NOAA-produced GRIB2 files, each record contains a
single
field.  This is seen in the wgrib2 output:

wgrib2 20190401_000000.grb2
1.1:0:d=2019040100:CEIL:local level type 215 0.1:2 hour fcst:
1.2:0:d=2019040100:VIS:surface:2 hour fcst:

1.1 and 1.2 mean fields 1 and 2 of the first record.  When you request
'level="R001";' that's requesting record number 1.  Both fields match
because they're both part of record number 1.  Since the visibility is
listed as the "surface", you can request 'level="Z0";' (i.e. vertical
level
height of 0) instead:

/usr/local/met-8.0/bin/plot_data_plane 20190401_000000.grb2
testplot1.ps
'name="VIS";level="Z0";' -v 2

And that runs without a warning.  But the resulting image (attached)
looks
a bit suspicious.  That grid looks really wide and flat.  But that
does
seem to match the grid definition in the wgrib2 output:

wgrib2 -V 20190401_000000.grb2

1.2:0:vt=2019040102:surface:2 hour fcst:VIS Visibility [m]:
    ndata=5597925:undef=4359165:mean=5.96557:min=0:max=9.94
    grid_template=0:winds(grid):
        lat-lon grid:(7575 x 739) units 1e-06 input WE:SN output WE:SN
res
56
        lat 30.000000 to 89.953064 by 0.081237
        lon 143.517264 to 297.339904 by 0.020309 #points=5597925

The lat's are 0.08 degrees apart while the lon's are 0.02 degrees
apart.

Is this the grid you're expecting?  And do you know why the data
producer
included 2 fields in one record instead of using 2 records?  Perhaps
they
don't realize that this is happening?

Thanks,
John

On Tue, Jun 11, 2019 at 11:18 AM Randy Bullock via RT
<met_help at ucar.edu>
wrote:

>
> Tue Jun 11 11:18:43 2019: Request 90553 was acted upon.
> Transaction: Given to johnhg (John Halley Gotway) by bullock
>        Queue: met_help
>      Subject: (No subject given)
>        Owner: johnhg
>   Requestors: tressa at ucar.edu
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=90553 >
>
>
> This transaction appears to have no content
>

------------------------------------------------