Thanks! Is the histogram calc the only thing that was causing issues on your end?

@kushalkolar I think one thing to note is that the histogram computation right now is nice if the user's data is loaded into RAM. If otoh the user is using ImageWidge to visualize on-the-fly motion correction, things get trickier because the image array object is doing the extra work of loading from disk. In this case, the histogram computations will involve a lot of extra work (loading a large chunk of data into memory just to estimate a histogram of the data). Maybe in that case the user should be able to just specify "absolute" vmin and vmax values without a histogram. I find that knowing the range of the data (via some scale bars) is very useful, even if there is no histogram.

@kushalkolar I think one thing to note is that the histogram computation right now is nice if the user's data is loaded into RAM. If otoh the user is using ImageWidge to visualize on-the-fly motion correction, things get trickier because the image array object is doing the extra work of loading from disk. In this case, the histogram computations will involve a lot of extra work (loading a large chunk of data into memory just to estimate a histogram of the data). Maybe in that case the user should be able to just specify "absolute" vmin and vmax values without a histogram. I find that knowing the range of the data (via some scale bars) is very useful, even if there is no histogram.

Ah so you mean like the lazy arrays you have? What about allowing HistogramLUTWidget to take a pre-computed histogram?

What about data that can be lazy loaded, such as memmaps? We only use a max of 500 x 100 x 100 pixels for computing the histogram, data is subsampled to meet that max number of pixels:

https://github.com/apasarkar/fastplotlib/blob/90af0d4a136d918f99551b3fead28773693e40cf/fastplotlib/widgets/histogram_lut.py#L140-L152

We could benchmark this.

If we add a kwarg to pass in a pre-computed histogram, we can just pass an "empty" histogram with all zero bins, but have a vmin and vmax so that it can be interacted with. Or a histogram=False kwarg that will not compute the histogram and just make a "vmin-vmax" widget, i.e. exactly same thing but it just makes all bins zero without you having to pass in a precomputed one.

is this good to go? LGTM. The other points, such as just operating as a vmin-vmax widget can be done in a later PR

@kushalkolar Missed your comment about the vmin/vmax. Strongly agree we need something like that -- I will submit a pull for it.