We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://github.com/keras-team/keras/blob/master/keras/callbacks.py#L360
This would be a nice addition to the distributed framework in order to multiple checkpoints of the weights being trained upon.
The text was updated successfully, but these errors were encountered:
how does this relate to your other issue, @sd12832 ? Can you please elaborate your idea a little more?
Sorry, something went wrong.
While #131 relates to the class History https://github.com/keras-team/keras/blob/master/keras/callbacks.py#L614 and https://github.com/keras-team/keras/blob/master/keras/callbacks.py#L477, This issue is related to the class ModelCheckpoint Class https://github.com/keras-team/keras/blob/master/keras/callbacks.py#L633. We can integrate both issues into one? Especially since they are both related to bringing in callbacks functionality into Elephas.
@sd12832 yeah, I'm closing this one. let's discuss in the other. I'll make the title more generic.
No branches or pull requests
https://github.com/keras-team/keras/blob/master/keras/callbacks.py#L360
This would be a nice addition to the distributed framework in order to multiple checkpoints of the weights being trained upon.
The text was updated successfully, but these errors were encountered: