Suggested workflow for running coupled noresm3_0_alphaX simulations on Betzy - NorESMhub/noresm3_dev_simulations GitHub Wiki
-
Read about current simulations and set ups here: https://github.com/NorESMhub/noresm3_dev_simulations/issues
-
Checkout the most recent tag
> git clone https://github.com/NorESMhub/NorESM.git <noresm-base>
> cd <noresm-base>
> git tag --list
> git checkout noresm3_0_alphaXX
> ./bin/git-fleximod update
- create a new case, e.g
./create_newcase --case <user_case_path>/n1850.ne30_tn14.<tag-info>.<some_kind_of_info>.yyyymmdd --compset 1850_CAM%DEV%LT%NORESM%CAMoslo_CLM60%FATES-SP_CICE_BLOM%ECO_MOSART_DGLC%NOEVOLVE_SWAV_SESP --res ne30pg3_tn14 --project nnXXXXk --run-unsupported --mach betzy --compiler intel-oneapi
- All changes in the env_*.xml files should be done with
./xmlchange, e.g.
./xmlchange NTASKS=1920
./xmlchange NTASKS_OCN=256
./xmlchange ROOTPE=0
./xmlchange ROOTPE_OCN=1920
./xmlchange STOP_OPTION=nyears
./xmlchange STOP_N=7
./xmlchange REST_N=1
./xmlchange REST_OPTION=nyears
./xmlchange RESUBMIT=3
./xmlchange --subgroup case.run JOB_WALLCLOCK_TIME=48:00:00
./xmlchange --subgroup case.st_archive JOB_WALLCLOCK_TIME=03:00:00
-
Store the history files on NIRD, in
/datalake/NS9560K/noresm3/cases/ -
Push your case to github by
- Determine what branch your experiment case directory will live on (this is not related to the alphaXX tag you used to create your case). Current supported branches are:
- noresm3_preindust_coupled
- noresm3_preindust_amip
- Determine a case name for your run using the proposed naming convention of compset_alias.grid_alias.codeversion.somekindofinfo.yyyyymmdd (How is this different from the case name we alraty made with the alpha tag - I'm confused!)
- Open an issue and fill out the template -- include a link to the branch in the issue (when pushed)
- Create your case directory and using the script (where is this script) push your case directory to the branch