[Met_help] [rt.rap.ucar.edu #84897] History for PB2NC test failing with MET7.0 build
Julie Prestopnik via RT
met_help at ucar.edu
Wed May 2 10:02:51 MDT 2018
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I have built MET7.0 without any apparent compile errors. However, the tests fail when running pb2nc. The portion of the output from the "make test" is listed below. I have built with and without the -disable-block4 configure option and I get the same result. The pb2nc executables built with and without the -disable-block4 configure option are the same size, but are not identical.
I built MET and the bufr library under Linux x86_64, PGI compilers 15.7 (FORTRAN, C, C++). The configure statement was:
./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
./configure CFLAGS="-D__64BIT__" --disable-block4 --prefix=/...../king/met-7.0
----- Output from the "make test" ------------
*** Running PB2NC on a PREPBUFR file ***
../src/tools/other/pb2nc/pb2nc \
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr \
../out/pb2nc/sample_pb.nc \
config/PB2NCConfig_G212 \
-v 2
DEBUG 1: Default Config File: /...../met-7.0/share/met/config/PB2NCConfig_default
DEBUG 1: User Config File: config/PB2NCConfig_G212
DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
DEBUG 1: Pre-processing BUFR File for variable names from ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
DEBUG 1: process_pbfile_metadata() -> the number of records: 0
WARNING:
WARNING: process_pbfile_metadata() -> No Bufr messages to process in file: ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
WARNING:
DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
DEBUG 1: Blocking Bufr file to: /tmp/tmp_pb2nc_blk_9124_0
WARNING:
WARNING: process_pbfile() -> No Bufr messages to process in file: ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
WARNING:
ERROR :
ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained. Nothing to write.
ERROR :
make[1]: *** [pb2nc] Error 1
make[1]: Leaving directory `/..... /met-7.0/scripts'
make: *** [test] Error 2
Please let me know what additional information I need to provide.
Stephen Masters
Senior Staff Scientist
321-775-7548 (o)
321-254-3293 (f)
4849 North Wickham Road
Melbourne, FL 32940
www.ensco.com<http://www.ensco.com/>
[ENSCO, Inc.]
Innovation. Collaboration. Solutions. Success.
________________________________
The information contained in this email message is intended only for the use of the individual(s) to whom it is addressed and may contain information that is privileged and sensitive. If you are not the intended recipient, or otherwise have received this communication in error, please notify the sender immediately by email at the above referenced address and note that any further dissemination, distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of technology originating in the United States. This includes the electronic transmission of information and software to foreign countries and to certain foreign nationals. Recipient agrees to abide by these laws and their regulations -- including the U.S. Department of Commerce Export Administration Regulations and the U.S. Department of State International Traffic in Arms Regulations -- and not to transfer, by electronic transmission or otherwise, any content derived from this email to either a foreign national or a foreign destination in violation of such laws.
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: PB2NC test failing with MET7.0 build
From: Julie Prestopnik
Time: Thu Apr 26 12:45:43 2018
Hi Steve.
I see you are having problems with the MET test scripts. I believe
the
problem lies with the -D__64BIT__ option to the GRIB2C library and the
same
option going to MET. It used to be that if you used that option with
both
GRIB2C and MET, everything worked fine. That is no longer the case.
And,
unfortunately, the makefile for the GRIB2C lib has this option as the
default. Please try rebuilding and installing the GRIB2C library as
directed on this page:
https://dtcenter.org/met/users/support/online_tutorial/METv6.1/tutorial.php?name=compilation&category=req_libs
Then, please configure MET (without the -D__64BIT__ option) and run
make_install and make_test again. I expect the tests to run
successfully
after that. If they are unsuccessful, however, please let me know and
please attach your log files for configure, make_install, and
make_test so
that I can take a look.
I'll leave this ticket open for now. Please let me know if you get a
successful run of the tests, and then I'll close this ticket.
I hope this helps!
Julie
On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> Transaction: Ticket created by masters.steve at ensco.com
> Queue: met_help
> Subject: PB2NC test failing with MET7.0 build
> Owner: Nobody
> Requestors: masters.steve at ensco.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84897 >
>
>
> I have built MET7.0 without any apparent compile errors. However,
the
> tests fail when running pb2nc. The portion of the output from the
"make
> test" is listed below. I have built with and without the -disable-
block4
> configure option and I get the same result. The pb2nc executables
built
> with and without the -disable-block4 configure option are the same
size,
> but are not identical.
>
> I built MET and the bufr library under Linux x86_64, PGI compilers
15.7
> (FORTRAN, C, C++). The configure statement was:
>
> ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
> ...or...
> ./configure CFLAGS="-D__64BIT__" --disable-block4
> --prefix=/...../king/met-7.0
>
> ----- Output from the "make test" ------------
> *** Running PB2NC on a PREPBUFR file ***
> ../src/tools/other/pb2nc/pb2nc \
>
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr \
> ../out/pb2nc/sample_pb.nc \
> config/PB2NCConfig_G212 \
> -v 2
> DEBUG 1: Default Config File: /...../met-7.0/share/met/
> config/PB2NCConfig_default
> DEBUG 1: User Config File: config/PB2NCConfig_G212
> DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> DEBUG 1: Pre-processing BUFR File for variable names from
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> WARNING:
> WARNING: process_pbfile_metadata() -> No Bufr messages to process in
file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> as.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: Blocking Bufr file to: /tmp/tmp_pb2nc_blk_9124_0
> WARNING:
> WARNING: process_pbfile() -> No Bufr messages to process in file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> ERROR :
> ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> Nothing to write.
> ERROR :
> make[1]: *** [pb2nc] Error 1
> make[1]: Leaving directory `/..... /met-7.0/scripts'
> make: *** [test] Error 2
>
> Please let me know what additional information I need to provide.
>
> Stephen Masters
> Senior Staff Scientist
>
> 321-775-7548 (o)
> 321-254-3293 (f)
> 4849 North Wickham Road
> Melbourne, FL 32940
> www.ensco.com<http://www.ensco.com/>
>
> [ENSCO, Inc.]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
>
> The information contained in this email message is intended only for
the
> use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
intended
> recipient, or otherwise have received this communication in error,
please
> notify the sender immediately by email at the above referenced
address and
> note that any further dissemination, distribution or copying of this
> communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
electronic
> transmission of information and software to foreign countries and to
> certain foreign nationals. Recipient agrees to abide by these laws
and
> their regulations -- including the U.S. Department of Commerce
Export
> Administration Regulations and the U.S. Department of State
International
> Traffic in Arms Regulations -- and not to transfer, by electronic
> transmission or otherwise, any content derived from this email to
either a
> foreign national or a foreign destination in violation of such laws.
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0 build
From: Masters.Steve
Time: Thu Apr 26 18:51:13 2018
Julie --
I am still getting the same results as before. I am going to do
another "make clean" and do a rebuild again to make sure I am using
the options and libraries I think I am. I will capture the configure,
build, and test logs and send them to you either Friday or early next
week.
Steve Masters
ENSCO, Inc.
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Thursday, April 26, 2018 2:46 PM
To: Masters.Steve <masters.steve at ensco.com>
Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
build
Hi Steve.
I see you are having problems with the MET test scripts. I believe
the problem lies with the -D__64BIT__ option to the GRIB2C library and
the same option going to MET. It used to be that if you used that
option with both GRIB2C and MET, everything worked fine. That is no
longer the case. And, unfortunately, the makefile for the GRIB2C lib
has this option as the default. Please try rebuilding and installing
the GRIB2C library as directed on this page:
https://urldefense.proofpoint.com/v2/url?u=https-
3A__dtcenter.org_met_users_support_online-
5Ftutorial_METv6.1_tutorial.php-3Fname-3Dcompilation-26category-3Dreq-
5Flibs&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=GJN3Z4FXZiCBX735z2P5JDy0GWLuDG1UU_FLnKW_UYs&s=YkTpCdEGQ_ffnDnF0PpN1EptJAGIWmSPKFO_lpFXGcE&e=
Then, please configure MET (without the -D__64BIT__ option) and run
make_install and make_test again. I expect the tests to run
successfully after that. If they are unsuccessful, however, please
let me know and please attach your log files for configure,
make_install, and make_test so that I can take a look.
I'll leave this ticket open for now. Please let me know if you get a
successful run of the tests, and then I'll close this ticket.
I hope this helps!
Julie
On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> Transaction: Ticket created by masters.steve at ensco.com
> Queue: met_help
> Subject: PB2NC test failing with MET7.0 build
> Owner: Nobody
> Requestors: masters.steve at ensco.com
> Status: new
> Ticket <URL:
> https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu_r
> t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2
> UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=GJ
>
N3Z4FXZiCBX735z2P5JDy0GWLuDG1UU_FLnKW_UYs&s=RdaqDxKcIgfVYJVAMrXCcMW9Pv
> qNfXG7xjyVIbPNfPo&e= >
>
>
> I have built MET7.0 without any apparent compile errors. However,
the
> tests fail when running pb2nc. The portion of the output from the
> "make test" is listed below. I have built with and without the
> -disable-block4 configure option and I get the same result. The
pb2nc
> executables built with and without the -disable-block4 configure
> option are the same size, but are not identical.
>
> I built MET and the bufr library under Linux x86_64, PGI compilers
> 15.7 (FORTRAN, C, C++). The configure statement was:
>
> ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
> ./configure CFLAGS="-D__64BIT__" --disable-block4
> --prefix=/...../king/met-7.0
>
> ----- Output from the "make test" ------------
> *** Running PB2NC on a PREPBUFR file ***
> ../src/tools/other/pb2nc/pb2nc \
>
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr \
> ../out/pb2nc/sample_pb.nc \
> config/PB2NCConfig_G212 \
> -v 2
> DEBUG 1: Default Config File: /...../met-7.0/share/met/
> config/PB2NCConfig_default DEBUG 1: User Config File:
> config/PB2NCConfig_G212
> DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> DEBUG 1: Pre-processing BUFR File for variable names from
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> WARNING:
> WARNING: process_pbfile_metadata() -> No Bufr messages to process in
file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> as.t00z.prepbufr.tm12.20070401.nr DEBUG 1: Blocking Bufr file to:
> /tmp/tmp_pb2nc_blk_9124_0
> WARNING:
> WARNING: process_pbfile() -> No Bufr messages to process in file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> ERROR :
> ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> Nothing to write.
> ERROR :
> make[1]: *** [pb2nc] Error 1
> make[1]: Leaving directory `/..... /met-7.0/scripts'
> make: *** [test] Error 2
>
> Please let me know what additional information I need to provide.
>
> Stephen Masters
> Senior Staff Scientist
>
> 321-775-7548 (o)
> 321-254-3293 (f)
> 4849 North Wickham Road
> Melbourne, FL 32940
> www.ensco.com<http://www.ensco.com/>
>
> [ENSCO, Inc.]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
>
> The information contained in this email message is intended only for
> the use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
> intended recipient, or otherwise have received this communication in
> error, please notify the sender immediately by email at the above
> referenced address and note that any further dissemination,
> distribution or copying of this communication is strictly
prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
> electronic transmission of information and software to foreign
> countries and to certain foreign nationals. Recipient agrees to
abide
> by these laws and their regulations -- including the U.S. Department
> of Commerce Export Administration Regulations and the U.S.
Department
> of State International Traffic in Arms Regulations -- and not to
> transfer, by electronic transmission or otherwise, any content
derived
> from this email to either a foreign national or a foreign
destination in violation of such laws.
>
>
________________________________
The information contained in this email message is intended only for
the use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the
intended recipient, or otherwise have received this communication in
error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
------------------------------------------------
Subject: PB2NC test failing with MET7.0 build
From: Masters.Steve
Time: Fri Apr 27 07:47:00 2018
Julie --
I am still getting the same failure within pb2nc. I've attached the
script that I "source" to set the environment and build MET. I've
also attached the log files for the configure, make, install, and
test. I've included the versions with and without the --disable-
block4 configure option. The "config.log" is the file created using
the --disable-block4 option.
I am building the MET 7.0 code with the patch files of 3/27 and 4/03
applied.
One suggestion...the instructions under item 4 on page 27 of the
Users' Guide are confusing with respect to whether the -D__64BIT__
option should be set. It states that this option needs to be set
consistently between MET and g2clib, but doesn't recommend that it
actually not be set. The web page instructions are more clear on this
point. I am going from the users' guide instructions working through
the build. I recommend the users' guide and web pages' instructions
be made more consistent (or, alternatively, the printed guide points
to the web page for build instructions).
Steve Masters
ENSCO, Inc.
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Thursday, April 26, 2018 2:46 PM
To: Masters.Steve <masters.steve at ensco.com>
Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
build
Hi Steve.
I see you are having problems with the MET test scripts. I believe
the problem lies with the -D__64BIT__ option to the GRIB2C library and
the same option going to MET. It used to be that if you used that
option with both GRIB2C and MET, everything worked fine. That is no
longer the case. And, unfortunately, the makefile for the GRIB2C lib
has this option as the default. Please try rebuilding and installing
the GRIB2C library as directed on this page:
https://urldefense.proofpoint.com/v2/url?u=https-
3A__dtcenter.org_met_users_support_online-
5Ftutorial_METv6.1_tutorial.php-3Fname-3Dcompilation-26category-3Dreq-
5Flibs&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=GJN3Z4FXZiCBX735z2P5JDy0GWLuDG1UU_FLnKW_UYs&s=YkTpCdEGQ_ffnDnF0PpN1EptJAGIWmSPKFO_lpFXGcE&e=
Then, please configure MET (without the -D__64BIT__ option) and run
make_install and make_test again. I expect the tests to run
successfully after that. If they are unsuccessful, however, please
let me know and please attach your log files for configure,
make_install, and make_test so that I can take a look.
I'll leave this ticket open for now. Please let me know if you get a
successful run of the tests, and then I'll close this ticket.
I hope this helps!
Julie
On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> Transaction: Ticket created by masters.steve at ensco.com
> Queue: met_help
> Subject: PB2NC test failing with MET7.0 build
> Owner: Nobody
> Requestors: masters.steve at ensco.com
> Status: new
> Ticket <URL:
> https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu_r
> t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2
> UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=GJ
>
N3Z4FXZiCBX735z2P5JDy0GWLuDG1UU_FLnKW_UYs&s=RdaqDxKcIgfVYJVAMrXCcMW9Pv
> qNfXG7xjyVIbPNfPo&e= >
>
>
> I have built MET7.0 without any apparent compile errors. However,
the
> tests fail when running pb2nc. The portion of the output from the
> "make test" is listed below. I have built with and without the
> -disable-block4 configure option and I get the same result. The
pb2nc
> executables built with and without the -disable-block4 configure
> option are the same size, but are not identical.
>
> I built MET and the bufr library under Linux x86_64, PGI compilers
> 15.7 (FORTRAN, C, C++). The configure statement was:
>
> ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
> ./configure CFLAGS="-D__64BIT__" --disable-block4
> --prefix=/...../king/met-7.0
>
> ----- Output from the "make test" ------------
> *** Running PB2NC on a PREPBUFR file ***
> ../src/tools/other/pb2nc/pb2nc \
>
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr \
> ../out/pb2nc/sample_pb.nc \
> config/PB2NCConfig_G212 \
> -v 2
> DEBUG 1: Default Config File: /...../met-7.0/share/met/
> config/PB2NCConfig_default DEBUG 1: User Config File:
> config/PB2NCConfig_G212
> DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> DEBUG 1: Pre-processing BUFR File for variable names from
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> WARNING:
> WARNING: process_pbfile_metadata() -> No Bufr messages to process in
file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> as.t00z.prepbufr.tm12.20070401.nr DEBUG 1: Blocking Bufr file to:
> /tmp/tmp_pb2nc_blk_9124_0
> WARNING:
> WARNING: process_pbfile() -> No Bufr messages to process in file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> ERROR :
> ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> Nothing to write.
> ERROR :
> make[1]: *** [pb2nc] Error 1
> make[1]: Leaving directory `/..... /met-7.0/scripts'
> make: *** [test] Error 2
>
> Please let me know what additional information I need to provide.
>
> Stephen Masters
> Senior Staff Scientist
>
> 321-775-7548 (o)
> 321-254-3293 (f)
> 4849 North Wickham Road
> Melbourne, FL 32940
> www.ensco.com<http://www.ensco.com/>
>
> [ENSCO, Inc.]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
>
> The information contained in this email message is intended only for
> the use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
> intended recipient, or otherwise have received this communication in
> error, please notify the sender immediately by email at the above
> referenced address and note that any further dissemination,
> distribution or copying of this communication is strictly
prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
> electronic transmission of information and software to foreign
> countries and to certain foreign nationals. Recipient agrees to
abide
> by these laws and their regulations -- including the U.S. Department
> of Commerce Export Administration Regulations and the U.S.
Department
> of State International Traffic in Arms Regulations -- and not to
> transfer, by electronic transmission or otherwise, any content
derived
> from this email to either a foreign national or a foreign
destination in violation of such laws.
>
>
________________________________
The information contained in this email message is intended only for
the use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the
intended recipient, or otherwise have received this communication in
error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
------------------------------------------------
Subject: PB2NC test failing with MET7.0 build
From: Julie Prestopnik
Time: Fri Apr 27 13:53:38 2018
Hi Steve.
Can you please tell me what version of BUFRLIB you are using?
Thanks,
Julie
On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> Transaction: Ticket created by masters.steve at ensco.com
> Queue: met_help
> Subject: PB2NC test failing with MET7.0 build
> Owner: Nobody
> Requestors: masters.steve at ensco.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84897 >
>
>
> I have built MET7.0 without any apparent compile errors. However,
the
> tests fail when running pb2nc. The portion of the output from the
"make
> test" is listed below. I have built with and without the -disable-
block4
> configure option and I get the same result. The pb2nc executables
built
> with and without the -disable-block4 configure option are the same
size,
> but are not identical.
>
> I built MET and the bufr library under Linux x86_64, PGI compilers
15.7
> (FORTRAN, C, C++). The configure statement was:
>
> ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
> ...or...
> ./configure CFLAGS="-D__64BIT__" --disable-block4
> --prefix=/...../king/met-7.0
>
> ----- Output from the "make test" ------------
> *** Running PB2NC on a PREPBUFR file ***
> ../src/tools/other/pb2nc/pb2nc \
>
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr \
> ../out/pb2nc/sample_pb.nc \
> config/PB2NCConfig_G212 \
> -v 2
> DEBUG 1: Default Config File: /...../met-7.0/share/met/
> config/PB2NCConfig_default
> DEBUG 1: User Config File: config/PB2NCConfig_G212
> DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> DEBUG 1: Pre-processing BUFR File for variable names from
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> WARNING:
> WARNING: process_pbfile_metadata() -> No Bufr messages to process in
file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> as.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: Blocking Bufr file to: /tmp/tmp_pb2nc_blk_9124_0
> WARNING:
> WARNING: process_pbfile() -> No Bufr messages to process in file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> ERROR :
> ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> Nothing to write.
> ERROR :
> make[1]: *** [pb2nc] Error 1
> make[1]: Leaving directory `/..... /met-7.0/scripts'
> make: *** [test] Error 2
>
> Please let me know what additional information I need to provide.
>
> Stephen Masters
> Senior Staff Scientist
>
> 321-775-7548 (o)
> 321-254-3293 (f)
> 4849 North Wickham Road
> Melbourne, FL 32940
> www.ensco.com<http://www.ensco.com/>
>
> [ENSCO, Inc.]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
>
> The information contained in this email message is intended only for
the
> use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
intended
> recipient, or otherwise have received this communication in error,
please
> notify the sender immediately by email at the above referenced
address and
> note that any further dissemination, distribution or copying of this
> communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
electronic
> transmission of information and software to foreign countries and to
> certain foreign nationals. Recipient agrees to abide by these laws
and
> their regulations -- including the U.S. Department of Commerce
Export
> Administration Regulations and the U.S. Department of State
International
> Traffic in Arms Regulations -- and not to transfer, by electronic
> transmission or otherwise, any content derived from this email to
either a
> foreign national or a foreign destination in violation of such laws.
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0 build
From: Masters.Steve
Time: Sat Apr 28 11:09:45 2018
Julie --
Based on the name of the tar file, it appears to be 10.2.3.
--Steve
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Friday, April 27, 2018 3:54 PM
To: Masters.Steve <masters.steve at ensco.com>
Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
build
Hi Steve.
Can you please tell me what version of BUFRLIB you are using?
Thanks,
Julie
On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> Transaction: Ticket created by masters.steve at ensco.com
> Queue: met_help
> Subject: PB2NC test failing with MET7.0 build
> Owner: Nobody
> Requestors: masters.steve at ensco.com
> Status: new
> Ticket <URL:
> https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu_r
> t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2
> UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=yY
> uzkozcKLAx5LnEOOB0gza7ovJgXhzgNHgO1wbOODc&s=T3PztC-_tHr-
BNvh1wP3LC5SUB
> zSi-TqRxOghgCG0T0&e= >
>
>
> I have built MET7.0 without any apparent compile errors. However,
the
> tests fail when running pb2nc. The portion of the output from the
> "make test" is listed below. I have built with and without the
> -disable-block4 configure option and I get the same result. The
pb2nc
> executables built with and without the -disable-block4 configure
> option are the same size, but are not identical.
>
> I built MET and the bufr library under Linux x86_64, PGI compilers
> 15.7 (FORTRAN, C, C++). The configure statement was:
>
> ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
> ./configure CFLAGS="-D__64BIT__" --disable-block4
> --prefix=/...../king/met-7.0
>
> ----- Output from the "make test" ------------
> *** Running PB2NC on a PREPBUFR file ***
> ../src/tools/other/pb2nc/pb2nc \
>
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr \
> ../out/pb2nc/sample_pb.nc \
> config/PB2NCConfig_G212 \
> -v 2
> DEBUG 1: Default Config File: /...../met-7.0/share/met/
> config/PB2NCConfig_default DEBUG 1: User Config File:
> config/PB2NCConfig_G212
> DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> DEBUG 1: Pre-processing BUFR File for variable names from
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> WARNING:
> WARNING: process_pbfile_metadata() -> No Bufr messages to process in
file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> as.t00z.prepbufr.tm12.20070401.nr DEBUG 1: Blocking Bufr file to:
> /tmp/tmp_pb2nc_blk_9124_0
> WARNING:
> WARNING: process_pbfile() -> No Bufr messages to process in file:
> ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> WARNING:
> ERROR :
> ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> Nothing to write.
> ERROR :
> make[1]: *** [pb2nc] Error 1
> make[1]: Leaving directory `/..... /met-7.0/scripts'
> make: *** [test] Error 2
>
> Please let me know what additional information I need to provide.
>
> Stephen Masters
> Senior Staff Scientist
>
> 321-775-7548 (o)
> 321-254-3293 (f)
> 4849 North Wickham Road
> Melbourne, FL 32940
> www.ensco.com<http://www.ensco.com/>
>
> [ENSCO, Inc.]
> Innovation. Collaboration. Solutions. Success.
>
>
> ________________________________
>
> The information contained in this email message is intended only for
> the use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
> intended recipient, or otherwise have received this communication in
> error, please notify the sender immediately by email at the above
> referenced address and note that any further dissemination,
> distribution or copying of this communication is strictly
prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
> electronic transmission of information and software to foreign
> countries and to certain foreign nationals. Recipient agrees to
abide
> by these laws and their regulations -- including the U.S. Department
> of Commerce Export Administration Regulations and the U.S.
Department
> of State International Traffic in Arms Regulations -- and not to
> transfer, by electronic transmission or otherwise, any content
derived
> from this email to either a foreign national or a foreign
destination in violation of such laws.
>
>
________________________________
The information contained in this email message is intended only for
the use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the
intended recipient, or otherwise have received this communication in
error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
------------------------------------------------
Subject: PB2NC test failing with MET7.0 build
From: Julie Prestopnik
Time: Mon Apr 30 09:48:59 2018
Hi Steve.
This one was a bit tricky.
I believe the problem lies with BUFRLIB being compiled with pgf90 and
MET
being compiled with pgf77.
While I believe our code has been updated to compile with pgf90, I see
that
our instructions in the online tutorial say:
Set *F77* to the full path for your Fortran 90 compiler (recommend GNU
> *gfortran*, PGI *pgf90*, or Intel *ifort*).
>
From:
https://dtcenter.org/met/users/support/online_tutorial/METv6.1/tutorial.php?name=compilation&category=configure
While I know it seems odd to set F77 equal to ppf90, I believe this
was a
quick fix to resolve this exact issue, and that we have not yet
updated our
code to look for F90. So, instead it is looking for F77, but it still
needs to be set to pgf90.
I see in your do.make.csh file you have set:
setenv F77 /opt/pgi/linux86-64/15.7/bin/pgf77
setenv F90 /opt/pgi/linux86-64/15.7/bin/pgf90
Please try setting:
setenv F77 /opt/pgi/linux86-64/15.7/bin/pgf90
>
instead and let me know how that works. Thank you for your patience as
we
fully resolve this issue with the MET code.
Julie
On Sat, Apr 28, 2018 at 11:09 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84897 >
>
> Julie --
>
> Based on the name of the tar file, it appears to be 10.2.3.
>
> --Steve
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Friday, April 27, 2018 3:54 PM
> To: Masters.Steve <masters.steve at ensco.com>
> Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
build
>
> Hi Steve.
>
> Can you please tell me what version of BUFRLIB you are using?
>
> Thanks,
> Julie
>
> On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> > Transaction: Ticket created by masters.steve at ensco.com
> > Queue: met_help
> > Subject: PB2NC test failing with MET7.0 build
> > Owner: Nobody
> > Requestors: masters.steve at ensco.com
> > Status: new
> > Ticket <URL:
> > https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu_r
> > t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2
> > UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=yY
> > uzkozcKLAx5LnEOOB0gza7ovJgXhzgNHgO1wbOODc&s=T3PztC-_tHr-
BNvh1wP3LC5SUB
> > zSi-TqRxOghgCG0T0&e= >
> >
> >
> > I have built MET7.0 without any apparent compile errors. However,
the
> > tests fail when running pb2nc. The portion of the output from the
> > "make test" is listed below. I have built with and without the
> > -disable-block4 configure option and I get the same result. The
pb2nc
> > executables built with and without the -disable-block4 configure
> > option are the same size, but are not identical.
> >
> > I built MET and the bufr library under Linux x86_64, PGI compilers
> > 15.7 (FORTRAN, C, C++). The configure statement was:
> >
> > ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
> > ./configure CFLAGS="-D__64BIT__" --disable-block4
> > --prefix=/...../king/met-7.0
> >
> > ----- Output from the "make test" ------------
> > *** Running PB2NC on a PREPBUFR file ***
> > ../src/tools/other/pb2nc/pb2nc \
> >
../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> \
> > ../out/pb2nc/sample_pb.nc \
> > config/PB2NCConfig_G212 \
> > -v 2
> > DEBUG 1: Default Config File: /...../met-7.0/share/met/
> > config/PB2NCConfig_default DEBUG 1: User Config File:
> > config/PB2NCConfig_G212
> > DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> > DEBUG 1: Pre-processing BUFR File for variable names from
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> > WARNING:
> > WARNING: process_pbfile_metadata() -> No Bufr messages to process
in
> file:
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > WARNING:
> > DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> > as.t00z.prepbufr.tm12.20070401.nr DEBUG 1: Blocking Bufr file to:
> > /tmp/tmp_pb2nc_blk_9124_0
> > WARNING:
> > WARNING: process_pbfile() -> No Bufr messages to process in file:
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > WARNING:
> > ERROR :
> > ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> > Nothing to write.
> > ERROR :
> > make[1]: *** [pb2nc] Error 1
> > make[1]: Leaving directory `/..... /met-7.0/scripts'
> > make: *** [test] Error 2
> >
> > Please let me know what additional information I need to provide.
> >
> > Stephen Masters
> > Senior Staff Scientist
> >
> > 321-775-7548 (o)
> > 321-254-3293 (f)
> > 4849 North Wickham Road
> > Melbourne, FL 32940
> > www.ensco.com<http://www.ensco.com/>
> >
> > [ENSCO, Inc.]
> > Innovation. Collaboration. Solutions. Success.
> >
> >
> > ________________________________
> >
> > The information contained in this email message is intended only
for
> > the use of the individual(s) to whom it is addressed and may
contain
> > information that is privileged and sensitive. If you are not the
> > intended recipient, or otherwise have received this communication
in
> > error, please notify the sender immediately by email at the above
> > referenced address and note that any further dissemination,
> > distribution or copying of this communication is strictly
prohibited.
> >
> > The U.S. Export Control Laws regulate the export and re-export of
> > technology originating in the United States. This includes the
> > electronic transmission of information and software to foreign
> > countries and to certain foreign nationals. Recipient agrees to
abide
> > by these laws and their regulations -- including the U.S.
Department
> > of Commerce Export Administration Regulations and the U.S.
Department
> > of State International Traffic in Arms Regulations -- and not to
> > transfer, by electronic transmission or otherwise, any content
derived
> > from this email to either a foreign national or a foreign
destination in
> violation of such laws.
> >
> >
>
>
> ________________________________
>
> The information contained in this email message is intended only for
the
> use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
intended
> recipient, or otherwise have received this communication in error,
please
> notify the sender immediately by email at the above referenced
address and
> note that any further dissemination, distribution or copying of this
> communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
electronic
> transmission of information and software to foreign countries and to
> certain foreign nationals. Recipient agrees to abide by these laws
and
> their regulations -- including the U.S. Department of Commerce
Export
> Administration Regulations and the U.S. Department of State
International
> Traffic in Arms Regulations -- and not to transfer, by electronic
> transmission or otherwise, any content derived from this email to
either a
> foreign national or a foreign destination in violation of such laws.
>
>
>
------------------------------------------------
Subject: RE: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0 build
From: Masters.Steve
Time: Tue May 01 08:19:09 2018
Hi Julie --
Success! The change in compiler to pgf90 fixed the problem. The MET
software compiled successfully and it looks like all of the tests
passed. For this system/compiler, I used the default -DBLOCK4
setting.
Thank you!
Steve Masters
ENSCO, Inc.
Melbourne, FL
-----Original Message-----
From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
Sent: Monday, April 30, 2018 11:49 AM
To: Masters.Steve <masters.steve at ensco.com>
Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
build
Hi Steve.
This one was a bit tricky.
I believe the problem lies with BUFRLIB being compiled with pgf90 and
MET being compiled with pgf77.
While I believe our code has been updated to compile with pgf90, I see
that our instructions in the online tutorial say:
Set *F77* to the full path for your Fortran 90 compiler (recommend GNU
> *gfortran*, PGI *pgf90*, or Intel *ifort*).
>
From:
https://urldefense.proofpoint.com/v2/url?u=https-
3A__dtcenter.org_met_users_support_online-
5Ftutorial_METv6.1_tutorial.php-3Fname-3Dcompilation-26category-
3Dconfigure&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=-cSzsiU3ABuLQ-rZpzxlBfo5PmAmPrxVZVTN-
a2EeYA&s=GYlgqlbaDbayBNSEOVI8TPzZDF3VhJvGhJADVYeMZX4&e=
While I know it seems odd to set F77 equal to ppf90, I believe this
was a quick fix to resolve this exact issue, and that we have not yet
updated our code to look for F90. So, instead it is looking for F77,
but it still needs to be set to pgf90.
I see in your do.make.csh file you have set:
setenv F77 /opt/pgi/linux86-64/15.7/bin/pgf77
setenv F90 /opt/pgi/linux86-64/15.7/bin/pgf90
Please try setting:
setenv F77 /opt/pgi/linux86-64/15.7/bin/pgf90
>
instead and let me know how that works. Thank you for your patience as
we fully resolve this issue with the MET code.
Julie
On Sat, Apr 28, 2018 at 11:09 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> <URL:
> https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu_r
> t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2
> UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=-c
> SzsiU3ABuLQ-rZpzxlBfo5PmAmPrxVZVTN-
a2EeYA&s=apVP_KAuQnQQSMIk8rDWXpvVfJ
> 3O3dKwOt-JLYQrefw&e= >
>
> Julie --
>
> Based on the name of the tar file, it appears to be 10.2.3.
>
> --Steve
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Friday, April 27, 2018 3:54 PM
> To: Masters.Steve <masters.steve at ensco.com>
> Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
> build
>
> Hi Steve.
>
> Can you please tell me what version of BUFRLIB you are using?
>
> Thanks,
> Julie
>
> On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
> <met_help at ucar.edu>
> wrote:
>
> >
> > Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> > Transaction: Ticket created by masters.steve at ensco.com
> > Queue: met_help
> > Subject: PB2NC test failing with MET7.0 build
> > Owner: Nobody
> > Requestors: masters.steve at ensco.com
> > Status: new
> > Ticket <URL:
> > https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu
> > _r
> > t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0
> > F2
> > UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=
> > yY
> > uzkozcKLAx5LnEOOB0gza7ovJgXhzgNHgO1wbOODc&s=T3PztC-_tHr-
BNvh1wP3LC5S
> > UB
> > zSi-TqRxOghgCG0T0&e= >
> >
> >
> > I have built MET7.0 without any apparent compile errors. However,
> > the tests fail when running pb2nc. The portion of the output from
> > the "make test" is listed below. I have built with and without
the
> > -disable-block4 configure option and I get the same result. The
> > pb2nc executables built with and without the -disable-block4
> > configure option are the same size, but are not identical.
> >
> > I built MET and the bufr library under Linux x86_64, PGI compilers
> > 15.7 (FORTRAN, C, C++). The configure statement was:
> >
> > ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
> > ./configure CFLAGS="-D__64BIT__" --disable-block4
> > --prefix=/...../king/met-7.0
> >
> > ----- Output from the "make test" ------------
> > *** Running PB2NC on a PREPBUFR file ***
> > ../src/tools/other/pb2nc/pb2nc \
> >
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> \
> > ../out/pb2nc/sample_pb.nc \
> > config/PB2NCConfig_G212 \
> > -v 2
> > DEBUG 1: Default Config File: /...../met-7.0/share/met/
> > config/PB2NCConfig_default DEBUG 1: User Config File:
> > config/PB2NCConfig_G212
> > DEBUG 1: Creating NetCDF File: ../out/pb2nc/sample_pb.nc
> > DEBUG 1: Pre-processing BUFR File for variable names from
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> > WARNING:
> > WARNING: process_pbfile_metadata() -> No Bufr messages to process
in
> file:
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > WARNING:
> > DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> > as.t00z.prepbufr.tm12.20070401.nr DEBUG 1: Blocking Bufr file to:
> > /tmp/tmp_pb2nc_blk_9124_0
> > WARNING:
> > WARNING: process_pbfile() -> No Bufr messages to process in file:
> > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > WARNING:
> > ERROR :
> > ERROR : write_netcdf_hdr_data() -> No PrepBufr messages retained.
> > Nothing to write.
> > ERROR :
> > make[1]: *** [pb2nc] Error 1
> > make[1]: Leaving directory `/..... /met-7.0/scripts'
> > make: *** [test] Error 2
> >
> > Please let me know what additional information I need to provide.
> >
> > Stephen Masters
> > Senior Staff Scientist
> >
> > 321-775-7548 (o)
> > 321-254-3293 (f)
> > 4849 North Wickham Road
> > Melbourne, FL 32940
> > www.ensco.com<http://www.ensco.com/>
> >
> > [ENSCO, Inc.]
> > Innovation. Collaboration. Solutions. Success.
> >
> >
> > ________________________________
> >
> > The information contained in this email message is intended only
for
> > the use of the individual(s) to whom it is addressed and may
contain
> > information that is privileged and sensitive. If you are not the
> > intended recipient, or otherwise have received this communication
in
> > error, please notify the sender immediately by email at the above
> > referenced address and note that any further dissemination,
> > distribution or copying of this communication is strictly
prohibited.
> >
> > The U.S. Export Control Laws regulate the export and re-export of
> > technology originating in the United States. This includes the
> > electronic transmission of information and software to foreign
> > countries and to certain foreign nationals. Recipient agrees to
> > abide by these laws and their regulations -- including the U.S.
> > Department of Commerce Export Administration Regulations and the
> > U.S. Department of State International Traffic in Arms Regulations
> > -- and not to transfer, by electronic transmission or otherwise,
any
> > content derived from this email to either a foreign national or a
> > foreign destination in
> violation of such laws.
> >
> >
>
>
> ________________________________
>
> The information contained in this email message is intended only for
> the use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
> intended recipient, or otherwise have received this communication in
> error, please notify the sender immediately by email at the above
> referenced address and note that any further dissemination,
> distribution or copying of this communication is strictly
prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
> electronic transmission of information and software to foreign
> countries and to certain foreign nationals. Recipient agrees to
abide
> by these laws and their regulations -- including the U.S. Department
> of Commerce Export Administration Regulations and the U.S.
Department
> of State International Traffic in Arms Regulations -- and not to
> transfer, by electronic transmission or otherwise, any content
derived
> from this email to either a foreign national or a foreign
destination in violation of such laws.
>
>
>
________________________________
The information contained in this email message is intended only for
the use of the individual(s) to whom it is addressed and may contain
information that is privileged and sensitive. If you are not the
intended recipient, or otherwise have received this communication in
error, please notify the sender immediately by email at the above
referenced address and note that any further dissemination,
distribution or copying of this communication is strictly prohibited.
The U.S. Export Control Laws regulate the export and re-export of
technology originating in the United States. This includes the
electronic transmission of information and software to foreign
countries and to certain foreign nationals. Recipient agrees to abide
by these laws and their regulations -- including the U.S. Department
of Commerce Export Administration Regulations and the U.S. Department
of State International Traffic in Arms Regulations -- and not to
transfer, by electronic transmission or otherwise, any content derived
from this email to either a foreign national or a foreign destination
in violation of such laws.
------------------------------------------------
Subject: PB2NC test failing with MET7.0 build
From: Julie Prestopnik
Time: Tue May 01 11:22:30 2018
That's great news, Steve! Thank you for following up and letting us
know.
Julie
On Tue, May 1, 2018 at 8:19 AM, Masters.Steve via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=84897 >
>
> Hi Julie --
>
> Success! The change in compiler to pgf90 fixed the problem. The
MET
> software compiled successfully and it looks like all of the tests
passed.
> For this system/compiler, I used the default -DBLOCK4 setting.
>
> Thank you!
>
> Steve Masters
> ENSCO, Inc.
> Melbourne, FL
>
> -----Original Message-----
> From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> Sent: Monday, April 30, 2018 11:49 AM
> To: Masters.Steve <masters.steve at ensco.com>
> Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with MET7.0
build
>
> Hi Steve.
>
> This one was a bit tricky.
>
> I believe the problem lies with BUFRLIB being compiled with pgf90
and MET
> being compiled with pgf77.
>
> While I believe our code has been updated to compile with pgf90, I
see
> that our instructions in the online tutorial say:
>
> Set *F77* to the full path for your Fortran 90 compiler (recommend
GNU
> > *gfortran*, PGI *pgf90*, or Intel *ifort*).
> >
>
> From:
>
> https://urldefense.proofpoint.com/v2/url?u=https-3A__
> dtcenter.org_met_users_support_online-5Ftutorial_
> METv6.1_tutorial.php-3Fname-3Dcompilation-26category-
> 3Dconfigure&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2UfNQZUfZhEPCv_2wBI0&r=
> VuUP78D2VHO8ziN7eh-DsCgmMeBUeha5u93niBuCCaE&m=-cSzsiU3ABuLQ-
> rZpzxlBfo5PmAmPrxVZVTN-a2EeYA&s=GYlgqlbaDbayBNSEOVI8TPzZDF3VhJ
> vGhJADVYeMZX4&e=
>
> While I know it seems odd to set F77 equal to ppf90, I believe this
was a
> quick fix to resolve this exact issue, and that we have not yet
updated our
> code to look for F90. So, instead it is looking for F77, but it
still
> needs to be set to pgf90.
>
> I see in your do.make.csh file you have set:
>
> setenv F77 /opt/pgi/linux86-64/15.7/bin/pgf77
> setenv F90 /opt/pgi/linux86-64/15.7/bin/pgf90
>
> Please try setting:
>
> setenv F77 /opt/pgi/linux86-64/15.7/bin/pgf90
> >
>
> instead and let me know how that works. Thank you for your patience
as we
> fully resolve this issue with the MET code.
>
> Julie
>
> On Sat, Apr 28, 2018 at 11:09 AM, Masters.Steve via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL:
> > https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu_r
> > t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0F2
> > UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=-c
> > SzsiU3ABuLQ-rZpzxlBfo5PmAmPrxVZVTN-
a2EeYA&s=apVP_KAuQnQQSMIk8rDWXpvVfJ
> > 3O3dKwOt-JLYQrefw&e= >
> >
> > Julie --
> >
> > Based on the name of the tar file, it appears to be 10.2.3.
> >
> > --Steve
> >
> > -----Original Message-----
> > From: Julie Prestopnik via RT [mailto:met_help at ucar.edu]
> > Sent: Friday, April 27, 2018 3:54 PM
> > To: Masters.Steve <masters.steve at ensco.com>
> > Subject: Re: [rt.rap.ucar.edu #84897] PB2NC test failing with
MET7.0
> > build
> >
> > Hi Steve.
> >
> > Can you please tell me what version of BUFRLIB you are using?
> >
> > Thanks,
> > Julie
> >
> > On Thu, Apr 26, 2018 at 11:30 AM, Masters.Steve via RT
> > <met_help at ucar.edu>
> > wrote:
> >
> > >
> > > Thu Apr 26 11:30:13 2018: Request 84897 was acted upon.
> > > Transaction: Ticket created by masters.steve at ensco.com
> > > Queue: met_help
> > > Subject: PB2NC test failing with MET7.0 build
> > > Owner: Nobody
> > > Requestors: masters.steve at ensco.com
> > > Status: new
> > > Ticket <URL:
> > > https://urldefense.proofpoint.com/v2/url?u=https-
3A__rt.rap.ucar.edu
> > > _r
> > > t_Ticket_Display.html-3Fid-3D84897&d=DwIDaQ&c=DsZY2bea7iNIzyp-
7sZ0t0
> > > F2
> > > UfNQZUfZhEPCv_2wBI0&r=VuUP78D2VHO8ziN7eh-
DsCgmMeBUeha5u93niBuCCaE&m=
> > > yY
> > > uzkozcKLAx5LnEOOB0gza7ovJgXhzgNHgO1wbOODc&s=T3PztC-_tHr-
BNvh1wP3LC5S
> > > UB
> > > zSi-TqRxOghgCG0T0&e= >
> > >
> > >
> > > I have built MET7.0 without any apparent compile errors.
However,
> > > the tests fail when running pb2nc. The portion of the output
from
> > > the "make test" is listed below. I have built with and without
the
> > > -disable-block4 configure option and I get the same result. The
> > > pb2nc executables built with and without the -disable-block4
> > > configure option are the same size, but are not identical.
> > >
> > > I built MET and the bufr library under Linux x86_64, PGI
compilers
> > > 15.7 (FORTRAN, C, C++). The configure statement was:
> > >
> > > ./configure CFLAGS="-D__64BIT__" --prefix=/..../king/met-7.0
...or...
> > > ./configure CFLAGS="-D__64BIT__" --disable-block4
> > > --prefix=/...../king/met-7.0
> > >
> > > ----- Output from the "make test" ------------
> > > *** Running PB2NC on a PREPBUFR file ***
> > > ../src/tools/other/pb2nc/pb2nc \
> > >
> > > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > \
> > > ../out/pb2nc/sample_pb.nc \
> > > config/PB2NCConfig_G212 \
> > > -v 2
> > > DEBUG 1: Default Config File: /...../met-7.0/share/met/
> > > config/PB2NCConfig_default DEBUG 1: User Config File:
> > > config/PB2NCConfig_G212
> > > DEBUG 1: Creating NetCDF File:
../out/pb2nc/sample_pb.nc
> > > DEBUG 1: Pre-processing BUFR File for variable names from
> > > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > > DEBUG 1: process_pbfile_metadata() -> the number of records: 0
> > > WARNING:
> > > WARNING: process_pbfile_metadata() -> No Bufr messages to
process in
> > file:
> > > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > > WARNING:
> > > DEBUG 1: Processing Bufr File: ../data/sample_obs/prepbufr/nd
> > > as.t00z.prepbufr.tm12.20070401.nr DEBUG 1: Blocking Bufr file
to:
> > > /tmp/tmp_pb2nc_blk_9124_0
> > > WARNING:
> > > WARNING: process_pbfile() -> No Bufr messages to process in
file:
> > > ../data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr
> > > WARNING:
> > > ERROR :
> > > ERROR : write_netcdf_hdr_data() -> No PrepBufr messages
retained.
> > > Nothing to write.
> > > ERROR :
> > > make[1]: *** [pb2nc] Error 1
> > > make[1]: Leaving directory `/..... /met-7.0/scripts'
> > > make: *** [test] Error 2
> > >
> > > Please let me know what additional information I need to
provide.
> > >
> > > Stephen Masters
> > > Senior Staff Scientist
> > >
> > > 321-775-7548 (o)
> > > 321-254-3293 (f)
> > > 4849 North Wickham Road
> > > Melbourne, FL 32940
> > > www.ensco.com<http://www.ensco.com/>
> > >
> > > [ENSCO, Inc.]
> > > Innovation. Collaboration. Solutions. Success.
> > >
> > >
> > > ________________________________
> > >
> > > The information contained in this email message is intended only
for
> > > the use of the individual(s) to whom it is addressed and may
contain
> > > information that is privileged and sensitive. If you are not the
> > > intended recipient, or otherwise have received this
communication in
> > > error, please notify the sender immediately by email at the
above
> > > referenced address and note that any further dissemination,
> > > distribution or copying of this communication is strictly
prohibited.
> > >
> > > The U.S. Export Control Laws regulate the export and re-export
of
> > > technology originating in the United States. This includes the
> > > electronic transmission of information and software to foreign
> > > countries and to certain foreign nationals. Recipient agrees to
> > > abide by these laws and their regulations -- including the U.S.
> > > Department of Commerce Export Administration Regulations and the
> > > U.S. Department of State International Traffic in Arms
Regulations
> > > -- and not to transfer, by electronic transmission or otherwise,
any
> > > content derived from this email to either a foreign national or
a
> > > foreign destination in
> > violation of such laws.
> > >
> > >
> >
> >
> > ________________________________
> >
> > The information contained in this email message is intended only
for
> > the use of the individual(s) to whom it is addressed and may
contain
> > information that is privileged and sensitive. If you are not the
> > intended recipient, or otherwise have received this communication
in
> > error, please notify the sender immediately by email at the above
> > referenced address and note that any further dissemination,
> > distribution or copying of this communication is strictly
prohibited.
> >
> > The U.S. Export Control Laws regulate the export and re-export of
> > technology originating in the United States. This includes the
> > electronic transmission of information and software to foreign
> > countries and to certain foreign nationals. Recipient agrees to
abide
> > by these laws and their regulations -- including the U.S.
Department
> > of Commerce Export Administration Regulations and the U.S.
Department
> > of State International Traffic in Arms Regulations -- and not to
> > transfer, by electronic transmission or otherwise, any content
derived
> > from this email to either a foreign national or a foreign
destination in
> violation of such laws.
> >
> >
> >
>
>
> ________________________________
>
> The information contained in this email message is intended only for
the
> use of the individual(s) to whom it is addressed and may contain
> information that is privileged and sensitive. If you are not the
intended
> recipient, or otherwise have received this communication in error,
please
> notify the sender immediately by email at the above referenced
address and
> note that any further dissemination, distribution or copying of this
> communication is strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of
> technology originating in the United States. This includes the
electronic
> transmission of information and software to foreign countries and to
> certain foreign nationals. Recipient agrees to abide by these laws
and
> their regulations -- including the U.S. Department of Commerce
Export
> Administration Regulations and the U.S. Department of State
International
> Traffic in Arms Regulations -- and not to transfer, by electronic
> transmission or otherwise, any content derived from this email to
either a
> foreign national or a foreign destination in violation of such laws.
>
>
>
------------------------------------------------
More information about the Met_help
mailing list