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.

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

ReadsToWiggle doesn't properly select read start and read stop #22

Open
gpratt opened this issue Jul 9, 2014 · 2 comments
Open

ReadsToWiggle doesn't properly select read start and read stop #22

gpratt opened this issue Jul 9, 2014 · 2 comments

Comments

@gpratt
Copy link
Collaborator

gpratt commented Jul 9, 2014

The code is here:

readsToWiggle.pyx
read_start = read.positions[0]
read_stop = read.positions[-1]

This will only work for positive strands, negative strands will get the END of the read. Fix is easy, just need to decide if it is easier to swap out to htseq instead of re-writing.

@mlovci
Copy link
Contributor

mlovci commented Jul 9, 2014

does htseq have the "start/middle/end" option?

@gpratt
Copy link
Collaborator Author

gpratt commented Jul 9, 2014

I'll wrap htseq a bit, but I like it more because it keeps read info for a bit longer, and is fairly fast.

I still don't use junction counting. Did you add in anything related to that with respect to clipper?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants