This repository has been archived by the owner on Sep 12, 2018. It is now read-only.
Add assembly finishing tools to the control panel #72
Labels
Comments
fedarko
changed the title
Facilitate manual edge resolution/etc.
Add assembly finishing tools to the control panel
Jan 20, 2017
fedarko
added a commit
that referenced
this issue
Apr 16, 2017
They don't really do anything yet, but I'll add functionality for them soon.
fedarko
added a commit
that referenced
this issue
Apr 16, 2017
TODOs left for this feature (filing under the purview of #72) -- -Make scaffolds play nice with this (since we set autounselectify to true while in finishing mode). Maybe have scaffolds just highlight their nodes a certain color (via style classes or something)? Basically, I want scaffolds to be viewable during finishing mode. Right now the problem is that they aren't. -Add undo/redo buttons (for adding nodes), I guess? -Optionally (?) enforce that paths can only be constructed from adjacent nodes (e.g. if a node A is the last node on the path, then node B can only be added to the path if there exists an edge from A to B).
This was referenced Apr 16, 2017
Namely, the main things left for this issue in particular are:
I'd like to get more input on desired features before I implement these in particular. Will update this soon with TODOs. |
fedarko
added a commit
that referenced
this issue
Apr 17, 2017
can automate some stuff (e.g. auto-proceeding on unambiguous connections) -- todo, do that.
fedarko
added a commit
that referenced
this issue
Apr 24, 2017
fedarko
added a commit
that referenced
this issue
May 2, 2017
Still needs to account for unambiguous edges from first finishing node, and could stand to be more efficient. Other features to add -- coloring the "dock" node that is the source of the potential nodes to add differently, and making the code a lot more readable via reusing stuff.
This issue was moved to marbl/MetagenomeScope#11 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
And, presumably, exporting the result to a FASTA file (or modified .db file, maybe?).
The text was updated successfully, but these errors were encountered: