| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
| Name | Name | Last commit date | ||
|---|---|---|---|---|
Warning
This project is archived and thus not updated anymore. If you are interested to revive this project, please contact us at info@eubic-ms.org.
This project aims at defining a set of guidelines to report mass spectrometry-based experiments in a reproducible fashion.
To view the guidelines, use https://eubic.github.io/ReproducibleMSGuidelines. This uses a JavaScript application to render the actual guidelines.md document. This rendering tool can also be used offline when downloading the repositories content and opening the index.html file.
There is a growing concern about a lack of reproducibility in science that also affects bioinformatics and mass spectrometry (MS-based) technologies. One aspect of this problem is that bioinformatic analysis are increasingly complex and greatly influence the outcome of a study. Current bioinformatic analysis commonly consist of multiple tools and algorithms, each with its own set of parameters. Recording all of these settings in full detail is rarely possible in methods sections of a research manuscript. This often leads to vital details about the bioinformatic processing of the data to be missing. In this work, we, therefore, try to establish a set of guidelines to describe
These guidelines aim to provide recommendations for mass spectrometry-based experimental techniques. The guidelines currently contain recommendations for
Fields that we are currently working on are
Contributions for any other MS-based method are highly welcome!
The complete guidelines are stored in the guidelines.md file in this repository. We created a JavaScript application that nicely renders this document as a webpage at https://eubic.github.io/ReproducibleMSGuidelines. The actual file is a standard markdown file that can be viewed here.
We are currently working on a more user-friendly web-based rendering of these guidelines.
Everyone! The creation of this guidelines as a completely community-driven project. How to contribute
While the guidelines.md file is a normal markdown file, it does follow some conventions in order to render a user-friendly version.
The guidelines are grouped into sections, each represented as the top level scope of the markdown file:
# Section name ...
Every section may have a description:
# Section name SectionDescription: A great description that may span multiple lines.
Finally, a section may have an example section:
# Section name SectionExample: A reference to a study that created a very reproducible workflow. Again, the example may span multiple lines.
Items are the actual recommendations in the guideline.
# Public Data Deposition Name: Raw data deposition Category: bronze Description: The complete RAW data must be deposited in a public repository. Fields: all
Items start with the Name: tag. Every item is assigned to a category, either "bronze", "silver", or "gold" and has a descrition. Items are linked to specific fields, such as "proteomics", or "metabolomics", but may also be applicable to "all" fields. The Fields: slot is a comma-delimited list of field names. Finally, every item may have an Example: field that again may span multiple lines. Items must end with an empty line.
| Back | FazBrowse Home | New Git URL |