Skip to content

v0.0.3: UMI extraction and exact deduplication - #7

Merged
alejandrogzi merged 4 commits into
masterfrom
v0.0.3
Aug 13, 2026
Merged

alejandrogzi merged 4 commits into
masterfrom
v0.0.3

Conversation

@alejandrogzi

Copy link
Copy Markdown
Member

What

The v0.0.3 feature release (version already bumped in Cargo.toml):

bqc umi — UMI extraction/relocation matching fastp --umi:

  • six locations (read1/read2/index1/index2/per_index/per_read)
  • fastp-compatible header tag (--umi-prefix/--umi-delimiter), both mate names
  • --umi-skip; short reads are an explicit error, never a truncated UMI
  • also a [umi] workflow stage running before correction

bqc dedup — exact whole-dataset deduplication:

  • two passes: Bloom discovery, then exact byte verification of every candidate
  • zero false deletions, deterministic, first occurrence preserved
  • parallel decode/hash and encode around a serial ordered classifier
  • memory scales with candidate families (--memory-mb)

Plus benchmarks vs fastp --umi/--dedup (bench.md + scripts), the user
guide (usage.md: bqc umi/5.7, bqc dedup/5.8, stage order, config
example) and README coverage.

Verification

cargo test: 363 passed (244 lib, 88 cbq, 6 dedup, 16 properties,
8 umi, 1 doctest).

alejandrogzi and others added 4 commits August 13, 2026 15:26
- bqc umi: six UMI locations, fastp-compatible header tagging, workflow stage
- bqc dedup: exact two-pass deduplication with parallel decode/hash/encode
- benchmarks vs fastp, user guide, README and changelog updated (v0.0.3)
process_chunk and Config::compile exceeded clippy's 100-line limit; the UMI
extraction/clipping, result translation and stage compilation move into
helpers. Behavior unchanged.
@alejandrogzi
alejandrogzi merged commit d6c9811 into master Aug 13, 2026
12 checks passed
@alejandrogzi
alejandrogzi deleted the v0.0.3 branch August 13, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant