[!IMPORTANT]
Always use the latest version for best results.
conda install bioconda::octopusv
[!NOTE]
Native GRIDSS support (v0.3.1+): OctopuSV directly processes GRIDSS VCF output
through octopusv correct. Paired BND records are resolved to standard SV types
(DEL/DUP/INV/INS/TRA) using the same logic as GRIDSS’s official
simple-event-annotation.R — including automatic INS detection from BND pairs
with inserted sequences. Single breakends are safely skipped.
No pre-processing with StructuralVariantAnnotation or other external tools required.
OctopuSV addresses four key challenges in structural variant (SV) analysis:
Smart BND standardization — Converts paired BND records into standard SV types (DEL/INV/DUP/INS/TRA), while preserving potential complex rearrangements as BNDs. Works out of the box with BND-heavy callers like GRIDSS and SvABA.
Multi-caller integration — Merge SVs from different tools (Manta, Sniffles, GRIDSS, PBSV, etc.) with flexible Boolean logic.
Multi-sample integration — Compare and analyze SVs across cohorts with customizable sample-level merging.
Somatic variant calling — Extract tumor-specific SVs by comparing tumor vs normal samples. Works with any SV caller, even those not designed for cancer analysis.
Whether you’re analyzing single samples, cohorts, or tumor/normal pairs, OctopuSV standardizes your workflow from raw calls to publication-ready results.
How OctopuSV Works
OctopuSV uses a standardized workflow to handle VCF inconsistencies across different SV callers:
Standardize: Convert any SV caller output to SVCF format using octopusv correct
Analyze: Perform merging, comparison, or somatic calling on standardized SVCF files
Export: Convert results back to standard VCF using octopusv svcf2vcf
Why SVCF? Different SV callers implement VCF inconsistently — varying field names, BND notations, coordinate systems. SVCF eliminates these compatibility issues by providing a unified intermediate format.
octopusv correct converts raw SV caller output into standardized SVCF format. This includes resolving paired BND records into concrete SV types and detecting insertions from BND pairs with long inserted sequences (e.g., from GRIDSS).
# Intersection: SVs found by ALL callers
octopusv merge -i manta.svcf sniffles.svcf pbsv.svcf -o intersection.svcf --intersect
# Union: SVs found by ANY caller
octopusv merge -i caller1.svcf caller2.svcf caller3.svcf -o union.svcf --union
# Specific caller: SVs unique to one caller
octopusv merge -i manta.svcf sniffles.svcf -o manta_specific.svcf --specific manta.svcf
# Minimum support: SVs supported by at least N callers
octopusv merge -i a.svcf b.svcf c.svcf d.svcf -o supported.svcf --min-support 3
# Complex Boolean logic: (A AND B) but NOT (C OR D)
octopusv merge -i A.svcf B.svcf C.svcf D.svcf \
--expression "(A AND B) AND NOT (C OR D)" -o filtered.svcf
# Multi-sample mode with custom names
octopusv merge -i sample1.svcf sample2.svcf sample3.svcf \
--mode sample --sample-names Patient1,Patient2,Patient3 \
--min-support 2 -o cohort.svcf
# Generate intersection plot
octopusv merge -i a.svcf b.svcf c.svcf -o merged.svcf --intersect \
--upsetr --upsetr-output venn_diagram.png
3. Somatic SV Calling
Use any SV caller to analyze tumor and normal samples separately, then let OctopuSV find somatic variants. Works even with callers not designed for cancer analysis.
Example multi-caller somatic workflow (e.g., with 3 callers on a tumor-normal pair):
# Run each caller separately on the tumor-normal pair, then standardize
octopusv correct manta_tumor.vcf manta_tumor.svcf
octopusv correct delly_tumor.vcf delly_tumor.svcf
octopusv correct gridss_tumor.vcf gridss_tumor.svcf
# Keep SVs supported by at least 2 out of 3 callers
octopusv merge -i manta_tumor.svcf delly_tumor.svcf gridss_tumor.svcf \
-o high_confidence_somatic.svcf --min-support 2
# Basic stat collection
octopusv stat -i input.svcf -o stats.txt
# Add HTML report
octopusv stat -i input.svcf -o stats.txt --report
# Plot figures from stats
octopusv plot stats.txt -o figure_prefix
The --report flag outputs an interactive HTML report covering SV type and size distributions, chromosome breakdowns, quality score summaries, and genotype and depth features.
6. Format Conversion
# To BED
octopusv svcf2bed -i input.svcf -o output.bed
# To BEDPE
octopusv svcf2bedpe -i input.svcf -o output.bedpe
# To standard VCF
octopusv svcf2vcf -i input.svcf -o output.vcf
If you use OctopuSV in your research, please cite:
Guo, Qingxiang, Yangyang Li, Ting-You Wang, Abhi Ramakrishnan, and Rendong Yang. “OctopuSV and TentacleSV: a one-stop toolkit for multi-sample, cross-platform structural variant comparison and analysis.” Bioinformatics (2025): btaf599. doi: https://doi.org/10.1093/bioinformatics/btaf599
@article{guo2025octopusv,
title={OctopuSV and TentacleSV: a one-stop toolkit for multi-sample, cross-platform structural variant comparison and analysis},
author={Guo, Qingxiang and Li, Yangyang and Wang, Ting-You and Ramakrishnan, Abhi and Yang, Rendong},
journal={Bioinformatics},
pages={btaf599},
year={2025},
publisher={Oxford University Press}
}
If you find OctopuSV useful, a ⭐ on GitHub helps others discover the project!
OctopuSV: Advanced structural variant analysis toolkit 🐙
OctopuSV addresses four key challenges in structural variant (SV) analysis:
Whether you’re analyzing single samples, cohorts, or tumor/normal pairs, OctopuSV standardizes your workflow from raw calls to publication-ready results.
How OctopuSV Works
OctopuSV uses a standardized workflow to handle VCF inconsistencies across different SV callers:
octopusv correctoctopusv svcf2vcfWhy SVCF? Different SV callers implement VCF inconsistently — varying field names, BND notations, coordinate systems. SVCF eliminates these compatibility issues by providing a unified intermediate format.
📋 SVCF Format Details: See our SVCF specification document for technical details.
Supported SV Callers
Long-read: Sniffles, Severus, SVDSS, DeBreak, SVIM, CuteSV, PBSV, nanomonsv
Short-read: Manta, Delly, GRIDSS, Lumpy, SvABA, Octopus, CLEVER
CNV callers: Dragen CNV (automatic conversion of CNV to DEL/DUP)
Continuously expanding support for additional callers.
Installation
Bioconda (recommended)
Or with mamba for faster dependency resolution:
PyPI
Docker
See octopusv/tags for valid values.
Quick Start
1. Correct and Standardize BND Annotations
octopusv correctconverts raw SV caller output into standardized SVCF format. This includes resolving paired BND records into concrete SV types and detecting insertions from BND pairs with long inserted sequences (e.g., from GRIDSS).2. Merge SV Calls (Multi-caller or Multi-sample)
3. Somatic SV Calling
Use any SV caller to analyze tumor and normal samples separately, then let OctopuSV find somatic variants. Works even with callers not designed for cancer analysis.
Example multi-caller somatic workflow (e.g., with 3 callers on a tumor-normal pair):
4. Benchmark Against Truth Sets
5. Generate Statistics and Visualizations
The
--reportflag outputs an interactive HTML report covering SV type and size distributions, chromosome breakdowns, quality score summaries, and genotype and depth features.6. Format Conversion
Example Visualizations
OctopuSV generates publication-ready visualizations:
Citation
If you use OctopuSV in your research, please cite:
If you find OctopuSV useful, a ⭐ on GitHub helps others discover the project!
See the companion pipeline: TentacleSV
Contributing
We welcome issues, suggestions, and pull requests!
Contact