Running ACCESS-C aps2_access_c

Running aps2_access_c is much simpler than doing aps1_access_c. On accessdev (anywhere), you check out the suite from ROSIE repository,

rosie checkout au-aa295  #au-aa295 is the id in `ROSIE` database for aps2_access_c suite

By default, the suite au-aa295 will be checked out onto $HOME/roses/; please go to $HOME/roses/au-aa295, you should see

total 12
drwxr-xr-x 3 wml548 dp9 4096 Apr 13 16:42 app
-rw-r--r-- 1 wml548 dp9    0 Apr 13 16:40 rose-suite.conf
-rw-r--r-- 1 wml548 dp9   70 Apr 13 16:40 rose-suite.info
-rwxr-xr-x 1 wml548 dp9 3808 Apr 13 16:48 suite.rc

In this folder, just run

rose suite-run

and a window pops up in seconds to let you monitor/control the running of the suite. The running of each job is actually on raijin.

Please go to /short/$PROJECT/$USER/au-aa295_S to check the input/output data, including initial conditions, lateral boundary conditions, forecast data etc.

Running ACCESS-C aps2_access_x

We also provide aps2_access_x to let users run variable domain. You need to specify at your $HOME@raijin two files, SW1 nad SW2, which look like,

# for ancil
 LAT_START=-38.0
 LAT_END=-30
 LON_START=147
 LON_END=155
 DELTA=0.0135

and check out suite au-aa318. Please run this suite as au-aa295. This aps2_access_x suite has more jobs, such as reading the SW1 and SW2

to produce all the namelist files, create necessary ancillary files to the variable domains. au-aa318 is quite similar to au-aa295 in other respects.