-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: invalid bam flag using picardtools #1027
fix: invalid bam flag using picardtools #1027
Conversation
Codecov ReportBase: 99.25% // Head: 99.25% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1027 +/- ##
========================================
Coverage 99.25% 99.25%
========================================
Files 28 28
Lines 1746 1747 +1
========================================
+ Hits 1733 1734 +1
Misses 13 13
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇 💯 🎁 🎄
Please check my comments before merging
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
This PR:
The bam files generated multiple errors showing an invalid bam flag for numerous reads. Samtools could fix a few of them, but not all. Picard tools fixmateinformation command performs better than samtools and fixes the invalid bam flags.
The possible origin of these errors could be concatenated fastq file. The current PR fixes the issue, but it would be better to use each fastq as input and merge bam files instead.
Fixed: invalid bam flag using
Picard tools
.Review and tests: