@@ -39,7 +39,7 @@ Source code used in the benchmarks (version of June 21, 2021) [./gadget/4.0/gadg
There are two files to obtain from the repository: gadget4.tar.gz and example_ics.tar.gz
gadget4.tar.gz includes the source code, examples, buildsystem, and documentation folders. It also includes Makefile and Makefile.systype (or a template of it)
gadget4.tar.gz includes the source code, examples, buildsystem, and documentation folders. It also includes Makefile and Makefile.systype (or a template)
example_ics.tar.gz includes initial conditions that are needed for each of the examples. When untarred you generate a folder named ExampleICs. You may download the examples initial conditions from (./gadget/4.0/example_ics.tar.gz)
...
...
@@ -63,13 +63,13 @@ where EXEC is the name of the executable.
5. Create a folder named Test-Case-A. Copy gadget4-exe to Test-Case-A. From the examples subfolder CollidingGalaxiesSFR copy the files param.txt and TREECOOL to Test-Case-A.
6. In the folder Test-Case-A modify the first line of param.txt in order to reproduce the path of the initial conditions file ics_collision_g4.dat located in the folder ExampleICs.
6. In the folder Test-Case-A modify param.txt to include the adequate path to the initial confidions file ics_collision_g4.dat located in the folder ExampleICs and modify the memory per core to that of the system you are using.
7. Run the code using mpirun or submit a SLURM script file
7. Run the code using mpirun or submit a SLURM script.
#### Building of the test cases executable.
##### Building of the test cases executable.
1. Download and untar a test case tarball, e.g., gadget4-caseA.tar.gz (see below) and the gadget code used in the benchmarks. The folder gadget4-caseA has the files Config.sh, ics_collision_g4.dat, param.txt, and TREECOOL.
1. Download and untar a test case tarball, e.g., gadget4-caseA.tar.gz (see below) and the gadget code used in the benchmarks. The folder gadget4-caseA has the files Config.sh, ics_collision_g4.dat, param.txt, and TREECOOL. The param.txt file has the path for the initial conditions.
2. Change to the folder named gadget4 and adapt the file Makefile.systype to your needs. Do not forget to adapt also the Makefile, by adding the following lines in 'define available Systems'
...
...
@@ -87,9 +87,9 @@ where XXX = cluster name and BBB= whatever you may want to include here, e.g., i
make CONFIG=../gadget4-caseA/Config.sh EXEC=../gadget4-caseA/gadget4-exe
```
4. Change to folder gadget4-caseA and make sure that the memory size per core is adequate to the system type.
4. Change to folder gadget4-caseA and make sure that in the file param.txt the memory size per core is the correct one for the system you are using.
5.run the code directly with mpirun or submit a script to, e.g., SLURM
5.Run the code directly with mpirun or submit a SLURM script.
### Mechanics of Running Benchmark
...
...
@@ -97,7 +97,7 @@ The general way to run the benchmarks, assuming SLURM Resource/Batch Manager is:
1. Set the environment modules (see Build the Executable section)
2.Submit a script to slurm
2.In the folder of the test cases, e.g., gadget4-caseA, adapt the SLURM script and submit it