You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,17 +41,21 @@ To build serial NERDSS, you need:
41
41
- For Ubuntu, install via apt
42
42
3. To compile using make:
43
43
- 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
46
46
47
47
To build parallel NERDSS, you need to checkout to the `mpi` branch:
48
48
49
+
```
50
+
git checkout mpi
51
+
```
52
+
49
53
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`
52
56
2. To compile using make:
53
57
- 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*)
55
59
- The executable will be placed in the ./bin directory
56
60
57
61
### Run Simulations
@@ -62,27 +66,23 @@ Click the following link to make a copy of the iPython notebook in your Google C
62
66
63
67
[](https://colab.research.google.com/github/mjohn218/nerdss_development/blob/master/docs/Run_NERDSS_colab.ipynb?copy=true)
64
68
65
-
#### Run a quick trial with our server
66
-
67
-
Go to the [NERDSS server](http://18.188.233.206:5000/).
68
-
69
69
#### Compile and run NERDSS on your local machine
70
70
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.
72
72
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`.
74
74
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`.
76
76
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`.
78
78
79
79
### Analyzing Results
80
80
81
81
1. Use the ioNERDSS PyPi library for visualizing simulation results.
82
82
2. Install ioNERDSS with *pip install ioNERDSS*.
83
83
3. Refer to the [ionerdss repository](https://github.com/JohnsonBiophysicsLab/ionerdss) for more details.
84
84
85
-
### Best Practices for Developers
85
+
### Style Guides for Developers
86
86
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