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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement option to export proofreading as segmentation #8286
base: master
Are you sure you want to change the base?
Implement option to export proofreading as segmentation #8286
Changes from 7 commits
6fb59f7
684a3a2
63f31b8
a935314
70b5ef0
b0a9982
721fc70
314a057
4024aa3
33ca75b
cf3b4e7
324db91
c73f474
5ed175d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be identical, but in your variant one has to know how JS serializes number arrays. I find it better to be explicit about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If my annotation contains two volume layers and only one has an editable mapping, that property will be true. However, i I want to export the layer that has no editable mapping,
true
will still be used in this UI and sent to the backend, which seems wrong?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only proofread layers support configuring the bbox? would it be easy to always support it when exporting volume annotations? no prio though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The question then would be what the consequences of this bounding boxes should be. We are currently using Zarr Streaming (where one can specify a bounding box that should be streamed) for merging the annotations only when the annotation includes proofreading. In other cases the worker currently just downloads the whole annotation because that has proven to be faster than streaming it. I could not find an easy option to specify a bouding box in this case. However It would be easily possible to use the streaming approach whenever a bounding box was specified. This could then be faster or slower depending on the relationship of the dataset size and the size of the selected bounding boxes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this could stay as is, I think. after downloading, one could only read the bbox from the annotation. however, as I said, it doesn't have a high priority. so, if it's not a quick thing to do, nevermind :)