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
Added fit_generator hooks for autolog #1757
Conversation
Thanks for the patch! Looks like this is causing some existing tests to fail though. Can you fix those, and also add tests that directly cover fit_generator? |
I fixed the failing tests. In my virtual env, some small and some large tests are still failing, but the same ones as in master. |
|
||
return client.get_run(run.info.run_id) | ||
|
||
|
||
@pytest.mark.large | ||
@pytest.mark.parametrize('fit_variant', ['fit', 'fit_generator']) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, could we also add this parametrization to test_keras_autolog_model_can_load_from_artifact
so that we have test coverage verifying that autologging logs a model when fit_generator
is used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment on test coverage, otherwise LGTM!
Done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thanks @charnger!
Keras autolog hooks now work when using model.fit_generator, not just model.fit.
Keras autolog hooks now work when using model.fit_generator, not just model.fit.
What changes are proposed in this pull request?
When using keras fit_generator instead it fit, the callback hooks are currently not installed. This patch fixes it.
How is this patch tested?
Only by running it on my data. I wasn't able to run the test_keras_autolog.py without errors on master with reasonable effort yet.
Release Notes
Is this a user-facing change?
Keras autolog hooks now work when using model.fit_generator, not just model.fit.
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s) does this PR affect?
How should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes