Skip to content

test a MOM6 only build of OM3#30

Closed
anton-seaice wants to merge 5 commits intomainfrom
mum6-nuopc-standalone-2
Closed

test a MOM6 only build of OM3#30
anton-seaice wants to merge 5 commits intomainfrom
mum6-nuopc-standalone-2

Conversation

@anton-seaice
Copy link
Collaborator

@anton-seaice anton-seaice commented Dec 11, 2024

testing building

access-om3-MOM6

without CICE6 or WW3


🚀 The latest prerelease access-om3/pr30-4 at 0beca0d is here: #30 (comment) 🚀


🚀 The latest prerelease access-om3/pr30-5 at 2daec22 is here: #30 (comment) 🚀

@anton-seaice anton-seaice mentioned this pull request Dec 11, 2024
@anton-seaice anton-seaice changed the title Update spack.yaml test a MOM6 only build of OM3 Dec 11, 2024
@github-actions
Copy link

🚀 Deploying access-om3 2024.12.mom6 as prerelease pr30-1 with commit c0c3dab

Details and usage instructions

This access-om3 model will be deployed as:

  • 2024.12.mom6 as a Release (when merged).
  • pr30-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr30-1

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr30-1 environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.07.08
  • access-nri/spack-config version 2024.11.27

If this is not what was expected, commit changes to config/versions.json.

@github-actions
Copy link

🚀 Deploying access-om3 2024.12.mom6 as prerelease pr30-2 with commit 7b76636

Details and usage instructions

This access-om3 model will be deployed as:

  • 2024.12.mom6 as a Release (when merged).
  • pr30-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr30-2

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr30-2 environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.07.08
  • access-nri/spack-config version 2024.11.27

If this is not what was expected, commit changes to config/versions.json.

@github-actions
Copy link

🚀 Deploying access-om3 2024.12.mom6 as prerelease pr30-3 with commit 1c6b7eb

Details and usage instructions

This access-om3 model will be deployed as:

  • 2024.12.mom6 as a Release (when merged).
  • pr30-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr30-3

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr30-3 environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.07.08
  • access-nri/spack-config version 2024.11.27

If this is not what was expected, commit changes to config/versions.json.

@github-actions
Copy link

🚀 Deploying access-om3 2024.12.mom6 as prerelease pr30-4 with commit 0beca0d

Details and usage instructions

This access-om3 model will be deployed as:

  • 2024.12.mom6 as a Release (when merged).
  • pr30-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr30-4

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr30-4 environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.07.08
  • access-nri/spack-config version 2024.11.27

If this is not what was expected, commit changes to config/versions.json.

@anton-seaice
Copy link
Collaborator Author

Hi @harshula - sorry me again.

the access-om3-nuopc package has a variants field called configurations, which allows multiple values. The default values are "MOM6-CICE6, CICE6-WW3, MOM6-CICE6-WW3"

When I run spack spec access-om3-nuopc configurations=MOM6, it solves as expected with the only value of configurations being MOM6:

$ spack spec access-om3-nuopc configurations=MOM6 
Input spec
--------------------------------
 -   access-om3-nuopc configurations=MOM6

Concretized
--------------------------------
 -   access-om3-nuopc@main%gcc@14.1.0~install_libraries~ipo~mom_symmetric~openmp build_system=cmake build_type=Release cice_io=PIO configurations=MOM6 generator=make arch=linux-rocky8-x86_64_v4
[e]      ^cmake@3.24.2%intel@2021.10.0~doc+ncurses+ownlibs build_system=generic build_type=Release arch=linux-rocky8-x86_64
[+]      ^esmf@8.6.0%intel@2021.10.0 cflags='-fp-model precise' fflags='-fp-mo...

However, if I add configurations=MOM6 to the access-om3 environment, it deploys the default configurations + MOM6

e.g.:

$ spack concretise --fresh
==> Warning: using "cmake@3.24.2" which is a deprecated version
==> Concretized access-om3@git.2024.09.0=2024.09.0
 -   fk4z43t  access-om3@git.2024.09.0=2024.09.0%intel@2021.10.0 build_system=bundle arch=linux-rocky8-x86_64
 -   bj7jjme      ^access-om3-nuopc@git.0.3.1=0.3.1%intel@2021.10.0~install_libraries~ipo~mom_symmetric~openmp build_system=cmake build_type=Release cice_io=PIO configurations=CICE6-WW3,MOM6,MOM6-CICE6,MOM6-CICE6-WW3 generator=make arch=linux-rocky8-x86_64 ...

Which seems like possibly a bug ? Also i can't figure out any syntax which turns off configurations (as multiple are allowed)

p.s. Not urgent, it builds what we need, it just also builds several things that are not needed in this case.

@github-actions
Copy link

🚀 Deploying access-om3 2024.12.mom6 as prerelease pr30-5 with commit 2daec22

Details and usage instructions

This access-om3 model will be deployed as:

  • 2024.12.mom6 as a Release (when merged).
  • pr30-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr30-5

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om3-pr30-5 environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.08, spack-config 2024.11.27

Details

It will be deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.07.08
  • access-nri/spack-config version 2024.11.27

If this is not what was expected, commit changes to config/versions.json.

@anton-seaice
Copy link
Collaborator Author

@helenmacdonald - This builds with the MOM6 only and mom_symmetric

There should an access-om3-MOM6 included in this module now :)

@access-hive-bot
Copy link

This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/creating-a-regional-access-om3/3979/8

@anton-seaice
Copy link
Collaborator Author

@helenmacdonald

This change will be included in #39

Please close this PR and use the new deployment when you are ready - closing it should delete this build from Gadi.

@anton-seaice anton-seaice deleted the mum6-nuopc-standalone-2 branch May 5, 2025 23:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants