Changes between Version 10 and Version 11 of RunningDynamico

Timestamp:

09/17/15 09:52:37 (9 years ago)

Author:

dubos

Comment:

--

RunningDynamico

@@ -6 +6 @@
 You will also need configuration files that define resolution, initial condition, etc. Sample files can be found in subdirectories of [source:codes/icosagcm/trunk/param_sets DYNAMICO/param_sets]. Copy the *.def files from the desired sub-directory. There is typically run.def and earth_const.def . run.def is the main configuration file and includes earth_const.def
 
-Currently DYNAMICO generates its own grid and only runs idealized test cases which define their own initial conditions. No other input files are needed beyond *.def .
+Currently DYNAMICO generates its own grid. It can run idealized test cases which define their own initial conditions. In that case no other input files are needed beyond *.def and,  if using XIOS, *.xml files controlling XIOS behavior. It may also restart from a previous run, reading from a restart file.
+
+
+== Tips and tricks ==
+Make sure you set 
+{{{
+ulimit -s unlimited
+}}}
+before running DYNAMICO in order to avoid stack overflows (segmentation faults) due to large automatic arrays. With OpenMP:
+{{{
+export OMP_STACK_SIZE=100M
+}}}
+or a larger value if necessary.
 
 == Running DYNAMICO as a multilayer shallow-water solver ==
@@ -67 +79 @@
 To run DYNAMICO on a parallel machine, you must first compile it with OpenMPI and/or MPI. Then use mpirun or the equivalent command to run it.
 There must be less MPIxOpenMP processes than the 10 x nsplit_i x nsplit_j tiles. There can be more tiles than processes, in which case each process will take care of several tiles.
-
-== Tips and tricks ==
-It may be useful to set 
-{{{
-ulimit -s unlimited
-}}}
-before running DYNAMICO in order to avoid stack overflows (segmentation faults) due to large automatic arrays. With OpenMP:
-{{{
-export OMP_STACK_SIZE=100M
-}}}
-or a larger value if necessary.