Reading from N5
See original GitHub issueI have volumes stored in N5 format, and I am serving them via a local http server (using serve
). I am also running neuroglancer via npm run dev-server
. In neuroglancer, I tried setting the source source to something like n5://http://localhost:5000/$CONTAINER.n5/$DATASET
, where $CONTAINER
and $DATASET
are the names of the n5 container and the dataset I want to view, but this doesn’t work. Specifically, I get Fetching "" resulted in HTTP error 0.
How should I get this to work?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
JLPT N5 reading test - Japanesetest4you.com
Improve your Japanese significantly with our free online practice tests. We have JLPT Kanji, grammar, vocabulary, reading and listening tests in all levels....
Read more >N5 - Dokushoclub
Reading simple stories will help you recognizing the characters and familiarize you with Japanese expressions. If a text is too difficult or ...
Read more >JLPT N5 Vocabulary List Part 1 - All the vocab you need
JLPT N5 Reading · 短文(80文字) short paragraphs with about 80 characters followed by one or more questions for comprehension. · 中分 (250文字) Mid-length ......
Read more >JLPT N5 Reading Practice
What can you possibly say with the 600 words that are covered at the N5 level? Well, with a little practice you can...
Read more >N5 Reading Test - JLPT Pro
N5 Reading Test. JLPT N5. Give a solid boost to your scoring potential by practicing the exam many times. Find your weak points...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The current n5 support is rather limited. It only supports 3d volumes in the format described here: https://github.com/saalfeldlab/n5-viewer
Your data source URL then needs to be of the form:
n5://http://localhost:5000/CONTAINER.n5/DATASET/c0
CONTAINER.n5/DATASET/attributes.json should contain something like:
{ “scales”:[[1,1,1]], “pixelResolution”:{“unit”:“um”,“dimensions”:[0.097,0.097,0.18]} }
CONTAINER.n5/DATASET/c0/attributes.json should not exist (or will be ignored if it does),
and
CONTAINER.n5/DATASET/c0/s0/attributes.json should be a normal n5 dataset attributes.json file (with raw or gzip compression).
The good news is that in a local branch I have already implemented better support for n5 that does not require such a specific directory structure, and I will be pushing it out soon. It is part of a large change that also adds support for 4-d, etc. volumes, but is not quite ready yet.
I just pushed the work in progress to the ndims branch, so you can play with it if you like.
It is still a work in progress, and various things still don’t work — e.g. annotations don’t work at the moment. However, N5 support basically works, though there may be bugs.
It should work with:
Additionally you can specify attributes: “axes”: [“x”, “y”, “z”, “t”] to specify the axis names, and “units”: [“um”, “um”, “um”, “s”] to specify the units for each dimension.
Neuroglancer now aggregates attributes from all parent directories as well, so the cN directories are no longer necessary or treated specially.