-
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
Updated documentation #7439
Updated documentation #7439
Conversation
docs/animations.md
Outdated
|
||
A picture is worth a thousand words. In this spirit, you can use WEBKNOSSOS to create eye-catching animation of your datasets as a video clip. You can use these short movies as part of a presentation, website, for social media or to promote a publication. | ||
|
||
// animation video |
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.
TODO
docs/tooling.md
Outdated
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.
Most of these libs are deprecated. Probably not worht having a whole page and take up space in the navbar
docs/animations.md
Outdated
@@ -0,0 +1,19 @@ | |||
# Animations | |||
|
|||
A picture is worth a thousand words. In this spirit, you can use WEBKNOSSOS to create eye-catching animation of your datasets as a video clip. You can use these short movies as part of a presentation, website, for social media or to promote a publication. |
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.
A picture is worth a thousand words. In this spirit, you can use WEBKNOSSOS to create eye-catching animation of your datasets as a video clip. You can use these short movies as part of a presentation, website, for social media or to promote a publication. | |
A picture is worth more than a thousand words. In this spirit, you can use WEBKNOSSOS to create an eye-catching animation of your datasets as a video clip. You can use these short movies as part of a presentation, website, for social media or to promote a publication. |
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.
"more than" is Genglish: https://en.wikipedia.org/wiki/A_picture_is_worth_a_thousand_words
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
WEBKNOSSOS expects the following file structure for N5 datasets: | ||
|
||
``` | ||
my_dataset.n5 # One root folder per dataset |
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.
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.
Kinda. Webknossos can explore links to N5 datasets with an attributes.json that contains "multiscales" metadata, which points to the different actual arrays. This corresponds to our "mag" concept.
It can also explore N5 links to individual arrays (like, just one mag)
What you describe here looks more like our "layer" concept, but has nothing with "mags"/"multiscales". Instead, when the user has multiple n5 arrays (that are not just different multiscales/mags), they will have to input their URIs individually in webknossos.
WEBKNOSSOS expects the following file structure for Neuroglancer Precomputed datasets: | ||
|
||
``` | ||
my_dataset.precomputed # One root folder per dataset |
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.
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
Co-authored-by: Norman Rzepka <[email protected]>
@normanrz I added the feedback. PR still needs approval |
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.
Looks good. Would be good to clarify the N5 questions, tho.
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.
Sorry, looks like I never hit “submit” on these comments 🙈
|
||
WEBKNOSSOS can read [N5 datasets](https://github.com/saalfeldlab/n5). | ||
|
||
!!!info |
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 think only with full datasource-properties.json and everything
WEBKNOSSOS expects the following file structure for N5 datasets: | ||
|
||
``` | ||
my_dataset.n5 # One root folder per dataset |
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.
Kinda. Webknossos can explore links to N5 datasets with an attributes.json that contains "multiscales" metadata, which points to the different actual arrays. This corresponds to our "mag" concept.
It can also explore N5 links to individual arrays (like, just one mag)
What you describe here looks more like our "layer" concept, but has nothing with "mags"/"multiscales". Instead, when the user has multiple n5 arrays (that are not just different multiscales/mags), they will have to input their URIs individually in webknossos.
PR updates the WK docs:
URL of deployed dev instance (used for testing):
Steps to test:
DO NOT MERGE WITHOUT WK_LIBS PR
(Please delete unneeded items, merge only when none are left open)