Skip to content

Conversation

@anton-seaice
Copy link
Collaborator

@anton-seaice anton-seaice commented Nov 20, 2025

Testing for #126

🚀 The latest prerelease access-om2/pr125-12 at 969e762 is here: #125 (comment) 🚀


🚀 The latest prerelease access-om2/pr125-20 at 75f8e0c is here: #125 (comment) 🚀

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-1 with commit 5fdff97

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-2 with commit 03d8a3a

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-3 with commit ede63f0

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-4 with commit bcb94bf

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-5 with commit 449be27

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om2, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.09.000 as a Release (when merged).
  • pr125-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr125-5

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om2-pr125-5 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-6 with commit 8163483

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

spack.environment.environment.SpackEnvironmentViewError: The environment view in /g/data/vk83/prerelease/apps/spack/0.22/environments/access-om2-pr125-6/.spack-env/view could not be created, because the following two specs project to the same prefix:
    access-om2@git.2025.09.000=latest%intel@=19.0.5.281~deterministic build_system=bundle arch=linux-rocky8-x86_64, and
    access-om2@git.2025.09.000=latest%intel@=19.0.5.281~deterministic build_system=bundle arch=linux-rocky8-x86_64.
    To resolve this issue:
        a. use `concretization:unify:true` to ensure there is only one package per spec in the environment, or
        b. disable views with `view:false`, or
        c. create custom view projections.

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-7 with commit b33d0dc

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-8 with commit 2145786

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-9 with commit 5c7f739

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-10 with commit 59ebc21

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

After prerelease injection:

   modules:
    default:
      tcl:
        projections:
          access-om2: '{name}/pr125-11'
          ^cice5: 'access-om2/dependencies/pr125-11/{name}/2025.12.000-{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'
          cice5: 'access-om2/dependencies/pr125-11/{name}/46ef92b232632663855abb4088ffbd76378c27b5-{hash:7}'
          libaccessom2: 'access-om2/dependencies/pr125-11/{name}/2025.05.001-{hash:7}'
          mom5: 'access-om2/dependencies/pr125-11/{name}/2025.08.000-{hash:7}'
          oasis3-mct: 'access-om2/dependencies/pr125-11/{name}/2025.03.001-{hash:7}'
          openmpi: 'access-om2/dependencies/pr125-11/{name}/4.1.5-{hash:7}'

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-11 with commit 0997ee6

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-12 with commit 969e762

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-12 with commit 969e762

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-14 with commit 969e762

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

!redeploy

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-15 with commit 969e762

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-16 with commit 5132b9f

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

Very close:

$module avail access-om2/pr125-16
--------------------------------------------------------------------------------------------------------------------------- /g/data/vk83/prerelease/modules ----------------------------------------------------------------------------------------------------------------------------
access-om2/pr125-16/2025.12.000-360x300  access-om2/pr125-16/2025.12.000-1440x1080  access-om2/pr125-16/2025.12.000-3600x2700  
$ module load access-om2/pr125-16/2025.12.000-3600x2700  
Loading access-om2/pr125-16/2025.12.000-3600x2700
  Loading requirement: access-om2/dependencies/pr125-16/openmpi/4.1.5-7hthlkf access-om2/dependencies/pr125-16/oasis3-mct/2025.03.001-fvxfc6y access-om2/dependencies/pr125-16/libaccessom2/2025.05.001-qsfaprb
    access-om2/dependencies/pr125-16/cice5/46ef92b232632663855abb4088ffbd76378c27b5-mksolsa access-om2/dependencies/pr125-16/mom5/2025.08.000-kpkemvt

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🚀 Attempted to deploy access-om2 Prerelease pr125-17 with commit 066be63

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om2, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.12.000 as a Release (when merged).
  • pr125-17 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr125-17

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om2-pr125-17 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 3, 2025

🚀 Attempted to deploy access-om2 Prerelease pr125-18 with commit 7fbd0d5

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om2, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.12.000 as a Release (when merged).
  • pr125-18 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr125-18

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om2-pr125-18 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

anton-seaice added a commit to ACCESS-NRI/cice5 that referenced this pull request Dec 17, 2025
The goal here is to enable multiple timesteps per history file when
using PIO, to be consistent with the access-esm1.6 branch. In the
access-esm1.6 branch, this
[change](#59) was implemented
only when using Netcdf for IO. Closes #58

1. This change relies on latest in ParallelIO
(NCAR/ParallelIO#2016). (Updating ParallelIO is
not answer changing -
[build](ACCESS-NRI/ACCESS-OM2#125) and
[repro](ACCESS-NRI/access-om2-configs#205 (comment))
)
2. This changes the time variable to be in the middle of the averaging
interval
3. error handling is added/modified on an as needed basis, rather than
comprehensively
4. Output files follow the ocean convention now, e.g
_iceh-1monthly-mean_1900.nc_
@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-19 with commit e10a727

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om2, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.12.000 as a Release (when merged).
  • pr125-19 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr125-19

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om2-pr125-19 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions
Copy link
Contributor

🚀 Attempted to deploy access-om2 Prerelease pr125-20 with commit 75f8e0c

🖥️ Gadi Deployment ✔️

Usage Instructions

access-om2, defined in ./spack.yaml, will be deployed to Gadi as:

  • 2025.12.000 as a Release (when merged).
  • pr125-20 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr125-20

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-om2-pr125-20 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

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