-
Notifications
You must be signed in to change notification settings - Fork 23
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
Estimate length of long homopolymers in DNA #63
Comments
Hello, Yes segmenter would probably be the tool to use. Estimation could be done roughly from sequencing speed and sampling rate, although it would be pretty rough estimate. James |
Ok, thank you for prompt response. I guess that would be still a better estimate than estimating the homopolymers length at the read level? Is the tool (Segmenter) agnostic on the chemistry (e.g. Kit 14) ? For running the I read the documentation but not too sure about setting following parameters for estimating homopolymers:
If I understand well, the output of the |
Hey, Ahh yes something like that. Let me look at that and get back to you. Need to have a look at it, it's been a few years... Also are you going from fast5, slow5, or pod5 files? James |
I have pod5 files (but otherwise I could also work with fast5 files with a simple conversion) Thanks a lot for looking into this |
Hey, do you have an example read you could share with me that has one of these homopolymers in it? It would help me a lot with what the expected bounds should be for detection. Originally, segmenter was designed around R9.4.1 cDNA (using our RAGE-seq 10X single cell data). So it's probably worth the time letting me run a read from regular DNA with a homopolymer example you want to measure so I can make sure everything is in order. James |
Hello,
Is it possible to use SquiggleKit to estimate the length of homopolymers in each read?
I guess I would have to use the Segmenter tool together with SquigglePull? However I'm not too sure about the options to use. It would be much appreciated if you could help me with this
The text was updated successfully, but these errors were encountered: