Issues when transitioning from hh5 to xp65 in suite runs

Hi all,

I’m trying to run the u-cy339 suite in ACCESS-CM2 following this instruction: Run ACCESS-CM - ACCESS-Hive Docs. Since I don’t have hh5 membership which I understand is being closed, I’m trying to transition everything regarding hh5 to xp65 in the suite. But I have encountered some issues:

1. Issue with loading conda environment:

At the beginning, I encountered an error in the [ocean_ke_check] step like:

Then, I found these lines in the suite.rc file:

module use /g/data3/hh5/public/modules
module unload python
module load conda/analysis3

Following the announcement: ACCESS-NRI Analysis3 Conda Environments – New Release Announcement. I replaced hh5 with xp65 in the path, and it seems to work now. Is it the correct approach to resolve this issue?

2. Issue with um2netcdf4 script:

However, I encountered another issue in [netcdf_conversion] step. The error message is as follows:

This error comes from um2netcdf4 command in suite.rc file:

module use ~access/modules
module unload python
module load pythonlib/um2netcdf4.

The following is the script of um2netcdf4 which still seems to rely on hh5:

$ cat ~access/modules/pythonlib/um2netcdf4/2.1
#%Module

set help            "Conversion of UM fieldsfiles to netCDF"
set prefix           ~access/apps/pythonlib/um2netcdf4/2.1
set install-contact "martin.dix@csiro.au"
set install-date    "2023-01-16"
set url             "https://bitbucket.csiro.au/users/dix043/src"

conflict pythonlib/um2netcdf4

if ![ is-loaded conda/analysis3 ] {
    module use /g/data3/hh5/public/modules
    module load conda/analysis3
}

prepend-path PYTHONPATH $prefix
prepend-path PATH $prefix
setenv UMDIR /g/data/access/projects/access/umdir

Would it be possible to update um2netcdf4 to use xp65, or is there an existing version that supports xp65?

Does anyone have any suggestions? Thanks in advance!

Hao Wang

2 Likes

um2netcdf4.py uses the mule package which isn’t yet included in xp65.

I’ll look at a workaround but for the moment stay with hh5.

Thanks for looking into a workaround, @MartinDix . I’ll hold off now.