Issues when transitioning from hh5 to xp65 in suite runs

General
, ,
22

Hi @wghuneke, hmmm, ok, I think I understand you now. My example above is from the unreleased version of AM3, so perhaps things work differently in the next release. There’s no um2netcdf4loaded in the suite I have.

If um2netcdf4 is where the environment is loaded then I suspect the global solution would be for ACCESS-NRI to create an xp65 version of um2netcdf4 in access/modules.

Otherwise as a temporary workaround, you could create your own local copy, change it to xp65, and call your local script.

23

@wghuneke EDIT: I’ve just had a poke around in access/modules - there’s an xp65 version in there already:

$ ll /g/data/access/modules/pythonlib/um2netcdf4/
total 12
-rw-r-----+ 1 mrd599 access.admin 525 Mar 10  2022 2.0
-rw-r-----+ 1 mrd599 access.admin 525 Jan 16  2023 2.1
-rw-r-----+ 1 mrd599 access.admin 735 Aug 15 08:58 xp65

Can you try explicitly loading it and see what happens (unless someone from NRI jumps in to say we shouldn’t be doing that)?:
module load pythonlib/um2netcdf4/xp65

24

Thanks @bethanwhite , your last suggestion worked!

In summary, to switch CM2 suites from hh5 to xp65, you will have to change 3 things in suite.rc :

  1. Update -l storage flag to include gdata/xp65

  2. [[ocean_ke_check]]: Load a specific (at least no newer than) version of the xp65 conda environment:
    module use /g/data/xp65/public/modules module unload python module load conda/analysis3-25.05

  3. [[netcdf_conversion]]: change to module load pythonlib/um2netcdf4/xp65

3 Likes
25

@wghuneke yay! I guess it pays to be nosy :joy: