Skip to content
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

Open
joaquinvanschoren opened this issue Apr 14, 2018 · 4 comments
Open

Show progress in OpenML Experimenter #12

joaquinvanschoren opened this issue Apr 14, 2018 · 4 comments

Comments

@joaquinvanschoren
Copy link

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.

@janvanrijn
Copy link
Member

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.

@joaquinvanschoren
Copy link
Author

joaquinvanschoren commented Apr 17, 2018

You agree that it would be good to show it in the GUI?
I think it should. I'm guessing 95% of users won't use the CLI.

@janvanrijn
Copy link
Member

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).

@joaquinvanschoren
Copy link
Author

joaquinvanschoren commented Apr 17, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants