@@ -82,17 +82,17 @@ where EXEC is the name of the executable.
##### Building a Test Case Executable | Case A
1. Download and untar a test case tarball, e.g., `gadget4-case-A.tar.gz` (see below) and the source code used in the benchmarks named `gadget4-benchmarks.tar.gz`. The folder gadget4-case-A has the files Config.sh, ics_collision_g4.dat, param.txt, and TREECOOL. The param.txt file has the path for the initial conditions and was adapted for a system with 2.0 GB RAM per core, in effect 1.8 GB.
1. Download and untar a test case tarball, e.g., [gadget4-case-A.tar.gz](./gadget/4.0/gadget4-case-A.tar.gz)(see below) and the source code used in the benchmarks named [gadget4-benchmarks.tar.gz](./gadget/4.0/gadget4-benchmarks.tar.gz). The folder `gadget4-case-A` has the files **Config.sh**, **ics_collision_g4.dat**, **param.txt**, **TREECOOL**, and **slurm_script.sh**. The **param.txt** file has the path for the initial conditions and was adapted for a system with 2.0 GB RAM per core, in effect 1.8 GB.
2. Change to the folder named gadget4-benchmarks and adapt the file Makefile.systype and Makefile to your needs. Follow instructions 1a), 1b) or 1c) in Section "General Building of the Executable".
2. Change to the folder named `gadget4-benchmarks` and adapt the file **Makefile.systype** and **Makefile** to your needs. Follow instructions 1a), 1b) or 1c) in Section "General Building of the Executable".
3. Compile the code using the Config.sh file in gadget4-case-A
3. Compile the code using the **Config.sh** file in `gadget4-case-A`
```
make CONFIG=../gadget4-case-A/Config.sh EXEC=../gadget4-case-A/gadget4-exe
```
4. Change to folder gadget4-case-A and make sure that the file param.txt has the correct memory size per core for the system you are using.
4. Change to folder `gadget4-case-A` and make sure that the file **param.txt** has the correct memory size per core for the system you are using.
5. Run the code directly with mpirun or submit a SLURM script.
