Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Locus start coordinate correction broken with newer versions of PySAM #11

Closed
rbonneville opened this issue Dec 18, 2017 · 1 comment
Closed

Locus start coordinate correction broken with newer versions of PySAM #11

rbonneville opened this issue Dec 18, 2017 · 1 comment
Assignees
@rbonneville
Labels
bug

Comments

@rbonneville
Copy link
Contributor

With PySam >=0.10.0, all loci report that they do not appear to be the starting sequence for a kmer.
@rbonneville rbonneville self-assigned this Dec 18, 2017
@rbonneville
Copy link
Contributor Author

With PySam 0.8.3, pysam.faidx returns a string like 'TCACACACACACACACACACACACACACACACAG'. In newer PySam, this is instead 'CHR1:6159227-6159260TCACACACACACACACACACACACACACACACAG'. This breaks starting coordinate correction.

@rbonneville rbonneville mentioned this issue Dec 18, 2017
Merged
@rbonneville rbonneville mentioned this issue Feb 27, 2018
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rbonneville rbonneville

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rbonneville