ACCESS-rAM3 Beta Feedback

Atmosphere Regional Nesting Suite
, , , ,
1

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.

2

Thank you NRI for this release, it is already very useful. One of the known issues in the alpha release is:

Large amounts of forcing data are created.

One potential solution is to delete initial conditions (ics), lateral boundaries (lbcs/cb) on the fly using the inbuilt housekeep app. In my free-running branch I’ve included the following lines to remove ics/cb files:

=$HK_CYCLE:'*/*/*/ics/*'
=$HK_CYCLE:'*/*/*/lbcs/*_alabc_*'
=$HK_CYCLE:'*/*/ec_cb*'

These files are then deleted at the successful completion of any individual cycle within the simulation. In my test this reduced daily scratch storage from 200 to 30 GB, without removing any actual um outputs.

You can see my branch changeset on MOSRS here.

2 Likes
3

Sometimes I need to redefine which project the suite will use for a) compute b) scratch.

For a) my solution to date has been to change my default $PROJECT definition in ~/.config/gadi-login.conf, re-login and run.

Then for b) (with thanks to Dale Roberts post here) I have included the following at the top of my rose-suite.conf

root-dir=*=/scratch/$PROJECT/$USER

Where $PROJECT can be updated as required, or left as default.

Perhaps there are cleaner ways to do this through the GUI?

2 Likes
4

Note there is also a command switchproj that will create a new shell with a modified $PROJECT

$ switchproj -h
switchproj: run a copy of your shell or a command after 
changing the effective group id
Usage: switchproj [-h] [-a <argv0>] [-l] <group> [<command> [args ...]]
<group> may be a group name or gid number.
<group> must be in the user's list of groups.
Options:
  -a <argv0>
    Set argv[0] to <argv0>. If this option is specified and <command> is not
    present, its value will be ignored
  -l
    Prepend argv[0] of the command to run with a hyphen
  Note that if both -a and -l are used, they must be in the order shown above.
  -h
    Print this

Though I can’t find any documentation on the NCI Opus docs.

1 Like
5

Thank you @mlipson for your suggestion about the housekeeping command - I agree it would be useful for longer runs.

We decided to leave the intermediate working files in the directories for beginner users so they can trace the inputs and outputs being created by RNS jobs. This decision was made for learning purposes, but I can definitely see the merit for the files being routinely removed once these steps have been learnt.

We can discuss having different branches of the suite with the output routinely removed or left behind and investigate the possibility of adding a switch to the RNS.

Thanks again for your feedback.

1 Like