HapCUT2 update #11
Merged
HapCUT2 update #11
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
…pdated samtools from v1.9 to v1.10.
|
Test run on tiny-bcl successful. |
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.
HapCUT2 v1.2 had a sporadic error, discussed here:
vibansal/HapCUT2#77
This was fixed in v1.3.
Updated HapCUT2 from v1.2 to v1.3, and to avoid package conflicts also updated samtools from v1.9 to v1.10.
No changes were made in HapCUT2 from v1.2 to v1.3 that have any significant effect on LinkSeq (https://github.com/vibansal/HapCUT2/releases).
In samtools from v1.9 to v1.10 there was one change that has some change to LinkSeq (see: https://github.com/samtools/samtools/releases/tag/1.10):
The BAM files produced in LinkSeq already had
@PGheaders, so this should not have an effect on LinkSeq.