-
Notifications
You must be signed in to change notification settings - Fork 2
Description
For example:
we have a job need to run archiver:
/scratch/p66/txz599/ACCESS_output/AERA2-spinup-03
Q1: where is the input data?
A1: base_dir=/scratch/p66/txz599/ACCESS_output/AERA2-spinup-03
correct answer
The base of the data shouldn’t have the run name
base_dir=/scratch/p66/txz599/ACCESS_output/
Q2: where should we keep the data?
A2: arch_dir==/g/data/p73/archive/non-CMIP/CMORised/AERA2/
correct answer
We are working on ARCHIVER not CMORise so shouldn’t touch CMORised folder.
arch_dir=/g/data/p66/$yourid/archive/non-CMIP/ACCESS-ESM1-5/
Q3: give a guess and let me know what do you think?
A3: Tilo provided the directory which store the very raw data output from model runs so this directory should be the base_dir. Tilo said “This is part of the Adaptive Emissions Reduction runs that you have cmorised recently.” So I guess the archive directory arch_dir should be the same as the one you send to Tilo before.
correct answer
The short answer is Tilo is running esm from script based not payu based so we need to change the run type to fit his run and that is
access_version=esmscript
Finally DO NOT forget to setup the job name you want to run!!
#loc_exps = list of local experiment names (stored in 'base_dir') to archive
loc_exps=(
#ch097
AERA2-spinup-03
)