Building

If you don't want to use a precompiled executable from /g/data/ik11/inputs/access-om3/bin/, you can build it yourself. Building access-om3 requires membership of the ik11 project - apply at https://my.nci.org.au/mancini/project/ik11 if needed.

Then cd to your clone of access-om3 (see the README for how to clone), and type

./build.sh

After a little while you'll get shiny new executables

bin/access-om3-CICE6-WW3-<hash>
bin/access-om3-MOM6-CICE6-<hash>
bin/access-om3-MOM6-CICE6-WW3-<hash>

which are labelled by the included model components and the git hash of the access-om3 repository so you can identify the sources they were built with. If the executable names also have a -modified suffix, this indicates that there were untracked files or uncommitted changes. If this happens it's a good idea to commit the changes and re-build so the executable sources are identifiable from the name of each executable.

Customising the included components (if needed)

build.sh invokes cmake in pairs. The first of each pair determines the included model components. By default the executable will have WW3, MOM6 and CICE enabled. If you'd like to change this, add the following to the first invocation of CMake in build.sh:

-DENABLE_WW3=ON -DENABLE_MOM6=ON  -DENABLE_CICE=ON

and replace ON with OFF where required (note that the default is ON for all components). You'd probably also want to change the executable name to specify the components used.

A note on dependencies

ACCESS-OM3 has several dependencies which are unavailable from NCI so we supply them via Spack using https://github.com/COSIMA/spack-config which is installed in /g/data/ik11/spack/.

TODO

We also want to coordinate with these plans https://github.com/ACCESS-NRI/model_builder