hparams: refactor to isolate TF dependencies #2163
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This sequence of commits turns the current
api
module into a wrapperaround two modules,
callback
(which depends on TensorFlow and onlyprovides the Keras callback) and
summary_v2
(which does not, andprovides everything else). Thus, it is now possible in principle to
write hparams summaries without a TensorFlow dependency, though in
practice
summary_v2
is currently implemented in terms ofsummary
,which depends on the TensorFlow copy of the
Summary
proto.This is an internal refactor; the demo code is unchanged.
Reorganization to match the structure described here:
#2139 (comment)
Test Plan:
Existing unit tests retained, up to refactoring. The demo still works.
wchargin-branch: hparams-api-refactor