You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
As mentioned in the documentation, warp_polar can be used in 3D.
Meanwhile, the performance are bad* in comparison to classical 2D warp_polar applied n-times on an array of shape (p, q) (considering an original 3D array of shape (n, p, q)).
Can this be improved ?
Thanks,
Patrick
My guess is that the for loops uses a lot less memory; that can sometimes help with performance. It's only 500MB of memory for the image, but the transformed coordinates also have to be computed and stored, so that's probably another 1500MB.
Even faster would be to precompute the warping coordinates for one slice, and to then re-apply those same coordinates repeatedly for each next slice.
Hey, there hasn't been any activity on this issue for more than 180 days. For now, we have marked it as "dormant" until there is some new activity. You are welcome to reach out to people by mentioning them here or on our forum if you need more feedback! If you think that this issue is no longer relevant, you may close it by yourself; otherwise, we may do it at some point (either way, it will be done manually). In any case, thank you for your contributions so far!
Description:
Hello,
As mentioned in the documentation, warp_polar can be used in 3D.
Meanwhile, the performance are bad* in comparison to classical 2D warp_polar applied n-times on an array of shape (p, q) (considering an original 3D array of shape (n, p, q)).
Can this be improved ?
Thanks,
Patrick
*+60 % in the example below with my PC
Way to reproduce:
Traceback or output:
No response
Version information:
The text was updated successfully, but these errors were encountered: