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 am a Master's student at Eindhoven University of Technology and the topic of my thesis is to improve the STM tool to better facilitate the exploration of pangenomes. To that end, I implemented a view that focuses on showing SV's (mostly insertions and deletions as of now) to improve horizontal scalability. The inaccuracies that are introduced by removing nodes are shown to the user by way of red "error" bars. Some other improvements regarding selecting nodes and merging tubes for vertical scalability are also in progress.
My intention was to add to the current state of the tool instead of changing is, that is why I created a fork. However, if another course of action is preferred, please let me know. Otherwise I will keep developing on that fork.
With kind regards,
Jasper
The text was updated successfully, but these errors were encountered:
That sounds quite interesting! We'd probably be interested in taking it upstream if you think you can submit it and it can be done without breaking what we already have.
Is this a new view that can be toggled on and off with some sort of control? Have you done something to factor the code appropriately to have a concept of view mode that's going to be manageable for future development?
Hello,
I am a Master's student at Eindhoven University of Technology and the topic of my thesis is to improve the STM tool to better facilitate the exploration of pangenomes. To that end, I implemented a view that focuses on showing SV's (mostly insertions and deletions as of now) to improve horizontal scalability. The inaccuracies that are introduced by removing nodes are shown to the user by way of red "error" bars. Some other improvements regarding selecting nodes and merging tubes for vertical scalability are also in progress.
My intention was to add to the current state of the tool instead of changing is, that is why I created a fork. However, if another course of action is preferred, please let me know. Otherwise I will keep developing on that fork.
With kind regards,
Jasper
The text was updated successfully, but these errors were encountered: