Skip to content

Commit 5d7bf48

Browse files
Update README.md
1 parent 12b8d8b commit 5d7bf48

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

README.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -41,17 +41,21 @@ To build serial NERDSS, you need:
4141
- For Ubuntu, install via apt
4242
3. To compile using make:
4343
- Navigate to the main directory
44-
- Run *make serial*
45-
- The executable will be placed in the *./bin* directory
44+
- Run `make serial`
45+
- The executable will be placed in the `./bin` directory
4646

4747
To build parallel NERDSS, you need to checkout to the `mpi` branch:
4848

49+
```
50+
git checkout mpi
51+
```
52+
4953
1. MPI:
50-
- For macOS, install OpenMPI with Homebrew: *brew install open-mpi*
51-
- For Ubuntu, install OpenMPI through apt: *sudo apt install openmpi-bin libopenmpi-dev*
54+
- For macOS, install OpenMPI with Homebrew: `brew install open-mpi`
55+
- For Ubuntu, install OpenMPI through apt: `sudo apt install openmpi-bin libopenmpi-dev`
5256
2. To compile using make:
5357
- Navigate to the main directory
54-
- Run *make mpi* (with profiling support: *make mpi ENABLE_PROFILING=1*)
58+
- Run `make mpi` (with profiling support: *make mpi ENABLE_PROFILING=1*)
5559
- The executable will be placed in the ./bin directory
5660

5761
### Run Simulations
@@ -62,27 +66,23 @@ Click the following link to make a copy of the iPython notebook in your Google C
6266

6367
[![Open in Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/mjohn218/nerdss_development/blob/master/docs/Run_NERDSS_colab.ipynb?copy=true)
6468

65-
#### Run a quick trial with our server
66-
67-
Go to the [NERDSS server](http://18.188.233.206:5000/).
68-
6969
#### Compile and run NERDSS on your local machine
7070

71-
1. Example input files are located in the subdirectories within the *sample_inputs* folder. They can also be generated using the [python GUI program](./gui.py), which is also included in the ioNERDSS tool.
71+
1. Example input files are located in the subdirectories within the `sample_inputs` folder.
7272

73-
2. To start the serial simulation, use the command *./nerdss -f parms.inp*.
73+
2. To start the serial simulation, use the command `./nerdss -f parms.inp`.
7474

75-
3. To start the parallel simulation, use the command *mpirun -np $nprocs ./nerdss_mpi -f parms.inp*.
75+
3. To start the parallel simulation, use the command `mpirun -np $nprocs ./nerdss_mpi -f parms.inp`.
7676

77-
4. To debug the parallel code, use the command *mpirun -np 2 xterm -e gdb --ex 'b error' --ex r --args ./nerdss_mpi -f parms.inp -s 123*.
77+
4. To debug the parallel code, use the command `mpirun -np 2 xterm -e gdb --ex 'b error' --ex r --args ./nerdss_mpi -f parms.inp -s 123`.
7878

7979
### Analyzing Results
8080

8181
1. Use the ioNERDSS PyPi library for visualizing simulation results.
8282
2. Install ioNERDSS with *pip install ioNERDSS*.
8383
3. Refer to the [ionerdss repository](https://github.com/JohnsonBiophysicsLab/ionerdss) for more details.
8484

85-
### Best Practices for Developers
85+
### Style Guides for Developers
8686

87-
1. Choose meaningful names for variables, functions, and classes. Comment on complex logic, and maintain consistent indentation and formatting. Use CamelCase for variables, snake_case for functions, and PascalCase for classes. Avoid global variables.
88-
2. Follow the Google C++ Style Guide and the C++ Core Guidelines. Prefer using the C++ Standard Library and modern C++ features. Provide comments and documentation to explain complex or non-obvious code sections. Write unit tests to ensure code quality.
87+
1. We use the Google C++ Style Guide and the C++ Core Guidelines and prefer the C++ Standard Library and modern C++ features.
88+
2. Provide comments and documentation to explain complex or non-obvious code sections. Write unit tests to ensure code quality.

0 commit comments

Comments
 (0)