Closed fm3 closed 4 years ago
I implemented the histogram route using the same data sampling strategy that is currently implemented in the webKnossos tracingstore. However, I noticed that loading 32³ voxels of data in each of the 28 sampled positions is pretty slow for some remotely hosted datasets (like, 20 seconds). Do you have an idea how we can improve on this @jstriebel ? (maybe loading different chunks on data depending on the data type?) @philippotto do you think it may be feasible to change the webknossos frontend so that viweing/tracing can already start before the histogram request completes?
Implement one of the missing routes (compare #22 ) which samples positions from the dataset to create an intensity histogram. (Integral datatypes only, for now) We still have to think about speed (took 22s for remotely hosted dataset)