Commit 98081e3b authored by Simon Spannagel's avatar Simon Spannagel
Browse files


parent e6570b36
Pipeline #285398 passed with stages
in 12 minutes and 43 seconds
# How to contribute
Thanks for considering to contribute to Corryvreckan. Any type of merge request, ranging from small bugfixes, improvements to the documentation to entirely new functionality, is much appreciated. We, the maintainers, will try to our best to look carefully at every merge request.
If you only want to submit an issue, that is also very welcome, please continue directly to the [issue tracker]( to open a ticket.
The following is a set of guidelines that will help both you as submitter as well as us maintainers to make it as easy as possible to contribute changes.
## Getting started
Please follow the next steps to setup your system for contributing. Note that these are slightly different from the normal installation instructions in the manual.
1. Make sure you have an account on [Gitlab]( (restricted to CERN associates).
2. Fork the repository by clicking on 'Fork' on the main [repository](
3. Clone your local fork using `git clone` (when using HTTPS, this has to be changed accordingly for SSH or KRB5)
4. Install the latest version of the *clang* package with the *clang-format* and *clang-tidy* programs.
5. Follow the build instructions using CMake explained in the User's manual.
## Making changes
Now you can start making changes and adding new functionality to the code.
1. Run `etc/git-hooks/` from the repository top folder to install the git-hook that automatically updates the format of the code to comply with the coding style.
2. Create a new branch from master with a description of the change using `git checkout -b my-new-branch-name`.
3. Read the relevant sections in the User's manual before starting to make changes.
4. Implement the new code and frequently commit using `git commit -m 'my commit message'`. Please use descriptive messages explaining what changed.
5. Push the code to your local mirror using `git push --set-upstream origin`.
6. Retrieve the latest changes to the upstream master every now and then. To do this add the upstream version to your remotes using `git remote add upstream` (or the SSH or KRB5 version if preferred). This only has to be done once, the first time after cloning the repository. Afterwards you fetch the changes using `git fetch upstream`. Then you can add the change preferably using rebase with `git rebase upstream master`. If that causes problems you can use merge with `git merge upstream master`.
## Submitting a pull request
As soon as there exists something in your branch, a merge request can be opened on the main repository. Do not forget that it is not a problem to open a merge request for incomplete implementations.
1. Retrieve the latest changes from the upstream version as explained above.
2. Optionally format the code if you did not add the git-hook from the beginning, this can be done manually by running `make format` from the build directory.
3. Go to [merge request]( and click on 'New merge request'.
4. Follow the instructions. Do not forget to use the 'WIP:' prefix if your code is only partially ready. Then submit the merge request.
5. Please wait for the maintainers to give you access to the continuous integration (CI) runners that will check your code if you do not already have it.
6. Add all the specific runners on your local repository at
7. The pipeline can now be restarted and the CI will check your changes. If the CI fails and gives an error please refer to the log containing a description about what went wrong. It is very likely that errors will appear because Corryvreckan enforces a very strict policy of compiler errors and requires full compliance of the clang-tidy 'linter' tool, which frequently complains about minor changes (it might help to search for `error:` to find the actual error(s) in the output). This clang-tidy tool can also be run locally on your pc by executing `make check-lint` from the build directory. Easy changes can be fixed automatically by executing `make lint`.
8. The maintainers will look at your proposed changes and likely provide some (constructive) feedback.
9. Please continue to update the code with the received comments until every reviewer and the continuous integration is happy :)
10. Your merge request can now be merged in. Congratulations and thank you very much, you have contributed something new to the repository!
# Corryvreckan
### The Maelstrom for Your Test Beam Data
[![build status](](
## Dependencies
* [ROOT]( (required, with the GenVector component)
## Installation
The CMake build system is used for compilation and installation. The install directory can be specified by adding `-DCMAKE_INSTALL_PREFIX=<prefix>` as argument to the CMake command below. Other configuration options are explained in the manual.
The dependencies need to be initialized for the build to succeed.
### Compilation
To compile and install a default installation of Corryvreckan, run the following commands
$ mkdir build && cd build/
$ cmake ..
$ make install
For more detailed installation instructions, please refer to the documentation below.
## Documentation
The latest PDF version of the User Manual can be created from source by executing
$ make pdf
After running the manual is available under `usermanual/corryvreckan-manual.pdf` in the build directory.
To build the HTML version of the latest Doxygen reference, run the following command
$ make reference
The main page of the reference can then be found at `reference/html/index.html` in the build folder.
## Development of Corryvreckan
Corryvreckan has been developed and is maintained by
* Morag Williams, University of Glasgow/CERN, @williamm
* Daniel Hynds, CERN, @dhynds
* Simon Spannagel, CERN, @simonspa
The following authors, in alphabetical order, have contributed to Corryvreckan:
* Matthew Daniel Buckland, University of Glasgow, @mbucklan
* Adrian Fiergolski, CERN, @afiergol
* Andreas Matthias Nürnberg, CERN, @nurnberg
* Florian Pitters, CERN, @fpipper
## Contributing
All types of contributions, being it minor and major, are very welcome. Please refer to our [contribution guidelines]( for a description on how to get started.
Before adding changes it is very much recommended to carefully read through the documentation in the User Manual first.
## Licenses
This software is distributed under the terms of the MIT license. A copy of this license can be found in [](
The documentation is distributed under the terms of the CC-BY-4.0 license. This license can be found in [doc/](doc/
The LaTeX and Pandoc CMake modules used by Corryvreckan are licensed under the BSD 3-Clause License.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment