[Met_help] building bufrlib and test code on Intel 32 or 64-bit
David Ovens
ovens at atmos.washington.edu
Fri Jun 26 14:09:07 MDT 2009
John,
Thanks for talking to me yesterday at the WRF Workshop.
I'm totatlly stuck on the BUFRLIB step of building for a 32-bit Debian
Linux machine using ifort and icc. I have been able to build the
libraries on both 64-bit and 32-bit platforms, but the sample prepbufr
files supplied with MET 2.0 cannot be read by the sample decoding
program that I found online at
http://www.emc.ncep.noaa.gov/mmb/data_processing/prepbufr.doc/decode_prepbufr_example.htm
I call that code decode_prepbufr.f and the executable
decode_prepbufr.Linux which I've compiled like this
ifort -o decode_prepbufr.Linux decode_prepbufr.f $BUFRLIB
I copy the ndas prepbufr file to prepbufr.in and run the code
like this:
/bin/cp METv2.0/data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr prepbufr.in
./decode_prepbufr.Linux
And I see:
**************BUFR ARCHIVE LIBRARY ABORT*****************
BUFRLIB: OPENBF - ERROR READING INPUT FILE CONNECTED TO UNIT 11 WHEN CHECKING
FOR 'BUFR' IN FIRST 4 BYTES OF RECORD
**************BUFR ARCHIVE LIBRARY ABORT*****************
This happens when I've done all steps on a 32-bit machine. I've gone
ahead and cut a few lines out of the supplied
ndas.t00z.prepbufr.tm12.20070401.nr file and run the code and I get
this:
+++++++++++++++++++++++WARNING+++++++++++++++++++++++++
BUFRLIB: OPENBF - INPUT BUFR FILE IN UNIT 11 IS EMPTY
+++++++++++++++++++++++WARNING+++++++++++++++++++++++++
1-All subsets read in and processed
This is very puzzling. With the original ndas file, it doesn't make
it out of the openbf routine, while the shorter files claim to be
empty. Check this behavior out:
226 mm5rt at clr% set i = 6496 ; echo $i ; head -$i METv2.0/data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr > ! prepbufr.in ; ./decode_prepbufr.Linux ; echo ""
6496
+++++++++++++++++++++++WARNING+++++++++++++++++++++++++
BUFRLIB: OPENBF - INPUT BUFR FILE IN UNIT 11 IS EMPTY
+++++++++++++++++++++++WARNING+++++++++++++++++++++++++
i got out of openbf
1-All subsets read in and processed
227 mm5rt at clr% set i = 6497 ; echo $i ; head -$i METv2.0/data/sample_obs/prepbufr/ndas.t00z.prepbufr.tm12.20070401.nr > ! prepbufr.in ; ./decode_prepbufr.Linux ; echo ""
6497
**************BUFR ARCHIVE LIBRARY ABORT*****************
BUFRLIB: OPENBF - ERROR READING INPUT FILE CONNECTED TO UNIT 11 WHEN CHECKING
FOR 'BUFR' IN FIRST 4 BYTES OF RECORD
**************BUFR ARCHIVE LIBRARY ABORT*****************
As you can see 6496 lines of the ndas file allow openbf to work, but
the file "claims" to be empty, while 6497 lines cause openbf to fail
claiming that the first 4 bytes are not 'BUFR'.
I am banging my head against the wall on this and can't imagine that
MET will work with this BUFRLIB. Do you agree? Do you have any
simple programs to test BUFRLIB or can you get the above to work on
your system?
David
--
David Ovens e-mail: ovens at atmos.washington.edu
Research Meteorologist phone: (206) 685-8108
Dept of Atm. Sciences plan: Real-time MM5 forecasting for the
Box 351640 Pacific Northwest
University of Washington http://www.atmos.washington.edu/mm5rt
Seattle, WA 98195 Weather Graphics and Loops
http://www.atmos.washington.edu/~ovens/loops
More information about the Met_help
mailing list