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 during unfairness mitigation #510
Comments
As noted on the original email thread, setting the logger to 'debug' level will at least get regular output from the algorithms, so users know that something is happening. |
Yeah, but that doesn't tell you much. You can sort of infer that each group of log messages is an iteration, but it's impossible to keep count... |
I haven't looked into fairlearn's GridSearch implementation so I don't know whether this is relevant, but I believe that in scikit-learn's GridSearchCV progress is printed through the joblib.Parallel dependency. |
@hildeweerts it’s definitely relevant. @adrinjalali suggested using GridSearchCV for this a while back, so if we make such a change we could get that perhaps for free. |
joblib.Parallel looks like the sort of thing we should be using to speed up GridSearch training. Would be a bit of an overkill just for adding a print statement for every iteration, though. |
How about using something like tqdm? |
That looks good as an option - please fork and PR :-) |
The consensus in #517 was not to use |
Is your feature request related to a problem? Please describe.
When running
GridSearch
orExponentiatedGradient
it may take a while to run all the iterations. It would be nice to have an idea about the progress.Describe the solution you'd like
For
GridSearch
this could be something simple likecompleted 7/100 iterations
, or perhaps something more sophisticated likecompleted 7/100 iterations, projected to finish in 4:32
. ForExponentiatedGradient
we can't know the number of iterations ahead of time, but we can tell the user how close we are to the stopping criterion as well as the current iteration number (in case we hit the maximum number of iterations).We should perhaps also think about solutions other packages have for this.
The text was updated successfully, but these errors were encountered: