openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro humble. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro jazzy. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro kilted. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro rolling. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd SQLiteCpp

Repository Summary

Description	The codebase of the OpenMS project
Checkout URI	https://github.com/openms/openms.git
VCS Type	git
VCS Version	develop
Last Updated	2025-08-14
Dev Status	UNKNOWN
Released	UNRELEASED
Tags	windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
SQLiteCpp	3.3.3

README

------------------------------
--     OpenMS library       --
------------------------------


This directory contains the source code of OpenMS.
License information can be found in the License.txt file.

If you downloaded a stable release, detailed installation
instructions and other information can be found in the 
documentation (doc/index.html).

If this is a development version obtained via git or as a
nightly snapshot, the documentation is not contained in
this package. Please refer to the OpenMS website for 
installation instructions.

------------------------------
--       TOPP tools         --
------------------------------

In addition to the OpenMS library 'The OpenMS 
PiPeline' (TOPP) is also included in this package.
The installation instructions for OpenMS also 
contain installation instructions for TOPP!

------------------------------
--      Contributing       --
------------------------------

If you would like to contribute to OpenMS, this is how 
to best get started: 

- Familiarize yourself with our online documentation, 
  available at http://www.openms.de/current_doxygen/html/

- Learn how to build OpenMS (by reading the building 
  instructions at the online documentation)

- Start reading the OpenMS tutorial for developers at 
  http://www.openms.de/current_doxygen/html/OpenMS_tutorial.html

- Any questions can be directed at the mailing list, 
  see http://openms.de/support for up-to-date information
  about how to contact the OpenMS developers.

CONTRIBUTING

Help us to make OpenMS better and become part of the OpenMS open-source community.

This document is displayed because you either opened an issue or you want to provide your code as a pull request for inclusion into OpenMS. Please take a look at the appropriate section below to find some details on how we handle this process. When interacting with other developers, users or anyone else from our community, please adhere to our CODE OF CONDUCT

Reporting an Issue:

You most likely came here to:

report bugs or annoyances
pose questions
point out missing documentation
request new features

To do so, open a new issue describing the bug, your question, etc.

If you found a bug, e.g. an OpenMS tool crashes during data processing, it is essential to provide some basic information:

the OpenMS version you are running
the platform you are running OpenMS on (Windows 10, …)
how you installed OpenMS (e.g., from within KNIME, binary installers, self compiled)
a description on how to reproduce the bug
relevant tool output (e.g., error messages)
data to repoduce the bug (If possible as a GitHub gist. Other platforms like Dropbox, Google Drive links also work. If you can’t share the data publicly please indicate this and we will contact you in private.)

If you are an official OpenMS team member:

label your issue using github labels (e.g. as: question, defect) that indicate the type of issue and which components of OpenMS (blue labels) are affected. The severity is usually assigned by OpenMS maintainers and used internally to e.g. indicate if a bug is a blocker for a new release.

Opening a Pull Request

Before getting started we recommend taking a look at our GitHub-Wiki: https://github.com/OpenMS/OpenMS/wiki#-for-developers

Before you open the pull request, make sure you

adhere to our coding conventions
have unit tests and functional tests - see also this example
Have proper documentation - see also this example
have Python bindings - see also these instructions and this example

A core developer will review your changes to the main development branch (develop) and approve them (or ask for modifications). You may indicate the prefered reviewer(s) by adding links to them in a comment section (e.g., @cbielow @hendrikweisser @hroest @jpfeuffer @timosachsenberg)

Also consider getting in contact with the core developers early. They might provide additional guidance and valuable information on how your specific aim is achieved. This might give you a head start in, for example, developing novel tools or algorithms.

Happy coding!

Help us to make OpenMS better and become part of the OpenMS open-source community. This document is displayed because you either opened an issue or you want to provide your code as a pull request for inclusion into OpenMS. Please take a look at the appropriate section below to find some details on how we handle this process. When interacting with other developers, users or anyone else from our community, please adhere to [our CODE OF CONDUCT](https://github.com/OpenMS/OpenMS/blob/develop/CODE_OF_CONDUCT.md) # Reporting an Issue: You most likely came here to: - report bugs or annoyances - pose questions - point out missing documentation - request new features To do so, open a [new issue](https://github.com/OpenMS/OpenMS/issues/new/choose) describing the bug, your question, etc. If you found a bug, e.g. an OpenMS tool crashes during data processing, it is essential to provide some basic information: - the OpenMS version you are running - the platform you are running OpenMS on (Windows 10, ...) - how you installed OpenMS (e.g., from within KNIME, binary installers, self compiled) - a description on how to reproduce the bug - relevant tool output (e.g., error messages) - data to repoduce the bug (If possible as a GitHub gist. Other platforms like Dropbox, Google Drive links also work. If you can't share the data publicly please indicate this and we will contact you in private.) If you are an official OpenMS team member: - label your issue using github labels (e.g. as: question, defect) that indicate the type of issue and which components of OpenMS (blue labels) are affected. The severity is usually assigned by OpenMS maintainers and used internally to e.g. indicate if a bug is a blocker for a new release. # Opening a Pull Request Before getting started we recommend taking a look at our GitHub-Wiki: https://github.com/OpenMS/OpenMS/wiki#-for-developers Before you open the pull request, make sure you - adhere to [our coding conventions](https://github.com/OpenMS/OpenMS/wiki/Coding-conventions) - have [unit tests and functional tests](https://github.com/OpenMS/OpenMS/wiki/Write-tests) - see also [this example](https://github.com/OpenMS/OpenMS/blob/develop/src/tests/class_tests/openms/source/MSNumpressCoder_test.cpp) - Have [proper documentation](https://github.com/OpenMS/OpenMS/wiki/Coding-conventions#doxygen) - see also [this example](https://github.com/OpenMS/OpenMS/blob/develop/src/openms/include/OpenMS/FORMAT/MSNumpressCoder.h) - have [Python bindings](https://pyopenms.readthedocs.io/en/latest/wrap_classes.html) - see also [these instructions](https://github.com/OpenMS/OpenMS/wiki/pyOpenMS#wrap) and [this example](https://github.com/OpenMS/OpenMS/blob/develop/src/pyOpenMS/pxds/MSNumpressCoder.pxd) A core developer will review your changes to the main development branch (develop) and approve them (or ask for modifications). You may indicate the prefered reviewer(s) by adding links to them in a comment section (e.g., @cbielow @hendrikweisser @hroest @jpfeuffer @timosachsenberg) Also consider getting in contact with the core developers early. They might provide additional guidance and valuable information on how your specific aim is achieved. This might give you a head start in, for example, developing novel tools or algorithms. Happy coding!

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro galactic. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro iron. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro melodic. Known supported distros are highlighted in the buttons above.

openms repository

windows macos linux c-plus-plus algorithms proteomics metabolomics mass-spectrometry openms ms-data analyses hacktoberfest 3-clause-bsd

No version for distro noetic. Known supported distros are highlighted in the buttons above.