new location of ESMFMKFILE?

[fyke@lanl_gov]

Hi,I am attempting to use the check_maps tool during generation of a new CLM grid.  This tool is located in $CCSMROOT/mapping/check_mapsIn the Makefile that comes with the cesm1_2_beta02 distribution it says if on Yellowstone to point $ESMFMKFILE to:   ESMFMKFILE=/glade/p/work/svasquez/install/esmf-6.1.0-O-netcdf4.2/lib/esmf.mkHowever, this file no longer exists and must have been moved from within svasquez's personal work directory fairly recently (as I was using this successfully until about a week ago).  Where is this file now, and are there any other recent changes or updates I should be aware of in using the check_maps utility? Thanks, Jeremy

 

[erik]

Hi Jeremy
This is now supported via the "modules" comand on yellowstone. So you "module load esmf" and then load the specific version of ESMF that you want. After you "module load esmf", you can use "module avail" to see all the versions of ESMF that are available (and there's a bunch).
For ESMF-6.1.1 you do this...
module load esmf-6.1.1-ncdfio-mpi-O

and then the esmf.mk file is in $ESMF_LIBDIR.

 

[erik]

Hi Jeremy
This is now supported via the "modules" comand on yellowstone. So you "module load esmf" and then load the specific version of ESMF that you want. After you "module load esmf", you can use "module avail" to see all the versions of ESMF that are available (and there's a bunch).
For ESMF-6.1.1 you do this...
module load esmf-6.1.1-ncdfio-mpi-O

and then the esmf.mk file is in $ESMF_LIBDIR.

 

[mlevy]

Hi Jeremy, It turns out the version of ESMF tools we were using when we first migrated to yellowstone were installed in a placeholder directory while ESMF worked with CISL to set up the modules that Erik mentioned above. As far as I can tell, removing the temporary location has had two unintended consequences in the mapping tools directory:

1. The ESMF makefile doesn't exist in the directory we used to recommend using, so you can't build check_maps. I've started using the one in /glade/apps/opt/esmf/6.1.1-ncdfio/intel/12.1.5/lib/libO/Linux.intel.64.mpiuni.default/esmf.mk, but Erik's suggestion of using the modules and the $ESMF_LIBDIR environment variable is a better one (and I'll make sure the README is updated prior to the CESM 1.2 release)
2. The create_ESMF_map.sh script won't work on yellowstone in versions prior to cesm1_2_beta06, an issue I will address on the CESM 1.1 Known Problems web page. In the mean time, here is an updated version of the create_ESMF_maps.sh tool that you should use instead of the one released with cesm1_2_beta02 -- make sure $ESMFBIN_PATH is not defined in your environment otherwise the script will still look for the ESMF executable in that directory. One nice feature of the linked version of the script is that you can execute it interactively from yellowstone and it will use the serial versions of the ESMF tools rather than requiring MPI (since mpirun.lsf won't run anything on the yellowstone login nodes). If you are making small maps, I recommend doing so on yellowstone instead of logging in to geyser or caldera.

Sorry you had to stumble on this the hard way, please keep updating this thread if you continue to have problems. ~Mike

 

[mlevy]

Hi Jeremy, It turns out the version of ESMF tools we were using when we first migrated to yellowstone were installed in a placeholder directory while ESMF worked with CISL to set up the modules that Erik mentioned above. As far as I can tell, removing the temporary location has had two unintended consequences in the mapping tools directory:

1. The ESMF makefile doesn't exist in the directory we used to recommend using, so you can't build check_maps. I've started using the one in /glade/apps/opt/esmf/6.1.1-ncdfio/intel/12.1.5/lib/libO/Linux.intel.64.mpiuni.default/esmf.mk, but Erik's suggestion of using the modules and the $ESMF_LIBDIR environment variable is a better one (and I'll make sure the README is updated prior to the CESM 1.2 release)
2. The create_ESMF_map.sh script won't work on yellowstone in versions prior to cesm1_2_beta06, an issue I will address on the CESM 1.1 Known Problems web page. In the mean time, here is an updated version of the create_ESMF_maps.sh tool that you should use instead of the one released with cesm1_2_beta02 -- make sure $ESMFBIN_PATH is not defined in your environment otherwise the script will still look for the ESMF executable in that directory. One nice feature of the linked version of the script is that you can execute it interactively from yellowstone and it will use the serial versions of the ESMF tools rather than requiring MPI (since mpirun.lsf won't run anything on the yellowstone login nodes). If you are making small maps, I recommend doing so on yellowstone instead of logging in to geyser or caldera.

Sorry you had to stumble on this the hard way, please keep updating this thread if you continue to have problems. ~Mike