Hi Julie, the line below means the model is pulling its spectral files from the UKMO fcm repository. This will fail if you haven’t successfully run mosrs-auth before running the model.
spectral_files=source=fcm:socrates.xm_tr/data/spectra/ga9@um13.1
I also thought this could be the case. I tried braking my mosrs authentication (moving the servers file) and the model still runs. There’s still the possibility that I already have those files cached somewhere but I haven’t found anything on the suite configuration.
Thanks @bethanwhite. I have finally got my mosrs-auth working, but the model still fails at the same point. Perhaps I need to join ki32_mosrs.
@JulieA yep, you do.
@Aidan @heidi @paigem the recent changes to running ACCESS models described here (and a separate email from Paige) indicated we won’t need to join ki32_mosrs, membership of df42 will take care of it. But perhaps we’re still in a transition phase given I’m having permission errors running AM3? I’m particularly interested now as our Honours/MSc students in my climate modelling unit will be running ACCESS ESM1.5 in a couple of weeks time so we need to ensure they’re members of all the required projects beforehand. Thanks!
The .xm here means it’s from the local ki32 mirror (needing ki32_mosrs membership), if it’s just .x it gets read from MOSRS
Thanks Scott. So Julie needs ki32_mosrs membership for this to not fail.
My ki32_mosrs application has been pending for 2 days. Any idea how long it usually takes for approval? Thanks!
@JulieA the description for ki32_mosrs states:
Needs the existing mosrs account to join. Please send your current mosrs account name to rui.yang@anu.edu.au after requesting the connection to ki32_mosrs.
Did you send the email to Rui? If you have done so, I would write to help@nci.org.au to see what is the hold up.
Thanks Claire. I’d missed seeing that detail when I requested to join ki32_mosrs. Rui has now approved my membership and I tried my AM3 experiment again. Unfortunately it still fails.
Thanks to a tip from @paocorrales it’s now running. I had changed to the latest release during my debugging previously so once I changed it back to the 2025-10 version it successfully got past the recon phase. Thanks for everyone’s help!
So the latest release doesn’t run for you, @JulieA?
@bethanwhite the official release works but if I change line 28 in ~/roses/access-am3-configs/rose-suite.conf_nci_gadi from SPACK_BUILD='access-am3/access-am3/2025.10.000’ to SPACK_BUILD='access-am3/access-am3/2026.03.000’ it fails
@JulieA That isn’t expected to work with the release-n96e configuration- there are some associated configuration changes that are required to run that particular release, which are currently in review. Use the dev-n96e branch of the configurations to get the latest working binary+configurations pair.
@JulieA , a bit late but the ki32_mosrs dependency will be removed from the beta release. To remove it before then, in this file app/um/rose-app.conf in the configuration, you need to change
SPECTRAL_FILE_DIR=spectral_files
to
SPECTRAL_FILE_DIR=/g/data/vk83/configurations/inputs/access-am3/atmosphere/socrates/spectral-um13.1/resolution_independent/2026.05.01/
And in the same file, you can remove these lines for good measure:
[file:spectral_files]
source=fcm:socrates.xm_tr/data/spectra/ga9@um$VN