Test replacing/removing -xCORE-AVX2 by dougiesquire · Pull Request #138 · ACCESS-NRI/ACCESS-OM2

dougiesquire · 2026-02-24T23:57:14Z

This PR is to test removing/replacing -xCORE-AVX2 across the ACCESS-OM2 stack

🚀 The latest prerelease access-om2/pr138-11 at e44855d is here: #138 (comment) 🚀

🚀 The latest prerelease access-om2/pr138-19 at 89234e2 is here: #138 (comment) 🚀

github-actions · 2026-02-25T00:21:17Z

🚀 Attempted to deploy access-om2 Prerelease pr138-1 with commit 329cf77

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr138-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr138-1

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/1.1/spack in the access-om2-pr138-1 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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version dbff638add68e70d48683d06b3bb3ae6ad0a7f38
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-02-25T00:51:59Z

!update-configs

github-actions · 2026-02-25T00:52:54Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om2-configs

Configurations Requested

Configurations requested from profile default:

dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

Auto update dev-1deg_jra55_ryf to use access-om2/pr138-1 access-om2-configs#261

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/22376965677

dougiesquire · 2026-02-25T02:14:25Z

From the linked PR above, with pr138-1:

✅ test_repro_historical
✅ test_repro_determinism
✅ test_repro_restart

dougiesquire · 2026-02-25T23:12:05Z

Hmm, this does appear to have a reasonable negative impact on performance. I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-1 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run -n 3. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/161644452.gadi-pbs.json:        "payu_run_duration_seconds": 839.5187113920692,
archive/payu_jobs/1/run/161645931.gadi-pbs.json:        "payu_run_duration_seconds": 843.7589967059903,
archive/payu_jobs/2/run/161647049.gadi-pbs.json:        "payu_run_duration_seconds": 838.253176500788,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/161646511.gadi-pbs.json:        "payu_run_duration_seconds": 945.3608389219735,
archive/payu_jobs/1/run/161647985.gadi-pbs.json:        "payu_run_duration_seconds": 945.074181515025,
archive/payu_jobs/2/run/161649727.gadi-pbs.json:        "payu_run_duration_seconds": 944.211514512077,

So ~12% slower with -mavx2 than with -xCORE-AVX2

github-actions · 2026-03-01T23:13:20Z

🚀 Attempted to deploy access-om2 Prerelease pr138-2 with commit d7fdf52

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr138-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr138-2

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/1.1/spack in the access-om2-pr138-2 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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-01T23:30:19Z

!update-configs

github-actions · 2026-03-01T23:31:17Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om2-configs

Configurations Requested

Configurations requested from profile default:

dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

Auto update dev-1deg_jra55_ryf to use access-om2/pr138-1 access-om2-configs#261

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/22555440525

dougiesquire · 2026-03-01T23:39:46Z

With pr138-2:
✅ test_repro_historical
✅ test_repro_determinism
✅ test_repro_restart

manodeep · 2026-03-02T00:10:18Z

@dougiesquire To use the cpu name specific targets, you will likely need to set the concretizer config concretizer->targets->granularity=microarchitectures. It's set to generic by default.

github-actions · 2026-03-02T00:17:06Z

🚀 Attempted to deploy access-om2 Prerelease pr138-3 with commit d22ab30

🖥️ `Gadi` Deployment ❌

(@dougiesquire cancelled this due to #138 (comment))

dougiesquire · 2026-03-02T00:53:50Z

Performance with -mavx2 removed from all packages (so no -xCORE-avx2 or -mavx2)

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-2 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run -n 3. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162056547.gadi-pbs.json:        "payu_run_duration_seconds": 833.1820627681445,
archive/payu_jobs/1/run/162059170.gadi-pbs.json:        "payu_run_duration_seconds": 830.3039888441563,
archive/payu_jobs/2/run/162061363.gadi-pbs.json:        "payu_run_duration_seconds": 836.3757481910288,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162056595.gadi-pbs.json:        "payu_run_duration_seconds": 939.527026204858,
archive/payu_jobs/1/run/162059610.gadi-pbs.json:        "payu_run_duration_seconds": 944.9940079760272,
archive/payu_jobs/2/run/162062341.gadi-pbs.json:        "payu_run_duration_seconds": 948.0654471958987,

So still ~12% slower

github-actions · 2026-03-02T01:09:25Z

🚀 Attempted to deploy access-om2 Prerelease pr138-4 with commit 2a2ec93

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr138-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr138-4

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/1.1/spack in the access-om2-pr138-4 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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-02T01:13:20Z

!update-configs

github-actions · 2026-03-02T01:14:16Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om2-configs

Configurations Requested

Configurations requested from profile default:

dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

Auto update dev-1deg_jra55_ryf to use access-om2/pr138-1 access-om2-configs#261

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/22557435246

dougiesquire · 2026-03-02T01:24:09Z

With pr138-4:
✅ test_repro_historical
✅ test_repro_determinism
✅ test_repro_restart

dougiesquire · 2026-03-02T01:46:11Z

Performance with target=cascadelake

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-4 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162071407.gadi-pbs.json:        "payu_run_duration_seconds": 832.9791051410139,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162071402.gadi-pbs.json:        "payu_run_duration_seconds": 945.2046530928928,

So still ~12% slower

dougiesquire · 2026-03-04T04:51:18Z

!update-configs

github-actions · 2026-03-04T04:52:14Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om2-configs

Configurations Requested

Configurations requested from profile default:

dev-01deg_jra55_ryf
dev-025deg_jra55_ryf
dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/22655605101

dougiesquire · 2026-03-04T06:01:06Z

Performance with no flags and target=x86_64_v2

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-13 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
        "payu_run_duration_seconds": 837.9251451641321,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
        "payu_run_duration_seconds": 860.9682809540536,

So ~3% slower

github-actions · 2026-03-04T06:28:54Z

🚀 Attempted to deploy access-om2 Prerelease pr138-14 with commit d1ee94d

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr138-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr138-14

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/1.1/spack in the access-om2-pr138-14 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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-04T06:30:21Z

!update-configs

github-actions · 2026-03-04T06:31:19Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om2-configs

Configurations Requested

Configurations requested from profile default:

dev-01deg_jra55_ryf
dev-025deg_jra55_ryf
dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/22657954237

github-actions · 2026-03-04T06:41:49Z

🚀 Attempted to deploy access-om2 Prerelease pr138-15 with commit c2075cf

🖥️ `Gadi` Deployment ❌

github-actions · 2026-03-04T07:30:06Z

🚀 Attempted to deploy access-om2 Prerelease pr138-16 with commit f9f50bf

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr138-16 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr138-16

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/1.1/spack in the access-om2-pr138-16 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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-04T07:47:58Z

!update-configs

github-actions · 2026-03-04T07:49:00Z

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om2-configs

Configurations Requested

Configurations requested from profile default:

dev-01deg_jra55_ryf
dev-025deg_jra55_ryf
dev-1deg_jra55_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/22660011408

dougiesquire · 2026-03-04T07:49:34Z

Performance with no flags and target=x86_64

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-14 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
        "payu_run_duration_seconds": 843.5014327599201,

Exp 2

grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
        "payu_run_duration_seconds": 874.2103985729627,

So ~4% slower

github-actions · 2026-03-04T09:15:31Z

🚀 Attempted to deploy access-om2 Prerelease pr138-17 with commit efd6395

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr138-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/pr138-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/1.1/spack in the access-om2-pr138-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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-04T10:11:55Z

Performance with no flags and target=haswell

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-16 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run -n 3. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162270387.gadi-pbs.json:        "payu_run_duration_seconds": 838.8389234167989,
archive/payu_jobs/1/run/162274169.gadi-pbs.json:        "payu_run_duration_seconds": 841.6124492289964,
archive/payu_jobs/2/run/162276958.gadi-pbs.json:        "payu_run_duration_seconds": 842.9676855828147,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162270386.gadi-pbs.json:        "payu_run_duration_seconds": 892.1444520510267,
archive/payu_jobs/1/run/162274170.gadi-pbs.json:        "payu_run_duration_seconds": 894.877702570986,
archive/payu_jobs/2/run/162276957.gadi-pbs.json:        "payu_run_duration_seconds": 890.5481417709962,

So ~6% slower

github-actions · 2026-03-04T22:19:44Z

🚀 Attempted to deploy access-om2 Prerelease pr138-18 with commit 4ad5704

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr138-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/pr138-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/1.1/spack in the access-om2-pr138-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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-04T23:13:05Z

Performance with -march=core-avx2 flags in spack.packages.all.prefer

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-18 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run -n 2. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162306425.gadi-pbs.json:        "payu_run_duration_seconds": 834.740109429229,
archive/payu_jobs/1/run/162307246.gadi-pbs.json:        "payu_run_duration_seconds": 842.9836442731321,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162306426.gadi-pbs.json:        "payu_run_duration_seconds": 921.1132797608152,
archive/payu_jobs/1/run/162307314.gadi-pbs.json:        "payu_run_duration_seconds": 889.0010685380548,

So ~6% slower

github-actions · 2026-03-04T23:34:54Z

🚀 Attempted to deploy access-om2 Prerelease pr138-19 with commit 89234e2

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.001 as a Release (when merged).
pr138-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/pr138-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/1.1/spack in the access-om2-pr138-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:

access-nri/spack on branch 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 900bb5e689803a4bfa7302500afb395b8e53beaa
access-nri/spack-config version 2026.02.003

If the above was not what was expected, commit changes to config/versions.json in this PR, or propose changes to build-cds config/settings.json.

dougiesquire · 2026-03-05T03:15:00Z

Performance with -march=core-avx2 only for key dependencies (cice5, mom5, libaccessom2, oasis3-mct, access-fms, access-generic-tracers, access-fms)

I ran this dev-1deg_jra55_ryf configuration with the following changes:

Exp 1

Use access-om2/2026.02.000
Set restart_format = 'pio' in cice_in.nml

Exp 2

Use access-om2/pr138-19 (this PR)
Set restart_format = 'pio' in cice_in.nml

I changed the run length to 1 year and ran payu run -n 2. These are the run durations:

Exp 1

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162310337.gadi-pbs.json:        "payu_run_duration_seconds": 842.1666844459251,
archive/payu_jobs/1/run/162311232.gadi-pbs.json:        "payu_run_duration_seconds": 840.5417929301038,

Exp 2

$ grep "payu_run_duration_seconds" archive/payu_jobs/*/run/*.gadi-pbs.json
archive/payu_jobs/0/run/162310338.gadi-pbs.json:        "payu_run_duration_seconds": 891.6344424730632,
archive/payu_jobs/1/run/162311416.gadi-pbs.json:        "payu_run_duration_seconds": 895.2898426400498,

So ~6% slower

Replace -xCORE-AVX2 with -mavx2

329cf77

dougiesquire self-assigned this Feb 24, 2026

dougiesquire temporarily deployed to Gadi Prerelease February 24, 2026 23:59 — with GitHub Actions Inactive

access-bot mentioned this pull request Feb 25, 2026

Auto update dev-1deg_jra55_ryf to use access-om2/pr138-1 ACCESS-NRI/access-om2-configs#261

Closed

dougiesquire mentioned this pull request Feb 25, 2026

CMake Build flags incompatible with AMD processors ACCESS-NRI/MOM5#72

Open

Remove -mavx2

d7fdf52

dougiesquire temporarily deployed to Gadi Prerelease March 1, 2026 22:56 — with GitHub Actions Inactive

dougiesquire changed the title ~~Test replacing -xCORE-AVX2 with -mavx2~~ Test replacing/removing -xCORE-AVX2 Mar 1, 2026

Set target=cascadelake

d22ab30

dougiesquire had a problem deploying to Gadi Prerelease March 2, 2026 00:06 — with GitHub Actions Error

Add targets:granularity:microarchitectures

2a2ec93

dougiesquire temporarily deployed to Gadi Prerelease March 2, 2026 00:20 — with GitHub Actions Inactive

dougiesquire mentioned this pull request Mar 2, 2026

Release 2026.02.001 (redo) #142

Merged

Use target=x86_64

d1ee94d

dougiesquire temporarily deployed to Gadi Prerelease March 4, 2026 06:04 — with GitHub Actions Inactive

Use target=haswell

c2075cf

dougiesquire had a problem deploying to Gadi Prerelease March 4, 2026 06:35 — with GitHub Actions Failure

Oops

f9f50bf

dougiesquire temporarily deployed to Gadi Prerelease March 4, 2026 06:47 — with GitHub Actions Inactive

Remove host_compatible: false

efd6395

dougiesquire temporarily deployed to Gadi Prerelease March 4, 2026 09:02 — with GitHub Actions Inactive

All -march=core-avx2

4ad5704

dougiesquire temporarily deployed to Gadi Prerelease March 4, 2026 21:43 — with GitHub Actions Inactive

Use -march=core-avx2 only for key dependencies

89234e2

dougiesquire temporarily deployed to Gadi Prerelease March 4, 2026 23:18 — with GitHub Actions Inactive

manodeep mentioned this pull request Mar 18, 2026

Performance optiimisation: Add debug flags, and target cascadelake ACCESS-NRI/ACCESS-OM3#210

Draft

Conversation

dougiesquire commented Feb 24, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 25, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Feb 25, 2026

Uh oh!

github-actions bot commented Feb 25, 2026

Uh oh!

dougiesquire commented Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dougiesquire commented Feb 25, 2026

Uh oh!

github-actions bot commented Mar 1, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Mar 1, 2026

Uh oh!

github-actions bot commented Mar 1, 2026

Uh oh!

dougiesquire commented Mar 1, 2026

Uh oh!

manodeep commented Mar 2, 2026

Uh oh!

github-actions bot commented Mar 2, 2026 • edited by dougiesquire Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🖥️ Gadi Deployment ❌

Uh oh!

dougiesquire commented Mar 2, 2026

Uh oh!

github-actions bot commented Mar 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Mar 2, 2026

Uh oh!

github-actions bot commented Mar 2, 2026

Uh oh!

dougiesquire commented Mar 2, 2026

Uh oh!

dougiesquire commented Mar 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dougiesquire commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

Uh oh!

dougiesquire commented Mar 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

Uh oh!

dougiesquire commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Mar 4, 2026

Uh oh!

github-actions bot commented Mar 4, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Mar 4, 2026

dougiesquire commented Feb 24, 2026 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ✔️

dougiesquire commented Feb 25, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

github-actions bot commented Mar 2, 2026 •

edited by dougiesquire

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

dougiesquire commented Mar 2, 2026 •

edited

Loading

dougiesquire commented Mar 4, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️