Setting build options for OM3

ANCOMS Regional MOM6
21

Hi Paul

Yes it sounds like are on the right track.

access3 needs to be in BOTH the packages and develop section of spack.yaml

the configurations get set in the packages:access3:require: section not the develop section.

So, don’t do this:

Instead use:

   access3:
      require:
      - '@git.2025.03.0'
      - configurations=MOM6
 #     - fflags="-O0 -g -check bounds -check pointers -fpe0 -check noarg_temp_created"

And revert this:

22

Hi Paul

Apologies - we need to remove -check uninit from the access-mom6 and access3-share packages as well. See example here: rOM3-MOM6 build test by anton-seaice · Pull Request #86 · ACCESS-NRI/ACCESS-OM3 · GitHub

the access3 and access3-share spack packages actually both reference the same git repository (GitHub - ACCESS-NRI/access3-share: Shared code for access 3 models using NUOPC + CMEPS), so the git ref can be the same for both packages. (To use the commit without -check uninit). I added a commit to remove -check uninit from MOM6 as well, see the example above.

Anton

1 Like
23

Hi Anton.

I had a good chat with @harshula this morning and I’m watching all the work you’re doing via the pull requests and issue comments Github CI build logs on ACCESS-OM3.

Do you still want me working on building locally? I can you and Harshula are trying a few options (including checking the old ifort debugger against oneapi).

24

You should be able to use the executable in :

module use /g/data/vk83/prerelease/modules
module load access-om3/pr86-31

for now. Assuming the debugger works with oneapi ?

1 Like
25

That’s a very good question.

Gadi has padb and TotalView installed. I guess I’ll find out next week.

Cheers

1 Like
26

At some point Linaro DDT was mooted:

Linaro Forge HPC Tools... - NCI Help - Opus - NCI Confluence…

I don’t know of anyone who has got it setup though.

27 
module use /g/data/vk83/prerelease/modules
module load access-om3/pr86-31

Hi Paul - I’ve closed this PR, so that the previous 30 failed attempts at a build get cleaned up but it also deletes the one build you could use. If you want to use it, just make a new draft PR from the same branch.

1 Like