-
-
Notifications
You must be signed in to change notification settings - Fork 47
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
wrapped function option #152
Comments
Hi @Sh4zKh4n The generic wrapping functions available for dask arrays/images are I'm not sure I saw the presentation of Juan's you are talking about here. If you're running into memory issues, I suspect you might want to reduce the size of your chunks. There are some best practices docs for dask arrays, and for dask in general you might like to check out. With those things in mind, then you can do a little trial and error to find out what works for you. |
Here's a table of the coverage of
|
Since this is a feature request for something we're not able to implement I'm going to mark this issue as closed, but I hope that the information I've given above is helpful to you. |
Do you maybe mean skimage.util.apply_parallel? That does use |
I am wondering if there could be a function thats generic to allow wrapping other imaging libraries?
I have had problems in porting over into dask scikit image functions and ndimage functions over. Though when I look at the code for dask image, one of the functions isnt there and looks like you have a util file to wrap the ndimage.median filter to suprress certain attributes. I wonder if there is an option to make this more widely usable or documented. I think ive even seen some code by @jni in a presentation which uses dask_image.utils but the docs have no information on the utils. One of the reasons I ask is that using some of the other functions can cause memory issues and I wanter if this is to do with the output arg and the util looks like it suppresses that and adds some common args that fit into these types of libraries.
I have tried map_blocks and overlay and bpth seem to have expanding memory issues when it comes to arrays bigger than memory. Especially with bigger than memory arrays.
as an example of a func I write for a 3d array function for map blocks I ways do something like this
def func(img, args)
img2 = library.func(img, args)
return img2
out = func(img,args)
out.to_zarr('filepath.zar', ovewrite=True)
I often have memory issues and nothign is written to file. It is intialised but the it gets stuck between memory and the hard disc and not to the file. So wondered if this could be documented to allow others to use? Unless theres another option?
The text was updated successfully, but these errors were encountered: