Repository navigation
feat: add --includelist option to simulate fastq-reads - #198
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds a new CLI option 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #198 +/- ##
==========================================
+ Coverage 86.12% 88.00% +1.87%
==========================================
Files 110 111 +1
Lines 51974 52464 +490
==========================================
+ Hits 44765 46173 +1408
+ Misses 7209 6291 -918 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/commands/simulate/fastq_reads.rs`:
- Around line 266-278: When overriding umi_length from includelist (the
includelist variable -> list[0].len()), validate that the includelist UMI length
does not exceed the configured read length (e.g., self.common.read_length) and
reject the request if it does: instead of silently overriding and truncating
later, return an error (or bail) with a clear message referencing the
includelist UMI length and read length; update the same validation logic at the
other includelist-handling site around the second occurrence (the block at
~580-587) so both places enforce list[0].len() <= read_length before assigning
umi_length or using the UMI. Ensure you reference the variables includelist,
umi_length, self.common.umi_length, and self.common.read_length when
implementing the check and message.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 7e8cde8d-ac67-435c-8de0-e565b260be94
📒 Files selected for processing (1)
src/commands/simulate/fastq_reads.rs
6e250d8 to
37156bb
Compare
When provided, UMIs are sampled from the includelist file instead of generated randomly. This enables generating synthetic FASTQ data that exercises the full correct → extract → ... → consensus pipeline, since the reads will contain UMIs from a known whitelist that fgumi correct can match against. The includelist file format is one UMI per line (same as fgumi correct). All UMIs must be the same length, which overrides --umi-length with a warning if they differ. Blank lines are skipped, lowercase is uppercased, and non-ACGT bases are rejected.
37156bb to
23dad2a
Compare
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
|
@coderabbitai review |
✅ Actions performedReview triggered.
|
Summary
--includelist/-ioption tofgumi simulate fastq-readsthat samples UMIs from a whitelist file instead of generating them randomly--umi-length(with a warning if they differ)This enables generating synthetic FASTQ data that exercises the full
correct → extract → ... → consensuspipeline in fgumi-benchmarks, since reads contain UMIs from a known whitelist thatfgumi correctcan match against.Test plan
load_includelist(valid, lowercase, blank lines, invalid bases, mismatched lengths, empty file)