Skip to main content

Phylotypes

Group features (e.g. 16s rRNA gene variable region sequence variants) placed on a common phylogenetic tree by phylogenetic distance.

This is particularly useful when attempting a metanalysis of 16s rRNA gene variable region amplicons, in which the amplicons were made with different primers, etc.

Input:

--jplace <file> A jplace file (deduplicated) as made by pplacer or epa-ng.

Output:

--out <file> Path where the output should be placed in CSV format. This will be a header-containing CSV file in long-format with two columns: phylogroup and feature-id.

Parameters:

--lwr-overlap <0.0 - 1.0> Minimum like-weight-ratio overlap for two placed features (e.g. sequence variants) to be pre-grouped. Default of 0.1 should be fine for most use cases.

--threshold_pd <float> Phylogenetic distance at which to cluster features. Default of 1.0 corresponds roughly to somewhere between species-level and genus-level grouping for 16s rRNA V4 region amplicons.

--distance {legacy,kr} Pairwise distance metric. legacy (default) is an exact, vectorized reimplementation of the original LCA-weighted-average metric and reproduces prior phylotypes. kr is the true tree-Wasserstein (Kantorovich-Rubinstein) distance, a proper metric -- opt-in.

Note: --threshold_pd's default of 1.0 is calibrated for --distance legacy. The kr metric is on a different (smaller-valued) scale, so the same threshold means a different cut. If you use --distance kr, re-calibrate --threshold_pd on your own data; the legacy default will over- or under-split. (No default kr threshold is provided yet -- this is a TODO pending empirical calibration on a real dataset.)

--no-distal-length Ignore distal length to nodes when computing distances. Default is False (distal length is included).

--incremental Use an incremental seed→apply→expand→reconcile clustering path instead of the default batch path. Scales to larger inputs with lower peak memory at the cost of approximate, order-dependent grouping near phylotype boundaries. It also does not enforce the batch path's LWR-pregroup partitions, so its results are not expected to reproduce batch mode exactly.

--seed-size <int> Number of (most specific) placements used to seed the initial phylotype pool when --incremental is set. Default: 200.

--expand-batch-size <int> Maximum number of orphaned placements clustered together per expand pass when --incremental is set. Default: 200.

--apply-chunk-size <int> Retained for compatibility. Incremental assignments are applied sequentially, so this setting does not change grouping. Default: 1000.

Incremental performance and stability

Incremental mode computes distances only between a placement and the members it is being compared with, and keeps reconciliation state compact. It therefore uses less memory than a full feature-by-feature matrix, but reconciliation still scales quadratically with the number of provisional phylotypes.

There is no universally optimal --seed-size or --expand-batch-size: the number of distinct phylotypes, placement ambiguity, and orphan rate matter more than the total feature count. Start with the defaults (200 and 200) and benchmark representative data. Increasing either size can reduce follow-up assignment work, but increases the quadratic distance calculation for that stage.

These are grouping parameters as well as performance parameters. Changing them changes the initial clusters and the order in which sampled assignments are made. Clearly separated groups tend to be stable; placements near the distance threshold or overlapping several groups can differ. For analyses where this matters, compare a 100/200/500 grid across several random seeds, recording pairwise group agreement, group counts, and small-group membership. Record the seed size, expansion batch size, random seed, distance metric, threshold, and sample size with each result.

--device <str> PyTorch device for tensor computations, e.g. cpu or cuda. Default: cpu.

--max-pregroup-size <int> Maximum SVs per batch pregroup. Oversized initial LWR groups raise an error: use incremental clustering or raise the limit. Oversized LCA merges retain their constituent groups. This bounds per-group pairwise matrices, but not placement tensors or the inter-pregroup LCA matrix. Nonpositive values disable LCA merges and the initial-group size check. Default: 5000.


add_phylotypes

Assign a new set of placed sequence variants into an existing set of phylotypes.

Given a previous JPLACE file and its phylotype assignments (produced by phylotypes), and a new JPLACE of sequence variants placed on the same reference tree, each new SV is assigned to the nearest existing phylotype.

Input:

--previous_jp / -P <file> Previous JPLACE file (same reference tree as --new_jp).

--previous_phylotypes / -p <file> CSV file with two columns (phylotype, sv) representing the existing phylotype assignments.

--new_jp / -N <file> New JPLACE file containing the sequence variants to be assigned.

Output:

--out / -O <file> Output CSV (phylotype, sv) placing the new SVs into the existing phylotypes. SVs that share no tree-edge overlap with any existing phylotype are reported as orphans in the log and omitted from the output.

Parameters:

--no-distal-length Ignore distal length when computing distances. Default: False.

--device <str> PyTorch device. Default: cpu.

--distance {legacy,kr} Pairwise distance metric. Default: legacy.


phylotype_taxonomy

Assign a consensus species (or best-effort taxon) to each phylotype using per-SV taxonomic annotations.

Input:

--phylotypes / -p <file> CSV with phylotype and sv columns (output of phylotypes).

--taxonomy / -t <file> Per-SV taxonomic assignments in long format (as produced by MaLiAmPi), with columns sv, rank, want_rank, and tax_name.

Output:

--out / -O <file> CSV with phylotype and species columns. Phylotypes without a species-level assignment are annotated at the best available rank with a spp. suffix.


Release notes

v2.0.1

  • add_phylotypes now shares the same JPLACE loader and distance metric as phylotypes, eliminating a divergent implementation that failed on standard SEPP/epa-ng edge-numbered trees.
  • New --incremental clustering path for large datasets.
  • GPU support via --device cuda (or any valid PyTorch device string).
  • KR-distance threshold caveat: the --distance kr metric is on a different (smaller-valued) scale than legacy. The default --threshold_pd 1.0 is calibrated for legacy only. If using --distance kr, re-calibrate the threshold on your own data.

Metadata

Release files for phylotypes 2.5.0

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

Source distribution (sdist)

Source distribution for phylotypes 2.5.0
File Size Uploaded Provenance Actions
phylotypes-2.5.0.tar.gz 40.3 kB With provenance Details for phylotypes-2.5.0.tar.gz

Built distribution (wheel)

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

Total release size: 71.1 kB

Release files / phylotypes-2.5.0.tar.gz

Download URL phylotypes-2.5.0.tar.gz
Size 40.3 kB
Tags Source
SHA-256 checksum
How to use checksums
0dd64bfea35bfb3a972bd01fd36e069c5a81155dccc71bd57488512539dc1a6a
BLAKE2b-256 checksum
How to use checksums
4e331c1e96531f0530a00321f3743d4d4613c8d58e0e01fdae8cef3dd134ac08
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 3, 2026.

Transparency log

Release files / phylotypes-2.5.0-py3-none-any.whl

Download URL phylotypes-2.5.0-py3-none-any.whl
Size 30.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fb5d9572dff56340b0a00e1ca27424aca64b4a9f54d9de0d4ada11075709440c
BLAKE2b-256 checksum
How to use checksums
19b22b69a8b24ed17605601a7b79d7dc40d1b2a40ac27dd15c4f6821bd343b99
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 3, 2026.

Transparency log

Security for phylotypes 2.5.0

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for phylotypes-2.5.0.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 Oct 3, 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