Traceback (most recent call last):
File "/g/data/vk83/apps/base_conda/envs/payu-1.1.6/bin/payu-run", line 10, in <module>
sys.exit(runscript())
File "/g/data/vk83/apps/base_conda/envs/payu-1.1.6/lib/python3.10/site-packages/payu/subcommands/run_cmd.py", line 133, in runscript
expt.setup()
File "/g/data/vk83/apps/base_conda/envs/payu-1.1.6/lib/python3.10/site-packages/payu/experiment.py", line 475, in setup
model.setup()
File "/g/data/vk83/apps/base_conda/envs/payu-1.1.6/lib/python3.10/site-packages/payu/models/um.py", line 127, in setup
super(UnifiedModel, self).setup()
File "/g/data/vk83/apps/base_conda/envs/payu-1.1.6/lib/python3.10/site-packages/payu/models/model.py", line 320, in setup
raise FileNotFoundError(
FileNotFoundError: Executable for atmosphere model not found on path: /scratch/y99/lcm561/access-esm/bin/um_hg3.exe
I don’t have any conda loaded
Thanks for your help!
I’ve moved your query to it’s own topic so the triage team can pick it up.
Today is a public holiday in the ACT, so there probably won’t be anyone who can look at it until then, but off the top of my head I can see you’re trying to access your own executable at /scratch/y99/lcm561/access-esm/bin/um_hg3.exe.
I’d suggest running
payu setup
payu sweep
payu run
and see if that helps payu to guess the right storage flags for your experiment.
Thanks Aidan, but I am not trying to access my own executable. Just trying the default setup as suggested on the Hive: Run ACCESS-ESM - ACCESS-Hive Docs
I have already run the 3 commands you mention.
Hi @LaurieM,
This error looks like you are lacking access to the modules that contain the UM executable. Are you a member of ki32 and ki32_mosrs projects on NCI? If not, send a request to join those groups. Note that this requires having a MOSRS account, which is a separate process.
There was also a temporary workaround in place for some new users, but I don’t know if this is available.
Regards,
David
ACCESS-NRI is in the process of finalising a Research Partnership agreement with the UKMO. Until that is finalised we have to use the existing processes to grant access to UKMO licensed material, and ACCESS-ESM1.5 uses the UM, which is a UKMO licensed product.
Aidan
(Aidan Heerdegen, ACCESS-NRI Release Team Lead)
8
@LaurieM confirmed the problem was not having the correct project memberships. This has been rectified so I will close this topic.