Newer
Older
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
Description:
============
Presentation
------------
This template is just here to show the way that we should present the README for a given application.
Here I describe that this template is not performing any scientific simulation, and uses no specific library.
Technical information:
----------------------
* website : http://this.url.doesnot.work
* Scientific domain : none
* Language : C/C++/Fortran/Python
* Parallelism : MPI + OpenMP
* GPU acceleration : Yes (CUDA)
* Scalability : high
* Vectorization: poor
Compilation and simulation:
===========================
Here we describe the different phases from the download to the validation of the simulation.
Download:
---------
Information (if needed) about how to get the sources.
For instance:
```
./download.sh
```
Compile:
--------
Information (if needed) about how to compile the application.
For instance:
Compile the code using:
```
source machines/occigen-bdw/env
./compile.sh
```
`machines/occigen-bdw/env` contains the information for compilation (module load gcc openmpi lapack hdf5 ...)
Run and validate the simulation:
--------------------------------
For each test case, given in a separate folder (e.g. testcase_small), you can find three scripts:
* prepare.sh: prepare the simulation (move data to the right location, recompile some minor changes, ...)
* run.sh : run the application and print out the evaluated metric
* validate.sh: validation of the simulation on a scientific point of view
For running and validating the simulation, one should be able to do:
```
cd testcase_XXX
./prepare.sh
./run.sh
./validate.sh
```
And getting no error code returned.
Those steps can also be used in a batch file for running the simulation using a job scheduler.