Skip to content
Discussion options

You must be logged in to vote

The ESMF team's sense is that this is a feature rather than a bug. Our suspicion is that the conda-forge ESMF versions you're using were built with the cray mpich MPI library, which may then require --mpi=cray_shasta for compatibility (similar to what's mentioned in https://slurm.schedmd.com/mpi_guide.html#hpe_cray_pmi). Perhaps there was a difference in the MPI library used in the ESMF 8.4.2 build from conda-forge? Or there may have been a difference between ESMF 8.4 and ESMF 8.6 in how ESMF detects / handles the cray MPI library in the build. We have also seen somewhat similar errors when the MPI library used in the mpi4py dependency differs from the system mpi library.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@schlunma
Comment options

Answer selected by schlunma
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
ESMPy
2 participants