Setting up ensemble runs in ACCESS-CM2

Earth System Coupled Model
, , , ,
1

Hi there,

I want to set up several ensemble runs in ACCESS-CM2. I have seen a previous post about setting up ensemble runs (Ensemble runs with ACCESS-CM2 - #5 by ars599). But the files they shared are not in those paths anymore. I’m not able to repeat those suggestions anymore. I was wondering if there have been any updates to the related functions, or if you happen to know a simpler way to set up ensemble runs in ACCESS-CM2? Thanks in advance for any suggestions.

Cheers,
Huazhen

3

Hi @huazhen, are you looking to follow the first method mentioned in the linked topic, which adds a perturbation to the atmosphere’s temperature field?

I’m unsure about the details of the second method mentioned as the instructions may have moved.

4

Hi Spencer,

Yes, I was trying to follow the first method in the previous post. However, I couldn’t find the file “perturbIC.py” they mentioned.

Thanks,
Huazhen

5

Thanks!

There’s a copy of the perturbation script located at /g/data/access/projects/access/apps/pythonlib/umfile_utils/access_cm2/perturbIC.py

The required dependencies are available in the xp65 conda/analysis3 module, which can be loaded with:

module use /g/data/xp65/public/modules
module load conda/analysis3

You should then be able to run the script with a selected amplitude -a (default 0.01) and random seed -s.

Note that this script edits the restart file in place, and so it might be best to make a backup copy of the original restart before applying the perturbation.

6

Hi Spencer,

Thanks for your help. I have tried to follow the instructions, but I got the following error message. Do you have any suggestions on this? Thanks.

Traceback (most recent call last):
  File "~/perturbIC.py", line 12, in <module>
    from numpy.random import MT19937, RandomState, SeedSequence
ImportError: cannot import name MT19937
7

Hi @huazhen, could you please paste the commands you used to run the perturbIC script here including the module import step?

Thanks,
Spencer

8

Hi Spencer,

The problem have resolved. It maybe conflicted with my default version. It worked well with a new terminal. Thank you so much for your help.

Cheers,
Huazhen

1 Like
9

Hi Huazhen, thanks for the update and glad to know that it is working now! I’ll close this issue now.