Set up simulation
-
-
Set up simulation
- Important files
-
config.card
- How to manage job name, start date, end date, and restart files
- How to continue a simulation
- How to manage calendar type
- How to manage monoprocessor or multiprocessor run
- How to set Init & Boundary condition's directory
- How to restart from another run
- How to have post treatement
- How to manage write output frequency
- How to manage Interannual or Climatological Runs
- How to manage Interannual or Climatological Runs
- How to have mail of end of Job, on ccrt's machines
-
Set up simulation
First of all see official documentation
Important files
Important files to set up a simulation are:
ORCA2_LIM/IGCM00/config.card
ORCA2_LIM/IGCM00/PARAM/iodef.xml
ORCA2_LIM/IGCM00/COMP/opa9.card
config.card
How to manage job name, start date, end date, and restart files
Here you can find a description of some parts of config.card
In ORCA2_LIM/IGCM00/config.card file
you have to put a JobName maximum of 8 characters
in LongName you can put a comment that can remember to you all properties of the Job.
you have to set duration of your experience and setting PeriodLength parameter, so you manage write output frequency of restart files.
( for example : if you have and experience of 10 years and a PeriodLength of 1 year, you will have 10 restart files )
#-- Début et fin de Job
#-- "YYYY-MM-DD"
DateBegin? =2001-01-01
DateEnd? =2010-12-31
#============================
#-- 1Y, 1M, 5D, 1D
PeriodLength? =1Y
Note : If you want to use restart data from another simulation ( already run not in this moment ) you have to manage "Restarts" part of config.card
How to continue a simulation
see french version : here
If you have finished a previous simulation and now you want to continue it you have to change :
in ORCA2_LIM/IGCM00/config.card you have to set :
new DateEnd?
in ORCA2_LIM/IGCM00/run.card
PeriodDateEnd?
PeriodState? = OnQueue?
How to manage calendar type
in ORCA2_LIM/IGCM00/config.card you have to set CalendarType like 360d or leap or noleap
# for 360d :
you have to be careful at
DateEnd? =2010-12-3 0
because every month has 30 days
If you put for example DateEnd? =2005-12-31, you will have another run, of duration like your PeriodLength
# for noleap :
How to manage rdt ( i.e. timestep )
in ORCA2_LIM/IGCM00/COMP/opa9.driver you have to change parameter : ORCA_NPDT_JOUR=15
( 15 corresponds to 86400s/5760s; it does mean that in one day you have 15 iterations; and it does mean that timestep is 5760)
How to manage monoprocessor or multiprocessor run
From nemo version 3_3 set up and compile a mono-processor run :
./makenemo -m SX8_BRODIE -n ORCA2_LIM
for multiprocessor run see :
parallelpage for nemo version 3_3
( To understand more on mono or multi proc run with nemo till version 3_2_2 see also :
parallelpage till nemo version 3_2_2 )
#-- PBS Class (required ONLY on brodie mono/multi)
JobClass? =mono
#JobClass? =multi
#============================
#-- Total Number of Processors
#JobNumProcTot? =4 (put same number of processors choosen at compiling time, in this example is 4)
JobNumProcTot? =1
#============================
#-- Run Options :
#JobRunOptions? ='"-np "${BATCH_NUM_PROC_TOT}"'
JobRunOptions? =
#============================
How to set Init & Boundary condition's directory
By default R_BC is commented, it does mean that INIT & Boundary files are in common account of IPSL, at IDRIS or CCRT :
#R_BC=/u/rech/psl/rpsl035/IGCM/BC
#R_BC=/dmnfs/cont003/p86ipsl/IGCM/BC
If you want to have you own directory you have to create a directory in wich you have to create OCE/ORCA2_LIM2 directory in which you have to put tar file : http://www.nemo-ocean.eu/Using-NEMO/Configurations/ORCA2_LIM
with all initial files for nemo, and where you have to add your forcing files.
How to restart from another run
In ORCA2_LIM/IGCM00/config.card :
If you want to restart from restart file of experience core260i (corersponding at the Job_core260i) of the year 2007 you have to put:
#================
#D-- Restarts -
[Restarts]
#D- If you want a GENERAL RULE FOR RESTARTS, put this flag to 'y'
OverRule? =y
#D- Last day of the experience used as restart
RestartDate? =2007-12-31
#D- Define restart simulation name
RestartJobName? =core260i
#D- Path Server Group Login
RestartPath? =${ARCHIVE}/IGCM_OUT/ORCA2_LIM2
How to have post treatement
if you want to activate post treatment with libigcm to have monitoring & ATLAS see : postprocessingpage
How to manage write output frequency
in ORCA2_LIM/IGCM00/config.card you have to set WriteFrequency of your experience
You can have multiple frequencies, you need to have a blank between every frequency, for example :
ocean output files every 1 year and 1 month :
#===================
#D-- OCE -
[OCE]
WriteFrequency? ="1Y 1M"
and ice output files every 1 month :
#===================
#D-- ICE -
[ICE]
WriteFrequency? ="1M"
These settings have to be coherents also with path in ORCA2_LIM/IGCM00/COMP/ opa9.card in part :
OutputFiles?
List= (${PREFIX_WF 1 }_grid_T.nc, ${R_OUT_OCE_WF 1 }/${PREFIX}_${WF 1 }_grid_T.nc, NONE),\
(${PREFIX_WF 1 }_grid_U.nc, ${R_OUT_OCE_WF 1 }/${PREFIX}_${WF 1 }_grid_U.nc, NONE),\
(${PREFIX_WF 1 }_grid_V.nc, ${R_OUT_OCE_WF 1 }/${PREFIX}_${WF 1 }_grid_V.nc, NONE),\
(${PREFIX_WF 2 }_grid_T.nc, ${R_OUT_OCE_WF 2 }/${PREFIX}_${WF 2 }_grid_T.nc, NONE),\
(${PREFIX_WF 2 }_grid_U.nc, ${R_OUT_OCE_WF 2 }/${PREFIX}_${WF 2 }_grid_U.nc, NONE),\
(${PREFIX_WF 2 }_grid_V.nc, ${R_OUT_OCE_WF 2 }/${PREFIX}_${WF 2 }_grid_V.nc, NONE),\
You have to put number of frequencies that you put in part [OCE] of config.card (in this case you have 2 frequencies : 1Y 1M)
The same for ice : ORCA2_LIM/IGCM00/COMP/ lim2.card (in this example you have only WF1)
VERY IMPORTANT NOTE : these settings are to be coherents with the ones in iodef.xml see doc : ????? (to add link to seb?)
In iodef.xml you can choose variables that you want to have in output at every frequency
How to manage Interannual or Climatological Runs
in ORCA2_LIM/IGCM00/COMP/opa9.card
You have to set
# Interannual_Run y if you want to do interannual runs or n if you want to do climatological runs
# In [Interannual] section you have to fill List_jobsbc of file names like they appear in namelist.
( for example if you want to do interannual run using clio bulk core you can put :
List_jobsbc=(flx, taux_1m, tauy_1m)
)
How to manage Interannual or Climatological Runs
in ORCA2_LIM/IGCM00/PARAM/namelist
You have to set in "namsbc" part if you want to do climatological run and if you want to do an interpolation :
time interpol. (logical) and clim (T/F)
see : change_BC
How to have mail of end of Job, on ccrt's machines
on mercure: in Job_Name: #PBS -M name@mail
on platine: In Job_Name: #BSUB -u name@mail
Simona Flavoni last update: Timestamp?