# 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:** 2
**Author:** ![cbull](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/cbull/32/2203_2.png) [@cbull](https://forum.access-hive.org.au/u/cbull)\ **Post date:** [18 November 2025 04:18 UTC](https://forum.access-hive.org.au/t/installing-access-om2-on-nesi-new-zealand-supercomputer/5566/2 "2025-11-18T04:18:50Z")
Hi Dave, Awesome to hear about the grant and your interest in getting OM2 over to NeSI! > before I dive in and start trying to do it myself, I wanted to check in and see if ACCESS-NRI has any capacity / interest to provide advice on this? AFAIK, this is not something we officially support at the present time and the release team are low on people-time at the moment. Still, as you’ve seen with Leonardo progress was possible with some perseverance as it has also been on Setonix (Pawsey). > Also, NeSI uses SLURM rather than PBS… again I can dive in and try to configure this myself (I did something similar with a much older version of payu), but any capacity to pick your brains would be helpful. A little work has been done on this in the past. Here’s a comment from @jo-basevi: > This is Aidans PR from a couple years ago to get something working on pawsey- [Porting to pawsey by aidanheerdegen · Pull Request #326 · payu-org/payu · GitHub](https://github.com/payu-org/payu/pull/326) - related to this [issue](https://github.com/payu-org/payu/issues/323). I think that is more likely likely to work than my [draft PR](https://github.com/payu-org/payu/pull/619) which is only just using the slurm client from hpcpy so far. @ChrisC28 and @john_reilly also have a hacked version of payu from a while back that has limited functionality (I’m told) on Pawsey, given that system also uses Slurm that might help. HPCpy is probably the better route to go long-term as it’s intended to be scheduler agnostic. As it happens, myself @helen @harshula have been working on similar things (OM3) over on Setonix recently. So below are a few things that might help you get started/have a clearer sense of what’s involved. I’d expect the general workflow to be similar-ish for OM2/OM3. I’ve got a mega-issue [here](https://github.com/ACCESS-NRI/access-om3-configs/issues/893) that collates the various issues. My latest problem is likely related to not setting up the [run folder correctly](https://github.com/ACCESS-NRI/access-om3-configs/issues/893?issue=ACCESS-NRI%7Caccess-om3-configs%7C896) but before that I had some [build issues](https://github.com/ACCESS-NRI/access-om3-configs/issues/893?issue=ACCESS-NRI%7Caccess-om3-configs%7C894). You can see my very scrappy notes [here](https://forum.access-hive.org.au/t/how-to-build-access-om3-on-setonix/5523) (these arn’t meant to be used by anyone else just yet!). Perhaps the most useful thing to look at to start is the [build changes that were made for Setonix](https://github.com/ACCESS-NRI/ACCESS-OM3/compare/main...api-v1-setonix). In the Setonix case, we’re lucky that spack is already installed on the system. [You might have to install it](https://docs.access-hive.org.au/getting_started/spack/), if it’s not there already. Chris --- _[View the full topic](https://forum.access-hive.org.au/t/installing-access-om2-on-nesi-new-zealand-supercomputer/5566)._