prideQC
prideQC computes quality-control metrics from raw mass-spectrometry data and uses that measured evidence to refine technical SDRF metadata.
It is designed around a simple separation of responsibilities:
- Measure QC evidence from the data.
- Summarize and report that evidence.
- Refine metadata only when the study-level evidence supports it.
Documentation
- Documentation: https://prideqc.readthedocs.io/
- Source: https://github.com/PRIDE-Archive/prideQC
- PRIDE Archive: https://www.ebi.ac.uk/pride/
Until the hosted documentation is enabled, the same material is available under docs/ in this repository.
Highlights
prideQC can:
- analyze local mzML and supported raw/vendor inputs;
- compute per-file mass-spectrometry QC metrics;
- estimate precursor and fragment measurement precision;
- scout recurrent neutral mass shifts and mass-compatible modification candidates;
- write structured JSON, TSV, and mzQC-compatible outputs;
- aggregate results for interactive pmultiqc / MultiQC reporting;
- synthesize QC evidence across a study/cohort;
- propose conservative, auditable SDRF refinements;
- validate refined SDRFs with
sdrf-pipelines.
Quick start
prideqc analyze sample1.mzML sample2.mzML \
--output-dir results \
--estimate-mass-error \
--estimate-mass-shifts \
--diagnostics
Refine an SDRF from existing QC results:
prideqc refine-sdrf-qc \
--results-root results \
--sdrf study.sdrf.tsv \
--output-dir refinement
Validate an SDRF:
prideqc check-sdrf study.sdrf.tsv
Reporting
prideQC's mzQC-compatible outputs can be aggregated into interactive HTML reports with pmultiqc / MultiQC:
multiqc --module mzqc \
--outdir report \
results/
See the documentation for the complete QC, reporting, and SDRF-refinement workflow.
Local documentation build
uv venv .venv-docs --python 3.12
uv pip install --python .venv-docs/bin/python -r docs/requirements.txt
.venv-docs/bin/sphinx-build -W --keep-going -b html docs docs/_build/html
The six scientific SVG figures are checked into docs/_static/figures/; a
normal Sphinx / Read the Docs build does not need pyOpenMS, matplotlib, or
to regenerate the figures. For intentional figure regeneration, see the
maintainer-only docs/figure_source/README.md.
License
See LICENSE, NOTICE, and licenses/.
Metadata
Release files for prideQC 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| prideqc-0.2.0.tar.gz | 368.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| prideqc-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 500.6 kB
Release files / prideqc-0.2.0.tar.gz
| Download URL | prideqc-0.2.0.tar.gz |
|---|---|
| Size | 368.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
28468233b34731609448dd838beb89815c2939a57c82c4d63ddf2ec5e84b53f3
|
|
BLAKE2b-256 checksum How to use checksums |
585a1e1bde1488fd384886e9a5d796db9b4236779d5e7c37da45d392b22eed27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency logRelease files / prideqc-0.2.0-py3-none-any.whl
| Download URL | prideqc-0.2.0-py3-none-any.whl |
|---|---|
| Size | 131.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2b99730e6b3a48423beb85a22d90fcc7859338071591f44671ba3f5e3d7e3581
|
|
BLAKE2b-256 checksum How to use checksums |
fff971490ad17de3beb0eded3b6c108d0c410f9716fdaaf27174116bddef4d18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 8, 2026.
Transparency log