Microsoft Word Page cronos gb doc

Figure 1: CRONOS software environment (use of the GSL library is planned instead of or as well as the NAG 
library, the MATLAB Java API could be useful for accessing some databases or creating a Web interface for 
CRONOS) 
 
 
CRONOS (figures 1 and 2) is available for alpha processor machines running under 
“OSF true 64”, on X86 (and shortly X86-64) machines under Linux (PC, JAC and PC farm). 

---

- 2 - 
For the compilation, CRONOS requires a development environment: MATLAB, NAG, 
LAPACK, BLAS, C and C++, FORTRAN (77 & 90) compiler. Under OSF, the FORTRAN 
used is the native FORTRAN of the machine. Under Linux, we use the “Portland” compilers 
(including the FORTRAN compiler). 
CRONOS is generally used via the graphic interface. This enables the user to perform 
the following: 
1. Prepare the data sets, either by connecting to the databases (TS, JET, FTU, TCV, ITPA 
DIII-D international database), or by preparing a data set from scratch (useful for future 
machines such as ITER or DEMO, or machines for which direct access to the data is not 
possible), or based on a CRONOS file corresponding to a previous simulation. 
2. Edit and modify the parameters and data in a data set. It is also possible to modify the 
parameters in command lines without using the interface (including the SIMULINK 
functional diagrams). 
3. Carry out an interactive or “batch” run of a CRONOS “case”. 
4. Display the data using pre-provided functions, a generic display tool (zdataplot) or creating 
one’s own diagrams (with MATLAB language graphic tools). 
5. Manipulate the data sets (modification of the version, the time base, the number of radial 
points, data import/export, manipulation of SIMULINK functional diagrams) 
6. Launch post-processes for calculating data as produced by the diagnostics. 
7. Launch “wizards”. The wizards are fast computer codes used to check the coherence of the 
data, adjust the modules or develop scenarios. 
8. Manage the access paths and generate the dynamic code and online help.
9. Certify a CRONOS version (partly functional: verification of the syntax of “mfiles”, 
detection of any change of source file, testing of standard cases and comparison of the 
results). 
It is also possible to handle the data directly in the MATLAB workspace. 
The CRONOS core is modular, in the sense that the source modules, the transport 
coefficients, and the equilibrium, MHD stability, and neoclassical calculation modules, are 
defined at graphic interface level and dynamically linked to the CRONOS computer code (see 
figure 3). Each user can add modules directly (placing the modules in his environment) or 
modify any CRONOS function or module. 

---

- 3 -