README.md 1.65 KB
Newer Older
cpenadep's avatar
cpenadep committed
# Nemo modelfactors

sparonuz's avatar
sparonuz committed
This project is intended to compute important performance metrics for a NEMO run.
cpenadep's avatar
cpenadep committed

sparonuz's avatar
sparonuz committed
The statistic produced is focusing on the timestep loop, so these numbers are not related to the initialization and finalization parts.
cpenadep's avatar
cpenadep committed

# Installation and requeriments
cpenadep's avatar
cpenadep committed

sparonuz's avatar
sparonuz committed
This script relies on the following tools:
cpenadep's avatar
cpenadep committed
 
cpenadep's avatar
cpenadep committed
* *Extrae (4.0.0 or above)* 
* *Paraver*
cpenadep's avatar
cpenadep committed
* *Dimemas (latest has a bug use 5.4.2-devel instead)* 
cpenadep's avatar
cpenadep committed
* *Basicanalysis* 
cpenadep's avatar
cpenadep committed

sparonuz's avatar
sparonuz committed
*They can be downloaded at https://tools.bsc.es/downloads* and need to be installed, loaded and available through the PATH environment variable.
cpenadep's avatar
cpenadep committed

sparonuz's avatar
sparonuz committed
Here the list of the modules that need to be loaded before the script execution.
* Perl interpreter.
* Fortran compiler (ifort, gfortran, pgfortran, ftn, …),
* Message Passing Interface (MPI) implementation (e.g. OpenMPI or MPICH).
* Network Common Data Form (NetCDF) library with its underlying Hierarchical Data Form (HDF).
* Copy all the content of this folder into the folder with the input data for NEMO.
* Edit the file perf_metrics.config and replace the parameters values with the suited information. 
cpenadep's avatar
cpenadep committed
* MINIMUM CHANGES perf_metrics.config :
	* Nemo_path, change the value to the path were NEMO is installed in your machine.
	* Compilation_arch, replace the value with the name of the arch file that you use to compile NEMO.
	* Modules, change the value to suit the name of the modules you need to load.
	* Jobs_scheduler, replace the value with the name of the scheduler installed in your machine (currently supports slurm, lsf and torque)
* Execute perf_metrics.bash
./perf_metrics.bash
sparonuz's avatar
sparonuz committed
* If the script executes without problems the data will be ready in the Metrics folder.