monoprop

HPC clusters

Running monoprop on HPC systems from its MPI-enabled container image.

Some HPC systems give their login nodes no outbound network, so monoprop cannot be installed there with pip. For those, every release, the main branch and pull requests that change the container recipes publish an MPI-enabled container image to the GitHub Container Registry:

ghcr.io/algorithmiq/monoprop:<tag>

Every tag ends with the CPU target the image is compiled for, currently sapphirerapids (Intel Sapphire Rapids, as in MareNostrum5 and Leonardo). The image does not run on CPUs without that instruction set.

TagContents
X.Y.Z-sapphirerapidsA monoprop release. latest-sapphirerapids points at the newest one.
main-sapphirerapidsThe tip of the main branch.
pr-N-sapphirerapidsPull request N, when it changes the container recipes, while it is open.

The image holds monoprop built with MPI, with its mpi and qiskit extras, on top of an MPI stack built for InfiniBand clusters that launch jobs with Slurm: Open MPI 5 with PMIx and UCX, and NVIDIA's DOCA-OFED user-space drivers. To build it yourself, see Container images.

  • MareNostrum5 — pulling the image, running it with Singularity under Slurm, and checking the CPU placement.