# Creating a regional ACCESS-OM3

**URL:** <https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979>\
**Category:** TWG\
**Tags:** 21centuryweather\
**Created:** [9 December 2024 04:18 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979 "2024-12-09T04:18:15Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Paul.Gregory](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/paul.gregory/32/2566_2.png) [@Paul.Gregory](https://forum.access-hive.org.au/u/Paul.Gregory)\
**Post date:** [9 December 2024 04:18 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/1 "2024-12-09T04:18:15Z")

</div>

A new thread to help build a regional ACCESS-OM3 configuration using MOM6 and NUOCPY.

Progress so far.

Firstly you want to get Spack installed:

[https://access-hive.org.au/getting\_started/spack/](https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess-hive.org.au%2Fgetting_started%2Fspack&data=05%7C02%7Cchris.bull%40anu.edu.au%7C6a7b026db48a404d7efc08dd13199fab%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638687722965722796%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=bwGAPwINBQTuOI%2FgGKhBGdPVwLNJzzBqmwcLHSwZHgo%3D&reserved=0)

Then to build using Spack, you want to use these instructions  
[https://access-hive.org.au/models/run-a-model/build\_a\_model/](https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faccess-hive.org.au%2Fmodels%2Frun-a-model%2Fbuild_a_model&data=05%7C02%7Cchris.bull%40anu.edu.au%7C6a7b026db48a404d7efc08dd13199fab%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C638687722965741225%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=B4sD6R4lrdPCy6ILhK%2FpWoy0droRohDFb8OoiFBrwIM%3D&reserved=0)

At this step:

```auto
git clone https://github.com/ACCESS-NRI/ACCESS-ESM1.5.git
spack env create mom5_dev ACCESS-ESM1.5/spack.yaml

```

Change it to

```auto
git clone https://github.com/ACCESS-NRI/ACCESS-OM3.git
spack env create mom6_dev ACCESS-OM3/spack.yaml
#update: typo fixed thanks to Paul's feedback

```

Note, if you attempt the `Test Spack (OPTIONAL)` section, the `concretize` step will fail.

If you want to start editing the source code, move to spack develop (my intuition suggests that this will be based on the repo’ you used to create the environment), namely:

```auto
[cyb561.gadi-login-01: environments]$ spack env activate mom6_dev
[2007][cyb561.gadi-login-01: environments]$ spack find
#get name of the nuopc version you've already set yourself up with, in my case..
#make sure you do a module purge!
spack -d develop access-om3-nuopc@git.0.3.1=0.3.1
#code for me ends up here
#/g/data/tm70/cyb561/spack/0.22/environments/mom6_dev/access-om3-nuopc
spack install

```

A successful install of the base MOM6 model will look like this

```auto
$ spack find
==> In environment mom6_dev
==> 1 root specs
[+] access-om3@git.2024.09.0=2024.09.0

==> Installed packages
-- linux-rocky8-x86_64 / intel@2021.10.0 ------------------------
access-om3@git.2024.09.0=2024.09.0 cmake@3.24.2 fortranxml@4.1.2 libaec@1.0.6 m4@1.4.19 parallelio@2.6.2 zstd@1.5.6
access-om3-nuopc@git.0.3.1=0.3.1 diffutils@3.10 glibc@2.28 libiconv@1.17 netcdf-c@4.9.2 pkgconf@2.2.0
bzip2@1.0.8 esmf@8.5.0 gmake@4.4.1 libsigsegv@2.14 netcdf-fortran@4.6.1 snappy@1.1.10
c-blosc@1.21.5 fms@2023.02 hdf5@1.14.3 lz4@1.9.4 openmpi@4.1.5 zlib-ng@2.1.6

```

To run an experiment, follow the guidelines here

[https://access-hive.org.au/models/run-a-model/run-access-om/](https://access-hive.org.au/models/run-a-model/run-access-om/)

You can execute the following in`~/access-om3` to clone an experiment from branch `dev-1deg_jra55do_ryf`, and creating a local branch `expt`:

```auto
$ payu clone -b expt -B dev-1deg_jra55do_ryf https://github.com/ACCESS-NRI/access-om3-configs 1deg_jra55do_ryf

Cloned repository from https://github.com/ACCESS-NRI/access-om3-configs to directory: /home/548/pag548/access-om3/1deg_jra55do_ryf
Created and checked out new branch: expt
laboratory path: /scratch/gb02/pag548/access-om3
binary path: /scratch/gb02/pag548/access-om3/bin
input path: /scratch/gb02/pag548/access-om3/input
work path: /scratch/gb02/pag548/access-om3/work
archive path: /scratch/gb02/pag548/access-om3/archive
Metadata and UUID generation is disabled. Experiment name used for archival: 1deg_jra55do_ryf
To change directory to control directory run:
  cd 1deg_jra55do_ryf

```

The `config.yaml` file for MOM6 is a bit simpler to MOM5. You only have to specific the location of a single executable. Find the location of your executable built using `spack` and assign it to the `exe` entry of your `~/access-om3/<branch-name>/config.yaml` file, e.g.

```auto
model: access-om3

exe: /g/data/gb02/pag548/spack/0.22/release/linux-rocky8-x86_64/intel-2021.10.0/access-om3-nuopc-git.0.3.1_0.3.1-756wxghdm5i75v26j5oybrutennrjdyi/bin/access-om3-MOM6-CICE6

input:
    - /g/data/vk83/configurations/inputs/access-om3/share/meshes/global.1deg/2024.01.25/access-om2-1deg-ESMFmesh.nc
    - /g/data/vk83/configurations/inputs/access-om3/share/meshes/global.1deg/2024.01.25/access-om2-1deg-nomask-ESMFmesh.nc

etc.

```

Then run `payu setup` and check the following files exist in `~/access-om3/<branch-name>/manifests/`  
e.g.

```auto
$ ls ~/access-om3/1deg_jra55do_ryf/manifests/
exe.yaml input.yaml restart.yaml

```

Then run your experiment using `payu run`.

The manifest files are scanned by `payu run` to locate the gadi projects for all required inputs (including your executable) and create the correct `-l storage` flag passed to the the PBS qsub command.

---

<div class="post-metadata">

**Author:** ![Paul.Gregory](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/paul.gregory/32/2566_2.png) [@Paul.Gregory](https://forum.access-hive.org.au/u/Paul.Gregory)\
**Post date:** [9 December 2024 04:41 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/2 "2024-12-09T04:41:56Z")

</div>

Ok @navidcy , @PSpence , @Helen , @AndyHoggANU and @cbull we are continuing this thread now on the hive.

Question : Did we find the answer to the problem of `payu` not being able to find the executable? e.g. my `config.yaml` has

```auto
exe: /g/data/gb02/pag548/spack/0.22/release/linux-rocky8-x86_64/intel-2021.10.0/access-om3-nuopc-git.0.3.1_0.3.1-756wxghdm5i75v26j5oybrutennrjdyi/bin/access-om3-MOM6-CICE6

```

But `payu` cannot run the model:

```auto
FileNotFoundError: Executable for access-om3 model not found on path: /g/data/gb02/pag548/spack/0.22/release/linux-rocky8-x86_64/intel-2021.1
0.0/access-om3-nuopc-git.0.3.1_0.3.1-756wxghdm5i75v26j5oybrutennrjdyi/bin/access-om3-MOM6-CICE6

```

---

<div class="post-metadata">

**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:** [9 December 2024 04:54 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/3 "2024-12-09T04:54:17Z")

</div>

Hi Paul, thanks for [collating my instructions and your experience into this post](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979) from [here](https://21centuryweather.discourse.group/t/develop-a-regional-coupled-modelling-strategy/168/29), specifically [1](https://21centuryweather.discourse.group/t/develop-a-regional-coupled-modelling-strategy/168/27), [2](https://21centuryweather.discourse.group/t/develop-a-regional-coupled-modelling-strategy/168/33), [3](https://21centuryweather.discourse.group/t/develop-a-regional-coupled-modelling-strategy/168/37), [4](https://21centuryweather.discourse.group/t/develop-a-regional-coupled-modelling-strategy/168/37).

> Question : Did we find the answer to the problem of `payu` not being able to find the executable?

Yeah, so, I suggest you try using my executable? (i.e. `/g/data/tm70/cyb561/spack/0.22/release/linux-rocky8-x86_64/intel-2021.10.0/access-om3-nuopc-git.0.3.1_0.3.1-va553vmg3iv3i7uknyyymh34nna2hz7s/bin/access-om3-MOM6-CICE6` from [here](https://21centuryweather.discourse.group/t/develop-a-regional-coupled-modelling-strategy/168/37)) It’s curious because @helen was able to use mine, so we expect there might be something wrong with the environment.

We discussed this at a standup last week (@minghangli @anton @ezhilsabareesh8), there were a few suggestions around your environment that can complicate:

- when one has done their own pip install of payu that will get preferentially used over a module load although your payu version looks quite new.
- worth looking at the standard output on `payu run` as this will tell you how the project code is being interpreted and whether you can expect to have access to your executable
- worth trying a `payu setup` as that will look to see if it can find the executable (if this works one then needs to try a `payu sweep`, then `payu run`)

---

<div class="post-metadata">

**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\
**Post date:** [9 December 2024 05:10 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/4 "2024-12-09T05:10:37Z")

</div>

I don’t think Chris’ build will work for you as you aren’t a member of the `tm70` project.

When you do a `payu run` it should print the qsub command out, the first thing is to check the `-l storage = ` flag includes your project.

I think you’ll need to run `payu setup` manually, and then next time `payu run` the paths within the `storage = ` flag will be updated.

---

<div class="post-metadata">

**Author:** ![Paul.Gregory](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/paul.gregory/32/2566_2.png) [@Paul.Gregory](https://forum.access-hive.org.au/u/Paul.Gregory)\
**Post date:** [9 December 2024 05:27 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/5 "2024-12-09T05:27:05Z")

</div>

Ok running `payu setup` worked. The file `manifests/exe.yaml` now contains

```auto
format: yamanifest
version: 1.0
---
work/access-om3-MOM6-CICE6:
  fullpath: /g/data/gb02/pag548/spack/0.22/release/linux-rocky8-x86_64/intel-2021.10.0/access-om3-nuopc-git.0.3.1_0.3.1-756wxghdm5i75v26j5oybrutennrjdyi/bin/access-om3-MOM6-CICE6
  hashes:
    binhash: 59a6707be5e899664bbf06105362ff54
    md5: db3315a0e5580b5e8ad2b4b78dc9f185

```

and the `-l storage` flag for the PBS sub command created by `payu` contains `gb02`:

```auto
qsub -q normal -P gb02 -l walltime=01:00:00 -l ncpus=240 -l mem=960GB -l jobfs=10GB -N 1deg_jra55do_ry -l wd -j n -v PAYU_PATH=/g/data/vk83/apps/payu/1.1.5/bin,MODULESHOME=/opt/Modules/v4.3.0,MODULES_CMD=/opt/Modules/v4.3.0/libexec/modulecmd.tcl,MODULEPATH=/g/data/vk83/modules:/etc/scl/modulefiles:/opt/Modules/modulefiles:/opt/Modules/v4.3.0/modulefiles:/apps/Modules/modulefiles -l storage=gdata/gb02+gdata/vk83 -- /g/data/vk83/apps/payu/1.1.5/bin/python3.10 /g/data/vk83/apps/payu/1.1.5/bin/payu-run

```

So what’s next? Should I move to a `spack` development branch and run `install` again?

Just to clarify : I’ve just run ACCESS-OM3 using MOM6 coupled to CICE6 using NUOPCY on a global grid.

What’s the next step? Building the regional OM3 suite using NUOPCY?

---

<div class="post-metadata">

**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\
**Post date:** [10 December 2024 05:43 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/6 "2024-12-10T05:43:14Z")

</div>

Hi Paul

We are going to meet tomorrow anyway, but I did manage to hack together a configuration without CICE which runs. There are some more ice related config lines which can probably be removed.

> **[Comparing ACCESS-NRI:dev-1deg\_jra55do\_ryf...anton-seaice:mom6-nuopc-standalone...](https://github.com/ACCESS-NRI/access-om3-configs/compare/dev-1deg_jra55do_ryf...anton-seaice:MOM6-CICE6:mom6-nuopc-standalone)**
>
> ACCESS-OM3 MOM6-CICE6 configurations . Contribute to ACCESS-NRI/access-om3-configs development by creating an account on GitHub.

Another thing to test is building without CICE, probably like this:

> <https://github.com/ACCESS-NRI/ACCESS-OM3/pull/29/files>

And then seeing if the resulting `access-om3-MOM6` executable works.

---

<div class="post-metadata">

**Author:** ![Paul.Gregory](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/paul.gregory/32/2566_2.png) [@Paul.Gregory](https://forum.access-hive.org.au/u/Paul.Gregory)\
**Post date:** [12 December 2024 00:03 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/7 "2024-12-12T00:03:44Z")

</div>

Good to catch up and meet @anton, @cbull and @ashjbarnes yesterday.

I’ll try at get regional MOM6 up and running soon.

@MartinDix and @kieranricardo - can you tell me the suite-id for the CM3 (?) development suite that uses NUOPCY?

Thanks

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [12 December 2024 22:36 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/8 "2024-12-12T22:36:51Z")

</div>

It was good to catchup the other day – thanks @anton and @ashjbarnes for coming along to help us out. I am just putting us a few helpful links that came out of the meeting for our reference.

1. A list of the changed needed to turn a global CESM into a regional CESM  
[Make a CESM workflow · Issue #1 · CROCODILE-CESM/regional-mom6 · GitHub](https://github.com/CROCODILE-CESM/regional-mom6/issues/1)

2. NCAR’s “wrapper” for regional mom6, which implements the above checklist to automate the global → regional model conversion.  
[GitHub - CROCODILE-CESM/regional-casegen at 300fbc1c87d022389ef11c67a8a54a5c9183da10](https://github.com/CROCODILE-CESM/regional-casegen/tree/300fbc1c87d022389ef11c67a8a54a5c9183da10)

3. Github repository of regional mom6. This will create a system-agnostic input files to run a regional mom-6 configuration, but extra files will be needed to run with nuopcy  
[GitHub - COSIMA/regional-mom6: Automatic generation of regional configurations of the Modular Ocean Model 6 (MOM6) in Python](https://github.com/COSIMA/regional-mom6)

4. COSIMA recipe for setting up a regional mom6 configuration using om2 model outputs. This is currently not with the nuopc coupler, but when we have something working on nuopc then we could modify this  
[cosima-recipes/Recipes/regional-mom6-forced-by-access-om2.ipynb at main · COSIMA/cosima-recipes · GitHub](https://github.com/COSIMA/cosima-recipes/blob/main/Recipes/regional-mom6-forced-by-access-om2.ipynb)

5. Anton has built ACCESS-OM3 with mom-only and symmetric (something @ashjbarnes flagged that we needed to do)  
[test a MOM6 only build of OM3 by anton-seaice · Pull Request #30 · ACCESS-NRI/ACCESS-OM3 · GitHub](https://github.com/ACCESS-NRI/ACCESS-OM3/pull/30)

6. A description of the input files:  
[Configurations · COSIMA/access-om3 Wiki · GitHub](https://github.com/COSIMA/access-om3/wiki/Configurations)

---

<div class="post-metadata">

**Author:** ![kieranricardo](https://avatars.discourse-cdn.com/v4/letter/k/e47c2d/32.png) [@kieranricardo](https://forum.access-hive.org.au/u/kieranricardo)\
**Post date:** [17 December 2024 04:19 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/9 "2024-12-17T04:19:54Z")

</div>

hey @Paul.Gregory, our CM3 suite is on GitHub - what’s your username? I’ll add you to the repo

---

<div class="post-metadata">

**Author:** ![Paul.Gregory](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/paul.gregory/32/2566_2.png) [@Paul.Gregory](https://forum.access-hive.org.au/u/Paul.Gregory)\
**Post date:** [17 December 2024 04:30 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/10 "2024-12-17T04:30:39Z")

</div>

Rush74

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [17 December 2024 05:24 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/11 "2024-12-17T05:24:30Z")

</div>

Hi @anton, I am attempting to compile and run mom6-standalone as a global configuration before trying as regional. I am using the above links to your spack build pull request for compiling and then running using your configuration files. Thanks for pulling these together – they almost worked straight out of the box for me.

However, I did encounter a couple of issues and I would like to flag them with you in case they are user errors that I should sort out before I go too much further!

_Issue 1_  
When I build spack using your mom-standalone version:

```auto
git clone -b mum6-nuopc-standalone-2 git@github.com:ACCESS-NRI/ACCESS-OM3.git
spack env mom6_standalone_dev create ACCESS-OM3/spack.yaml
spack env activate -p mom6_standalone_dev
cd ACCESS-OM3
spack concretize -f –fresh

```

I get an error:

> 2024.12.mom6 is not a valid git ref for access-om3

I think this is similar to the error that Paul and I received when running this command in the spack test to check we had compiled correctly. I believe that this is reported and being delt with?

Instead, I used an already working version of OM3 spack build but included your modifications

i.e. in spack.yaml I added

> - configurations=MOM6  
> - +mom\_symmetric

under

> access-om3-nuopc:  
> require:

I then followed the usually instructions for compiling with spack and this seems to work. I _think_ I now have a symmetrical mom-only executable (but am unsure, given the next errors!). Should the two lines I added be enough to make it symmetric and mom-only?

_Issue 2_  
At run time I am using your version of the configuration files, my newly compiled executable and payu to setup the experiment:

```auto
payu clone -b expt -B mom6-nuopc-standalone https://github.com/anton-seaice/MOM6-CICE6 mom6-nuopc
payu setup

```

I get this error from payu:

> ntasks = int(self.runconfig.get(“PELAYOUT\_attributes”, f"{realm}\_ntasks"))

I think the issue is that payu is still expecting an “ntasks” for waves and ice in nuopc.runconfig so I added these lines back, but changed the numbers so no resources were given to ice  
i.e. I added this into nuopc.runconfig

> ice\_ntasks = 1  
> ice\_nthreads = 1  
> ice\_pestride = 0  
> ice\_rootpe = 0

I added something similar for waves. This now runs for a bit (using payu run), but I get some errorrs as it tries to output CICE variables. I am still investigating this but thought I should check in with what I have done to see if I need to fix up some earlier missteps first. Thanks!

---

<div class="post-metadata">

**Author:** ![anton](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/anton/32/1836_2.png) [@anton](https://forum.access-hive.org.au/u/anton)\
**Post date:** [17 December 2024 05:47 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/12 "2024-12-17T05:47:32Z")

</div>

Hi Helen

You are correct about _Issue 2_, we removed the requirement for these lines in [https://github.com/payu-org/payu/pull/496](https://github.com/payu-org/payu/pull/496) (as the model doesn’t need them). This would be solved in the next payu release, (or you can use the payu pre-release version `module use /g/data/vk83/prerelease/modules; module load payu/dev` ).

I have not got my head around _Issue 1_. The git ref for the spac spec for a deployment package (in [this case](https://github.com/ACCESS-NRI/ACCESS-OM3/blob/2daec2211e67175b8f3191aae4053e6665fe76c2/spack.yaml#L9) `access-om3`) is the tag that would be created if that version was deployed. So I don’t understand how it can be “not a valid git ref” because it doesn’t exist yet.

If there is an ‘access-om3-MOM6’ executable available then it has built the MOM6 only version.

I think running `spack find -v access-om3-nuopc` should confirm if its built with symmetric memory (i.e. +mom\_symmetric) or not (i.e. ~mom\_symmetric)

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [17 December 2024 23:47 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/13 "2024-12-17T23:47:16Z")

</div>

Thanks @anton!

I will swap to payu/dev – so I think issue 2 is now not an issue.

For issue 1: I have an access-om3-MOM6 executable that is “+mom\_symmertric” so things are looking good!

I believe that the “not a valid git ref” issue has appeared before and has been raised by Paul here:

> <https://github.com/ACCESS-NRI/access-hive.org.au/issues/846>
>
> \## Description
> 
> Hello. I'm completely new to spack and I ran through the documen…tation here: https://access-hive.org.au/getting\_started/spack/#compile-packages 
> 
> I attempted the \`Test Spack (OPTIONAL)\` section. The \`concretize\` step failed.
> \`\`\`
> \[pag548@gadi-login-04 0.22\]$ spack env create test ACCESS-TEST/spack.yaml
> ==\> Created environment test in: /g/data/gb02/pag548/spack/0.22/environments/test
> ==\> Activate with: spack env activate test
> \[pag548@gadi-login-04 0.22\]$ spack env activate -p test
> \[test\] \[pag548@gadi-login-04 0.22\]$ spack find
> ==\> In environment test
> ==\> 1 root specs
> - access-test@git.2024.11.15
> 
> ==\> 0 installed packages
> \[test\] \[pag548@gadi-login-04 0.22\]$ spack concretize -f --fresh
> ==\> Fetching https://mirror.spack.io/bootstrap/github-actions/v0.5/build\_cache/linux-centos7-x86\_64-gcc-10.2.1-clingo-bootstrap-spack-t4yf34cuvquqp5xd66zybmcfyhwbdlsf.spec.json
> ==\> Fetching https://mirror.spack.io/bootstrap/github-actions/v0.5/build\_cache/linux-centos7-x86\_64/gcc-10.2.1/clingo-bootstrap-spack/linux-centos7-x86\_64-gcc-10.2.1-clingo-bootstrap-spack-t4yf34cuvquqp5xd66zybmcfyhwbdlsf.spack
> ==\> Installing "clingo-bootstrap@=spack%gcc@=10.2.1~docs+ipo+optimized+python+static\_libstdcpp build\_system=cmake build\_type=Release generator=make patches=bebb819,ec99431 arch=linux-centos7-x86\_64" from a buildcache
> ==\> Warning: The default behavior of tarfile extraction has been changed to disallow common exploits (including CVE-2007-4559). By default, absolute/parent paths are disallowed and some mode bits are cleared. See https://access.redhat.com/articles/7004769 for more details.
> ==\> Error: 2024.11.15 is not a valid git ref for access-test
> \[test\] \[pag548@gadi-login-04 0.22\]$ spack install
> ==\> Error: 2024.11.15 is not a valid git ref for access-test
> \[test\] \[pag548@gadi-login-04 0.22\]$ spack find
> ==\> In environment test
> ==\> 1 root specs
> - access-test@git.2024.11.15
> 
> ==\> 0 installed packages
> \`\`\`
> 
> \## Why
> 
> Chris Bull offered the following:
> 
> Looking at your output I think it’s this line that’s the problem:
> \`\`\`
> ==\> Error: 2024.11.15 is not a valid git ref for access-test
> \`\`\`
> which is probably related to the spec in your spack.yaml file
> 
> \## Close Criteria

---

<div class="post-metadata">

**Author:** ![mmr0](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/mmr0/32/2485_2.png) [@mmr0](https://forum.access-hive.org.au/u/mmr0)\
**Post date:** [8 January 2025 05:15 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/14 "2025-01-08T05:15:04Z")

</div>

Hey folks, psyched to see all this action! I’ve just started with 21st Century Weather and will be commencing my MOM6 journey with Ashley’s MOM6-R package. But I am lurking on this issue to follow your progress & learn in the hope of contributing soon!

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [8 January 2025 21:59 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/15 "2025-01-08T21:59:01Z")

</div>

Hi Madi - I am excited to hear that you are getting straight into this!

I have now (as of 2 days ago!) configured regional mom6 standalone to run on nuopc and I have run a 4-day test case. I am writing up some instructions on the steps I needed to do to get this which will hopefully be available in the next week or so. It would be great if you (and @Paul.Gregory?) had some time to follow my instructions and provide feedback. Step 1 will be something along the lines of “commence your MOM6 journey with Ashley’s MOM6-R package” – so I think this is a great place to get started.

---

<div class="post-metadata">

**Author:** ![mmr0](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/mmr0/32/2485_2.png) [@mmr0](https://forum.access-hive.org.au/u/mmr0)\
**Post date:** [8 January 2025 22:35 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/16 "2025-01-08T22:35:57Z")

</div>

Hi Helen that’s incredible! I’d love to test it at any stage! let me know 😃

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [29 January 2025 04:49 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/17 "2025-01-29T04:49:46Z")

</div>

In the next few posts I am posing some instructions on the changes I needed to do to run regional mom6 on NUOPC.

Some of these changes will need to occur for each simulation, some will only need changing once. To get things started quickly, I am happy to chat about a temporary shared storage place for files with the “only need changing once” already done– and long term we are discussing less clunky and more official way to manage the changes needed.

The other thing to note is that we are using ACCESS-OM3 and regional-mom6 codes that are under active development so these instructions will need modifying in the coming weeks as a couple of changes are pushed through. I have tried to note where these changes are but if you notice something isn’t working with my suggested changes then please let me know.

@mmr0 Thank you for testing the instructions for me – please do tell me about mistakes!

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [29 January 2025 23:00 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/26 "2025-01-29T23:00:05Z")

</div>

A post was merged into an existing topic: [ACCESS-ROM3 setup instructions](https://forum.access-hive.org.au/t/access-rom3-setup-instructions/4107/2)

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [29 January 2025 23:14 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/27 "2025-01-29T23:14:48Z")

</div>

@mmr0  
It looks like it will be easier if I convert these instructions to a wiki as I can edit when changes occur. I will post a link to the wiki when it is finished.

---

<div class="post-metadata">

**Author:** ![helen](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/helen/32/2840_2.png) [@helen](https://forum.access-hive.org.au/u/helen)\
**Post date:** [3 February 2025 00:11 UTC](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/28 "2025-02-03T00:11:08Z")

</div>

@mmr0 instructions are [here](https://forum.access-hive.org.au/t/access-rom3-setup-instructions/4107)

[Next page](https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979.md?page=2)