Path selection with `isolate` is messy in case of loops
Tharos-ux opened this issue · comments
If a loop occurs, more than required is selected for the path, resulting in a messy GFA file.
A first fix was deployed in commits e39a61c and e8db344, however it only seeks for the closest nodes that do match the following condition:
- all paths goes through the source/sink node
- there's no loop on this node
Problem: a loop can occur before, after or in between and go unnoticed. As of now, function is passing but kinda broken.
For now, isolate and neighborhood are deprecated. Will be re-implemented from scratch in the future.