CELE-126 Allows the EM viewer to not have any segmentation information #80
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.
Currently, the EM viewer assumes that segmentation information will be present. The basic information for the segmentation impacts the “extent” of the EM viewer, which is used to computer properly the size of the final canvas and ensure that the positions of the polygons when a segmentation is displayed is there.
There is some dataset that might not have a segmentation, we need to tackle those cases.
Various aspect of the software need to be modified:
Changes:
emData. maxResolution
with the maximum resolution of the EM tilesmaxResolution
is calculated during dataset ingestion and pushed in to the bucketmaxResolution
is saved in to the DB when the files are ingestedNoEMData
component instead of the EM viewer 1maxResolution
) in the EM viewer (something is not working correctly and needs to be understood why)python -m ingestion.em_metadata ../data/witvliet_2020_7/em
Footnotes
↩