google / google/neuroglancer

scales ordering in precomputed info file

Open
#237 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1.5k
Forks
389
Avg merge
3d 21h
Merged PRs (30d)
3

Description

It looks like the order of the scale metadata has an effect on how neuroglancer renders multiscale data.

Somehow tensorstore seems to occasionally mis-order the entries in the `scales` field of `info` (possibly a side-effect of delayed evaluation?), which on its own should be OK, since the elements of `scales` can and should be sorted on their resolution, not on their index. But it seems that when this mis-ordering occurs, neuroglancer fails to render all the scales. e.g., when my lowest resolution scale is the first entry in `scales`, neuroglancer only detects that scale level and will not render higher resolution scales. A solution would be to ignore the order of the `scales` metadata element and instead generate the list of scales by parsing the `resolution` property of every element in `scales`.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.