[Met_help] [rt.rap.ucar.edu #86299] History for problems in regridding

John Halley Gotway via RT met_help at ucar.edu
Thu Jul 26 09:55:38 MDT 2018


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

Dear MET helpdesk,
I'm writing to ask some help in regridding files from MRMS to stageIV
resolution.
I'm working on Theia and I have the MRMS files
in /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data

if I'm doing wgrib2 of one file:

[Francesca.Viterbo at tfe05 MRMS_data]$ wgrib2
GaugeCorrQPE01H201805270100.grib2
1:0:d=2018052701:var discipline=209 master_table=255 parmcat=6 parm=9:0 m
above mean sea level:anl:


For this reason I was doing the following command:

regrid_data_plane GaugeCorrQPE01H201805270200.grib2
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
prova_cut.nc -field 'GRIB2_disc=209; GRIB2_parm_cat=6;
GRIB2_parm=9;level="L0";'


but I get the following error:

[Francesca.Viterbo at tfe05 MRMS_data]$ regrid_data_plane
GaugeCorrQPE01H201805270200.grib2
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
prova_cut.nc -field 'GRIB2_disc=209; GRIB2_parm_cat=6;
GRIB2_parm=9;level="L0";'
DEBUG 1: Reading data file: GaugeCorrQPE01H201805270200.grib2
DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll: 20.005
lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107 Lat_LL:
37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone: 0.623 Bx:
-505.8243 By: 2643.0009
DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
SQUARE, vld_thresh = 0.5
ERROR  :
ERROR  : VarInfoGrib2::set_dict() -> no parameter found with matching
GRIB2_disc (209) GRIB2_parm_cat (6) GRIB2_parm (9). Use the MET_GRIB_TABLES
environment variable to define custom GRIB tables.
ERROR  :


How can I solve the problem?

Thank you,
Francesca



-- 
-- 
Francesca Viterbo, Ph.D.
Physical Sciences Division
NOAA Earth System Research Laboratory
R/PSD2, 325 Broadway
Boulder, CO 80305-3337
303-497-6702
francesca.viterbo at noaa.gov


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

Subject: problems in regridding
From: John Halley Gotway
Time: Mon Jul 23 10:25:39 2018

Francesa,

I see you're having issues using MRMS data in MET.  Hopefully, we can
get
this all sorted out.

Unfortunately, the version of wgrib2 on theia is too old:
   module load wgrib2
   wgrib2 -version
   v0.2.0.1 7/2014

That version from 2014 does not include definitions for the MRMS data,
and
so you get a listing of the identifying parameter numbers:
   wgrib2 GaugeCorrQPE01H201805270100.grib2
   1:0:d=2018052701:var discipline=209 master_table=255 parmcat=6
parm=9:0
m above mean sea level:anl:

I copied that sample file down to my local machine which has a newer
version of wgrib2 from 2015:
   wgrib2 -version
   v0.2.0.3 11/2015

Running that sample file through the new version reveals:
   wgrib2 GaugeCorrQPE01H201805270100.grib2
   1:0:d=2018052701:GaugeCorrQPE01H:0 m above mean sea level:anl:

MET version 7.0 does include support for MRMS GRIB files, and that
table
can be seen here:
   /contrib/met/7.0/share/met/table_files/grib2_mrms.txt

So running regrid_data_plane as follows should work:
   regrid_data_plane \

/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
\

/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc \
   prova_cut.nc \
   -field 'name="GaugeCorrQPE01H"; level="Z0";'

***BUT*** I've found a problem in how met-7.0 is compiled on theia.  I
see
the following warning message:
   libpng warning: Application built with libpng-1.5.13 but running
with
1.6.34

This basically means that MET is not reading data values correctly
from the
GRIB2 file.  So while you'll get an output file, it'll contain bad
data.

We'll recompile met-7.0 as needed to get this issue resolved and will
let
you know when it's ready.

Thanks,
John Halley Gotway

------------------------------------------------
Subject: problems in regridding
From: John Halley Gotway
Time: Mon Jul 23 10:44:25 2018

Francesca,

One more detail here.  The command you ran *should* have worked just
fine.
But I found a pesky little bug in the code that was preventing it from
working.  Using the current version of the code, you'd also have to
explicitly specify the master table, center, and local table numbers.

Run wgrib2 with the -varX option:

wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
1:0:var209_255_1_161_6_9
Where you interpret these numbers as:
 -varX            inv         raw variable name - discipline mastertab
localtab center parmcat parmnum

So here's the field string that will work with the current version:
   -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
GRIB2_cntr=161;
GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'

I've fixed the little bug in the development version of the code, and
it'll
be included in the next release.  If needed, we could also post a
bugfix
for met-7.0.  Just let me know you're preference.

And we still need to resolve the libpng linker issue...

Thanks,
John

On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT <
met_help at ucar.edu> wrote:

>
> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
> Transaction: Given to johnhg (John Halley Gotway) by RT_System
>        Queue: met_help
>      Subject: problems in regridding
>        Owner: johnhg
>   Requestors: francesca.viterbo at noaa.gov
>       Status: new
>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299 >
>
>
> This transaction appears to have no content
>

------------------------------------------------
Subject: problems in regridding
From: John Halley Gotway
Time: Mon Jul 23 11:44:31 2018

Francesca,

Good news, my colleague recompiled met-7.0 on theia and the libpng
issue
should now be fixed.  Here's a plot_data_plane command you can run to
visualize this data:

  module use /contrib/modulefiles
  module load met/7.0
  plot_data_plane \

/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
\
   GaugeCorrQPE01H201805270100.ps \
   'name="GaugeCorrQPE01H"; level="Z0";'

But there's one thing to be very careful about with MRMS data.  The
areas
of bad data near the edge of the domain are encoded as a real data
value of
-3.  The data producers do not do a good job indicating this as bad
data.
MET will treat these -3 values as valid data and include them in the
statistics... unless you tell it not to.  You can tell it to treat is
as
bad data by "censoring" the data like this:

  plot_data_plane \

/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
\
   GaugeCorrQPE01H201805270100.ps \
   'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
censor_val=-9999;'

The 'censor_thresh=eq-3; censor_val=-9999' options tell MET to replace
any
values of -3 with a new value of -9999, which is MET's internal value
for
bad data.  A png version of the resulting plot is attached.  The dark
gray
areas over the edge of the domain are now being treated as bad data in
MET.

Thanks,
John


On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway <johnhg at ucar.edu>
wrote:

> Francesca,
>
> One more detail here.  The command you ran *should* have worked just
> fine.  But I found a pesky little bug in the code that was
preventing it
> from working.  Using the current version of the code, you'd also
have to
> explicitly specify the master table, center, and local table
numbers.
>
> Run wgrib2 with the -varX option:
>
> wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
> 1:0:var209_255_1_161_6_9
> Where you interpret these numbers as:
>  -varX            inv         raw variable name - discipline
mastertab
> localtab center parmcat parmnum
>
> So here's the field string that will work with the current version:
>    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
GRIB2_cntr=161;
> GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>
> I've fixed the little bug in the development version of the code,
and
> it'll be included in the next release.  If needed, we could also
post a
> bugfix for met-7.0.  Just let me know you're preference.
>
> And we still need to resolve the libpng linker issue...
>
> Thanks,
> John
>
> On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
>> Transaction: Given to johnhg (John Halley Gotway) by RT_System
>>        Queue: met_help
>>      Subject: problems in regridding
>>        Owner: johnhg
>>   Requestors: francesca.viterbo at noaa.gov
>>       Status: new
>>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299 >
>>
>>
>> This transaction appears to have no content
>>
>

------------------------------------------------
Subject: problems in regridding
From: francesca.viterbo at noaa.gov
Time: Mon Jul 23 16:51:08 2018

Hi John,
thank you very much for your help and for compiling again for the bug
issue. I was following your updates but I didn't have time to try the
suggestion yet because my monday was full of meetings.
I will try this and let you know how it goes.


On Mon, Jul 23, 2018 at 11:44 AM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:

> Francesca,
>
> Good news, my colleague recompiled met-7.0 on theia and the libpng
issue
> should now be fixed.  Here's a plot_data_plane command you can run
to
> visualize this data:
>
>   module use /contrib/modulefiles
>   module load met/7.0
>   plot_data_plane \
>
> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/
> GaugeCorrQPE01H201805270100.grib2
> \
>    GaugeCorrQPE01H201805270100.ps \
>    'name="GaugeCorrQPE01H"; level="Z0";'
>
> But there's one thing to be very careful about with MRMS data.  The
areas
> of bad data near the edge of the domain are encoded as a real data
value of
> -3.  The data producers do not do a good job indicating this as bad
data.
> MET will treat these -3 values as valid data and include them in the
> statistics... unless you tell it not to.  You can tell it to treat
is as
> bad data by "censoring" the data like this:
>
>   plot_data_plane \
>
> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/
> GaugeCorrQPE01H201805270100.grib2
> \
>    GaugeCorrQPE01H201805270100.ps \
>    'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
> censor_val=-9999;'
>
> The 'censor_thresh=eq-3; censor_val=-9999' options tell MET to
replace any
> values of -3 with a new value of -9999, which is MET's internal
value for
> bad data.  A png version of the resulting plot is attached.  The
dark gray
> areas over the edge of the domain are now being treated as bad data
in MET.
>
> Thanks,
> John
>
>
> On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
> > Francesca,
> >
> > One more detail here.  The command you ran *should* have worked
just
> > fine.  But I found a pesky little bug in the code that was
preventing it
> > from working.  Using the current version of the code, you'd also
have to
> > explicitly specify the master table, center, and local table
numbers.
> >
> > Run wgrib2 with the -varX option:
> >
> > wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
> > 1:0:var209_255_1_161_6_9
> > Where you interpret these numbers as:
> >  -varX            inv         raw variable name - discipline
mastertab
> > localtab center parmcat parmnum
> >
> > So here's the field string that will work with the current
version:
> >    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
GRIB2_cntr=161;
> > GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
> >
> > I've fixed the little bug in the development version of the code,
and
> > it'll be included in the next release.  If needed, we could also
post a
> > bugfix for met-7.0.  Just let me know you're preference.
> >
> > And we still need to resolve the libpng linker issue...
> >
> > Thanks,
> > John
> >
> > On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT <
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
> >> Transaction: Given to johnhg (John Halley Gotway) by RT_System
> >>        Queue: met_help
> >>      Subject: problems in regridding
> >>        Owner: johnhg
> >>   Requestors: francesca.viterbo at noaa.gov
> >>       Status: new
> >>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299 >
> >>
> >>
> >> This transaction appears to have no content
> >>
> >
>
>


--
--
Francesca Viterbo, Ph.D.
Physical Sciences Division
NOAA Earth System Research Laboratory
R/PSD2, 325 Broadway
Boulder, CO 80305-3337
303-497-6702
francesca.viterbo at noaa.gov

------------------------------------------------
Subject: problems in regridding
From: francesca.viterbo at noaa.gov
Time: Mon Jul 23 17:48:43 2018

Dear John,
I've starting trying to regrid using met version 6.1 on Theia using
the
command you mentioned in the email:

regrid_data_plane GaugeCorrQPE01H201805270200.grib2
/scratch4/NCEPDEV/ohd/
Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
NWM/MRMS_cut_data/prova_cut.nc -field 'GRIB2_disc=209; GRIB2_mtab=255;
GRIB2_ltab=1; GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9;
level="Z0";'

and I get it regridded, but with

libpng warning: Application built with libpng-1.5.13 but running with
1.6.34

also for v6.1

I'm worried because I did my previous regrids (for other Stage IV to
HRRR
in my paper) using v6.1 regrid data plane. does it mean that all that
regridded data I performed the analysis on are potentially wrong?


I have tried to run the same command for version 6.1 and 7.0 and
actually I
got the warning only for version 6.1... And the two files differs. If
i use
the command for v7.0 I have my problem solved. But now I'm concerned
for my
previous regrids with 6.1 and HRRR data.


COMMAND for V6.1

regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc prova_cut_6.9.nc -field
'name="GaugeCorrQPE01H";
level="Z0";'

DEBUG 1: Reading data file:
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2

DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll:
20.005
lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010

DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
Lat_LL:
37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone: 0.623
Bx:
-505.8243 By: 2643.0009

DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
SQUARE, vld_thresh = 0.5

libpng warning: Application built with libpng-1.5.13 but running with
1.6.34

DEBUG 2: Range of input data (name="GaugeCorrQPE01H"; level="Z0";) is
-3 to
-3.

DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H"; level="Z0";)
is
-3 to -3.

DEBUG 1: Writing output file: prova_cut_6.9.nc


COMMAND for V7.0

regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc prova_cut_7.0.nc -field
'name="GaugeCorrQPE01H";
level="Z0";'

DEBUG 1: Reading data file:
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2

DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll:
20.005
lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010

DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
Lat_LL:
37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone: 0.623
Bx:
-505.8243 By: 2643.0009

DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
SQUARE, vld_thresh = 0.5

DEBUG 2: Range of input data (name="GaugeCorrQPE01H"; level="Z0";) is
-3 to
54.9.

DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H"; level="Z0";)
is 0
to 21.

DEBUG 1: Writing output file: prova_cut_7.0.nc


Thank you very much,
Francesca




Thank you very much,
Francesca

On Mon, Jul 23, 2018 at 4:51 PM, Francesca Viterbo - NOAA Affiliate <
francesca.viterbo at noaa.gov> wrote:

> Hi John,
> thank you very much for your help and for compiling again for the
bug
> issue. I was following your updates but I didn't have time to try
the
> suggestion yet because my monday was full of meetings.
> I will try this and let you know how it goes.
>
>
> On Mon, Jul 23, 2018 at 11:44 AM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Francesca,
>>
>> Good news, my colleague recompiled met-7.0 on theia and the libpng
issue
>> should now be fixed.  Here's a plot_data_plane command you can run
to
>> visualize this data:
>>
>>   module use /contrib/modulefiles
>>   module load met/7.0
>>   plot_data_plane \
>>
>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_
>> data/GaugeCorrQPE01H201805270100.grib2
>> \
>>    GaugeCorrQPE01H201805270100.ps \
>>    'name="GaugeCorrQPE01H"; level="Z0";'
>>
>> But there's one thing to be very careful about with MRMS data.  The
areas
>> of bad data near the edge of the domain are encoded as a real data
value
>> of
>> -3.  The data producers do not do a good job indicating this as bad
data.
>> MET will treat these -3 values as valid data and include them in
the
>> statistics... unless you tell it not to.  You can tell it to treat
is as
>> bad data by "censoring" the data like this:
>>
>>   plot_data_plane \
>>
>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_
>> data/GaugeCorrQPE01H201805270100.grib2
>> \
>>    GaugeCorrQPE01H201805270100.ps \
>>    'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
>> censor_val=-9999;'
>>
>> The 'censor_thresh=eq-3; censor_val=-9999' options tell MET to
replace any
>> values of -3 with a new value of -9999, which is MET's internal
value for
>> bad data.  A png version of the resulting plot is attached.  The
dark gray
>> areas over the edge of the domain are now being treated as bad data
in
>> MET.
>>
>> Thanks,
>> John
>>
>>
>> On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway
<johnhg at ucar.edu>
>> wrote:
>>
>> > Francesca,
>> >
>> > One more detail here.  The command you ran *should* have worked
just
>> > fine.  But I found a pesky little bug in the code that was
preventing it
>> > from working.  Using the current version of the code, you'd also
have to
>> > explicitly specify the master table, center, and local table
numbers.
>> >
>> > Run wgrib2 with the -varX option:
>> >
>> > wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
>> > 1:0:var209_255_1_161_6_9
>> > Where you interpret these numbers as:
>> >  -varX            inv         raw variable name - discipline
mastertab
>> > localtab center parmcat parmnum
>> >
>> > So here's the field string that will work with the current
version:
>> >    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
GRIB2_cntr=161;
>> > GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>> >
>> > I've fixed the little bug in the development version of the code,
and
>> > it'll be included in the next release.  If needed, we could also
post a
>> > bugfix for met-7.0.  Just let me know you're preference.
>> >
>> > And we still need to resolve the libpng linker issue...
>> >
>> > Thanks,
>> > John
>> >
>> > On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT <
>> > met_help at ucar.edu> wrote:
>> >
>> >>
>> >> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
>> >> Transaction: Given to johnhg (John Halley Gotway) by RT_System
>> >>        Queue: met_help
>> >>      Subject: problems in regridding
>> >>        Owner: johnhg
>> >>   Requestors: francesca.viterbo at noaa.gov
>> >>       Status: new
>> >>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299
>> >
>> >>
>> >>
>> >> This transaction appears to have no content
>> >>
>> >
>>
>>
>
>
> --
> --
> Francesca Viterbo, Ph.D.
> Physical Sciences Division
> NOAA Earth System Research Laboratory
> R/PSD2, 325 Broadway
> Boulder, CO 80305-3337
> 303-497-6702
> francesca.viterbo at noaa.gov
>



--
--
Francesca Viterbo, Ph.D.
Physical Sciences Division
NOAA Earth System Research Laboratory
R/PSD2, 325 Broadway
Boulder, CO 80305-3337
303-497-6702
francesca.viterbo at noaa.gov

------------------------------------------------
Subject: problems in regridding
From: francesca.viterbo at noaa.gov
Time: Mon Jul 23 17:54:06 2018

Hi John,
sorry again. i actually tried to run my old script with v6.1 that was
regridding stageIV to HRRR and it seems to work fine wthout the
library
warning:

DEBUG 1: Reading data file: ST4.2018052818.06h

DEBUG 2: Input grid: Projection: Stereographic Nx: 1121 Ny: 881
IsNorthHemisphere: true Lon_orient: 105.000 Bx: 399.440 By: 1599.329
Alpha:
2496.0783

DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
Lat_LL:
37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone: 0.623
Bx:
-505.8243 By: 2643.0009

DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
SQUARE, vld_thresh = 0.5

DEBUG 2: Range of input data (name="APCP";level="L0";) is 0 to 123.1.

DEBUG 2: Range of regridded data (name="APCP";level="L0";) is 0 to
17.3.

I'm very happy about that because i was already figuring re-doing my
analysis again, but can you explain me why in this case i don't have
the
same warning but only for the MRMS in v6.1?

Thanks,

On Mon, Jul 23, 2018 at 5:48 PM, Francesca Viterbo - NOAA Affiliate <
francesca.viterbo at noaa.gov> wrote:

> Dear John,
> I've starting trying to regrid using met version 6.1 on Theia using
the
> command you mentioned in the email:
>
> regrid_data_plane GaugeCorrQPE01H201805270200.grib2
> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/
> STAGEIV_cut_1h_2728052018/ST4.2018052702.01h_cut.nc
> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
> prova_cut.nc -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
> GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>
> and I get it regridded, but with
>
> libpng warning: Application built with libpng-1.5.13 but running
with
> 1.6.34
>
> also for v6.1
>
> I'm worried because I did my previous regrids (for other Stage IV to
HRRR
> in my paper) using v6.1 regrid data plane. does it mean that all
that
> regridded data I performed the analysis on are potentially wrong?
>
>
> I have tried to run the same command for version 6.1 and 7.0 and
actually
> I got the warning only for version 6.1... And the two files differs.
If i
> use the command for v7.0 I have my problem solved. But now I'm
concerned
> for my previous regrids with 6.1 and HRRR data.
>
>
> COMMAND for V6.1
>
> regrid_data_plane /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/
> Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
> ST4.2018052702.01h_cut.nc prova_cut_6.9.nc -field
> 'name="GaugeCorrQPE01H"; level="Z0";'
>
> DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
>
> DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll:
20.005
> lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
>
> DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
> Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494
Cone:
> 0.623 Bx: -505.8243 By: 2643.0009
>
> DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
> SQUARE, vld_thresh = 0.5
>
> libpng warning: Application built with libpng-1.5.13 but running
with
> 1.6.34
>
> DEBUG 2: Range of input data (name="GaugeCorrQPE01H"; level="Z0";)
is -3
> to -3.
>
> DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";) is
> -3 to -3.
>
> DEBUG 1: Writing output file: prova_cut_6.9.nc
>
>
> COMMAND for V7.0
>
> regrid_data_plane /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/
> Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
> ST4.2018052702.01h_cut.nc prova_cut_7.0.nc -field
> 'name="GaugeCorrQPE01H"; level="Z0";'
>
> DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
>
> DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll:
20.005
> lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
>
> DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
> Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494
Cone:
> 0.623 Bx: -505.8243 By: 2643.0009
>
> DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
> SQUARE, vld_thresh = 0.5
>
> DEBUG 2: Range of input data (name="GaugeCorrQPE01H"; level="Z0";)
is -3
> to 54.9.
>
> DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";) is
> 0 to 21.
>
> DEBUG 1: Writing output file: prova_cut_7.0.nc
>
>
> Thank you very much,
> Francesca
>
>
>
>
> Thank you very much,
> Francesca
>
> On Mon, Jul 23, 2018 at 4:51 PM, Francesca Viterbo - NOAA Affiliate
<
> francesca.viterbo at noaa.gov> wrote:
>
>> Hi John,
>> thank you very much for your help and for compiling again for the
bug
>> issue. I was following your updates but I didn't have time to try
the
>> suggestion yet because my monday was full of meetings.
>> I will try this and let you know how it goes.
>>
>>
>> On Mon, Jul 23, 2018 at 11:44 AM, John Halley Gotway via RT <
>> met_help at ucar.edu> wrote:
>>
>>> Francesca,
>>>
>>> Good news, my colleague recompiled met-7.0 on theia and the libpng
issue
>>> should now be fixed.  Here's a plot_data_plane command you can run
to
>>> visualize this data:
>>>
>>>   module use /contrib/modulefiles
>>>   module load met/7.0
>>>   plot_data_plane \
>>>
>>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
>>> ta/GaugeCorrQPE01H201805270100.grib2
>>> \
>>>    GaugeCorrQPE01H201805270100.ps \
>>>    'name="GaugeCorrQPE01H"; level="Z0";'
>>>
>>> But there's one thing to be very careful about with MRMS data.
The areas
>>> of bad data near the edge of the domain are encoded as a real data
value
>>> of
>>> -3.  The data producers do not do a good job indicating this as
bad data.
>>> MET will treat these -3 values as valid data and include them in
the
>>> statistics... unless you tell it not to.  You can tell it to treat
is as
>>> bad data by "censoring" the data like this:
>>>
>>>   plot_data_plane \
>>>
>>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
>>> ta/GaugeCorrQPE01H201805270100.grib2
>>> \
>>>    GaugeCorrQPE01H201805270100.ps \
>>>    'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
>>> censor_val=-9999;'
>>>
>>> The 'censor_thresh=eq-3; censor_val=-9999' options tell MET to
replace
>>> any
>>> values of -3 with a new value of -9999, which is MET's internal
value for
>>> bad data.  A png version of the resulting plot is attached.  The
dark
>>> gray
>>> areas over the edge of the domain are now being treated as bad
data in
>>> MET.
>>>
>>> Thanks,
>>> John
>>>
>>>
>>> On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway
<johnhg at ucar.edu>
>>> wrote:
>>>
>>> > Francesca,
>>> >
>>> > One more detail here.  The command you ran *should* have worked
just
>>> > fine.  But I found a pesky little bug in the code that was
preventing
>>> it
>>> > from working.  Using the current version of the code, you'd also
have
>>> to
>>> > explicitly specify the master table, center, and local table
numbers.
>>> >
>>> > Run wgrib2 with the -varX option:
>>> >
>>> > wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
>>> > 1:0:var209_255_1_161_6_9
>>> > Where you interpret these numbers as:
>>> >  -varX            inv         raw variable name - discipline
mastertab
>>> > localtab center parmcat parmnum
>>> >
>>> > So here's the field string that will work with the current
version:
>>> >    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
>>> GRIB2_cntr=161;
>>> > GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>>> >
>>> > I've fixed the little bug in the development version of the
code, and
>>> > it'll be included in the next release.  If needed, we could also
post a
>>> > bugfix for met-7.0.  Just let me know you're preference.
>>> >
>>> > And we still need to resolve the libpng linker issue...
>>> >
>>> > Thanks,
>>> > John
>>> >
>>> > On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT <
>>> > met_help at ucar.edu> wrote:
>>> >
>>> >>
>>> >> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
>>> >> Transaction: Given to johnhg (John Halley Gotway) by RT_System
>>> >>        Queue: met_help
>>> >>      Subject: problems in regridding
>>> >>        Owner: johnhg
>>> >>   Requestors: francesca.viterbo at noaa.gov
>>> >>       Status: new
>>> >>  Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299
>>> >
>>> >>
>>> >>
>>> >> This transaction appears to have no content
>>> >>
>>> >
>>>
>>>
>>
>>
>> --
>> --
>> Francesca Viterbo, Ph.D.
>> Physical Sciences Division
>> NOAA Earth System Research Laboratory
>> R/PSD2, 325 Broadway
>> Boulder, CO 80305-3337
>> 303-497-6702
>> francesca.viterbo at noaa.gov
>>
>
>
>
> --
> --
> Francesca Viterbo, Ph.D.
> Physical Sciences Division
> NOAA Earth System Research Laboratory
> R/PSD2, 325 Broadway
> Boulder, CO 80305-3337
> 303-497-6702
> francesca.viterbo at noaa.gov
>



--
--
Francesca Viterbo, Ph.D.
Physical Sciences Division
NOAA Earth System Research Laboratory
R/PSD2, 325 Broadway
Boulder, CO 80305-3337
303-497-6702
francesca.viterbo at noaa.gov

------------------------------------------------
Subject: problems in regridding
From: John Halley Gotway
Time: Tue Jul 24 11:28:40 2018

Francesca,

OK, sounds like that libpng issue is also present with the met-6.1
release.  So we'll need to recompile that version as well.

I do not know why the libpng warning was or was not present when
running
through your script.  This sort of thing is the result of the contents
of
the LD_LIBRARY_PATH environment variable.  And the runtime environment
from
your script can differ from your command line.  For example, if your
script
is bash and your login shell is c-shell, the environments would
differ.

I'll ask Julie Prestopnik to recompile the met-6.1 release on theia
and
make sure the libpng warning goes away.

Unless you have a good reason for continuing to use met-6.1, I'd
suggest
using met-7.0 instead.

Thanks,
John

On Mon, Jul 23, 2018 at 5:54 PM francesca.viterbo at noaa.gov via RT <
met_help at ucar.edu> wrote:

>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299 >
>
> Hi John,
> sorry again. i actually tried to run my old script with v6.1 that
was
> regridding stageIV to HRRR and it seems to work fine wthout the
library
> warning:
>
> DEBUG 1: Reading data file: ST4.2018052818.06h
>
> DEBUG 2: Input grid: Projection: Stereographic Nx: 1121 Ny: 881
> IsNorthHemisphere: true Lon_orient: 105.000 Bx: 399.440 By: 1599.329
Alpha:
> 2496.0783
>
> DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
Lat_LL:
> 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone: 0.623
Bx:
> -505.8243 By: 2643.0009
>
> DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape =
> SQUARE, vld_thresh = 0.5
>
> DEBUG 2: Range of input data (name="APCP";level="L0";) is 0 to
123.1.
>
> DEBUG 2: Range of regridded data (name="APCP";level="L0";) is 0 to
17.3.
>
> I'm very happy about that because i was already figuring re-doing my
> analysis again, but can you explain me why in this case i don't have
the
> same warning but only for the MRMS in v6.1?
>
> Thanks,
>
> On Mon, Jul 23, 2018 at 5:48 PM, Francesca Viterbo - NOAA Affiliate
<
> francesca.viterbo at noaa.gov> wrote:
>
> > Dear John,
> > I've starting trying to regrid using met version 6.1 on Theia
using the
> > command you mentioned in the email:
> >
> > regrid_data_plane GaugeCorrQPE01H201805270200.grib2
> > /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/
> > STAGEIV_cut_1h_2728052018/ST4.2018052702.01h_cut.nc
> >
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
> > prova_cut.nc -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
> > GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
> >
> > and I get it regridded, but with
> >
> > libpng warning: Application built with libpng-1.5.13 but running
with
> > 1.6.34
> >
> > also for v6.1
> >
> > I'm worried because I did my previous regrids (for other Stage IV
to HRRR
> > in my paper) using v6.1 regrid data plane. does it mean that all
that
> > regridded data I performed the analysis on are potentially wrong?
> >
> >
> > I have tried to run the same command for version 6.1 and 7.0 and
actually
> > I got the warning only for version 6.1... And the two files
differs. If i
> > use the command for v7.0 I have my problem solved. But now I'm
concerned
> > for my previous regrids with 6.1 and HRRR data.
> >
> >
> > COMMAND for V6.1
> >
> > regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> > NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/
> > Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
> > ST4.2018052702.01h_cut.nc prova_cut_6.9.nc -field
> > 'name="GaugeCorrQPE01H"; level="Z0";'
> >
> > DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
> >
>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
> >
> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll:
20.005
> > lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
> >
> > DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
> > Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494
Cone:
> > 0.623 Bx: -505.8243 By: 2643.0009
> >
> > DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape
=
> > SQUARE, vld_thresh = 0.5
> >
> > libpng warning: Application built with libpng-1.5.13 but running
with
> > 1.6.34
> >
> > DEBUG 2: Range of input data (name="GaugeCorrQPE01H"; level="Z0";)
is -3
> > to -3.
> >
> > DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";) is
> > -3 to -3.
> >
> > DEBUG 1: Writing output file: prova_cut_6.9.nc
> >
> >
> > COMMAND for V7.0
> >
> > regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> > NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/
> > Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
> > ST4.2018052702.01h_cut.nc prova_cut_7.0.nc -field
> > 'name="GaugeCorrQPE01H"; level="Z0";'
> >
> > DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
> >
>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
> >
> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500 lat_ll:
20.005
> > lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
> >
> > DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
> > Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494
Cone:
> > 0.623 Bx: -505.8243 By: 2643.0009
> >
> > DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape
=
> > SQUARE, vld_thresh = 0.5
> >
> > DEBUG 2: Range of input data (name="GaugeCorrQPE01H"; level="Z0";)
is -3
> > to 54.9.
> >
> > DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";) is
> > 0 to 21.
> >
> > DEBUG 1: Writing output file: prova_cut_7.0.nc
> >
> >
> > Thank you very much,
> > Francesca
> >
> >
> >
> >
> > Thank you very much,
> > Francesca
> >
> > On Mon, Jul 23, 2018 at 4:51 PM, Francesca Viterbo - NOAA
Affiliate <
> > francesca.viterbo at noaa.gov> wrote:
> >
> >> Hi John,
> >> thank you very much for your help and for compiling again for the
bug
> >> issue. I was following your updates but I didn't have time to try
the
> >> suggestion yet because my monday was full of meetings.
> >> I will try this and let you know how it goes.
> >>
> >>
> >> On Mon, Jul 23, 2018 at 11:44 AM, John Halley Gotway via RT <
> >> met_help at ucar.edu> wrote:
> >>
> >>> Francesca,
> >>>
> >>> Good news, my colleague recompiled met-7.0 on theia and the
libpng
> issue
> >>> should now be fixed.  Here's a plot_data_plane command you can
run to
> >>> visualize this data:
> >>>
> >>>   module use /contrib/modulefiles
> >>>   module load met/7.0
> >>>   plot_data_plane \
> >>>
> >>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
> >>> ta/GaugeCorrQPE01H201805270100.grib2
> >>> \
> >>>    GaugeCorrQPE01H201805270100.ps \
> >>>    'name="GaugeCorrQPE01H"; level="Z0";'
> >>>
> >>> But there's one thing to be very careful about with MRMS data.
The
> areas
> >>> of bad data near the edge of the domain are encoded as a real
data
> value
> >>> of
> >>> -3.  The data producers do not do a good job indicating this as
bad
> data.
> >>> MET will treat these -3 values as valid data and include them in
the
> >>> statistics... unless you tell it not to.  You can tell it to
treat is
> as
> >>> bad data by "censoring" the data like this:
> >>>
> >>>   plot_data_plane \
> >>>
> >>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
> >>> ta/GaugeCorrQPE01H201805270100.grib2
> >>> \
> >>>    GaugeCorrQPE01H201805270100.ps \
> >>>    'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
> >>> censor_val=-9999;'
> >>>
> >>> The 'censor_thresh=eq-3; censor_val=-9999' options tell MET to
replace
> >>> any
> >>> values of -3 with a new value of -9999, which is MET's internal
value
> for
> >>> bad data.  A png version of the resulting plot is attached.  The
dark
> >>> gray
> >>> areas over the edge of the domain are now being treated as bad
data in
> >>> MET.
> >>>
> >>> Thanks,
> >>> John
> >>>
> >>>
> >>> On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway
<johnhg at ucar.edu>
> >>> wrote:
> >>>
> >>> > Francesca,
> >>> >
> >>> > One more detail here.  The command you ran *should* have
worked just
> >>> > fine.  But I found a pesky little bug in the code that was
preventing
> >>> it
> >>> > from working.  Using the current version of the code, you'd
also have
> >>> to
> >>> > explicitly specify the master table, center, and local table
numbers.
> >>> >
> >>> > Run wgrib2 with the -varX option:
> >>> >
> >>> > wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
> >>> > 1:0:var209_255_1_161_6_9
> >>> > Where you interpret these numbers as:
> >>> >  -varX            inv         raw variable name - discipline
> mastertab
> >>> > localtab center parmcat parmnum
> >>> >
> >>> > So here's the field string that will work with the current
version:
> >>> >    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
> >>> GRIB2_cntr=161;
> >>> > GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
> >>> >
> >>> > I've fixed the little bug in the development version of the
code, and
> >>> > it'll be included in the next release.  If needed, we could
also
> post a
> >>> > bugfix for met-7.0.  Just let me know you're preference.
> >>> >
> >>> > And we still need to resolve the libpng linker issue...
> >>> >
> >>> > Thanks,
> >>> > John
> >>> >
> >>> > On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT <
> >>> > met_help at ucar.edu> wrote:
> >>> >
> >>> >>
> >>> >> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
> >>> >> Transaction: Given to johnhg (John Halley Gotway) by
RT_System
> >>> >>        Queue: met_help
> >>> >>      Subject: problems in regridding
> >>> >>        Owner: johnhg
> >>> >>   Requestors: francesca.viterbo at noaa.gov
> >>> >>       Status: new
> >>> >>  Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299
> >>> >
> >>> >>
> >>> >>
> >>> >> This transaction appears to have no content
> >>> >>
> >>> >
> >>>
> >>>
> >>
> >>
> >> --
> >> --
> >> Francesca Viterbo, Ph.D.
> >> Physical Sciences Division
> >> NOAA Earth System Research Laboratory
> >> R/PSD2, 325 Broadway
> >> Boulder, CO 80305-3337
> >> 303-497-6702
> >> francesca.viterbo at noaa.gov
> >>
> >
> >
> >
> > --
> > --
> > Francesca Viterbo, Ph.D.
> > Physical Sciences Division
> > NOAA Earth System Research Laboratory
> > R/PSD2, 325 Broadway
> > Boulder, CO 80305-3337
> > 303-497-6702
> > francesca.viterbo at noaa.gov
> >
>
>
>
> --
> --
> Francesca Viterbo, Ph.D.
> Physical Sciences Division
> NOAA Earth System Research Laboratory
> R/PSD2, 325 Broadway
> Boulder, CO 80305-3337
> 303-497-6702
> francesca.viterbo at noaa.gov
>
>

------------------------------------------------
Subject: problems in regridding
From: John Halley Gotway
Time: Wed Jul 25 13:01:36 2018

Francesca,

Good news.  Julie was able to identify and fix the problem in the met-
6.1
build.  It was a problem in the module file for that build.  Please
try
running:
   module purge
   module use /contrib/modulefiles
   module load met/6.1

regrid_data_plane \
GaugeCorrQPE01H201805270200.grib2
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
ST4.2018052702.01h_cut.nc \
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
prova_cut.nc \
-field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'

And confirm that the libpng warning is gone.

Thanks,
John

On Tue, Jul 24, 2018 at 11:28 AM John Halley Gotway <johnhg at ucar.edu>
wrote:

> Francesca,
>
> OK, sounds like that libpng issue is also present with the met-6.1
> release.  So we'll need to recompile that version as well.
>
> I do not know why the libpng warning was or was not present when
running
> through your script.  This sort of thing is the result of the
contents of
> the LD_LIBRARY_PATH environment variable.  And the runtime
environment from
> your script can differ from your command line.  For example, if your
script
> is bash and your login shell is c-shell, the environments would
differ.
>
> I'll ask Julie Prestopnik to recompile the met-6.1 release on theia
and
> make sure the libpng warning goes away.
>
> Unless you have a good reason for continuing to use met-6.1, I'd
suggest
> using met-7.0 instead.
>
> Thanks,
> John
>
> On Mon, Jul 23, 2018 at 5:54 PM francesca.viterbo at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
>>
>> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299 >
>>
>> Hi John,
>> sorry again. i actually tried to run my old script with v6.1 that
was
>> regridding stageIV to HRRR and it seems to work fine wthout the
library
>> warning:
>>
>> DEBUG 1: Reading data file: ST4.2018052818.06h
>>
>> DEBUG 2: Input grid: Projection: Stereographic Nx: 1121 Ny: 881
>> IsNorthHemisphere: true Lon_orient: 105.000 Bx: 399.440 By:
1599.329
>> Alpha:
>> 2496.0783
>>
>> DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny: 107
>> Lat_LL:
>> 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone:
0.623 Bx:
>> -505.8243 By: 2643.0009
>>
>> DEBUG 2: Interpolation options: method = NEAREST, width = 1, shape
=
>> SQUARE, vld_thresh = 0.5
>>
>> DEBUG 2: Range of input data (name="APCP";level="L0";) is 0 to
123.1.
>>
>> DEBUG 2: Range of regridded data (name="APCP";level="L0";) is 0 to
17.3.
>>
>> I'm very happy about that because i was already figuring re-doing
my
>> analysis again, but can you explain me why in this case i don't
have the
>> same warning but only for the MRMS in v6.1?
>>
>> Thanks,
>>
>> On Mon, Jul 23, 2018 at 5:48 PM, Francesca Viterbo - NOAA Affiliate
<
>> francesca.viterbo at noaa.gov> wrote:
>>
>> > Dear John,
>> > I've starting trying to regrid using met version 6.1 on Theia
using the
>> > command you mentioned in the email:
>> >
>> > regrid_data_plane GaugeCorrQPE01H201805270200.grib2
>> > /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/
>> > STAGEIV_cut_1h_2728052018/ST4.2018052702.01h_cut.nc
>> >
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
>> > prova_cut.nc -field 'GRIB2_disc=209; GRIB2_mtab=255;
GRIB2_ltab=1;
>> > GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>> >
>> > and I get it regridded, but with
>> >
>> > libpng warning: Application built with libpng-1.5.13 but running
with
>> > 1.6.34
>> >
>> > also for v6.1
>> >
>> > I'm worried because I did my previous regrids (for other Stage IV
to
>> HRRR
>> > in my paper) using v6.1 regrid data plane. does it mean that all
that
>> > regridded data I performed the analysis on are potentially wrong?
>> >
>> >
>> > I have tried to run the same command for version 6.1 and 7.0 and
>> actually
>> > I got the warning only for version 6.1... And the two files
differs. If
>> i
>> > use the command for v7.0 I have my problem solved. But now I'm
concerned
>> > for my previous regrids with 6.1 and HRRR data.
>> >
>> >
>> > COMMAND for V6.1
>> >
>> > regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
>> > NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/
>> > Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
>> > ST4.2018052702.01h_cut.nc prova_cut_6.9.nc -field
>> > 'name="GaugeCorrQPE01H"; level="Z0";'
>> >
>> > DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
>> >
>>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
>> >
>> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500
lat_ll:
>> 20.005
>> > lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
>> >
>> > DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
>> > Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494
Cone:
>> > 0.623 Bx: -505.8243 By: 2643.0009
>> >
>> > DEBUG 2: Interpolation options: method = NEAREST, width = 1,
shape =
>> > SQUARE, vld_thresh = 0.5
>> >
>> > libpng warning: Application built with libpng-1.5.13 but running
with
>> > 1.6.34
>> >
>> > DEBUG 2: Range of input data (name="GaugeCorrQPE01H";
level="Z0";) is -3
>> > to -3.
>> >
>> > DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";)
>> is
>> > -3 to -3.
>> >
>> > DEBUG 1: Writing output file: prova_cut_6.9.nc
>> >
>> >
>> > COMMAND for V7.0
>> >
>> > regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
>> > NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
/scratch4/NCEPDEV/ohd/
>> > Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
>> > ST4.2018052702.01h_cut.nc prova_cut_7.0.nc -field
>> > 'name="GaugeCorrQPE01H"; level="Z0";'
>> >
>> > DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
>> >
>>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
>> >
>> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500
lat_ll:
>> 20.005
>> > lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
>> >
>> > DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
>> > Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494
Cone:
>> > 0.623 Bx: -505.8243 By: 2643.0009
>> >
>> > DEBUG 2: Interpolation options: method = NEAREST, width = 1,
shape =
>> > SQUARE, vld_thresh = 0.5
>> >
>> > DEBUG 2: Range of input data (name="GaugeCorrQPE01H";
level="Z0";) is -3
>> > to 54.9.
>> >
>> > DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";)
>> is
>> > 0 to 21.
>> >
>> > DEBUG 1: Writing output file: prova_cut_7.0.nc
>> >
>> >
>> > Thank you very much,
>> > Francesca
>> >
>> >
>> >
>> >
>> > Thank you very much,
>> > Francesca
>> >
>> > On Mon, Jul 23, 2018 at 4:51 PM, Francesca Viterbo - NOAA
Affiliate <
>> > francesca.viterbo at noaa.gov> wrote:
>> >
>> >> Hi John,
>> >> thank you very much for your help and for compiling again for
the bug
>> >> issue. I was following your updates but I didn't have time to
try the
>> >> suggestion yet because my monday was full of meetings.
>> >> I will try this and let you know how it goes.
>> >>
>> >>
>> >> On Mon, Jul 23, 2018 at 11:44 AM, John Halley Gotway via RT <
>> >> met_help at ucar.edu> wrote:
>> >>
>> >>> Francesca,
>> >>>
>> >>> Good news, my colleague recompiled met-7.0 on theia and the
libpng
>> issue
>> >>> should now be fixed.  Here's a plot_data_plane command you can
run to
>> >>> visualize this data:
>> >>>
>> >>>   module use /contrib/modulefiles
>> >>>   module load met/7.0
>> >>>   plot_data_plane \
>> >>>
>> >>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
>> >>> ta/GaugeCorrQPE01H201805270100.grib2
>> >>> \
>> >>>    GaugeCorrQPE01H201805270100.ps \
>> >>>    'name="GaugeCorrQPE01H"; level="Z0";'
>> >>>
>> >>> But there's one thing to be very careful about with MRMS data.
The
>> areas
>> >>> of bad data near the edge of the domain are encoded as a real
data
>> value
>> >>> of
>> >>> -3.  The data producers do not do a good job indicating this as
bad
>> data.
>> >>> MET will treat these -3 values as valid data and include them
in the
>> >>> statistics... unless you tell it not to.  You can tell it to
treat is
>> as
>> >>> bad data by "censoring" the data like this:
>> >>>
>> >>>   plot_data_plane \
>> >>>
>> >>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
>> >>> ta/GaugeCorrQPE01H201805270100.grib2
>> >>> \
>> >>>    GaugeCorrQPE01H201805270100.ps \
>> >>>    'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
>> >>> censor_val=-9999;'
>> >>>
>> >>> The 'censor_thresh=eq-3; censor_val=-9999' options tell MET to
replace
>> >>> any
>> >>> values of -3 with a new value of -9999, which is MET's internal
value
>> for
>> >>> bad data.  A png version of the resulting plot is attached.
The dark
>> >>> gray
>> >>> areas over the edge of the domain are now being treated as bad
data in
>> >>> MET.
>> >>>
>> >>> Thanks,
>> >>> John
>> >>>
>> >>>
>> >>> On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway
<johnhg at ucar.edu>
>> >>> wrote:
>> >>>
>> >>> > Francesca,
>> >>> >
>> >>> > One more detail here.  The command you ran *should* have
worked just
>> >>> > fine.  But I found a pesky little bug in the code that was
>> preventing
>> >>> it
>> >>> > from working.  Using the current version of the code, you'd
also
>> have
>> >>> to
>> >>> > explicitly specify the master table, center, and local table
>> numbers.
>> >>> >
>> >>> > Run wgrib2 with the -varX option:
>> >>> >
>> >>> > wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
>> >>> > 1:0:var209_255_1_161_6_9
>> >>> > Where you interpret these numbers as:
>> >>> >  -varX            inv         raw variable name - discipline
>> mastertab
>> >>> > localtab center parmcat parmnum
>> >>> >
>> >>> > So here's the field string that will work with the current
version:
>> >>> >    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
>> >>> GRIB2_cntr=161;
>> >>> > GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>> >>> >
>> >>> > I've fixed the little bug in the development version of the
code,
>> and
>> >>> > it'll be included in the next release.  If needed, we could
also
>> post a
>> >>> > bugfix for met-7.0.  Just let me know you're preference.
>> >>> >
>> >>> > And we still need to resolve the libpng linker issue...
>> >>> >
>> >>> > Thanks,
>> >>> > John
>> >>> >
>> >>> > On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via RT
<
>> >>> > met_help at ucar.edu> wrote:
>> >>> >
>> >>> >>
>> >>> >> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
>> >>> >> Transaction: Given to johnhg (John Halley Gotway) by
RT_System
>> >>> >>        Queue: met_help
>> >>> >>      Subject: problems in regridding
>> >>> >>        Owner: johnhg
>> >>> >>   Requestors: francesca.viterbo at noaa.gov
>> >>> >>       Status: new
>> >>> >>  Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299
>> >>> >
>> >>> >>
>> >>> >>
>> >>> >> This transaction appears to have no content
>> >>> >>
>> >>> >
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >> --
>> >> Francesca Viterbo, Ph.D.
>> >> Physical Sciences Division
>> >> NOAA Earth System Research Laboratory
>> >> R/PSD2, 325 Broadway
>> >> Boulder, CO 80305-3337
>> >> 303-497-6702
>> >> francesca.viterbo at noaa.gov
>> >>
>> >
>> >
>> >
>> > --
>> > --
>> > Francesca Viterbo, Ph.D.
>> > Physical Sciences Division
>> > NOAA Earth System Research Laboratory
>> > R/PSD2, 325 Broadway
>> > Boulder, CO 80305-3337
>> > 303-497-6702
>> > francesca.viterbo at noaa.gov
>> >
>>
>>
>>
>> --
>> --
>> Francesca Viterbo, Ph.D.
>> Physical Sciences Division
>> NOAA Earth System Research Laboratory
>> R/PSD2, 325 Broadway
>> Boulder, CO 80305-3337
>> 303-497-6702
>> francesca.viterbo at noaa.gov
>>
>>

------------------------------------------------
Subject: problems in regridding
From: francesca.viterbo at noaa.gov
Time: Wed Jul 25 15:50:36 2018

Hi John,
I just tried and i confirm that the bug is disappeared!
Thank you very much for your help and for your colleagues'
collaboration.

Francesca

On Wed, Jul 25, 2018 at 1:01 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:

> Francesca,
>
> Good news.  Julie was able to identify and fix the problem in the
met-6.1
> build.  It was a problem in the module file for that build.  Please
try
> running:
>    module purge
>    module use /contrib/modulefiles
>    module load met/6.1
>
> regrid_data_plane \
> GaugeCorrQPE01H201805270200.grib2
> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> NWM/STAGEIV_cut_1h_2728052018/
> ST4.2018052702.01h_cut.nc \
> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
> prova_cut.nc \
> -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
> GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
>
> And confirm that the libpng warning is gone.
>
> Thanks,
> John
>
> On Tue, Jul 24, 2018 at 11:28 AM John Halley Gotway
<johnhg at ucar.edu>
> wrote:
>
> > Francesca,
> >
> > OK, sounds like that libpng issue is also present with the met-6.1
> > release.  So we'll need to recompile that version as well.
> >
> > I do not know why the libpng warning was or was not present when
running
> > through your script.  This sort of thing is the result of the
contents of
> > the LD_LIBRARY_PATH environment variable.  And the runtime
environment
> from
> > your script can differ from your command line.  For example, if
your
> script
> > is bash and your login shell is c-shell, the environments would
differ.
> >
> > I'll ask Julie Prestopnik to recompile the met-6.1 release on
theia and
> > make sure the libpng warning goes away.
> >
> > Unless you have a good reason for continuing to use met-6.1, I'd
suggest
> > using met-7.0 instead.
> >
> > Thanks,
> > John
> >
> > On Mon, Jul 23, 2018 at 5:54 PM francesca.viterbo at noaa.gov via RT
<
> > met_help at ucar.edu> wrote:
> >
> >>
> >> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299 >
> >>
> >> Hi John,
> >> sorry again. i actually tried to run my old script with v6.1 that
was
> >> regridding stageIV to HRRR and it seems to work fine wthout the
library
> >> warning:
> >>
> >> DEBUG 1: Reading data file: ST4.2018052818.06h
> >>
> >> DEBUG 2: Input grid: Projection: Stereographic Nx: 1121 Ny: 881
> >> IsNorthHemisphere: true Lon_orient: 105.000 Bx: 399.440 By:
1599.329
> >> Alpha:
> >> 2496.0783
> >>
> >> DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
> >> Lat_LL:
> >> 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha: 4203.494 Cone:
0.623 Bx:
> >> -505.8243 By: 2643.0009
> >>
> >> DEBUG 2: Interpolation options: method = NEAREST, width = 1,
shape =
> >> SQUARE, vld_thresh = 0.5
> >>
> >> DEBUG 2: Range of input data (name="APCP";level="L0";) is 0 to
123.1.
> >>
> >> DEBUG 2: Range of regridded data (name="APCP";level="L0";) is 0
to 17.3.
> >>
> >> I'm very happy about that because i was already figuring re-doing
my
> >> analysis again, but can you explain me why in this case i don't
have the
> >> same warning but only for the MRMS in v6.1?
> >>
> >> Thanks,
> >>
> >> On Mon, Jul 23, 2018 at 5:48 PM, Francesca Viterbo - NOAA
Affiliate <
> >> francesca.viterbo at noaa.gov> wrote:
> >>
> >> > Dear John,
> >> > I've starting trying to regrid using met version 6.1 on Theia
using
> the
> >> > command you mentioned in the email:
> >> >
> >> > regrid_data_plane GaugeCorrQPE01H201805270200.grib2
> >> > /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/
> >> > STAGEIV_cut_1h_2728052018/ST4.2018052702.01h_cut.nc
> >> >
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_cut_data/
> >> > prova_cut.nc -field 'GRIB2_disc=209; GRIB2_mtab=255;
GRIB2_ltab=1;
> >> > GRIB2_cntr=161;GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
> >> >
> >> > and I get it regridded, but with
> >> >
> >> > libpng warning: Application built with libpng-1.5.13 but
running with
> >> > 1.6.34
> >> >
> >> > also for v6.1
> >> >
> >> > I'm worried because I did my previous regrids (for other Stage
IV to
> >> HRRR
> >> > in my paper) using v6.1 regrid data plane. does it mean that
all that
> >> > regridded data I performed the analysis on are potentially
wrong?
> >> >
> >> >
> >> > I have tried to run the same command for version 6.1 and 7.0
and
> >> actually
> >> > I got the warning only for version 6.1... And the two files
differs.
> If
> >> i
> >> > use the command for v7.0 I have my problem solved. But now I'm
> concerned
> >> > for my previous regrids with 6.1 and HRRR data.
> >> >
> >> >
> >> > COMMAND for V6.1
> >> >
> >> > regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> >> > NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
> /scratch4/NCEPDEV/ohd/
> >> > Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
> >> > ST4.2018052702.01h_cut.nc prova_cut_6.9.nc -field
> >> > 'name="GaugeCorrQPE01H"; level="Z0";'
> >> >
> >> > DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
> >> >
> >>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.
> grib2
> >> >
> >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500
lat_ll:
> >> 20.005
> >> > lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
> >> >
> >> > DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
> >> > Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha:
4203.494 Cone:
> >> > 0.623 Bx: -505.8243 By: 2643.0009
> >> >
> >> > DEBUG 2: Interpolation options: method = NEAREST, width = 1,
shape =
> >> > SQUARE, vld_thresh = 0.5
> >> >
> >> > libpng warning: Application built with libpng-1.5.13 but
running with
> >> > 1.6.34
> >> >
> >> > DEBUG 2: Range of input data (name="GaugeCorrQPE01H";
level="Z0";) is
> -3
> >> > to -3.
> >> >
> >> > DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";)
> >> is
> >> > -3 to -3.
> >> >
> >> > DEBUG 1: Writing output file: prova_cut_6.9.nc
> >> >
> >> >
> >> > COMMAND for V7.0
> >> >
> >> > regrid_data_plane
/scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_
> >> > NWM/MRMS_data/GaugeCorrQPE01H201805270100.grib2
> /scratch4/NCEPDEV/ohd/
> >> > Francesca.Viterbo/Ellicott_NWM/STAGEIV_cut_1h_2728052018/
> >> > ST4.2018052702.01h_cut.nc prova_cut_7.0.nc -field
> >> > 'name="GaugeCorrQPE01H"; level="Z0";'
> >> >
> >> > DEBUG 1: Reading data file: /scratch4/NCEPDEV/ohd/
> >> >
> >>
Francesca.Viterbo/Ellicott_NWM/MRMS_data/GaugeCorrQPE01H201805270100.
> grib2
> >> >
> >> > DEBUG 2: Input grid: Projection: Lat/Lon Nx: 7000 Ny: 3500
lat_ll:
> >> 20.005
> >> > lon_ll: 129.995 delta_lat: 0.010 delta_lon: 0.010
> >> >
> >> > DEBUG 2: Output grid: Projection: Lambert Conformal Nx: 166 Ny:
107
> >> > Lat_LL: 37.932 Lon_LL: 80.096 Lon_orient: 97.500 Alpha:
4203.494 Cone:
> >> > 0.623 Bx: -505.8243 By: 2643.0009
> >> >
> >> > DEBUG 2: Interpolation options: method = NEAREST, width = 1,
shape =
> >> > SQUARE, vld_thresh = 0.5
> >> >
> >> > DEBUG 2: Range of input data (name="GaugeCorrQPE01H";
level="Z0";) is
> -3
> >> > to 54.9.
> >> >
> >> > DEBUG 2: Range of regridded data (name="GaugeCorrQPE01H";
level="Z0";)
> >> is
> >> > 0 to 21.
> >> >
> >> > DEBUG 1: Writing output file: prova_cut_7.0.nc
> >> >
> >> >
> >> > Thank you very much,
> >> > Francesca
> >> >
> >> >
> >> >
> >> >
> >> > Thank you very much,
> >> > Francesca
> >> >
> >> > On Mon, Jul 23, 2018 at 4:51 PM, Francesca Viterbo - NOAA
Affiliate <
> >> > francesca.viterbo at noaa.gov> wrote:
> >> >
> >> >> Hi John,
> >> >> thank you very much for your help and for compiling again for
the bug
> >> >> issue. I was following your updates but I didn't have time to
try the
> >> >> suggestion yet because my monday was full of meetings.
> >> >> I will try this and let you know how it goes.
> >> >>
> >> >>
> >> >> On Mon, Jul 23, 2018 at 11:44 AM, John Halley Gotway via RT <
> >> >> met_help at ucar.edu> wrote:
> >> >>
> >> >>> Francesca,
> >> >>>
> >> >>> Good news, my colleague recompiled met-7.0 on theia and the
libpng
> >> issue
> >> >>> should now be fixed.  Here's a plot_data_plane command you
can run
> to
> >> >>> visualize this data:
> >> >>>
> >> >>>   module use /contrib/modulefiles
> >> >>>   module load met/7.0
> >> >>>   plot_data_plane \
> >> >>>
> >> >>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
> >> >>> ta/GaugeCorrQPE01H201805270100.grib2
> >> >>> \
> >> >>>    GaugeCorrQPE01H201805270100.ps \
> >> >>>    'name="GaugeCorrQPE01H"; level="Z0";'
> >> >>>
> >> >>> But there's one thing to be very careful about with MRMS
data.  The
> >> areas
> >> >>> of bad data near the edge of the domain are encoded as a real
data
> >> value
> >> >>> of
> >> >>> -3.  The data producers do not do a good job indicating this
as bad
> >> data.
> >> >>> MET will treat these -3 values as valid data and include them
in the
> >> >>> statistics... unless you tell it not to.  You can tell it to
treat
> is
> >> as
> >> >>> bad data by "censoring" the data like this:
> >> >>>
> >> >>>   plot_data_plane \
> >> >>>
> >> >>> /scratch4/NCEPDEV/ohd/Francesca.Viterbo/Ellicott_NWM/MRMS_da
> >> >>> ta/GaugeCorrQPE01H201805270100.grib2
> >> >>> \
> >> >>>    GaugeCorrQPE01H201805270100.ps \
> >> >>>    'name="GaugeCorrQPE01H"; level="Z0"; censor_thresh=eq-3;
> >> >>> censor_val=-9999;'
> >> >>>
> >> >>> The 'censor_thresh=eq-3; censor_val=-9999' options tell MET
to
> replace
> >> >>> any
> >> >>> values of -3 with a new value of -9999, which is MET's
internal
> value
> >> for
> >> >>> bad data.  A png version of the resulting plot is attached.
The
> dark
> >> >>> gray
> >> >>> areas over the edge of the domain are now being treated as
bad data
> in
> >> >>> MET.
> >> >>>
> >> >>> Thanks,
> >> >>> John
> >> >>>
> >> >>>
> >> >>> On Mon, Jul 23, 2018 at 10:44 AM John Halley Gotway <
> johnhg at ucar.edu>
> >> >>> wrote:
> >> >>>
> >> >>> > Francesca,
> >> >>> >
> >> >>> > One more detail here.  The command you ran *should* have
worked
> just
> >> >>> > fine.  But I found a pesky little bug in the code that was
> >> preventing
> >> >>> it
> >> >>> > from working.  Using the current version of the code, you'd
also
> >> have
> >> >>> to
> >> >>> > explicitly specify the master table, center, and local
table
> >> numbers.
> >> >>> >
> >> >>> > Run wgrib2 with the -varX option:
> >> >>> >
> >> >>> > wgrib2 -varX GaugeCorrQPE01H201805270100.grib2
> >> >>> > 1:0:var209_255_1_161_6_9
> >> >>> > Where you interpret these numbers as:
> >> >>> >  -varX            inv         raw variable name -
discipline
> >> mastertab
> >> >>> > localtab center parmcat parmnum
> >> >>> >
> >> >>> > So here's the field string that will work with the current
> version:
> >> >>> >    -field 'GRIB2_disc=209; GRIB2_mtab=255; GRIB2_ltab=1;
> >> >>> GRIB2_cntr=161;
> >> >>> > GRIB2_parm_cat=6; GRIB2_parm=9; level="Z0";'
> >> >>> >
> >> >>> > I've fixed the little bug in the development version of the
code,
> >> and
> >> >>> > it'll be included in the next release.  If needed, we could
also
> >> post a
> >> >>> > bugfix for met-7.0.  Just let me know you're preference.
> >> >>> >
> >> >>> > And we still need to resolve the libpng linker issue...
> >> >>> >
> >> >>> > Thanks,
> >> >>> > John
> >> >>> >
> >> >>> > On Mon, Jul 23, 2018 at 10:26 AM The RT System itself via
RT <
> >> >>> > met_help at ucar.edu> wrote:
> >> >>> >
> >> >>> >>
> >> >>> >> Mon Jul 23 10:25:39 2018: Request 86299 was acted upon.
> >> >>> >> Transaction: Given to johnhg (John Halley Gotway) by
RT_System
> >> >>> >>        Queue: met_help
> >> >>> >>      Subject: problems in regridding
> >> >>> >>        Owner: johnhg
> >> >>> >>   Requestors: francesca.viterbo at noaa.gov
> >> >>> >>       Status: new
> >> >>> >>  Ticket <URL:
> >> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=86299
> >> >>> >
> >> >>> >>
> >> >>> >>
> >> >>> >> This transaction appears to have no content
> >> >>> >>
> >> >>> >
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >> --
> >> >> Francesca Viterbo, Ph.D.
> >> >> Physical Sciences Division
> >> >> NOAA Earth System Research Laboratory
> >> >> R/PSD2, 325 Broadway
> >> >> Boulder, CO 80305-3337
> >> >> 303-497-6702
> >> >> francesca.viterbo at noaa.gov
> >> >>
> >> >
> >> >
> >> >
> >> > --
> >> > --
> >> > Francesca Viterbo, Ph.D.
> >> > Physical Sciences Division
> >> > NOAA Earth System Research Laboratory
> >> > R/PSD2, 325 Broadway
> >> > Boulder, CO 80305-3337
> >> > 303-497-6702
> >> > francesca.viterbo at noaa.gov
> >> >
> >>
> >>
> >>
> >> --
> >> --
> >> Francesca Viterbo, Ph.D.
> >> Physical Sciences Division
> >> NOAA Earth System Research Laboratory
> >> R/PSD2, 325 Broadway
> >> Boulder, CO 80305-3337
> >> 303-497-6702
> >> francesca.viterbo at noaa.gov
> >>
> >>
>
>


--
--
Francesca Viterbo, Ph.D.
Physical Sciences Division
NOAA Earth System Research Laboratory
R/PSD2, 325 Broadway
Boulder, CO 80305-3337
303-497-6702
francesca.viterbo at noaa.gov

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


More information about the Met_help mailing list