Parse scores and exon-frames in refGene.txt #3
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
Codecov Report
@@ Coverage Diff @@
## master #3 +/- ##
==========================================
+ Coverage 33.75% 33.87% +0.11%
==========================================
Files 12 12
Lines 1108 1110 +2
Branches 32 32
==========================================
+ Hits 374 376 +2
Misses 702 702
Partials 32 32
Continue to review full report at Codecov.
|
totakke
approved these changes
Dec 14, 2017
|
No, there are no apparent reason for it. Maybe it's because those fields are not used in varity. You're right. |
|
Thank you for merging! 😺 |
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.
I think it's better to parse
scoreandexon-framesin refGene.txt.If you're intentionally leaving these fields unparsed for performance reason or something, please ignore this PR.
Thank you.