About This topic is a catch-all location for feedback for the ACCESS-rAM3 Beta Release. Please reply to this topic if you have feedback on the ACCESS-rAM3 Beta. Feedback can be to point out problems encountered, or positive to highlight what worked well. If your feedback is involved and will require specific #help feel free to make a topic on the ACCESS-Hive Forum. If you’re not sure, reply here and your query can be moved to a separate topic if required.

This error I was having on 1 or 3 hour runs may be because: suite conf - Nesting Suite - General run options - CRUN_LEN = 6 Setting CRUN_LEN = 1 allows for runs less than 6 hours I think(?).

[image] cchambers: Setting CRUN_LEN = 1 allows for runs less than 6 hours I think(?). Chermelle is on leave otherwise I would defer to her. When we discussed supporting modifying the run length “chunks” Chermelle mentioned some complications that were non-trivial for inexperienced users, hence the decision to not support modifying it. If this works for your testing use case, great!

Hi @mlipson . In your changeset, why do you use $HK_CYCLE rather than -PT0H? Which cycle directory do you mean to refer to, the current one or (e.g.) the previous one?

The reason that I ask is that I need to understand the exact effects of this change so that I can test it.

Hi Paul, the reason to use the variable $HK_CYCLE is to support free-running as well as “normal” cycling modes. Free-running needs some files from the previous cycle for the next’s initial conditions, so the housekeep actions have to be one cycle behind ($HK_CYCLE… but I’m not sure what HK stands for! edit: ahhh HouseKeep) HK_CYCLE is defined in the suite.rc file with: {% if FREE_RUN %} HK_CYCLE = $CYCLE_OFFSET {% else %} HK_CYCLE = -PT0H {% endif %} Edit: Paul on reflection I might have applied this deletion delay to some of the variables unnecessarily, e.g. ICS shouldn’t need to be kept for the next cycle. So if you prefer to replace with -PT0H and that works, then please do so, thanks for spotting this.

@mlipson Thanks for the info. I am re-running the test of the changes on u-dg768 now.

@mlipson Could you please clarify what housekeeping can be done for the current cycle vs what needs to be done for the previous one? I am currently testing with [pcl851@gadi-login-07 u-dg768]$ cat app/housekeep/opt/rose-app-nci-gadi.conf [prune] prune{share/cycle}=-PT0H:'*/*/*_da*' =-PT0H:'*/*/*/ics/*' =$HK_CYCLE:'*/*/*/lbcs/*_alabc_*' =$HK_CYCLE:'*/*/ec_cb*' =$HK_CYCLE:'*/*/*/*/*_da*'

Hi Paul, I think you might be able to do prune{share/cycle}=-PT0H:'*/*/*_da*' =-PT0H:'*/*/*/ics/*' =-PT0H::'*/*/*/lbcs/*_alabc_*' =$HK_CYCLE:'*/*/ec_cb*' =$HK_CYCLE:'*/*/*/*/*_da*' as the linkprev task says it only acts on the boundaries of the driving model, which in our case is ec. But you would need to test with free-running mode on. The last line I left unchanged, that is as it is in the RAS.

Thanks. For the moment, I have left it as I described above. Let’s see what the test comes up with.

@mlipson The job failed in 20220227T0000Z/Lismore_d1000_GAL9_um_recon_cyclen with ls: cannot access '/home/851/pcl851/cylc-run/u-dg768/share/cycle/20220226T0000Z/Lismore/d1000/GAL9/ics/*a_da*': No such file or directory 2025-04-15T09:20:22Z CRITICAL - failed/EXIT

ACCESS-rAM3 Beta Feedback

Atmosphere rAM3/Regional Nesting Suite

Topic		Replies	Views
ACCESS-rAM3: Release Information ACCESS-NRI Releases release , model , access-ram3	5	844	23 October 2026
ACCESS-AM3 1.0 Alpha Feedback AM3	35	620	5 June 2026
ACCESS-rAM3 2.0-beta Feedback rAM3/Regional Nesting Suite regional , atmosphere , feedback , beta , access-ram , access-ram3	13	215	3 September 2026
ACCESS-rAM3 'Flagship' Experiments rAM3/Regional Nesting Suite	17	371	20 February 2026
Scope of ACCESS-NRI ACCESS-OM2 release COSIMA release , access-nri	27	1796	31 January 2023

ACCESS-rAM3 Beta Feedback

Related topics