Allow using mean read length in FASTQ-trained read simulation#4855
Open
faithokamoto wants to merge 2 commits intomasterfrom
Open
Allow using mean read length in FASTQ-trained read simulation#4855faithokamoto wants to merge 2 commits intomasterfrom
faithokamoto wants to merge 2 commits intomasterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog Entry
To be copied to the draft changelog by merger:
vg sim --use-average-lengthoptionDescription
When
vg sim -Fis given a FASTQ file to try to match, it auto-detects a read length and then simulates a bunch of reads of that length. The current auto-detection logic uses the mode, i.e. the most common read length. While that works fine for short reads where the common read length is probably the target, for long reads it is problematic. This PR adds a--use-average-length/-Loption which tells the sampler to calculate an average read length and use that instead.The ideal state would probably be simulating from a read length distribution. However, we're only set up to simulate a single read length at a time, and since I'm currently doing HiFi reads (not nanopore) this is good enough for now.