Code_Saturne v7.0.2
Running the application
The GUI of Code_Saturne v7.0.2 can be launched by typing:
code_saturne gui setup.xml "or" ./code_saturne setup.xml
in the DATA directory.
Note: You need to ensure you have connected to the CSF with X-forwarding enabled (e.g. ssh -X). For more information on how to do this please see the Logging in to use GUI apps documentation.
Further information and available options can be found after executing
code_saturne --help
Once you have set up your study/case file structure, you will need to edit the “runcfg” file for submission to the queue.
Follow the guidelines on https://ri.itservices.manchester.ac.uk/csf3/batch/parallel-jobs/ as to what flags and what parallel environment you should use. The recommended ones are:
* smp.pe (for 2 to 32 cores)
* mpi-24-ib.pe (for 48 cores or more in multiples of 24)
After editing the “runcfg” you can submit it by typing:
code_saturne submit
Note: It is highly recommended that if you are using any user subroutine, do a test compilation before submitting by typing:
code_saturne compile
The DEBUG version of the code has been installed which it allows to use a debugger to trace back of any errors and memory leaks. In order to view the available options of the gdb debugger, add the
-h
or
--help
flag, i.e.:
gdb -h
In order to find more information of a potential error in either the setup or the routines prepared for the case, the following commands need to be executed in the failed directory “RESU/YYYY-MM-DD-HH-MM”:
gdb cs_solver run
backtrace
To exit the debugger:
quit
In addition to run the gdb debugger, some hints about the error or the reason for the case failure can be extracted by calling the”addr2line” utility in the failed run directory:
addr2line -e ./cs_solver 0x400819
where 0x400819 is an example of an address in the call stack.
Further info
NB: A tutorial on how to run Code_Saturne on CSF3 is made available in:
/opt/apps/apps/intel-18.0/Code_Saturne/code_saturne_training_csf3.tar.gz