-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Show progress in OpenML Experimenter #12
Comments
The cli prints per fold information. This could be transferred to the weka interface, but that would overrule default weka behavior. The benchmark information is also in the CLI. As this is not default weka behavior I completely agree. |
You agree that it would be good to show it in the GUI? |
I agree this would be great, *BUT it would be even better if this was done in the main weka repo (as our plugin inherits from that, we get it for free). |
OK, if you can convince the developers :)
On Wed, 18 Apr 2018 at 00:13 janvanrijn ***@***.***> wrote:
I agree this would be great, *BUT it would be even better if this was done
in the main weka repo (as our plugin inherits from that, we get it for
free).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABpQVzaLkKPuVnnyEeBBSrgbgJXS1fLfks5tpmj8gaJpZM4TVPz_>
.
--
Thank you,
Joaquin
|
If you do a long experiment, the 'Run' window just says 'Started' and then nothing until it is 'Finished'. For a long experiment, you have no idea whether it is still progressing or whether something went wrong. Some experiments take hours or days. If no sign of life is shown, this becomes unnerving for users.
Would it be hard to print out status updates (e.g. 'Running A on task B, Fold x')? That would be very helpful.
Ideally it should update after every fold has been completed, because sometimes even a single fold can take a long time. Or maybe do something clever where you only do this when the first fold takes more that a minute or so.
It would also be good to print a message when running the hardware benchmark. It is surprising if running a decision tree on Iris takes more than a few seconds.
The text was updated successfully, but these errors were encountered: