-
Notifications
You must be signed in to change notification settings - Fork 74.2k
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
[TF 2.0] Provide a tool to convert checkpoints for optimizers, from TF 1.x to TF 2.0. #26353
Comments
I'm looking into this, seems reasonably straightforward. |
I am also happy to help, @dynamicwebpaige please lemme know if this issue is still open |
This Issue Looks Interesting. Anyone working on this issue? Would love to work on this.😄 |
I have been busier than I imagined, so I've just done some research and haven't started working on it. If the people above that are interested want to start outlining what such a tool would look like I'm happy to collaborate on a solution. Alternatively, I won't be offended if someone just does the whole thing. I'll continue to post as I make progress. |
@dynamicwebpaige am i in a right direction.
|
for the P0 item, A checkpoint converter tool for converting optimizers is included with the 2.0.0-beta0 release. This checkpoint converter tool is mainly for Canned Estimators, including DNN Note that, this converter is not suitable for the case where 'dnn_optimizer' If your current canned estimators and checkpoints are from TF 1.x, after you |
I think this was resolved already with the detailed guide on migrating checkpoints from TF1.x to 2.x. I am closing this issue as this was already resolved. Please feel free to reopen if I am mistaken. Thanks! |
Checkpoints will break with RNNs and shared embedding columns, which is unfortunate but acceptable. For optimizers, though, checkpoint breaking is a bit more extensive.
Ideally this feature request would result in a function or tool that could take the old checkpoint and some information about the old + new optimizers, and replace the old checkpoint with the new. This should involve some variable renaming, and some new variables added in. (Hyperparameters are now variables, so we will need to add those in to the checkpoints, and set with reasonable values-- either the defaults, or with user-specified values.)
Priority:
P0 - optimizers
P1 - RNNs
P1 - shared embeddings
The text was updated successfully, but these errors were encountered: