Skip to content
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

desired resolution should be more explicitly about what it means #189

Open
emjoyce opened this issue Jun 4, 2024 · 0 comments
Open

desired resolution should be more explicitly about what it means #189

emjoyce opened this issue Jun 4, 2024 · 0 comments

Comments

@emjoyce
Copy link

emjoyce commented Jun 4, 2024

for example the documentation string should read something like..

if you pass for example, desired_resolution = [1,1,1] then when you have a position value of [1,1,1] in your result, that means that point is located 1 nanometers from the x,y,z origin.
if you pass desired_resolution=[4,4,40] then a value of [1,1,1] in you result means that point is 4 nanometers in x, 4 in y, and 40 in z from the x,y,z origin.

common usage patterns are

to get nanometer units

desired_resolution=[1,1,1]

to get microns

desired_resolution=[1000,1000,1000]

to get units compatible with the default neuroglancer view of a datastack

ngl_resolution = client.info.get_datastack_info()['viewer_resolution']
desired_resolution = ngl_resolution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant