Set up a simulation

First of all see official documentation

​http://forge.ipsl.jussieu.fr/libigcm/wiki/

Important files

Important files to set up a simulation are:
modipsl/config/ORCA2_LIM/IGCM00/config.card
modipsl/config/ORCA2_LIM/IGCM00/PARAM/iodef.xml
modipsl/config/ORCA2_LIM/IGCM00/COMP/opa9.card

config.card : How to manage job name, start date, end date, and restart files

In modipsl/config/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 For example 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 manage write output frequency

in modipsl/config/ORCA2_LIM/IGCM00/config.card you have to set WriteFrequency of your experience

for example : if you want output files every 1 month you have to put for Ocean.

You can have multiple frequencies, you need to have a blank between every frequency

#===================
#D-- OCE -
[OCE]
WriteFrequency?="1Y 1M"

and if you want output files every 1 month you have to put for ICE

#===================
#D-- ICE -
[ICE]
WriteFrequency?="1M"

How to manage calendar type

in modipsl/config/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-30

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 modipsl/config/ORCA2_LIM/IGCM00/COMP/nemo.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 Interannual or Climatological Runs

in modipsl/config/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 modipsl/config/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?