WIP - Large db #46
Draft
WIP - Large db #46
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP PR to enable opening a huge database (say thousands of cells per window). Neuromasts are fine, since they only have 50 cells per frame, so we can visualize around 100 frames without problems. However, the zebrafish datasets have around 5000 cells per frame, this makes: 1) the graph view extremely large and slow, and 2) the hierarchy viewer has too many segments, so also slow.
Idea:
Instead of showing all cells, we follow an individual cell. For now, this cell is chosen when opening TrackEdit (by providing the
node_id). Later, this can be extended to allow taking in a list of node_ids in combination with a widget to cycle through them.