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
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
|
# Contributing to the NMODL Framework
We would love for you to contribute to the NMODL Framework and help make it better than it is today. As a
contributor, here are the guidelines we would like you to follow:
- [Question or Problem?](#question)
- [Issues and Bugs](#issue)
- [Feature Requests](#feature)
- [Submission Guidelines](#submit)
- [Development Conventions](#devconv)
## <a name="question"></a> Got a Question?
Please do not hesitate to raise an issue on [github project page][github].
## <a name="issue"></a> Found a Bug?
If you find a bug in the source code, you can help us by [submitting an issue](#submit-issue) to our [GitHub Repository][github]. Even better, you can [submit a Pull Request](#submit-pr) with a fix.
## <a name="feature"></a> Missing a Feature?
You can *request* a new feature by [submitting an issue](#submit-issue) to our GitHub Repository. If you would like to *implement* a new feature, please submit an issue with a proposal for your work first, to be sure that we can use it.
Please consider what kind of change it is:
* For a **Major Feature**, first open an issue and outline your proposal so that it can be
discussed. This will also allow us to better coordinate our efforts, prevent duplication of work,
and help you to craft the change so that it is successfully accepted into the project.
* **Small Features** can be crafted and directly [submitted as a Pull Request](#submit-pr).
## <a name="submit"></a> Submission Guidelines
### <a name="submit-issue"></a> Submitting an Issue
Before you submit an issue, please search the issue tracker, maybe an issue for your problem already exists and the
discussion might inform you of workarounds readily available.
We want to fix all the issues as soon as possible, but before fixing a bug we need to reproduce and confirm it. In order to reproduce bugs we will need as much information as possible, and preferably a sample MOD file or Python example.
### <a name="submit-pr"></a> Submitting a Pull Request (PR)
When you wish to contribute to the code base, please consider the following guidelines:
* Make a [fork](https://guides.github.com/activities/forking/) of this repository.
* Make your changes in your fork, in a new git branch:
```shell
git checkout -b my-fix-branch master
```
* Create your patch, **including appropriate test cases**.
* Enable `NMODL_TEST_FORMATTING` CMake variable
to ensure that your change follows the coding conventions of this project when running the tests.
The formatting utility can also be used directly:
* to format CMake and C++ files: `cmake/hpc-coding-conventions/bin/format`
* to format only the C++ files: `cmake/hpc-coding-conventions/bin/format --lang c++`
* to format a subset of files or directories: `cmake/hpc-coding-conventions/bin/format src/codegen/ src/main.cpp`
* to check the formatting of CMake files: `cmake/hpc-coding-conventions/bin/format --dry-run --lang cmake`
* Run the full test suite, and ensure that all tests pass.
* Commit your changes using a descriptive commit message.
```shell
git commit -a
```
* Push your branch to GitHub:
```shell
git push origin my-fix-branch
```
* In GitHub, send a Pull Request to the `master` branch of the upstream repository of the relevant component.
* If we suggest changes then:
* Make the required updates.
* Re-run the test suites to ensure tests are still passing.
* Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
```shell
git rebase master -i
git push -f
```
That’s it! Thank you for your contribution!
#### After your pull request is merged
After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream)
repository:
* Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
```shell
git push origin --delete my-fix-branch
```
* Check out the master branch:
```shell
git checkout master -f
```
* Delete the local branch:
```shell
git branch -D my-fix-branch
```
* Update your master with the latest upstream version:
```shell
git pull --ff upstream master
```
[github]: https://github.com/BlueBrain/nmodl
## <a name="devconv"></a> Development Conventions
If you are developing NMODL, make sure to enable both `NMODL_FORMATTING` and `NMODL_PRECOMMIT`
CMake variables to ensure that your contributions follow the coding conventions of this project:
```cmake
cmake -DNMODL_FORMATTING:BOOL=ON -DNMODL_PRECOMMIT:BOOL=ON <path>
```
The first variable provides the following additional targets to format
C, C++, and CMake files:
```
make clang-format cmake-format
```
The second option activates Git hooks that will discard commits that
do not comply with coding conventions of this project. These 2 CMake variables require additional utilities:
* [ClangFormat 7](https://releases.llvm.org/7.0.0/tools/clang/docs/ClangFormat.html)
* [cmake-format](https://github.com/cheshirekow/cmake_format)
* [pre-commit](https://pre-commit.com/)
clang-format can be installed on Linux thanks
to [LLVM apt page](http://apt.llvm.org/). On MacOS, you can simply install llvm with brew:
`brew install llvm`.
_cmake-format_ and _pre-commit_ utilities can be installed with *pip*.
### Validate the Python package
You may run the Python test-suites if your contribution has an impact
on the Python API:
1. setup a sandbox environment with either _virtualenv_,
_pyenv_, or _pipenv_. For instance with _virtualenv_:
`python -m venv .venv && source .venv/bin/activate`
1. build the Python package with the command: `python setup.py build`
1. install _pytest_ Python package: `pip install pytest`
1. execute the unit-tests: `pytest`
### Memory Leaks and clang-tidy
If you want to test for memory leaks, do :
```
valgrind --leak-check=full --track-origins=yes ./bin/nmodl_lexer
```
Or using CTest as:
```
ctest -T memcheck
```
If you want to enable `clang-tidy` checks with CMake, make sure to have `CMake >= 3.15` and use following cmake option:
```
cmake .. -DENABLE_CLANG_TIDY=ON
```
|
