-
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
Explore remote N5 datasets #6520
Conversation
@philippotto if you have time, maybe you could adapt the front-end to reflect the change that remote datasets can now also be n5 instead of zarr (not sure how prominently we want to promote this feature). |
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.
LGTM, love the new Explorer
hierarchy ❤️
case "" => Fox.successful(1.0) | ||
case "ym" => Fox.successful(1e-15) | ||
case "zm" => Fox.successful(1e-12) | ||
case "am" => Fox.successful(1e-9) | ||
case "fm" => Fox.successful(1e-6) | ||
case "pm" => Fox.successful(1e-3) | ||
case "nm" => Fox.successful(1.0) | ||
case "µm" => Fox.successful(1e3) | ||
case "mm" => Fox.successful(1e6) | ||
case "cm" => Fox.successful(1e7) | ||
case "dm" => Fox.successful(1e8) | ||
case "m" => Fox.successful(1e9) |
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.
Maybe this can be shared with the other unit definitions? Or are those too different?
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.
From what I’ve seen, ngff uses nanometer
while n5 uses nm
so they are pretty distinct. Of course, we could still merge the matching into one big function, what would you prefer?
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.
Let's keep it separate as-is for now 👍
The only reference I found is https://github.com/saalfeldlab/n5-viewer/blob/23f86b32e77ff1856893fa955523fb016cef3d82/README.md#container-structure,
where it says that not setting anything assumes µm
, I think that is currently not the case. Also, it specifically shows the string um
, which is missing in this list.
…jects-created * 'master' of github.com:scalableminds/webknossos: (337 commits) Fix docs for the annotation download file format (#6546) Added total runtime information to VX reports (#6543) fix VX report for completed + skipped tasks (#6540) Avoid allocating spire uint objects during apply agglomerate (#6532) Explore remote N5 datasets (#6520) Fix MeshChunk byteOffset (Long, not Int) (#6536) update browserslist (#6505) Support new Mesh File (v3) (#6491) makes workflow_yamlContent optional (#6518) Always return 404 for Failures in Zarr Streaming (#6515) Poll wk version to notify during upgrade (#6451) add script which extracts newest changelog and creates GH release for it (#6504) release 22.10.0 (#6500) voxel³ -> voxel (#6501) Allow task type summary to identify task type when creating tasks in bulk (#6486) Fix sql evolution 090 (defer not null constraint) (#6498) SQL schema cleanup (#6492) Fix validation of layer selection when trying to start globalization of floodfills (#6497) Add "shift + w" shortcut to cycle backwards through tools (#6493) Fix filtering for public datasets in dataset table (#6496) ...
Note for reviewer: git didn’t catch the renaming of ExploreRemoteLayerService. When checking the diff, note that many of its functions have been moved to other files, but not changed
URL of deployed dev instance (used for testing):
Steps to test:
Issues: