Make nnfwtbn Dask compatible
One should look into Dask and see how this might fit into the nnfwtbn landscape.
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Frank Sauerburger added EM::A (Urgent Important) label
added EM::A (Urgent Important) label
- Frank Sauerburger assigned to @fsauerbu
assigned to @fsauerbu
- Frank Sauerburger added Scrum::To do label
added Scrum::To do label
- Frank Sauerburger changed due date to June 09, 2020
changed due date to June 09, 2020
- Frank Sauerburger changed time estimate to 3h
changed time estimate to 3h
- Author Maintainer
Dask is probably the solution when the dateframe does not fit into memory.
- Frank Sauerburger changed title from Evaluate application of dask to Make nnfwtbn Dask compatible
changed title from Evaluate application of dask to Make nnfwtbn Dask compatible
- Frank Sauerburger added Type::Feature request label
added Type::Feature request label
- Frank Sauerburger mentioned in merge request !51 (merged)
mentioned in merge request !51 (merged)
- Frank Sauerburger created merge request !51 (merged) to address this issue
created merge request !51 (merged) to address this issue
- Author Maintainer
Dask non-compatible lines
- plot.py:470
- plot.py:623
- interface.py:82
- ROC.ipynb
Edited by Frank Sauerburger - Frank Sauerburger added 1h 45m of time spent at 2020-06-08
added 1h 45m of time spent at 2020-06-08
- Frank Sauerburger added Scrum::Doing label and removed Scrum::To do label
added Scrum::Doing label and removed Scrum::To do label
- Frank Sauerburger added 3h of time spent at 2020-06-09
added 3h of time spent at 2020-06-09
- Author Maintainer
On a superficial level this is achieved. For optimizations see #55
- Frank Sauerburger closed
closed
Please register or sign in to reply