# Installing ACCESS-OM2 on NeSI (New Zealand supercomputer) **URL:** \ **Category:** COSIMA\ **Tags:** help, access-om2, technical, community-help\ **Created:** [18 November 2025 03:51 UTC](https://forum.access-hive.org.au/t/installing-access-om2-on-nesi-new-zealand-supercomputer/5566 "2025-11-18T03:51:15Z")\ **Posts on this page:** 1\ **Showing post:** 53
**Author:** ![dkhutch](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/dkhutch/32/510_2.png) [@dkhutch](https://forum.access-hive.org.au/u/dkhutch)\ **Post date:** [20 February 2026 01:16 UTC](https://forum.access-hive.org.au/t/installing-access-om2-on-nesi-new-zealand-supercomputer/5566/53 "2026-02-20T01:16:39Z")
Ok… so I couldn’t figure out how to fix my deprecated build that was crashing at the end of CICE5. I did however go back and try again with the spack installation based on Harshula’s instructions: > [@How to build ACCESS-OM2 on NeSI HPC](https://forum.access-hive.org.au/t/how-to-build-access-om2-on-nesi-hpc/5623): > > How to build ACCESS-OM2 on NeSI HPC (v2) [18/12/2025: Add instructions on how to use the oneapi compiler] Ensure that the initial setup requirements have been completed: [Set up Spack for building ACCESS models on NeSI HPC](https://forum.access-hive.org.au/t/set-up-spack-for-building-access-models-on-nesi-hpc/5622) Login to mahuika cd to the parent directory of the Spack instance. Enable Spack: . spack-config/spack-enable.bash Choose the compiler: a) To use gcc, run: git clone https://github.com/ACCESS-NRI/ACCESS-OM2 --branch api-v2-nesi-gcc b) To use oneapi, run: spa… **And I got it to run successfully with no error**! I think I must have stuffed up the mpirun call earlier, and the PMI and SLURM issues are resolved by calling the correct path for mpirun. So, I may have just run around in a giant circle with my alternative build, but never mind. So, **thank you** to @harshula for providing this build recipe. In the end spack wins. I did however use a bunch of `spack develop` steps to download the code packages and edit the AVX2 vectorization flags. My spack.yaml is attached: [spack.yaml](https://forum.access-hive.org.au/uploads/short-url/3gwSmtADOKKZMuvG0VCLcmADr8Q.yaml) (1.9 KB) In each of my “develop” packages, I just did a recursive grep for -xCORE-AVX2 or -axCORE-AVX2 and then updated that flag to -mavx2 to avoid the Intel / AMD problem. Mostly was updating CMakeLists.txt. Strangely, some of my edits (e.g. in the CICE5 build) got ignored, and the -axCORE-AVX2 persisted in the build. This didn’t seem to matter (I don’t know why). It did matter for the MOM5 build, and my edits to CMakeLists.txt did change the compilation to avoid the -xCORE-AVX2 flag. Regards, David --- _[View the full topic](https://forum.access-hive.org.au/t/installing-access-om2-on-nesi-new-zealand-supercomputer/5566)._