Changes between Version 10 and Version 11 of Doc/Models/DYNAMICO

Timestamp:

03/13/24 16:32:01 (3 months ago)

Author:

falletti

Comment:

--

Doc/Models/DYNAMICO

@@ -15 +15 @@
 The latest version is accessible through svn :
 {{{
-svn co http://forge.ipsl.jussieu.fr/dynamico/svn/codes/icosagcm/trunk
+svn co http://forge.ipsl.fr/dynamico/svn/codes/icosagcm/trunk
 }}}
 
 Registered IPSL forge users belonging to the DYNAMICO group can do :
 {{{
-svn co svn+ssh://mylogin@forge.ipsl.jussieu.fr/ipsl/forge/projets/dynamico/svn/codes/icosagcm/trunk DYNAMICO
+svn co svn+ssh://mylogin@forge.ipsl.fr/ipsl/forge/projets/dynamico/svn/codes/icosagcm/trunk DYNAMICO
 }}}
 
 'mylogin' should be your forge login. svn will create the DYNAMICO directory and download the source code there.
-Source can also been browsed at https://forge.ipsl.jussieu.fr/dynamico/browser/codes/icosagcm/trunk
+Source can also been browsed at https://forge.ipsl.fr/dynamico/browser/codes/icosagcm/trunk
 
 # Compiling DYNAMICO #
@@ -32 +32 @@
 DYNAMICO depends on the NetCDF and BLAS libraries.
 
-The compiling process is automated but some information is needed to guide it. This information is contained in text files in https://forge.ipsl.jussieu.fr/dynamico/browser/codes/icosagcm/trunk/arch . Sample files corresponding to a few machines (Jean-Zay at IDRIS, Irène at TGCC) are present. Assuming you compile on Irène :
+The compiling process is automated but some information is needed to guide it. This information is contained in text files in https://forge.ipsl.fr/dynamico/browser/codes/icosagcm/trunk/arch . Sample files corresponding to a few machines (Jean-Zay at IDRIS, Irène at TGCC) are present. Assuming you compile on Irène :
 
 {{{
@@ -50 +50 @@
 == Compiling with XIOS output ==
 
-DYNAMICO can direct its output through XIOS, a parallel I/O library and server. See https://forge.ipsl.jussieu.fr/ioserver.
+DYNAMICO can direct its output through XIOS, a parallel I/O library and server. See https://forge.ipsl.fr/ioserver.
 To enable XIOS output :
  * get and compile XIOS in a separate directory
@@ -57 +57 @@
 Why use XIOS :
  * without XIOS, each output field is written to a separate NetCDF file. Post-processing is required to group several fields together.
- * with XIOS, several fields can be written to a few output files. This behavior is controlled by the input file xios.xml (required). See https://forge.ipsl.jussieu.fr/ioserver for the syntax of this XML file.
+ * with XIOS, several fields can be written to a few output files. This behavior is controlled by the input file xios.xml (required). See https://forge.ipsl.fr/ioserver for the syntax of this XML file.
  * without XIOS, data to be written is communicated to the main MPI process, which writes to the NetCDF files while other MPI processes stay idle. This is not expected to scale to a large number of MPI processes. 
  * XIOS provides asynchronous, parallel I/O in order to scale to large MPI process counts.
@@ -66 +66 @@
 In this directory, copy the executable icosa_gcm.exe. You will find it in DYNAMICO/bin/, where DYNAMICO is the main directory containing the source code.
 
-You will also need configuration files that define resolution, initial condition, etc. Sample files can be found in subdirectories of [https://forge.ipsl.jussieu.fr/dynamico/browser/codes/icosagcm/trunk/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
+You will also need configuration files that define resolution, initial condition, etc. Sample files can be found in subdirectories of [https://forge.ipsl.fr/dynamico/browser/codes/icosagcm/trunk/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. 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.