Enhanced GFF updating #135
Open
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
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.
--gffoption tosplitasm, allowing user to avoid splitting the assembly at gaps that intersect features in a gff. Gff parsing conventions match (and import a function from) theragtag_correct.py-storagtag_update_gff.pythat works similar to-cfor the case of correcting a gff that has been split bysplitasm. When enabled, it handles gaps in the AGP by simply skipping any gff feature that spans multiple sequences, logging a warning to the screen. Any child features of a parent overlapping a gap will also be skipped to prevent output of orphan features, e.g a stop codon after the gap.Outside of feature enhancements, all current behavior and functionality is exactly preserved.