[Met_help] [rt.rap.ucar.edu #80781] History for pb2nc incorrectly making a netcdf file
John Halley Gotway via RT
met_help at ucar.edu
Thu Jun 15 10:32:09 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi,
I'm trying to make a netcdf file, using the MET software on my linux
workstation (not wcoss). It was recently installed on my linux workstation
similar to the WPC installation. I am able to use pb2nc with a different
prepbufr file than what I used on wcoss. This is a non-restricted file,
gfs.t00z.prepbufr.nr. The file was created "correctly", with no obvious
errors. I quick check of the data, using ncdump -v obs_arr <prepbufr.nr>,
shows good values. But, when I checked the date string, hdr_vld, I got
garbage in the beginning of the file, and good dates toward the end. I've
attached the ncdump file.
Then, when I tried to use point_stat, I got the error message:
ERROR : timestring_to_unix(const char *) -> can't parse date/time string
"0194514A"
I actually tried point_stat first, got the message and then double checked
with the ncdump.
So, are non-restricted prepbufr files not supported? Or, is there a work
around for this?
Thanks in advance.
Roz
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: John Halley Gotway
Time: Wed Jun 07 14:05:33 2017
Roz,
Yes, both restricted and non-restricted datasets *should* work fine in
PB2NC. This is the first time I've seen this type of behavior
reported, so
we'll need to dive into the details to diagnose the problem.
Are you able to either send me the input PREPBUFR file you used or
point me
to it somewhere online? Also, please send me your PB2NC config file
and
the command you ran on the command line.
If I'm able to replicate the behavior here, it should be fairly easy
to
debug.
You can post data to our anonymous ftp site following these
instructions:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
Thanks,
John Halley Gotway
On Wed, Jun 7, 2017 at 1:36 PM, Rosalyn MacCracken - NOAA Affiliate
via RT <
met_help at ucar.edu> wrote:
>
> Wed Jun 07 13:36:02 2017: Request 80781 was acted upon.
> Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> Queue: met_help
> Subject: pb2nc incorrectly making a netcdf file
> Owner: Nobody
> Requestors: rosalyn.maccracken at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781 >
>
>
> Hi,
>
> I'm trying to make a netcdf file, using the MET software on my linux
> workstation (not wcoss). It was recently installed on my linux
workstation
> similar to the WPC installation. I am able to use pb2nc with a
different
> prepbufr file than what I used on wcoss. This is a non-restricted
file,
> gfs.t00z.prepbufr.nr. The file was created "correctly", with no
obvious
> errors. I quick check of the data, using ncdump -v obs_arr
<prepbufr.nr>,
> shows good values. But, when I checked the date string, hdr_vld, I
got
> garbage in the beginning of the file, and good dates toward the end.
I've
> attached the ncdump file.
>
> Then, when I tried to use point_stat, I got the error message:
> ERROR : timestring_to_unix(const char *) -> can't parse date/time
string
> "0194514A"
>
> I actually tried point_stat first, got the message and then double
checked
> with the ncdump.
>
> So, are non-restricted prepbufr files not supported? Or, is there a
work
> around for this?
>
> Thanks in advance.
>
> Roz
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu Jun 08 06:36:20 2017
Hi John,
I'm attaching a file of the input and output error message and the two
config files. It contains the the two commands that I used on the
command
line, for pb2nc (with the output message) and point_stat. Should I
just
share the data on the google drive? Or is it better to put them on
the
ftp site?
Now, this all worked on wcoss, so, I don't know what's different.
Also,
this didn't work on WPC's machine either.
Roz
On Wed, Jun 7, 2017 at 8:05 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Roz,
>
> Yes, both restricted and non-restricted datasets *should* work fine
in
> PB2NC. This is the first time I've seen this type of behavior
reported, so
> we'll need to dive into the details to diagnose the problem.
>
> Are you able to either send me the input PREPBUFR file you used or
point me
> to it somewhere online? Also, please send me your PB2NC config file
and
> the command you ran on the command line.
>
> If I'm able to replicate the behavior here, it should be fairly easy
to
> debug.
>
> You can post data to our anonymous ftp site following these
instructions:
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> Thanks,
> John Halley Gotway
>
> On Wed, Jun 7, 2017 at 1:36 PM, Rosalyn MacCracken - NOAA Affiliate
via RT
> <
> met_help at ucar.edu> wrote:
>
> >
> > Wed Jun 07 13:36:02 2017: Request 80781 was acted upon.
> > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > Queue: met_help
> > Subject: pb2nc incorrectly making a netcdf file
> > Owner: Nobody
> > Requestors: rosalyn.maccracken at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781 >
> >
> >
> > Hi,
> >
> > I'm trying to make a netcdf file, using the MET software on my
linux
> > workstation (not wcoss). It was recently installed on my linux
> workstation
> > similar to the WPC installation. I am able to use pb2nc with a
different
> > prepbufr file than what I used on wcoss. This is a non-restricted
file,
> > gfs.t00z.prepbufr.nr. The file was created "correctly", with no
obvious
> > errors. I quick check of the data, using ncdump -v obs_arr
<prepbufr.nr
> >,
> > shows good values. But, when I checked the date string, hdr_vld,
I got
> > garbage in the beginning of the file, and good dates toward the
end.
> I've
> > attached the ncdump file.
> >
> > Then, when I tried to use point_stat, I got the error message:
> > ERROR : timestring_to_unix(const char *) -> can't parse date/time
string
> > "0194514A"
> >
> > I actually tried point_stat first, got the message and then double
> checked
> > with the ncdump.
> >
> > So, are non-restricted prepbufr files not supported? Or, is there
a work
> > around for this?
> >
> > Thanks in advance.
> >
> > Roz
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu Jun 08 06:36:20 2017
>/opt/MET6/met6.0/bin/pb2nc
/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.prepbufr
/export/opcnfs/users/rfmaccracken/MET_output/test_window/uv_wind_pb_2017060500.nc
/export/opcnfs/users/rfmaccracken/MET_output/progs/oper_scr_progs_Jun3/PB2NCConfig_working
-v 2
DEBUG 1: Default Config File:
/opt/MET6/met6.0/share/met/config/PB2NCConfig_default
DEBUG 1: User Config File:
/export/opcnfs/users/rfmaccracken/MET_output/progs/oper_scr_progs_Jun3/PB2NCConfig_working
DEBUG 1: Creating NetCDF File:
/export/opcnfs/users/rfmaccracken/MET_output/test_window/uv_wind_pb_2017060500.nc
DEBUG 1: Processing PrepBufr File:
/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.prepbufr
DEBUG 1: Blocking PrepBufr file to: /tmp/tmp_pb2nc_blk_8367_0
DEBUG 2: PrepBufr Time Center: 20170605_000000
DEBUG 2: Searching Time Window: 20170604_210000 to 20170605_030000
DEBUG 2: Processing 959858 PrepBufr messages...
5% 10% 15% 20% 25% 30% 35% 40% 45% 50% 55% 60% 65% 70% 75% 80% 85% 90%
95%
DEBUG 2: Total PrepBufr Messages processed = 959858
DEBUG 2: Rejected based on message type = 761332
DEBUG 2: Rejected based on station id = 0
DEBUG 2: Rejected based on valid time = 0
DEBUG 2: Rejected based on masking grid = 0
DEBUG 2: Rejected based on masking polygon = 0
DEBUG 2: Rejected based on elevation = 0
DEBUG 2: Rejected based on pb report type = 0
DEBUG 2: Rejected based on input report type = 0
DEBUG 2: Rejected based on instrument type = 0
DEBUG 2: Rejected based on zero observations = 0
DEBUG 2: Total PrepBufr Messages retained = 198526
DEBUG 2: Total observations retained or derived = 595578
>/opt/MET6/met6.0/bin/point_stat
/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.master.grb2f00
/export/opcnfs/users/rfmaccracken/MET_output/test_window/uv_wind_pb_2017060500.nc
/export/opcnfs/users/rfmaccracken/MET_output/progs/oper_scr_progs_Jun3/PointStatConfig_working
-outdir /export/opcnfs/users/rfmaccracken/MET_output/test_window/ -v 3
DEBUG 1: Default Config File:
/opt/MET6/met6.0/share/met/config/PointStatConfig_default
DEBUG 1: User Config File:
/export/opcnfs/users/rfmaccracken/MET_output/progs/oper_scr_progs_Jun3/PointStatConfig_working
WARNING:
WARNING: Multiple GRIB2 table entries match lookup criteria (parm_name
= UGRD):
WARNING: parm_name: UGRD, index_a = 0, grib2_mtab = 1, grib2_cntr =
0, grib2_ltab = 0, index_b = 2, index_c = 2
WARNING: parm_name: UGRD, index_a = 0, grib2_mtab = 14, grib2_cntr =
57, grib2_ltab = 0, index_b = 2, index_c = 2
WARNING: Using: parm_name: UGRD, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0, grib2_ltab = 0, index_b = 2, index_c = 2
WARNING:
WARNING:
WARNING: Multiple GRIB2 table entries match lookup criteria (parm_name
= VGRD):
WARNING: parm_name: VGRD, index_a = 0, grib2_mtab = 1, grib2_cntr =
0, grib2_ltab = 0, index_b = 2, index_c = 3
WARNING: parm_name: VGRD, index_a = 0, grib2_mtab = 14, grib2_cntr =
57, grib2_ltab = 0, index_b = 2, index_c = 3
WARNING: Using: parm_name: VGRD, index_a = 0, grib2_mtab = 1,
grib2_cntr = 0, grib2_ltab = 0, index_b = 2, index_c = 3
WARNING:
GSL_RNG_TYPE=mt19937
GSL_RNG_SEED=18446744073462167897
DEBUG 1: Forecast File:
/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.master.grb2f00
DEBUG 1: Observation File:
/export/opcnfs/users/rfmaccracken/MET_output/test_window/uv_wind_pb_2017060500.nc
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for UGRD/Z10.
DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match for
"UGRD/Z10" in GRIB2 record 505 field 1 of GRIB2 file
"/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.master.grb2f00"
DEBUG 3: Use the matching forecast and observation grids.
DEBUG 3: Grid Definition: Projection: Lat/Lon Nx: 1440 Ny: 721 lat_ll:
-90.000 lon_ll: -0.000 delta_lat: 0.250 delta_lon: 0.250
DEBUG 2: Processing masking regions.
DEBUG 3: Processing grid mask: FULL
DEBUG 2: For UGRD/Z10 found 1 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for VGRD/Z10.
DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match for
"VGRD/Z10" in GRIB2 record 506 field 1 of GRIB2 file
"/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.master.grb2f00"
DEBUG 2: For VGRD/Z10 found 1 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Reading data for WIND/Z10.
DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match for
"WIND/Z10" in GRIB2 record 505 field 1 of GRIB2 file
"/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.master.grb2f00"
DEBUG 3: MetGrib2DataFile::data_plane_array() - Found exact match for
"WIND/Z10" in GRIB2 record 506 field 1 of GRIB2 file
"/export/opcnfs/users/rfmaccracken/MET_output/input_data/wcoss_prod_data/20170605/gfs.t00z.master.grb2f00"
DEBUG 3: Deriving wind speed from U and V wind components.
DEBUG 3:
DEBUG 3: MetGrib2DataFile::data_plane_array() - Wind speed/direction
derivation found 1 matching records found for 'WIND/Z10'
DEBUG 3:
DEBUG 2: For WIND/Z10 found 1 forecast levels and 0 climatology
levels.
DEBUG 2:
DEBUG 2:
--------------------------------------------------------------------------------
DEBUG 2:
DEBUG 2: Searching 595578 observations from 198526 messages.
ERROR :
ERROR : timestring_to_unix(const char *) -> can't parse date/time
string "0194514A"
ERROR :
------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: Howard Soh
Time: Thu Jun 08 06:49:41 2017
There was an overflow with global data (MET-796). It's fixed.
Cheers,
Howard
On Thu Jun 08 06:36:20 2017, rosalyn.maccracken at noaa.gov wrote:
> Hi John,
>
> I'm attaching a file of the input and output error message and the
two
> config files. It contains the the two commands that I used on the
> command
> line, for pb2nc (with the output message) and point_stat. Should I
> just
> share the data on the google drive? Or is it better to put them on
> the
> ftp site?
>
> Now, this all worked on wcoss, so, I don't know what's different.
> Also,
> this didn't work on WPC's machine either.
>
> Roz
>
> On Wed, Jun 7, 2017 at 8:05 PM, John Halley Gotway via RT
> <met_help at ucar.edu
> > wrote:
>
> > Roz,
> >
> > Yes, both restricted and non-restricted datasets *should* work
fine
> > in
> > PB2NC. This is the first time I've seen this type of behavior
> > reported, so
> > we'll need to dive into the details to diagnose the problem.
> >
> > Are you able to either send me the input PREPBUFR file you used or
> > point me
> > to it somewhere online? Also, please send me your PB2NC config
file
> > and
> > the command you ran on the command line.
> >
> > If I'm able to replicate the behavior here, it should be fairly
easy
> > to
> > debug.
> >
> > You can post data to our anonymous ftp site following these
> > instructions:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Wed, Jun 7, 2017 at 1:36 PM, Rosalyn MacCracken - NOAA
Affiliate
> > via RT
> > <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Jun 07 13:36:02 2017: Request 80781 was acted upon.
> > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > Queue: met_help
> > > Subject: pb2nc incorrectly making a netcdf file
> > > Owner: Nobody
> > > Requestors: rosalyn.maccracken at noaa.gov
> > > Status: new
> > > Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781 >
> > >
> > >
> > > Hi,
> > >
> > > I'm trying to make a netcdf file, using the MET software on my
> > > linux
> > > workstation (not wcoss). It was recently installed on my linux
> > workstation
> > > similar to the WPC installation. I am able to use pb2nc with a
> > > different
> > > prepbufr file than what I used on wcoss. This is a non-
restricted
> > > file,
> > > gfs.t00z.prepbufr.nr. The file was created "correctly", with no
> > > obvious
> > > errors. I quick check of the data, using ncdump -v obs_arr
> > > <prepbufr.nr
> > > ,
> > > shows good values. But, when I checked the date string,
hdr_vld, I
> > > got
> > > garbage in the beginning of the file, and good dates toward the
> > > end.
> > I've
> > > attached the ncdump file.
> > >
> > > Then, when I tried to use point_stat, I got the error message:
> > > ERROR : timestring_to_unix(const char *) -> can't parse
date/time
> > > string
> > > "0194514A"
> > >
> > > I actually tried point_stat first, got the message and then
double
> > checked
> > > with the ncdump.
> > >
> > > So, are non-restricted prepbufr files not supported? Or, is
there
> > > a work
> > > around for this?
> > >
> > > Thanks in advance.
> > >
> > > Roz
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: John Halley Gotway
Time: Thu Jun 08 07:36:58 2017
Roz,
One of our developers reminded me that we did already find and fix a
problem in the pb2nc tool. The fix is included in the set of bugfixes
posted to the MET website and that patch has already been applied to
the
wcoss version.
If you are compiling the original 6.0 release without the latest set
of
patches that would explain the difference in behavior.
Please apply the latest set of patches, recompile, and try again. I
suspect that'll solve this issue:
http://www.dtcenter.org/met/users/support/known_issues/METv6.0/index.php
Thanks,
John
On Thu, Jun 8, 2017 at 6:49 AM Howard Soh via RT <
met_help-comment at rap.ucar.edu> wrote:
>
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781
> This is a comment. It is not sent to the Requestor(s):
>
> There was an overflow with global data (MET-796). It's fixed.
>
> Cheers,
> Howard
>
> On Thu Jun 08 06:36:20 2017, rosalyn.maccracken at noaa.gov wrote:
> > Hi John,
> >
> > I'm attaching a file of the input and output error message and the
two
> > config files. It contains the the two commands that I used on the
> > command
> > line, for pb2nc (with the output message) and point_stat. Should
I
> > just
> > share the data on the google drive? Or is it better to put them
on
> > the
> > ftp site?
> >
> > Now, this all worked on wcoss, so, I don't know what's different.
> > Also,
> > this didn't work on WPC's machine either.
> >
> > Roz
> >
> > On Wed, Jun 7, 2017 at 8:05 PM, John Halley Gotway via RT
> > <met_help at ucar.edu
> > > wrote:
> >
> > > Roz,
> > >
> > > Yes, both restricted and non-restricted datasets *should* work
fine
> > > in
> > > PB2NC. This is the first time I've seen this type of behavior
> > > reported, so
> > > we'll need to dive into the details to diagnose the problem.
> > >
> > > Are you able to either send me the input PREPBUFR file you used
or
> > > point me
> > > to it somewhere online? Also, please send me your PB2NC config
file
> > > and
> > > the command you ran on the command line.
> > >
> > > If I'm able to replicate the behavior here, it should be fairly
easy
> > > to
> > > debug.
> > >
> > > You can post data to our anonymous ftp site following these
> > > instructions:
> > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Wed, Jun 7, 2017 at 1:36 PM, Rosalyn MacCracken - NOAA
Affiliate
> > > via RT
> > > <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Jun 07 13:36:02 2017: Request 80781 was acted upon.
> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > Queue: met_help
> > > > Subject: pb2nc incorrectly making a netcdf file
> > > > Owner: Nobody
> > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > Status: new
> > > > Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781 >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm trying to make a netcdf file, using the MET software on my
> > > > linux
> > > > workstation (not wcoss). It was recently installed on my
linux
> > > workstation
> > > > similar to the WPC installation. I am able to use pb2nc with
a
> > > > different
> > > > prepbufr file than what I used on wcoss. This is a non-
restricted
> > > > file,
> > > > gfs.t00z.prepbufr.nr. The file was created "correctly", with
no
> > > > obvious
> > > > errors. I quick check of the data, using ncdump -v obs_arr
> > > > <prepbufr.nr
> > > > ,
> > > > shows good values. But, when I checked the date string,
hdr_vld, I
> > > > got
> > > > garbage in the beginning of the file, and good dates toward
the
> > > > end.
> > > I've
> > > > attached the ncdump file.
> > > >
> > > > Then, when I tried to use point_stat, I got the error message:
> > > > ERROR : timestring_to_unix(const char *) -> can't parse
date/time
> > > > string
> > > > "0194514A"
> > > >
> > > > I actually tried point_stat first, got the message and then
double
> > > checked
> > > > with the ncdump.
> > > >
> > > > So, are non-restricted prepbufr files not supported? Or, is
there
> > > > a work
> > > > around for this?
> > > >
> > > > Thanks in advance.
> > > >
> > > > Roz
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
>
>
>
>
------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: John Halley Gotway
Time: Thu Jun 08 07:37:55 2017
Roz,
One of our developers reminded me that we did already find and fix a
problem in the pb2nc tool. The fix is included in the set of bugfixes
posted to the MET website and that patch has already been applied to
the
wcoss version.
If you are compiling the original 6.0 release without the latest set
of
patches that would explain the difference in behavior.
Please apply the latest set of patches, recompile, and try again. I
suspect that'll solve this issue:
http://www.dtcenter.org/met/users/support/known_issues/METv6.0/index.php
Thanks,
John
On Thu, Jun 8, 2017 at 6:36 AM Rosalyn MacCracken - NOAA Affiliate via
RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781 >
>
> Hi John,
>
> I'm attaching a file of the input and output error message and the
two
> config files. It contains the the two commands that I used on the
command
> line, for pb2nc (with the output message) and point_stat. Should I
just
> share the data on the google drive? Or is it better to put them on
the
> ftp site?
>
> Now, this all worked on wcoss, so, I don't know what's different.
Also,
> this didn't work on WPC's machine either.
>
> Roz
>
> On Wed, Jun 7, 2017 at 8:05 PM, John Halley Gotway via RT <
> met_help at ucar.edu
> > wrote:
>
> > Roz,
> >
> > Yes, both restricted and non-restricted datasets *should* work
fine in
> > PB2NC. This is the first time I've seen this type of behavior
reported,
> so
> > we'll need to dive into the details to diagnose the problem.
> >
> > Are you able to either send me the input PREPBUFR file you used or
point
> me
> > to it somewhere online? Also, please send me your PB2NC config
file and
> > the command you ran on the command line.
> >
> > If I'm able to replicate the behavior here, it should be fairly
easy to
> > debug.
> >
> > You can post data to our anonymous ftp site following these
instructions:
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > Thanks,
> > John Halley Gotway
> >
> > On Wed, Jun 7, 2017 at 1:36 PM, Rosalyn MacCracken - NOAA
Affiliate via
> RT
> > <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > Wed Jun 07 13:36:02 2017: Request 80781 was acted upon.
> > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > Queue: met_help
> > > Subject: pb2nc incorrectly making a netcdf file
> > > Owner: Nobody
> > > Requestors: rosalyn.maccracken at noaa.gov
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781
> >
> > >
> > >
> > > Hi,
> > >
> > > I'm trying to make a netcdf file, using the MET software on my
linux
> > > workstation (not wcoss). It was recently installed on my linux
> > workstation
> > > similar to the WPC installation. I am able to use pb2nc with a
> different
> > > prepbufr file than what I used on wcoss. This is a non-
restricted
> file,
> > > gfs.t00z.prepbufr.nr. The file was created "correctly", with no
> obvious
> > > errors. I quick check of the data, using ncdump -v obs_arr <
> prepbufr.nr
> > >,
> > > shows good values. But, when I checked the date string,
hdr_vld, I got
> > > garbage in the beginning of the file, and good dates toward the
end.
> > I've
> > > attached the ncdump file.
> > >
> > > Then, when I tried to use point_stat, I got the error message:
> > > ERROR : timestring_to_unix(const char *) -> can't parse
date/time
> string
> > > "0194514A"
> > >
> > > I actually tried point_stat first, got the message and then
double
> > checked
> > > with the ncdump.
> > >
> > > So, are non-restricted prepbufr files not supported? Or, is
there a
> work
> > > around for this?
> > >
> > > Thanks in advance.
> > >
> > > Roz
> > > --
> > > Rosalyn MacCracken
> > > Support Scientist
> > >
> > > Ocean Applilcations Branch
> > > NOAA/NWS Ocean Prediction Center
> > > NCWCP
> > > 5830 University Research Ct
> > > College Park, MD 20740-3818
> > >
> > > (p) 301-683-1551
> > > rosalyn.maccracken at noaa.gov
> > >
> > >
> >
> >
>
>
> --
> Rosalyn MacCracken
> Support Scientist
>
> Ocean Applilcations Branch
> NOAA/NWS Ocean Prediction Center
> NCWCP
> 5830 University Research Ct
> College Park, MD 20740-3818
>
> (p) 301-683-1551
> rosalyn.maccracken at noaa.gov
>
>
------------------------------------------------
Subject: pb2nc incorrectly making a netcdf file
From: Rosalyn MacCracken - NOAA Affiliate
Time: Thu Jun 08 07:41:43 2017
Hi John,
Ok, I'll have to put in a help ticket here to have it fixed and
recompiled. I don't get to get to do any of that stuff (thank
goodness).
I'll let you know how I make out.
Roz
On Thu, Jun 8, 2017 at 1:37 PM, John Halley Gotway via RT
<met_help at ucar.edu
> wrote:
> Roz,
>
> One of our developers reminded me that we did already find and fix a
> problem in the pb2nc tool. The fix is included in the set of
bugfixes
> posted to the MET website and that patch has already been applied to
the
> wcoss version.
>
> If you are compiling the original 6.0 release without the latest set
of
> patches that would explain the difference in behavior.
>
> Please apply the latest set of patches, recompile, and try again. I
> suspect that'll solve this issue:
>
>
http://www.dtcenter.org/met/users/support/known_issues/METv6.0/index.php
>
> Thanks,
> John
>
> On Thu, Jun 8, 2017 at 6:36 AM Rosalyn MacCracken - NOAA Affiliate
via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=80781 >
> >
> > Hi John,
> >
> > I'm attaching a file of the input and output error message and the
two
> > config files. It contains the the two commands that I used on the
> command
> > line, for pb2nc (with the output message) and point_stat. Should
I just
> > share the data on the google drive? Or is it better to put them
on the
> > ftp site?
> >
> > Now, this all worked on wcoss, so, I don't know what's different.
Also,
> > this didn't work on WPC's machine either.
> >
> > Roz
> >
> > On Wed, Jun 7, 2017 at 8:05 PM, John Halley Gotway via RT <
> > met_help at ucar.edu
> > > wrote:
> >
> > > Roz,
> > >
> > > Yes, both restricted and non-restricted datasets *should* work
fine in
> > > PB2NC. This is the first time I've seen this type of behavior
> reported,
> > so
> > > we'll need to dive into the details to diagnose the problem.
> > >
> > > Are you able to either send me the input PREPBUFR file you used
or
> point
> > me
> > > to it somewhere online? Also, please send me your PB2NC config
file
> and
> > > the command you ran on the command line.
> > >
> > > If I'm able to replicate the behavior here, it should be fairly
easy to
> > > debug.
> > >
> > > You can post data to our anonymous ftp site following these
> instructions:
> > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >
> > > Thanks,
> > > John Halley Gotway
> > >
> > > On Wed, Jun 7, 2017 at 1:36 PM, Rosalyn MacCracken - NOAA
Affiliate via
> > RT
> > > <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > Wed Jun 07 13:36:02 2017: Request 80781 was acted upon.
> > > > Transaction: Ticket created by rosalyn.maccracken at noaa.gov
> > > > Queue: met_help
> > > > Subject: pb2nc incorrectly making a netcdf file
> > > > Owner: Nobody
> > > > Requestors: rosalyn.maccracken at noaa.gov
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=80781
> > >
> > > >
> > > >
> > > > Hi,
> > > >
> > > > I'm trying to make a netcdf file, using the MET software on my
linux
> > > > workstation (not wcoss). It was recently installed on my
linux
> > > workstation
> > > > similar to the WPC installation. I am able to use pb2nc with
a
> > different
> > > > prepbufr file than what I used on wcoss. This is a non-
restricted
> > file,
> > > > gfs.t00z.prepbufr.nr. The file was created "correctly", with
no
> > obvious
> > > > errors. I quick check of the data, using ncdump -v obs_arr <
> > prepbufr.nr
> > > >,
> > > > shows good values. But, when I checked the date string,
hdr_vld, I
> got
> > > > garbage in the beginning of the file, and good dates toward
the end.
> > > I've
> > > > attached the ncdump file.
> > > >
> > > > Then, when I tried to use point_stat, I got the error message:
> > > > ERROR : timestring_to_unix(const char *) -> can't parse
date/time
> > string
> > > > "0194514A"
> > > >
> > > > I actually tried point_stat first, got the message and then
double
> > > checked
> > > > with the ncdump.
> > > >
> > > > So, are non-restricted prepbufr files not supported? Or, is
there a
> > work
> > > > around for this?
> > > >
> > > > Thanks in advance.
> > > >
> > > > Roz
> > > > --
> > > > Rosalyn MacCracken
> > > > Support Scientist
> > > >
> > > > Ocean Applilcations Branch
> > > > NOAA/NWS Ocean Prediction Center
> > > > NCWCP
> > > > 5830 University Research Ct
> > > > College Park, MD 20740-3818
> > > >
> > > > (p) 301-683-1551
> > > > rosalyn.maccracken at noaa.gov
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Rosalyn MacCracken
> > Support Scientist
> >
> > Ocean Applilcations Branch
> > NOAA/NWS Ocean Prediction Center
> > NCWCP
> > 5830 University Research Ct
> > College Park, MD 20740-3818
> >
> > (p) 301-683-1551
> > rosalyn.maccracken at noaa.gov
> >
> >
>
>
--
Rosalyn MacCracken
Support Scientist
Ocean Applilcations Branch
NOAA/NWS Ocean Prediction Center
NCWCP
5830 University Research Ct
College Park, MD 20740-3818
(p) 301-683-1551
rosalyn.maccracken at noaa.gov
------------------------------------------------
More information about the Met_help
mailing list