No results hours after timelimit. about autoweka HOT 4 CLOSED

Issue turns out to be RAM related - the result buffer wasn't printing, however no message or log information was displayed to notify end user of the failure. Increases allocated memory on startup resolved the initial problem, however a bug remains such that there is no user notification of the failure.

from autoweka.

This is a difficult one unfortunately because for memory issues Auto-WEKA may not get any indication that something has gone wrong -- for example the garbage collector may simply be running pretty much all the time. Or a sub-process may simply go away without any indication that anything has gone wrong.

Suggestions of course appreciated, but I'm not aware of a way of doing this reliably.

from autoweka.

Thinking about it some more, it's more of a Weka bug that an Auto-WEKA bug. I ran into a similar issue just doing a standard (long running) classification where the process completed or hung and nothing was in the log buffer. I'd think something like that could get punted off to a tmp log file, instead it looks like its cached in mem. You can close this, I'd say, because you've just inherited the issue from Weka and it's not specific to AW.

from autoweka.

Thanks will do -- I agree that WEKA's handling of this could be better, but of course temporary files come with their own complications, so I can see why they implemented it this way.

All in all, once you run out of memory, pretty much all bets are off.

from autoweka.