ACCESS-rAM3 Beta Feedback

[paulleopardi]

@mlipson See MOSRS roses-u Trac ticket #641 for changes to the housekeep app. The changes have been made on the beta branch of u-dg768, and are awaiting review.

[paulleopardi]

Hi @cchambers , the Conda environments use up inode capacity on vk83 so the alpha environment has been deleted. Please test the beta environment.

$ ls /g/data/vk83/apps/conda/access-ram
2025.03.0

@atteggiani

[cchambers (Christopher Chambers)]

Thanks! So I have been modifying the rose suite GUI settings in the alpha - adding variables, time profiles, domain profiles etc., I’m not familiar with the different environments or where they are set. Is my best approach to start with the beta suite and redo my profiles in the GUI there or can I just set my old suite to use the beta environment in some way.

[Aidan (Aidan Heerdegen, ACCESS-NRI Release Team Lead)]

@cchambers

So I have been modifying the rose suite GUI settings in the alpha - adding variables, time profiles, domain profiles etc.

It is always fraught relying on an alpha (or beta) release, as we’re explicitly not supporting them for long term use.

@cchambers

I’m not familiar with the different environments or where they are set

You can view the change log for the trunk to find out what was changed. Then select the revisions to view the specific change to update the conda environment.

@cchambers

Is my best approach to start with the beta suite and redo my profiles in the GUI there or can I just set my old suite to use the beta environment in some way.

Your best approach is to wait for the full release, the plan is in the next two weeks, then changes you make will be on top of a stable base.

Having said which, the beta is more stable than the alpha and we’re not targeting any changes to the supporting conda environment at this stage.

[Aidan (Aidan Heerdegen, ACCESS-NRI Release Team Lead)]

The beta release has been updated, we are now at our second iteration:

ACCESS-rAM3: Release Information

To receive email notifications when a new release is announced, please watch this topic. ACCESS-rAM3 Release: Beta, iteration 2 This is the first ACCESS-NRI supported release of ACCESS-rAM3, an implementation of the UK Met Office (UKMO) regional nesting suite. More information about the model is available on the ACCESS Hive Docs. Importantly, unlike other models this is a suite that supports creating regional atmosphere/land configurations in an Australian context. The suite enabl…

Notably:

Fixed in this release update

Regional Ancillary Suite: queue settings have been fixed
Regional Nesting Suite: automated house-keeping of driving data

Any testing of the netCDF output and the changes made above would be welcome.
What should be observed:

• The RAS should run much quicker. At the very least the runtime should be more consistent. Previously it was using HUGEMEM queues, which can often suffer very long wait times.
• The RNS should use a lot less disk space in total, and not increase with overall run length. @mlipson noted above the driving data should be capped at 30GB, but we have not independently verified this figure yet.

[paulleopardi]

The total size of cylc-run/u-dg768 after the change to housekeeping is about 60G, of which:

19G     u-dg768/share
41G     u-dg768/work

Prior to the change, the total size was about 225G+, of which

185G    u-dg768/share
 41G    u-dg768/work