MET configuration with grib2

[scatt11]

Hello MET team,

I am having issues using Grib2 files with MET V10.0.0 #1245. The issue is believed to be linked to installation/configuration. I have read up on installing with grib2 functionality, and it seems I have done so. I am using the compile_MET_all.sh script and a configuration file which can also be referenced in #1245. I refrain from explicitly setting MET_GRIB2CLIB in order for the script to install and link GRIB2C. My log messages for successful installation are attached.
log.log

What needs to be changed to ensure that I configure with grib2 compatibility?

[jprestop]

HI @scatt11.

From your log file it looks like everything is set correctly to have GRIB enabled.. I see that --enable-grib2 is being set at the configure step. Have you tried running with the the new MET binaries that were created from this build? If you have and there are still problems, please send the make.log file from the G2CLIB build:

Compiling G2CLIB at Mon Nov 15 22:16:47 CET 2021
cd /home/computeadmin/meteo/Libraries/MET_install/external_libs/g2clib/g2clib-1.6.0
make > make.log 2>&1

along with the config.log, make.log, and make_test.log files from the MET build (in /home/computeadmin/meteo/Libraries/MET_install/met-10.0.0). Please also send the command line you are running along with the output from the run. Thanks!

[jprestop]

Hi @scatt11. Could you please send your install_met_env.ripper file? Thanks!

[scatt11]

Here you have it. Thanks
install_met_env.ripper.txt

[jprestop]

@scatt11 Thank you!

I see that you have the following set:

export SET_D64BIT=TRUE
export CFLAGS="-D_64BIT_"

Could you please remove both of those settings from the file? We want to try compiling without the D_64BIT flag set. Then, please rerun the compile script so that the external libraries and MET will be recompiled. Please let us know how it goes.

[scatt11]

@jprestop The compile was successful and plot_data_plane now completes successfully. Thanks for all the help and please let me know if you need further information for tracking the source of this issue.

[jprestop]

That's great news! Thank you for letting us know and for marking this Discussion as answered.