-
Notifications
You must be signed in to change notification settings - Fork 24
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
Zarr3 download for volume annotation, supporting nd #7288
Conversation
… additional coordinates as hardcoded ones
…o array of objects (analoguous to backend)
- enforce annotation download in zarr when having nd datasets
@@ -1035,21 +1035,28 @@ export async function downloadAnnotation( | |||
annotationType: APIAnnotationType, | |||
showVolumeFallbackDownloadWarning: boolean = false, | |||
versions: Versions = {}, | |||
volumeDataZipFormat: string = "wkw", |
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 type could be "zarr3" | "wkw"
instead of string, I think.
@@ -268,10 +278,13 @@ function _DownloadModalView({ | |||
(state: OxalisState) => state.temporaryConfiguration.isMergerModeEnabled, | |||
); | |||
const hasVolumeFallback = tracing.volumes.some((volume) => volume.fallbackLayer != null); | |||
const isVolumeNDimensional = tracing.volumes.some((tracing) => tracing.additionalAxes.length > 0); | |||
const hasVolumes = hasVolumeTracings(tracing); | |||
const initialFilesToDownload = hasVolumes ? (isVolumeNDimensional ? "zarr" : "wkw") : "nml"; |
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.
I'd rename initialFilesToDownload
and filesToDownload
to [initial]fileFormatToDownload
. otherwise, it sounds like the vars would contain arrays.
@@ -547,46 +555,42 @@ function _DownloadModalView({ | |||
}} | |||
> | |||
Select the data you would like to download. | |||
<Hint style={{ marginTop: 12 }}> | |||
An NML file will always be included with any download. |
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.
will the NML always contain the skeletons? if not, then it's not possible to download volume + skeleton at the same time? and if yes, then it's not possible to download volume without skeletons? either way, it seems as this gives less control to the user? is this intended?
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.
Indeed, skeletons are always included. This was already the case before this PR. We might want to change that in the future, but that’s unrelated to this change.
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.
Ah, I see, then never mind :)
URL of deployed dev instance (used for testing):
Steps to test:
TODOs:
Issues: