Changes between Version 18 and Version 19 of user/flavoni/libIGCM/setupsimupage

Timestamp:

2010-04-21T15:35:45+02:00 (14 years ago)

Author:

flavoni

Comment:

--

user/flavoni/libIGCM/setupsimupage

@@ -17 +17 @@
  === 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 modipsl/config/ORCA2_LIM/IGCM00/'''config.card''' file  [[BR]]
  you have to put a '''!JobName''' maximum of 8 characters [[BR]]
@@ -34 +36 @@
 
  '''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:  
 
- #================ [[BR]]
- #D-- Restarts -[[BR]]
- [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 monoprocessor or multiprocessor run ===
 
+ to understand more see also : [https://forge.ipsl.jussieu.fr/nemo/wiki/private/libIGCM/parallelpage]
 
+ #-- PBS Class (required ONLY on brodie mono/multi)
+ JobClass=mono
+ #JobClass=multi
+ #============================
+ #-- Total Number of Processors 
+ #JobNumProcTot=4
+ JobNumProcTot=1
+ #============================
+ #-- Run Options : 
+ #JobRunOptions='"-np "${BATCH_NUM_PROC_TOT}"'
+ JobRunOptions=''
+ #============================
  
+ === 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-3'''0''' [[BR]]
+
+ 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 write output frequency ===
 
@@ -72 +99 @@
 
 
- === How to manage calendar type ===
+ === How to restart from another run ===
 
- in modipsl/config/ORCA2_LIM/IGCM00/config.card you have to set !CalendarType  like 360d or leap or noleap 
+ If you want to restart from restart file of experience core260i (corersponding at the Job_core260i) of the year 2007 you have to put:  
 
- # for '''360d''' :
- 
- you have to be careful at
+ #================ [[BR]]
+ #D-- Restarts -[[BR]]
+ [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
 
- DateEnd=2010-12-3'''0''' [[BR]]
-
- 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 ===