Skip to main content

BrucellaID: Brucella species identification and MLST from reads

Tests Coverage Release PyPI Python 3.10–3.14 License Documentation DOI

Identify the Brucella species of a fastq sample by its MASH distance to 16 reference genomes, and type it with the nine-locus Whatmore MLST scheme, whose alleles are called from the reads with Seal from BBTools. Point it at a sample, or a folder of samples.

$ brucellaid -r1 sample_R1.fastq.gz -r2 sample_R2.fastq.gz -o results/
Sample  Species           SpeciesSource         ClosestReference           SharedHashes  SequenceType  STSpecies
sample  Brucella abortus  MASH+ST (agree)       NC_006932-NC_006933.fasta  999/1000      1             Brucella abortus
canis   Brucella canis    MASH+ST (arbitrated)  NC_010103-NC_010104.fasta  1000/1000     20            Brucella canis

(Columns elided to fit; brucellaid.tsv also holds MashDistance, AlleleProfile, Reads and Notes.)

Both the reference sketch and the MLST database come with the package: nothing to download, index or configure.

Features

  • Two independent answers: the species, from the closest of 16 Brucella reference genomes, and the sequence type, from the nine MLST alleles. Both come with the numbers they rest on, and neither is quietly rewritten by the other.
  • The ST decides the one pair a distance cannot. B. canis and B. suis bv. 4 are 0.00024 apart — the closest pair of the sixteen, closer than two B. suis references are to each other — so which one a canis read set lands on first is noise. The two species share no sequence type at all, so where MASH leaves both within reach, the ST chooses, from a table of the species of every ST counted over 3,426 PubMLST isolates. A SpeciesSource column says what each call rested on, and an ST that contradicts a species MASH picked cleanly is reported, never obeyed.
  • Nothing is hidden: the distance to every reference, the reads behind every allele call and the runner-up that call had to beat, a note when a second reference was nearly as close, and a tie reported as a tie rather than broken by a coin toss.
  • A quality assurance report you can sign: every run writes brucellaid_report.html, one self-contained file — no script, no stylesheet, nothing fetched from anywhere — holding the closest reference genomes and not only the winning one, how the species was decided, every allele call with the margin it had, the input files with their MD5, the exact command, and the checksum of every reference data file the run measured against, so two runs a year apart can be shown to have used the same data. One sample to a printed page, with a box for a reviewer's name, date and signature. --pdf writes the same thing as a PDF. See an example report, or the same thing as a PDF.
  • Fits your pipeline: a JSON report with everything in it, and a MultiQC file, so multiqc results/ folds the run into the report your pipeline already produces.
  • Batch mode: point it at a folder; fastq files are found recursively, R1/R2 paired, and several samples run at a time. A sample that fails leaves the others readable.
  • Current reference data: the MLST database is PubMLST's, 309 alleles and 122 sequence types, plus the species of 118 of them counted over PubMLST's isolate database — all rebuilt by scripts in the repository. The sketch is vSNP's 16 Brucella genomes, with the species, biovar, strain and accession of each.
  • Backwards compatible where it counts: the MASH identification is vSNP's, down to the threshold of 150 shared hashes (--no-st-species reports it alone), and --xlsx still writes the stat_alignment_summary_<date>.xlsx of the first version.
  • Nothing to configure: only the Python standard library, plus MASH and BBTools. The two optional output formats, xlsx and PDF, are the only things that want a package, and neither is needed.
  • Tested: 345 tests, 100% coverage, end to end on a synthetic genome and on reads tiled over the real MLST alleles.
  • Validated on 16 genomes with a known answer: every species and closest reference right, and all 14 sequence types the one the genome carries — read off the assembly by exact match, which shares no code with the read-based caller. The B. canis genome is the one call the distance did not make on its own, and the ST made it; not one of the sixteen came back as a disagreement. The nearest neighbouring species shares 4 of 1000 hashes and comes back as not identified (Validation).

Installation

conda create -n brucellaid -c conda-forge -c bioconda mash "gsl=2.7.0" bbmap "python>=3.10"
conda activate brucellaid
pip install brucellaid

MASH and BBTools (which provides seal.sh) are not on PyPI, so they come from bioconda; BrucellaID itself needs nothing else. A bioconda package that installs all three in one command is awaiting review, so conda install brucellaid does not find it yet. See Installation for the details and for running it from a clone.

Quick start

brucellaid -r1 sample_R1.fastq.gz -r2 sample_R2.fastq.gz -o results/  # Paired-end reads
brucellaid -r1 sample.fastq.gz -o results/                            # Single-end reads
brucellaid -i reads/ -o results/ -p 4                                 # A folder, 4 samples at a time
brucellaid -i reads/ -o results/ --no-mlst                            # Species only

The results are printed and saved in results/: one row per sample, one row per locus, every MASH distance, a JSON report, a MultiQC file, and brucellaid_report.html — a self-contained quality assurance report with the evidence behind every call and a box to sign. To see it work on data with a known answer, run bash examples/run_example.sh, which builds its own reads from the alleles of a sequence type.

What the two answers mean: the species is the species of the closest reference genome, except where a reference of another species is just as close and the sequence type chooses between the two — the SpeciesSource column says which happened. The sequence type is new when the nine alleles are called but the combination is not in the table, and ND when a locus could not be called. There is no biovar: BrucellaID cannot measure one, and says why rather than guessing. See How it works.

Documentation

The wiki covers installation, a tutorial on public read sets, usage and options, output files, how it works, validation, troubleshooting and the FAQ.

Citing

If you use BrucellaID, please cite it together with the tools and the data it rests on:

Duceppe M-O. BrucellaID: Brucella species identification and MLST from sequencing reads. Zenodo. https://doi.org/10.5281/zenodo.23845956

This DOI always points to the latest version; each release also has its own DOI, listed on Zenodo.

Ondov BD, Treangen TJ, Melsted P, et al. Mash: fast genome and metagenome distance estimation using MinHash. Genome Biology 2016;17:132. https://doi.org/10.1186/s13059-016-0997-x

Bushnell B. BBTools. https://sourceforge.net/projects/bbmap/

Whatmore AM, Perrett LL, MacMillan AP. Characterisation of the genetic diversity of Brucella by multilocus sequencing. BMC Microbiology 2007;7:34. https://doi.org/10.1186/1471-2180-7-34

Jolley KA, Bray JE, Maiden MCJ. Open-access bacterial population genomics: BIGSdb software, the PubMLST.org website and their applications. Wellcome Open Research 2018;3:124. https://doi.org/10.12688/wellcomeopenres.14826.1

GitHub's "Cite this repository" button gives the citation in APA and BibTeX formats, from CITATION.cff.

  • brucetyper — in silico Bruce-ladder, Suis-ladder, AMOS and RB51 junction PCR for Brucella, from assemblies. Where BrucellaID gives the species from a distance and the sequence type from the alleles, brucetyper reads the assays a laboratory would run on a gel.
  • seqcounter — count the occurrences of any reference sequences in reads or assemblies.
  • spoligotyper — in silico spoligotyping of the M. tuberculosis complex.

Contributing

Bug reports, questions and pull requests are welcome: see CONTRIBUTING.md.

Author

Marc-Olivier Duceppe, Canadian Food Inspection Agency (CFIA): marc-olivier.duceppe@inspection.gc.ca

License

MIT

Metadata

Release files for brucellaid 1.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for brucellaid 1.2.1
File Size Uploaded Provenance Actions
brucellaid-1.2.1.tar.gz 170.9 kB With provenance Details for brucellaid-1.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for brucellaid 1.2.1
File Interpreter ABI Platform Actions
brucellaid-1.2.1-py3-none-any.whl Python 3 none any Details for brucellaid-1.2.1-py3-none-any.whl

Total release size: 310.9 kB

Release files / brucellaid-1.2.1.tar.gz

Download URL brucellaid-1.2.1.tar.gz
Size 170.9 kB
Tags Source
SHA-256 checksum
How to use checksums
9c181601e9df0b93f08f9e28e266b1dbc2b4ff917ac78bfe2baa14f0e54c9522
BLAKE2b-256 checksum
How to use checksums
c9589acb92830c64296cc83f9ff1f7244168af512dd5ff316d0e9dd3b884c6a4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Release files / brucellaid-1.2.1-py3-none-any.whl

Download URL brucellaid-1.2.1-py3-none-any.whl
Size 140.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0c20cd659005154262ea4266a2adbb4293e03ab9e736057452502427cc4120dc
BLAKE2b-256 checksum
How to use checksums
6c5ce85019c4402548afeade249f6e140f3108638f1bd9df3356642195b8574b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 Nov 2, 2026.

Transparency log

Security for brucellaid 1.2.1

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for brucellaid-1.2.1.tar.gz

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 Nov 2, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page