[Met_help] [rt.rap.ucar.edu #41500] History for Question about PB2NC v3.0
RAL HelpDesk {for John Halley Gotway}
met_help at ucar.edu
Wed Oct 13 10:04:00 MDT 2010
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
MET team,
Quick question for you:
I just recently installed the latest version (3.0) of the MET package.
Upon compiling and running all the sample scripts to test the various
executables, I received one WARNING in my test_all.log file:
"WARNING: process_obs_file() -> can't open observation netCDF
file: ../out/pb2nc/sample_pb.nc"
I'm not exactly sure why the package was unable to write to this .nc file.
Any suggestions? I didn't see this in the MET email archive, so I figured
I would ask you. Again, this was the only warning/error when I tested all
the executables with the test_all.sh script.
Any information you can provide me with will help me greatly.
Thanks,
James
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #41500] Question about PB2NC v3.0
From: John Halley Gotway
Time: Wed Oct 13 09:21:43 2010
James,
I believe what's going on here is that the "test_pb2nc.sh" script
experienced a runtime error and didn't produce any output. That's
causing this warning message from the "test_point_stat.sh" script.
Please take a closer look in the "test_all.log" file and search for
"PB2NC", and then scroll down and look for errors. One common error
is shown below:
**************BUFR ARCHIVE LIBRARY ABORT*****************
BUFRLIB: OPENBF - FIRST 4 BYTES READ FROM RECORD IN INPUT FILE
CONNECTED TO UNIT 11 NOT 'BUFR', DOES NOT CONTAIN BUFR DATA
**************BUFR ARCHIVE LIBRARY ABORT*****************
If you see this error message in that log file, please do the
following:
- Open up the top-level MET Makefile for editing.
- In the line for "ARCH_FLAGS", either comment out or uncomment the
flag for "-DBLOCK4" (basically, switch whatever it is currently).
- Then do a "make clean", followed by a "make".
- Lastly, go into the "scripts" directory and rerun the
"test_pb2nc.sh" script to verify that that error went away.
If that is NOT the error message you see, and you see something else,
please send me a copy of your "test_all.log" file.
Thanks,
John Halley Gotway
met_help at ucar.edu
On 10/13/2010 08:09 AM, RAL HelpDesk {for James P Cipriani} wrote:
>
> Wed Oct 13 08:09:58 2010: Request 41500 was acted upon.
> Transaction: Ticket created by jpcipria at us.ibm.com
> Queue: met_help
> Subject: Question about PB2NC v3.0
> Owner: Nobody
> Requestors: jpcipria at us.ibm.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=41500 >
>
>
>
>
> MET team,
>
> Quick question for you:
>
> I just recently installed the latest version (3.0) of the MET
package.
> Upon compiling and running all the sample scripts to test the
various
> executables, I received one WARNING in my test_all.log file:
>
> "WARNING: process_obs_file() -> can't open observation netCDF
> file: ../out/pb2nc/sample_pb.nc"
>
> I'm not exactly sure why the package was unable to write to this .nc
file.
> Any suggestions? I didn't see this in the MET email archive, so I
figured
> I would ask you. Again, this was the only warning/error when I
tested all
> the executables with the test_all.sh script.
>
>
> Any information you can provide me with will help me greatly.
>
>
> Thanks,
> James
------------------------------------------------
Subject: Question about PB2NC v3.0
From: James P Cipriani
Time: Wed Oct 13 09:59:17 2010
John,
That was indeed the error.
I followed the steps you provided and everything is now working
properly.
Thanks for the help. If I have any other questions or issues, I'll be
sure
to let you know.
Regards,
James
From: "RAL HelpDesk {for John Halley Gotway}" <met_help at ucar.edu>
To: James P Cipriani/Watson/IBM at IBMUS
Date: 10/13/2010 11:21 AM
Subject: Re: [rt.rap.ucar.edu #41500] Question about PB2NC v3.0
James,
I believe what's going on here is that the "test_pb2nc.sh" script
experienced a runtime error and didn't produce any output. That's
causing
this warning message from the "test_point_stat.sh" script.
Please take a closer look in the "test_all.log" file and search for
"PB2NC", and then scroll down and look for errors. One common error
is
shown below:
**************BUFR ARCHIVE LIBRARY ABORT*****************
BUFRLIB: OPENBF - FIRST 4 BYTES READ FROM RECORD IN INPUT FILE
CONNECTED TO UNIT 11 NOT 'BUFR', DOES NOT CONTAIN BUFR DATA
**************BUFR ARCHIVE LIBRARY ABORT*****************
If you see this error message in that log file, please do the
following:
- Open up the top-level MET Makefile for editing.
- In the line for "ARCH_FLAGS", either comment out or uncomment the
flag
for "-DBLOCK4" (basically, switch whatever it is currently).
- Then do a "make clean", followed by a "make".
- Lastly, go into the "scripts" directory and rerun the
"test_pb2nc.sh"
script to verify that that error went away.
If that is NOT the error message you see, and you see something else,
please send me a copy of your "test_all.log" file.
Thanks,
John Halley Gotway
met_help at ucar.edu
On 10/13/2010 08:09 AM, RAL HelpDesk {for James P Cipriani} wrote:
>
> Wed Oct 13 08:09:58 2010: Request 41500 was acted upon.
> Transaction: Ticket created by jpcipria at us.ibm.com
> Queue: met_help
> Subject: Question about PB2NC v3.0
> Owner: Nobody
> Requestors: jpcipria at us.ibm.com
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=41500 >
>
>
>
>
> MET team,
>
> Quick question for you:
>
> I just recently installed the latest version (3.0) of the MET
package.
> Upon compiling and running all the sample scripts to test the
various
> executables, I received one WARNING in my test_all.log file:
>
> "WARNING: process_obs_file() -> can't open observation netCDF
> file: ../out/pb2nc/sample_pb.nc"
>
> I'm not exactly sure why the package was unable to write to this .nc
file.
> Any suggestions? I didn't see this in the MET email archive, so I
figured
> I would ask you. Again, this was the only warning/error when I
tested
all
> the executables with the test_all.sh script.
>
>
> Any information you can provide me with will help me greatly.
>
>
> Thanks,
> James
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #41500] Question about PB2NC v3.0
From: John Halley Gotway
Time: Wed Oct 13 10:03:46 2010
James,
Glad that did the trick. Sorry for the trouble in the first place.
We'd like to set up a configure/compile script that'd check your
system and perform the correct setting for you, but we just
haven't gotten it done yet.
Feel free to write if any more issues come up.
I'll go ahead and resolve this ticket.
Thanks,
John
On 10/13/2010 09:59 AM, RAL HelpDesk {for James P Cipriani} wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=41500 >
>
>
> John,
>
> That was indeed the error.
>
> I followed the steps you provided and everything is now working
properly.
>
> Thanks for the help. If I have any other questions or issues, I'll
be sure
> to let you know.
>
> Regards,
> James
>
>
>
> From: "RAL HelpDesk {for John Halley Gotway}" <met_help at ucar.edu>
> To: James P Cipriani/Watson/IBM at IBMUS
> Date: 10/13/2010 11:21 AM
> Subject: Re: [rt.rap.ucar.edu #41500] Question about PB2NC v3.0
>
>
>
> James,
>
> I believe what's going on here is that the "test_pb2nc.sh" script
> experienced a runtime error and didn't produce any output. That's
causing
> this warning message from the "test_point_stat.sh" script.
>
> Please take a closer look in the "test_all.log" file and search for
> "PB2NC", and then scroll down and look for errors. One common error
is
> shown below:
>
> **************BUFR ARCHIVE LIBRARY ABORT*****************
> BUFRLIB: OPENBF - FIRST 4 BYTES READ FROM RECORD IN INPUT FILE
> CONNECTED TO UNIT 11 NOT 'BUFR', DOES NOT CONTAIN BUFR DATA
> **************BUFR ARCHIVE LIBRARY ABORT*****************
>
> If you see this error message in that log file, please do the
following:
> - Open up the top-level MET Makefile for editing.
> - In the line for "ARCH_FLAGS", either comment out or uncomment the
flag
> for "-DBLOCK4" (basically, switch whatever it is currently).
> - Then do a "make clean", followed by a "make".
> - Lastly, go into the "scripts" directory and rerun the
"test_pb2nc.sh"
> script to verify that that error went away.
>
> If that is NOT the error message you see, and you see something
else,
> please send me a copy of your "test_all.log" file.
>
> Thanks,
> John Halley Gotway
> met_help at ucar.edu
>
> On 10/13/2010 08:09 AM, RAL HelpDesk {for James P Cipriani} wrote:
>>
>> Wed Oct 13 08:09:58 2010: Request 41500 was acted upon.
>> Transaction: Ticket created by jpcipria at us.ibm.com
>> Queue: met_help
>> Subject: Question about PB2NC v3.0
>> Owner: Nobody
>> Requestors: jpcipria at us.ibm.com
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=41500 >
>>
>>
>>
>>
>> MET team,
>>
>> Quick question for you:
>>
>> I just recently installed the latest version (3.0) of the MET
package.
>> Upon compiling and running all the sample scripts to test the
various
>> executables, I received one WARNING in my test_all.log file:
>>
>> "WARNING: process_obs_file() -> can't open observation netCDF
>> file: ../out/pb2nc/sample_pb.nc"
>>
>> I'm not exactly sure why the package was unable to write to this
.nc
> file.
>> Any suggestions? I didn't see this in the MET email archive, so I
> figured
>> I would ask you. Again, this was the only warning/error when I
tested
> all
>> the executables with the test_all.sh script.
>>
>>
>> Any information you can provide me with will help me greatly.
>>
>>
>> Thanks,
>> James
>
>
------------------------------------------------
More information about the Met_help
mailing list