Added shovill-se for processing single-end reads #105
Conversation
This file contains 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
…he main shovill pipeline
bump to 1.0.7
Pull latest changes to Shovill
pull in latest changes
Bump to latest Shovill 1.1.0
|
This is really great, thanks! |
|
That's a great question, for some reason I had it in my head Lighter only supported paired-end reads. I'll get it added back |
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.
This PR addresses issue: Support single-end (SE) reads #43
I went with
shovill-seto avoid disrupting the mainshovillpipeline, and I used--se|--singleto follow how SE reads work with Snippy.I've tested each of the assemblers and received expected outputs, but I would not be opposed to further testing (@lindechun you've mentioned interest in SE support)