xp65 analysis3 environments from 25.06 onwards are incompatible with NCI’s cylc7 environment. A minimal example: module purge module use /g/data/xp65/public/modules module use /g/data/hr22/modulefiles module load conda/analysis3-25.07 module load cylc7/23.09 rose task-env Produces a stack trac…

Thank you @Scott ! Is there a recommended analysis environment for cylc7? And specifying an exact (compatible) environment should fix things?

conda/analysis3-25.05 works fine from what I’ve tested just running Cylc, I think @am1625 is checking the suite itself

Fab, I’ll hold off until I hear from Anderson. Fast problem-solving on a Thursday morning, hats off!

Thanks for flagging this issue @Scott . I just encountered it while trying to run an ACCESS-CM2 suite. @rbeucher do you have an update?

No update yet. @CharlesTurner do you think you can have a look at this? Any reason to not use analysis3-25.06?

Haven’t had a look yet but I’m working on some other help stuff this morning so I’ll take a look at this too. Off the top of my head, there are have been no major package changes/upgrades in the past few months, so sticking to the old version of the environment for now shouldn’t be an issue.

Okay: it looks like _CONDA_PYTHON_SYSCONFIGDATA_NAME changed from _sysconfigdata_x86_64_conda_cos6_linux_gnu to _sysconfigdata_x86_64_conda_linux_gnu in 25.06. I’ve turfed up some old stuff related to conda-forge migrating default compiler toolchains - apparently the _cos6 part related to a CentOS6…

Is there a reason for the module file to set this variable? It should only be required inside the container so maybe all the variables the module sets can be moved to the wrapper script instead. The variables were needed in the modulefile before containers as we were effectively doing a ‘conda acti…

I’m not sure we can fix this without aligning conda versions - the environment variable is set by micromamba when it creates the conda environment, and so looks like it would require either an upgrade to the cylc conda version or a downgrade to the analysis3 version. Unless there are packages in ne…

Analysis3-25.06 onwards incompatible with cylc7

General

rbeucher (Romain Beucher) 28 October 2025 03:58 17

Is there any reason to stick with Cylc7? It still uses Python 2.7 apparently so it would be a good move…

Deprecation of conda/analysis3-25.05

Topic		Replies	Views
Deprecation of conda/analysis3-25.05 Coupled Model help	11	183	19 March 2026
Module import error in ocean_ke_check with xp65 conda environment Coupled Model help	1	80	9 October 2025
ACCESS-NRI Analysis3 Conda Environments – New Release Announcement ACCESS-NRI Releases python , conda , model-evaluation , climate-conda-enviro , hh5	0	1136	2 April 2025
Important Announcement – New `analysis3-26.03` Conda Environment ACCESS-NRI Releases python , conda , climate-conda-enviro	0	54	13 March 2026
Using xp65 in UM suites Infrastructure python , help , um	16	320	28 October 2025

Analysis3-25.06 onwards incompatible with cylc7

Related topics