Commit 5b54241d authored by Valeriu Codreanu's avatar Valeriu Codreanu
Browse files

added v1.1 of UEABS

parent 8f86cba9
# Unified European Applications Benchmark Suite, version 1.0
# Unified European Applications Benchmark Suite, version 1.1
The Unified European Application Benchmark Suite (UEABS) is a set of 12 application codes taken from the pre-existing PRACE and DEISA application benchmark suites to form a single suite, with the objective of providing a set of scalable, currently relevant and publically available codes and datasets, of a size which can realistically be run on large systems, and maintained into the future. This work has been undertaken by Task 7.4 "Unified European Applications Benchmark Suite for Tier-0 and Tier-1" in the PRACE Second Implementation Phase (PRACE-2IP) project and will be updated and maintained by subsequent PRACE Implementation Phase projects.
For more details of the codes and datasets, and sample results, please see http://www.prace-ri.eu/IMG/pdf/d7.4_3ip.pdf
Release notes for version 1.1, released on 31st May 2014 as a resut of PRACE-3IP activities.
Changes from version 1.0 are as follows:
ALYA: new version of code and new datasets.
Code_Saturne: additional large dataset, using tetrahedralelements.
CP2K: new build instructions.
GPAW: new dataset with reduced runtime.
The codes composing the UEABS are:
......@@ -222,4 +230,4 @@ In many geological models in the context of seismic wave propagation studies (ex
- Build instructions: http://www.geodynamics.org/wsvn/cig/seismo/3D/SPECFEM3D_GLOBE/trunk/doc/USER_MANUAL/manual_SPECFEM3D_GLOBE.pdf?op=file&rev=0&sc=0
- Test Case A: http://www.prace-ri.eu/UEABS/SPECFEM3D/SPECFEM3D_TestCaseA.tar.gz
- Test Case B: http://www.prace-ri.eu/UEABS/SPECFEM3D/SPECFEM3D_TestCaseA.tar.gz
- Run instructions: https://repository.prace-ri.eu/git/UEABS/ueabs/blob/v1.0/specfem3d/SPECFEM3D_Run_README.txt
\ No newline at end of file
- Run instructions: https://repository.prace-ri.eu/git/UEABS/ueabs/blob/v1.0/specfem3d/SPECFEM3D_Run_README.txt
In order to run ALYA, you need at least the following input files per execution:
X.dom.dat
X.typ.dat
X.geo.dat
X.bcs.dat
X.inflow_profile.bcs
X.ker.dat
X.nsi.dat
X.dat
In our case, there are 2 different inputs, so X={1_1p1mill,3_27p3mill}
To execute a simulation, you must be inside the input directory and you should submit a job like:
mpirun Alya.x 1_1p1mill
or
mpirun Alya.x 3_27p3mill
Data sets
---------
The parameters used in the datasets try to represent at best typical industrial runs in order to obtain representative speedups. For example, the iterative solvers
are never converged to machine accuracy, as the system solution is inside a non-linear loop.
The datasets represent the solution of the cavity flow at Re=100. A small mesh of 10M elements should be used for Tier-1 supercomputers while a 30M element mesh
is specifically designed to run on Tier-0 supercomputers.
However, the number of elements can be multiplied by using the mesh multiplication option in the file *.ker.dat (DIVISION=0,2,3...). The mesh multiplication is
carried out in parallel and the numebr of elements is multiplied by 8 at each of these levels. "0" means no mesh multiplication.
The different datasets are:
cavity10_tetra ... 10M tetrahedra mesh
cavity30_tetra ... 30M tetrahedra mesh
How to execute Alya with a given dataset
----------------------------------------
In order to run ALYA, you need at least the following input files per execution:
X.dom.dat
X.typ.dat
X.geo.dat
X.bcs.dat
X.inflow_profile.bcs
X.ker.dat
X.nsi.dat
X.dat
In our case, there are 2 different inputs, so X={cavity10_tetra,cavity30_tetra}
To execute a simulation, you must be inside the input directory and you should submit a job like:
mpirun Alya.x cavity10_tetra
or
mpirun Alya.x cavity30_tetra
How to measure the speedup
--------------------------
1. Edit the fensap.nsi.cvg file
2. You will see ten rows, each one corresponds to one simulation timestep
3. Go to the second row, it starts with a number 2
4. Get the last number of this row, that corresponds to the elapsed CPU time of this timestep
5. Use this value in order to measure the speedup
Contact
-------
If you have any question regarding the runs, please feel free to contact Guillaume Houzeaux: guillaume.houzeaux@bsc.es
Installation:
-------------
Running a case is described in the following page:
http://www.code-saturne.org
Code_Saturne is open source and the documentation about how to install
it is to be found under http://www.code-saturne.org
Two test cases are available, the former using an hexa-based grid
and the latter a tetra-based grid.
However, the version 3.0.1 has been copied to the current folder.
Running - Test case:
----------------
Running a case is described in the following page: http://www.code-saturne.org
The test case deals with the flow in a bundle of tubes.
Test Case A deals with the flow in a bundle of tubes.
A larger mesh (51M cells) is built from an original mesh of 13M cells.
The original mesh_input file (already preprocessed for Code_Saturne)
......@@ -22,8 +14,9 @@ The user subroutines are under XE6_INTERLAGOS/SRC
The test case has been set up to run for 10 time-steps.
Contact:
--------
Test Case B models a lid-driven cavity and the cells are all tetras.
The total number of cells is about 110M.
The mesh is called mesh_input and the usersubroutines are available under SRC_UEABS
If you have any question, please contact Charles Moulinec (STFC Daresbury Laboratory)
at charles.moulinec@stfc.ac.uk
10 time-steps are run.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment