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
Optimize CREFL for memory #10
Comments
@mraspaud iirc you did this with the python version. It still requires quite a bit of memory but should we consider this closable? Or maybe we should leave it open as incentive to rewrite it in cython/C? That way we can benefit from element-wise for-loops like the original C code. |
Yes I used the python version, and I would like to keep it open for the reason you mention |
I'm closing this as dask made this much better |
Do we know if crefl actually works right now? |
nope :)
On Tue, 22 May 2018 at 20:32 David Hoese ***@***.***> wrote:
Do we know if crefl actually works right now?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#10 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAKPeoaeM2R_2q-G-3YERQ4Z_r0RNOUVks5t1FnJgaJpZM4KBRke>
.
--
Martin Raspaud, PhD
Software engineer
SMHI, SE-60176
|
No description provided.
The text was updated successfully, but these errors were encountered: