Segment counts #360
Draft
Segment counts #360
Conversation
This file contains 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
Note that this does not work for label Paintera datasets (yet)
The actual type of the FragmentSegmentAssignment does not need to be specified. This makes relative datasets a lot easier!
Add remarks to add UI configuration for offset/resolution in the future
The number of channels is not the same as the number of mipmap levels!
The backend should not hold on to the source. Instead, it should create it on demand. WIP because of weird compilation error.
… dataset To make datasets really relative to project directory, label-block lookup has to be relative to containing Paintera dataset.
Even on a small CREMI dataset, extracting count features is pretty slow already. Use caches instead.
It is important that the user to make this decision instead of automatic, implicit conversion
- channels not deserialized correctly - channelIndex not deserialized correctly - converter not deserialized correctly - checked for wrong source class
The lookup is always provided in the Paintera dataset backend, no need to deserialize when converting.
Currently, there is still concurrent exceptions. Fix those, then get this ready for discussion!
Still experiencing concurrent modification exceptions
Before adding the data to the table, it is sorted already at the moment
|
Unfortunately, I do not think, that this will work without an explicit feature store concept. Trying to extract the counts for a larger block than CREMI (e.g. lauritzen 03) takes forever and freezes on my relatively powerful laptop. In order to proceed with this, we will need to create a fragment feature store that is pre-computed (e.g. when converting into Paintera data format) with only targeted updates after painting. This feature store can be either (1) a database or (2) N5 based |
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.
This is a WIP draft PR to track work on segment counts and how to expose them through the UI to navigate to the (next) smallest segment.
This will only be merged after #343