Tom White
Tom White
> Just for my understanding, why does this the write take another 100 bytes of RAM? Haven't you already allocated space for `c`, and counted that in your total already?...
Another reason to do this is that as a user you want to know how much memory the whole computation will take. So it would be useful to report the...
I've got a fix for this in #836 I think it would be even more useful if you could call `visualize` to get a plan that you can look at...
> Can Cubed’s spec model be extended here? Cubed has a simple model of upper bounds for memory usage, derived from knowledge about the different operations in the array API....
Thanks @shoyer! That's very useful.
> I see, this is coming from Dask. Unfortunately our experience has been that it's quite hard to keep a handle on Dask's memory usage - this is one of...
It would be useful to have the precise call to `window_by_position` (there are lots of options), and the `variant_contig` and `variant_position` data, if possible.
I've got some updates for this. First, here's a PR that gets `diversity` working under Cubed: #1291. And secondly, here's an example that computes diversity over fixed-sized windows specified by...
Thanks for trying Cubed @norlandrhagen! I think the problem may be that you need to supply a list of callbacks. I will write some docs to cover this case!
I like this suggestion.