Skip to main content

LocusSnap

CI

Create an IGV-like image from an indexed BAM without opening a genome browser.

Install

pip install locus-snap

This installs the locus-snap command and the locus_snap package.

Basic usage

locus-snap \
  --bam sample.bam \
  --region chr9:101867481-101867620 \
  --output_dir out \
  --output_name locus

The result is out/locus.png.

Run from a source checkout

git clone https://github.com/GENCARDIO/LocusSnap.git
cd LocusSnap
pip3 install -e .

python3 locus_snap.py \
  --bam sample.bam \
  --region chr9:101867481-101867620 \
  --output_dir out \
  --output_name locus

python3 -m locus_snap ... is equivalent when running from the repository.

The input can be BAM or CRAM and must be indexed. If it is not:

samtools index sample.bam    # produces sample.bam.bai
samtools index sample.cram   # produces sample.cram.crai

CRAM additionally requires --fasta, since decoding CRAM reads needs the same reference the file was compressed against.

Regions are 1-based and inclusive. Add --flank 500 to show 500 bp on each side.

For human BAMs, the first run may download and index the matching NCBI RefSeq gene annotation. Use --refseq none if you want the image immediately without that track.

Examples

Click any preview for the full-resolution figure.

Default genomic snapshot with RefSeq isoforms, coverage, and alignments
Default genomic snapshot
Ideogram, RefSeq isoforms, coverage, alignments, and grouped legend.
MET exon 14 splice-site variant with RNA-seq and sashimi evidence
MET exon 14 skipping
Splice-site VCF, gene model, RNA-seq coverage, sashimi arcs, and split reads.
Deletion, tandem duplication, inversion, and translocation with multiple classes of sequencing evidence
Structural-variant evidence
Deletion, tandem duplication, inversion, and chr1–chr2 translocation with event-specific coverage, pair orientation, split reads, and soft clips.
Coverage track with SNV variant allele fractions
SNV allele fractions
Coverage with strand-aware alternative-allele evidence and VAF labels.
Reads separated into phased haplotype lanes
Phased haplotype lanes
HP/PS-aware read colouring and lane separation.
Copy-number segments with B-allele fractions and loss of heterozygosity
CNV with BAF/LOH and genomic bands
Alternating coordinate bands align purity-aware CN1 loss (BAF 0.20/0.80), CN3 gain (BAF 0.36/0.64), and their matching depth shifts.
Normalized CTCF ChIP-seq signal profiles
ChIP-seq signal profiles
Track-only normalized signal comparison with gene annotations.
Multiple BAM samples with companion VCF tracks
Multi-sample comparison
Stacked BAM panels with sample-matched companion VCFs.
Paired reads linked on shared alignment rows
View as pairs
Visible primary mates share rows and are connected across their genomic gap.
Primary locus beside an inferred discordant-mate window
Two-locus mate window
The requested locus is shown beside the automatically inferred discordant-mate region.
Reads grouped by their nucleotide at a selected SNV
Sort by SNV base
Alternative-allele reads are grouped and prioritized at the selected position.
BED, GTF, and VCF tracks in one genomic snapshot
Mixed custom tracks
BED regions, transcript models, and VCF variants are composed in one figure.
Close genomic zoom showing individual soft-clipped nucleotide letters
Soft-clipped bases at close zoom
A 40 bp expanded view retains each read's background while colouring the clipped A/C/G/T letters like IGV.
Close genomic zoom showing purple insertion markers at a shared breakpoint
Insertions at close zoom
Short CIGAR insertions appear as narrow purple breakpoint markers with a white I, matching IGV.

The synthetic examples use expanded, deterministic datasets: 240 tumour, 180 normal, 210 relapse, 300 METex14 RNA alignments, 703 structural-variant alignments, and 16,000 reads across a purity-aware CNV locus; 12 general VCF records; 83 heterozygous BAF loci; 12 H3K27ac, 7 H3K27me3, and 24 DNase peaks; and three 4 kb normalized CTCF signal profiles. DNA cohorts include a sparse 0.15% low-quality substitution-error model. The CNV cohort couples read depth, SEG log2 ratios, and BAF bands for diploid, single-copy-loss/LOH, and three-copy gain states. Rendered figures remain directly under out/; their generated inputs are grouped by type:

out/demo_data/
├── alignments/   # BAM and BAI
├── annotations/  # BED, GTF, SEG, and peak calls
├── config/       # Example YAML themes
├── reference/    # FASTA and FAI
├── signals/      # Quantitative signal tracks and indexes
└── variants/     # VCF and tabix indexes

Rebuild the demo inputs, indexes, and the twelve curated figures shown above with:

bash regenerate_demo_examples.sh

What you get by default

  • chromosome ideogram with the current window marked in red
  • RefSeq isoforms for recognized hg19/GRCh37 and hg38/GRCh38 BAMs
  • Coverage and packed read alignments
  • Automatic alignment downsampling above 100× depth
  • Discordant-pair, indel, mismatch, and soft-clip colours

Add --fasta reference.fa to enable reference bases, mismatch detection, and SNV allele fractions in coverage. A missing FASTA index is created when possible.

Pick the view you need

Goal Add these options
Normal IGV-like view --display_mode expand --layout pack
Very deep region --display_mode squish --layout pack
Overlay everything --display_mode collapse
One sorted read per row --layout expand --sort_by gap_length
Link visible mates --view_as_pairs
Two loci: region + inferred mate locus --mate_view
Only event-supporting reads --only discordant gapped split softclip
Hide the legend --no_legend
Hide the background grid --grid_mode none
Add coordinate subdivisions --grid_mode major_minor
Use alternating genomic bands --grid_mode bands
Highlight a genomic interval --highlight chr1:100100-100250 --highlight_color '#ffd54f'
Center the figure title --title_align center
Hide coverage --no_coverage
Hide chromosome overview --no_ideogram
Add a center guide --center_guide

display_mode controls read height. layout controls row placement. They are independent.

--grid_mode controls the genomic background consistently across alignment, coverage, annotation, multi-sample, and mate-window panels. The default is major. Grid colours, line styles, opacity, widths, band opacity, and the number of minor subdivisions can all be adjusted under visual_colors and styles in the YAML configuration.

Use repeatable --highlight chrom:start-end intervals to shade selected loci through every data track. --highlight_color accepts Matplotlib colours and --highlight_alpha controls their shared opacity. Highlights also work in multi-sample and mate-window figures; in mate view, each interval is applied only to the panel with the matching chromosome.

--title_align left|center|right positions the complete figure heading block, including its subtitle. It applies consistently to single-locus, multi-sample, and mate-window figures without moving individual track or panel labels.

Common recipes

Small window with reference bases

Reference bases are shown automatically for windows up to 250 bp.

locus-snap \
  --bam sample.bam \
  --fasta reference.fa \
  --region chr1:100001-100140 \
  --output_name base-detail

Change the limit with --max_reference_span BP; use 0 to hide the reference row while keeping FASTA-backed mismatch detection.

High-depth region

locus-snap \
  --bam deep.bam \
  --region chr1:100000-110000 \
  --display_mode squish \
  --layout pack \
  --max_alignment_depth 100 \
  --output_name deep-region

Coverage still uses all filtered reads. Only the displayed alignment track is downsampled. Use --max_alignment_depth 0 to disable downsampling or --max_rows N to impose a hard row limit.

View paired alignments

locus-snap \
  --bam sample.bam \
  --region chr9:101867481-101867620 \
  --view_as_pairs \
  --display_mode squish \
  --output_name paired-reads

Visible primary mates share a row and are connected. Off-window, inter-chromosomal, supplementary, and incomplete pairs remain individual alignments.

Two-panel breakpoint or translocation view

locus-snap \
  --bam tumour.bam \
  --region chr3:187721000-187721500 \
  --mate_view \
  --mate_window_source discordant \
  --only discordant \
  --output_name breakpoint

--mate_window_source accepts:

  • discordant: mapped mate positions from discordant pairs;
  • split: supplementary positions from SA tags;
  • softclip: mapped mates of soft-clipped reads.

Candidates are grouped by chromosome. The busiest chromosome is selected and the panel is centered on the mean candidate position. Set its width with --mate_window_size BP. Mate view currently accepts one BAM.

Sort reads carrying an SNV

locus-snap \
  --bam sample.bam \
  --fasta reference.fa \
  --region chr9:101867520-101867570 \
  --layout expand \
  --sort_by base \
  --sort_base_position 101867542 \
  --output_name snv-sort

Alternative A/C/G/T alleles are placed first, followed by the reference, deletions, skips, and reads that do not cover the position. Without a FASTA, the most frequent observed base is used as the local reference.

Show SNV allele fractions in coverage

locus-snap \
  --bam sample.bam \
  --fasta reference.fa \
  --region chr1:100001-100140 \
  --coverage_vaf_threshold 0.10 \
  --min_baseq 20 \
  --min_variant_mapq 20 \
  --show_variant_counts \
  --output_name vaf

The default threshold is VAF > 0.20. Only SNVs are included. Labels show ALT/depth, VAF, strand counts, mean base quality, and mean MAPQ when there is enough room.

Haplotype-aware view

locus-snap \
  --bam phased.bam \
  --region chr1:100001-100500 \
  --haplotype_view split \
  --haplotype_filter 1 2 untagged \
  --output_name haplotypes

color colours reads by the HP tag. split also creates HP lanes and shows phase-set information from PS. Override the tags with --haplotype_tag and --phase_set_tag.

RNA-seq sashimi view

locus-snap \
  --bam rnaseq.bam \
  --region chr1:100000-110000 \
  --sashimi \
  --min_junction_reads 3 \
  --sashimi_strand split \
  --display_mode squish \
  --output_name sashimi

Junctions come from CIGAR N operations. Arc labels are supporting-read counts. combined merges strands; split mirrors plus and minus junctions.

Stack several BAMs and matched VCFs

locus-snap \
  --bam tumour.bam \
  --bam normal.bam \
  --bam relapse.bam \
  --sample_label Tumour \
  --sample_label Normal \
  --sample_label Relapse \
  --vcf_companion tumour.vcf.gz \
  --vcf_companion none \
  --vcf_companion relapse.vcf.gz \
  --region chr9:101867492-101867612 \
  --output_name multi-sample

Repeat labels and companion VCFs in BAM order. Use none when a sample has no VCF. Each BAM keeps its own coverage, alignments, downsampling, and summary.

Batch rendering and reports

Render every region in a BED file with one command, using a single BAM:

# candidates.bed  (BED3/BED4: chrom, start, end[, name])
chr9	101867480	101867620	MET_ex14
chr1	100000	101000
locus-snap \
  --bam sample.bam \
  --batch_regions candidates.bed \
  --report \
  --output_dir out/candidates

Each row renders to its own image, named from the optional 4th BED column (or chrom_start_end when omitted); --flank, --display_mode, --track, and every other single-region option still apply to every region. One bad region (e.g. a contig missing from the BAM) is logged and skipped rather than aborting the whole batch; the process exits non-zero if any region failed.

--batch_regions also accepts a VCF/VCF.gz/BCF directly (picked by file extension) — one region per variant record, no BED needed:

locus-snap \
  --bam sample.bam \
  --batch_regions calls.vcf.gz \
  --flank 50 \
  --report \
  --output_dir out/calls

Each region is named from the VCF ID column when set (e.g. an rsID), otherwise chrom_pos_REF_ALT. A multi-allelic line still renders as one region, not one per ALT. The variant span comes from the record's resolved start/end, so symbolic/structural records with an INFO/END (declared as Type=Integer in the VCF header, as any spec-compliant SV caller does) are handled automatically. --flank matters more here than for BED: most variants are point-sized, so --flank 0 (the default) renders a ~1bp-wide image — set --flank to whatever context you want around each call. Records with no ALT allele (e.g. gVCF reference blocks) are skipped.

--report (optionally --report NAME.html) additionally writes one self-contained HTML file with every rendered image embedded inline, alongside a summary table of reads/gapped%/discordant%/soft-clipped per region — useful for reviewing a panel of candidate variants without opening each PNG. It requires --batch_regions and a browser-viewable --output_format (png, jpg, jpeg, webp, or svg — not pdf/tiff/svgz).

--batch_regions currently supports one --bam at a time and does not combine with --sort_base_position or --metrics_tsv.

Add genomic tracks

The short form is enough when the filename identifies the format:

locus-snap \
  --bam sample.bam \
  --region chr9:101867492-101867612 \
  --track genes.gtf.gz \
  --track variants.vcf.gz \
  --track_label Genes \
  --track_label Variants \
  --output_name annotated

For full control, use one quoted CSV value per track:

--custom_track 'FILE,TYPE,NAME,COLOR[,DISPLAY[,HEIGHT_IN]]'

Example:

--custom_track 'regions.bed,bed,Candidates,#000000,collapse,0.30' \
--custom_track 'genes.gtf.gz,gtf,GENCODE,#17217a,expand,0.85' \
--custom_track 'variants.vcf.gz,vcf,Variants,#7a1f5c,collapse,0.25'

Quote the entire value so # is not treated as a shell comment.

Supported tracks

Type Use for Default rendering
BED/BED12 regions, probes, custom features black blocks
GFF/GFF3/GTF genes and transcripts UCSC navy exon/UTR models
VCF SNVs and structural variants burgundy variant intervals
narrowPeak/broadPeak ChIP-seq, ATAC-seq, DNase-seq filled signal peaks
signal normalized ChIP/ATAC/DNase pileup continuous filled profile
BigWig the same, distributed as an indexed binary file continuous filled profile
SEG segmented copy number gain/loss log2 track
bedGraph/log2/CNV binned or segmented log2 ratios signed zero-centered track

The accepted custom TYPE values are bed, gff, gff3, gtf, vcf, narrowpeak, broadpeak, peak, signal, bigwig (alias bw), seg, bedgraph, log2, cnv, and auto.

BigWig tracks

A .bw/.bigWig file (the format most ChIP-seq/ATAC-seq/RNA-seq coverage tracks, e.g. from deepTools or the UCSC/ENCODE archives, are already distributed as) works with either track form:

locus-snap \
  --bam sample.bam \
  --region chr9:101867492-101867612 \
  --track coverage.bw \
  --track_label "Input signal" \
  --output_name bigwig-track

BigWig is self-indexed, so no separate .tbi/.csi file is needed. By default it loads as a signal track (continuous, non-negative, scaled by styles.signal_y_max like any other signal track — see "Configure everything with YAML"). For signed BigWig data (e.g. a log2 ratio track), override the type explicitly:

--custom_track 'ratio.bw,log2,Log2 ratio,#2878b5'

Use --track_display to control annotation density:

Mode Result
collapse merge transcript isoforms into one model per gene
pack preserve models and share non-overlapping rows
expand one transcript per row
density compact binned feature count

Gene introns carry strand arrows: right for +, left for -. Exons are thick; UTRs are thinner. Use --primary_isoforms prefer to select MANE Select, RefSeq Select, Ensembl canonical, APPRIS principal, or another recognized primary marker, while keeping all isoforms for genes without a marker. Use only to remove genes without a primary marker; all is the default. Packed and expanded gene models retain both identifiers in gene-first form, for example TGFBR1 · NM_004612.4; collapsed models show the gene name only.

Compressed tracks must be indexed

Plain-text tracks work directly. A .gz, .bgz, or .bgzf track must be BGZF-compressed and have a .tbi or .csi index. It is fetched by region with tabix; ordinary gzip is not enough. BigWig (.bw/.bigWig) is a binary, self-indexed format and is exempt from this — never gzip it, and no separate index file is needed.

bgzip genes.gtf
tabix -p gff genes.gtf.gz

bgzip regions.bed
tabix -p bed regions.bed.gz

bgzip variants.vcf
tabix -p vcf variants.vcf.gz

bgzip H3K27ac.narrowPeak
tabix -p bed H3K27ac.narrowPeak.gz

ChIP-seq and accessibility

locus-snap \
  --bam sample.bam \
  --region chr1:100000-140000 \
  --track H3K27ac.narrowPeak.gz \
  --track_label H3K27ac \
  --custom_track 'H3K27me3.broadPeak,broadpeak,H3K27me3,#d95f02,collapse' \
  --custom_track 'DNase.narrowPeak.gz,narrowpeak,DNase,#2166ac,density' \
  --output_name chromatin

Peak-call files remain discrete intervals: height uses signalValue, then BED score, and narrowPeak summits are marked. Four-column signal files are drawn as one continuous filled pileup profile:

locus-snap \
  --bam sample.bam \
  --region chr1:100000-104000 \
  --custom_track 'control.signal.gz,signal,Control,#00695c,collapse' \
  --custom_track 'knockdown.signal.gz,signal,Knockdown,#22d3a6,collapse' \
  --no_alignments \
  --no_coverage \
  --output_name ctcf-signal

Set one shared styles.signal_y_max in YAML when comparing normalized samples; 0 keeps automatic scaling. Use density when called intervals would otherwise overplot.

Copy number, BAF, and LOH

locus-snap \
  --bam tumour.bam \
  --region chr9:101000000-102000000 \
  --track tumour.seg \
  --track_label 'Tumour CNV' \
  --baf_vcf germline-snps.vcf.gz \
  --baf_sample Tumour \
  --baf_track_label 'Tumour BAF / LOH' \
  --output_name cnv-baf

BAF uses heterozygous biallelic SNVs. It prefers FORMAT/AD and falls back to FORMAT/AF. Compressed VCF/BCF files require an index.

Human references and ideograms

--genome auto identifies hg19 or hg38 only from exact chromosome lengths in the BAM header. The ideogram uses bundled UCSC cytobands and spans the same width as the genomic plot.

Useful controls:

--genome hg19|grch37|hg38|grch38|none
--cytoband_file custom.cytoBand.txt.gz
--no_ideogram

--refseq auto similarly selects and caches an indexed NCBI RefSeq track.

--refseq hg19|grch37|hg38|grch38|none
--refseq_dir /shared/refseq-cache

Pre-download both supported assemblies with:

python3 download_refseq.py

The fixed sources are NCBI Annotation Release 105.20220307 for GRCh37.p13 and Annotation Release 110 for GRCh38.p14.

Configure everything with YAML

Pass --config FILE.yaml. Command-line options override YAML preferences.

preferences:
  display_mode: squish
  max_alignment_depth: 150
  primary_isoforms: prefer
  fig_width: 16
  dpi: 200

alignment_colors:
  normal: "#c8c8c8"
  large_insert: "#d73027"
  small_insert: "#4a3aa7"

track_colors:
  bed: "#000000"
  gene: "#17217a"
  vcf: "#7a1f5c"

styles:
  row_height_in: 0.06
  squish_row_height_in: 0.015
  coverage_track_height_in: 1.40
  annotation_row_height_in: 0.30
  alignment_edge_width: 0.00
  gene_arrow_size: 2.70
  gene_arrow_spacing_px: 24.0

See config.example.yaml for every colour, preference, height, opacity, line width, legend setting, ideogram colour, and sashimi style. Unknown keys and invalid values fail early.

Every track height is configurable:

Track YAML key
Alignments row_height_in, squish_row_height_in
Coverage coverage_track_height_in
BED/GFF/GTF/VCF annotation_row_height_in
CNV cnv_track_height_in
BAF/LOH baf_track_height_in
Peaks/signal/density peak_track_height_in
Sashimi sashimi_track_height_in
Reference bases reference_height_in
Ideogram ideogram_height_in

The sixth --custom_track CSV field overrides the height for one track.

Output format and resolution

PNG is the default. Use a filename extension or --output_format:

# Editable vector image
locus-snap \
  --bam sample.bam --region chr1:100000-101000 \
  --output_name locus.svg

# High-resolution PNG
locus-snap \
  --bam sample.bam --region chr1:100000-101000 \
  --output_name locus --output_format png --fig_width 16 --dpi 300

Supported formats: PNG, SVG, SVGZ, PDF, JPEG, TIFF, and WebP. Raster width is fig_width × dpi; height adapts to the tracks and read rows.

Read colours and evidence

Read appearance Meaning
grey normal/concordant
red unexpectedly large FR insert
dark blue unexpectedly small FR insert
purple CIGAR insertion marker
teal / blue FF/RR same-strand pair (IGV orientation colours)
green everted RF pair
IGV chromosome colour inter-chromosomal pair, keyed by the mate chromosome
lighter fill lower MAPQ

The expected insert-size range is estimated from eligible FR pairs in the window. Disable pair colours with --no_pair_colors; disable MAPQ shading with --no_mapq_shading.

CIGAR insertion and deletion lengths are hidden by default. Show them with --show_indel_lengths.

Options people use most

Option Purpose
--bam BAM indexed BAM or CRAM input; repeat for multiple samples
--region chr:start-end 1-based inclusive window
--batch_regions BED|VCF render every region in a BED file, or every variant in a VCF (single BAM)
--report [NAME.html] self-contained HTML report for --batch_regions
--fasta FASTA reference bases, mismatches, and coverage VAF
--flank BP add context on both sides
--display_mode collapse|expand|squish read-track density
--layout pack|expand packed rows or one sorted unit per row
--sort_by KEY base, gap_length, mapq, start, and more
--only TYPE [...] keep discordant, gapped, split, or soft-clipped reads
--no_legend hide legend cards and reclaim their space
--grid_mode MODE none, major, major_minor, or alternating bands
--highlight REGION shade a repeatable interval through every data track
--highlight_color COLOR colour shared by highlighted intervals
--highlight_alpha A highlight opacity in the range (0, 1]
--title_align ALIGN place the figure title at left, center, or right
--min_mapq N filter low-MAPQ reads
--max_alignment_depth N downsample displayed reads above N×; default 100
--view_as_pairs link visible primary mates
--mate_view add an inferred mate-locus panel
--track PATH add a genomic track; repeatable
--custom_track SPEC add a named, coloured, sized track
--config YAML reusable defaults and styles
--metrics_tsv PATH export per-read classifications and metrics
--fig_width INCHES --dpi N output size and raster resolution

Run this for the full option list:

locus-snap --help

Test supported Python versions with Tox

Install the development tools and run the complete Python 3.9–3.14 matrix:

python3 -m pip install -e '.[dev]'
tox run

Tox creates isolated environments, builds and installs the package wheel, and runs the complete pytest suite in each available interpreter. Missing local interpreters are reported and skipped. Run one version or pass pytest options after --:

tox run -e py312
tox run -e py310 -- -k highlight

When several interpreters are installed, run them concurrently with:

tox run-parallel --parallel all

Performance: what happens on large windows

  • Coverage is binned to the physical image width. Wide windows do not create one plotting object per base.
  • Alignment display is downsampled above 100× by default. Coverage, summaries, sashimi counts, and TSV metrics still use the complete filtered cohort.
  • Indexed tracks are fetched only for the requested region.
  • Alternative alleles and discordant/gapped/split/soft-clipped evidence are prioritized during downsampling.

For a faster, smaller deep-region image, start with:

--display_mode squish --layout pack --max_alignment_depth 100

Add --max_rows 200 if the image is still too tall. Add --only when you need event evidence rather than every read.

Troubleshooting

“The BAM has no index”

samtools index sample.bam    # or samtools index sample.cram

CRAM fails to open or decode

CRAM needs --fasta pointing at the same reference it was compressed against; a missing or mismatched reference is the most common cause.

A compressed track will not load

It must be BGZF, not ordinary gzip, and it needs .tbi or .csi beside it. Recompress and index it with bgzip and tabix.

Reference bases or mismatches are missing

Pass --fasta reference.fa. Check that FASTA and BAM chromosome names match (chr1 versus 1) and that the window is no larger than --max_reference_span for the visible base row.

The automatic gene track is missing

Assembly detection requires exact hg19/GRCh37 or hg38/GRCh38 chromosome lengths. Select explicitly with --refseq hg19 or --refseq hg38. The first download also needs network access. Use --refseq none to disable it.

The image is too tall or uses too much memory

Use --display_mode squish, keep the default 100× downsampling, and set --max_rows. For a targeted review, add --only discordant gapped split softclip.

Mate view cannot find a locus

Try another --mate_window_source, lower --min_softclip, or remove an overly restrictive --only filter.

Tests

pytest -q

A GitHub Actions workflow (.github/workflows/ci.yml) runs the complete suite on every push and pull request against Python 3.9–3.14, mirroring the Tox matrix above.

Releasing to PyPI

.github/workflows/publish.yml publishes a new release automatically when a tag matching X.Y.Z or vX.Y.Z is pushed (both are accepted, matching this repo's existing tag history):

# 1. bump the version (single source of truth for the whole package)
#    in pyproject.toml, e.g. version = "0.3.0"
git commit -am "Release 0.3.0"
git tag 0.3.0
git push origin main 0.3.0

The workflow runs the full test suite first; publishing only proceeds if it passes, and it independently double-checks that the pushed tag matches pyproject.toml's version before building, so a stray or mistyped tag fails loudly instead of publishing the wrong version. Ordinary commits to main never trigger a publish.

It authenticates to PyPI via Trusted Publishing (OIDC) — no API token is stored in this repo. This requires a one-time setup on PyPI's side: on the locus-snap PyPI project page, under PublishingAdd a new publisher, register a GitHub publisher with:

Field Value
Owner GENCARDIO
Repository name LocusSnap
Workflow name publish.yml
Environment name pypi

The pypi environment name must match environment.name in publish.yml; creating a matching GitHub Environment named pypi in this repo's settings (Settings → Environments) additionally lets you require manual approval before a publish runs, if wanted.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

locus_snap-0.3.0.tar.gz (158.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

locus_snap-0.3.0-py3-none-any.whl (114.2 kB view details)

Uploaded Python 3

File details

Details for the file locus_snap-0.3.0.tar.gz.

File metadata

  • Download URL: locus_snap-0.3.0.tar.gz
  • Upload date:
  • Size: 158.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for locus_snap-0.3.0.tar.gz
Algorithm Hash digest
SHA256 4c3e02ca99de8b533b161be94e6aeba784a9bf931a61007adcb4662b90c6c733
MD5 fa0b71780cbad0c19bcbd1dd8af5784a
BLAKE2b-256 8930983742f0f6e6c060eef0d238e24809415d6c1c92002e738480e5556826b6

See more details on using hashes here.

Provenance

The following attestation bundles were made for locus_snap-0.3.0.tar.gz:

Publisher: publish.yml on GENCARDIO/LocusSnap

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file locus_snap-0.3.0-py3-none-any.whl.

File metadata

  • Download URL: locus_snap-0.3.0-py3-none-any.whl
  • Upload date:
  • Size: 114.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for locus_snap-0.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 1e6a451c2e55415388e10b99d782911e35fe0548b5c361a088f554f897808cc4
MD5 747be0cba875f2306f1805e79235ae2a
BLAKE2b-256 f60f6cecd4b3a68e8b980b0dc2b86517af386d2a2834687cb5520b64f8787bf2

See more details on using hashes here.

Provenance

The following attestation bundles were made for locus_snap-0.3.0-py3-none-any.whl:

Publisher: publish.yml on GENCARDIO/LocusSnap

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page