You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I've found a graph where using the distance index without distances is much slower than the old snarl manager.
This came up for me because I've started running path normalization vg paths -n as a part of the mc pipeline on the unclipped graphs. And on this graph it's been running for more than a day. I've had it in gdb for a few hours, and it's still on vg::fill_in_distance_index().
It also reproduces on the command line: vg snarls finishes in about 10 minutes but the vg index version's been going for hours.
cd /private/home/hickey/dev/work/path-norm/
# slow
vg index chr2.vg.gfaffixed.clip -j chr2.vg.gfaffixed.clip.dist --snarl-limit 0
# fast
vg snarls chr2.vg.gfaffixed.clip > chr2.vg.gfaffixed.clip.snarls
The text was updated successfully, but these errors were encountered:
I think I've found a graph where using the distance index without distances is much slower than the old snarl manager.
This came up for me because I've started running path normalization
vg paths -n
as a part of the mc pipeline on the unclipped graphs. And on this graph it's been running for more than a day. I've had it in gdb for a few hours, and it's still onvg::fill_in_distance_index()
.It also reproduces on the command line:
vg snarls
finishes in about 10 minutes but thevg index
version's been going for hours.The text was updated successfully, but these errors were encountered: