access_RoseStem_VN9.0_N512_EndGame - ACCESS-NRI/accessdev-Trac-archive GitHub Wiki

Rose Stem VN9.0 N512 ENDGame test at NCI

Description of a N512 ENDGame test at NCI with UM VN9.0.

This test is done within the rose-stem component of the UM source.

It is easily repeatable by anyone in access group on accessdev through the following steps

  1. On accessdev, check out the branch: !https://access-svn.nci.org.au/svn/um/branches/dev/axs599/my9.0_adv_rosestem for example, into $HOME/rs90/my9.0_adv_rosestem/

  2. Set up your input data on raijin:

    • mkdir -p /short/$PROJECT/$USER/cylc-run/TEST_IC/
    • ln -s /projects/access/data/rose-stem/20130121_qwqu12.T+3_n768_eg.ic /short/$PROJECT/$USER/cylc-run/TEST_IC/test.ic

  3. On accessdev, execute rose stem --source $HOME/rs90/my9.0_adv_rosestem --group=nci_n512_noomp_eg

** NOTES: **

(i) Better practice would be create your own branch from the URL above, and check out your own branch.

(ii) Branch name, directory names are only examples. You can name your directory and branch to suit your own working practice.

(iii) If the working directory where you execute the "rose stem" command is the directory where you check out the branch, the "--source" parameter can be omitted from the "rose stem" command.

(iv) For convenience, trac browser link to branch above is supplied here:
Trac browser link: https://access-svn.nci.org.au/trac/um/browser/branches/dev/axs599/my9.0_adv_rosestem

(v) This same test can easily be adapted to run at N768. It only require editing of source file rose-stem/app/recon_nci_n512_eg/rose-app.conf

  • modify global_row_length from 1024 to 1536 and global_rows from 768 to 1152
  • change wherever ancilfilename appear to point to ENDGame_n768e rather than ENDGame_n512e.
  • Succesful run at N768 starting using downloaded UKMO N512 I.C have been made.
  • More details will be made available later if required. It is likely that some redesign will be made to make the switch between resolution even easier, and the app name changed to reflect that.

(vi) There have been model issues when starting from some initial conditions. This is under investigation.

CHANGES MADE TO STANDARD VN9.0

  • New rose-stem apps:

      1. Create rose-stem/app/fcm_make_nci_um_high_noomp based on app/fcm_make_linux_um_high_noomp
      1. Create rose-stem/app/recon_nci_n512_eg from rose-stem/app/um_hpc_n512_eg/
      1. Create rose-stem/app/um_nci_n512_noomp_eg/ also from from rose-stem/app/um_hpc_n512_eg/
      1. Create rose-stem/app/rose_ana_nci_n512_noomp_eg_recon_kgo/ (currently place-holder only)
      1. Create rose-stem/app/rose_ana_nci_n512_noomp_eg_atmos_kgo/ (currently place-holder only)

  • Create new file rose-stem/suite-graph-nci-group.rc and update rose-stem/suite.rc to include it.

  • Modify the existing "rc" files in rose-stem

  • Modify rose-stem/rose-suite.conf customising it to NCI environment.

SUMMARY OF MODIFIED AND NEW SOURCES

MODIFIED SOURCE:

  rose-stem/suite.rc                      

  rose-stem/suite-graph-nci-standard.rc   

  rose-stem/suite-graph-nci-integ.rc      

  rose-stem/suite-runtime-nci.rc          

  rose-stem/suite-family-nci.rc           


  rose-stem/rose-suite.conf

NEW SOURCES:

rose-stem/suite-graph-nci-group.rc

rose-stem/app/fcm_make_nci_um_high_noomp/rose-app.conf

rose-stem/app/fcm_make_nci_um_high_noomp/file/fcm-make.cfg

rose-stem/app/recon_nci_n512_eg/rose-app.conf

rose-stem/app/recon_nci_n512_eg/file/INITFILEENV

rose-stem/app/recon_nci_n512_eg/file/user.PRESM_A

rose-stem/app/um_nci_n512_noomp_eg/rose-app.conf

rose-stem/app/um_nci_n512_noomp_eg/file/INITFILEENV

rose-stem/app/um_nci_n512_noomp_eg/file/user.PRESM_A

rose-stem/app/rose_ana_nci_n512_noomp_eg_recon_kgo/rose-app.conf

rose-stem/app/rose_ana_nci_n512_noomp_eg_atmos_kgo/rose-app.conf