Install ISSM on Frontera

xip220

Hi, I am new to ISSM. Recently I want to install ISSM on Frontera. First I used pre-compile binaries. After I unzip the file, what should I do? Because I follow the steps in https://issm.jpl.nasa.gov/download/binaries/ and after I run os.getenv('ISSM_DIR') it return none. I replaced ISSM_DIR with the path to the unzipped file.

justinquinn

Hi,
What is Frontera, a computing cluster? In this case, the pre-compiled binaries will not be suitable unless you are only running on a single node (which kind of defeats the purpose of installing to a cluster).

Also, what is the OS and shell? Normally, we would export ISSM_DIR in, say, ~/.bashrc on Linux-based OS's and that would make it available to Python.

xip220

justinquinn Thanks for the reply. Yes, Frontera is a supercomputer. I tried to use Linux source installation and I followed https://issm.ess.uci.edu/trac/issm/wiki/frontera.

But during the "make" and "make install" processes, I got two errors.

The first is "./classes/Elements/Tria.cpp(7602): warning #823: reference is to variable "ae" (declared at line 7539) -- under old for-init scoping rules it would have been variable "ae" (declared at line 7592)
for (ae=0;ae<loads->nactivesubloads[l];ae++){"
from line 7602 and line 7750
"./classes/Elements/Tria.cpp(7750): warning #823: reference is to variable "ae" (declared at line 7625) -- under old for-init scoping rules it would have been variable "ae" (declared at line 7724)
grdfield[b+t]+=G[a+t]*projected_subloads[l][ae];".

The second error is "*** Warning: Linking the shared library libISSMCore.la against the
*** static library ../ISSM/trunk/externalpackages/m1qn3/install/libm1qn3.a is not portable!

*** Warning: Linking the shared library libISSMCore.la against the
*** static library ../ISSM/trunk/externalpackages/m1qn3/install/libddot.a is not portable!"

justinquinn

xip220 Nice, well it looks like a lot of the configuration and compilation issues have been sorted out already.

You can effectively ignore the warning about linking against static libs. In fact, both appear to be warnings and not errors. Does ISSM compile and run? If not, there must be a separate error in the log somewhere.

xip220

justinquinn I tried the whole installation process today again and when I installed petsc, I met two errors.

The first one is can not install hdf5. But I think I can install it later so I modify the install-3.16-linux.sh and deleted --download-hdf5=1.

Then I met an error, "Cannot use fblaslapack without Fortran, make sure you do NOT have --with-fc=0". I do not know how to deal with it, so I continue next step.

But after all processes, "from issmversion import issmversion" still return "no module named issmversion"

justinquinn

xip220 I’ll send you an email to the address attached to this account.