-
Notifications
You must be signed in to change notification settings - Fork 6
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
How to extract most likely position of series of nodes #104
Comments
I'm not sure if this is a |
Thank you for the reply, yes I did try |
I think you could do what you're describing by using |
odgi position provides this interface. Not sure if that helps your case.
…On Fri, Mar 26, 2021, 18:48 Jordan Eizenga ***@***.***> wrote:
I think you could do what you're describing by using
for_each_step_on_handle to get all of the path steps on the node and then
using get_next_step or get_previous_step to walk the paths locally and
check for the adjacent node.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#104 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABDQEPWC2NAAB753VLBO4LTFTCITANCNFSM4ZZWSVMA>
.
|
Hello,
I've imported a pg graph in python using the bdsg module. I'm processing a series of alignments to the graph itself.
For practical reasons I'm processing them as gaf alignments generated with
vg convert -G
.For each read, I've got a path represented in the
>47102051>47102052>47102053
format. For these I can extract all the possible positions for each node on every path. However, this is quite impractical when it comes to defining the most likely contiguous set of intervals. Is there a way to extract this type of information based on this information?For example, if node
47102051
can come from "chr1:0-10" and "chr1:50-70", and node47102052
comes from chr1:11-24, then the interval succession is likely to be: chr1:0-10 > chr1:11-24. Not sure if I'm explaining my problems clearly, but I hope it makes sense.Thank you in advance,
Andrea
The text was updated successfully, but these errors were encountered: