-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Exposing solver callbacks to python #3020
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
philkr
force-pushed
the
python_solver_callback
branch
2 times, most recently
from
September 18, 2015 21:17
a27adf4
to
a683f9e
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
September 21, 2015 22:01
a683f9e
to
60d82c0
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
September 29, 2015 01:43
60d82c0
to
b7a9e7b
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
October 14, 2015 18:05
b7a9e7b
to
7aa3265
Compare
philkr
force-pushed
the
python_solver_callback
branch
2 times, most recently
from
October 30, 2015 20:16
ed660f8
to
53f37c0
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
January 6, 2016 14:38
53f37c0
to
a765b56
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
January 15, 2016 18:25
a765b56
to
7bc5a0c
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
January 23, 2016 20:55
7bc5a0c
to
107899e
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
February 29, 2016 20:42
107899e
to
38ca256
Compare
philkr
force-pushed
the
python_solver_callback
branch
2 times, most recently
from
April 29, 2016 20:36
00eb614
to
35e91e5
Compare
philkr
force-pushed
the
python_solver_callback
branch
2 times, most recently
from
May 27, 2016 20:20
4a304ba
to
b97e74c
Compare
+1 This is a great addition. Code is elegant. Please accept this pull request. |
@longjon @shelhamer thoughts? |
|
philkr
force-pushed
the
python_solver_callback
branch
from
June 17, 2016 21:35
b97e74c
to
5506065
Compare
philkr
force-pushed
the
python_solver_callback
branch
from
June 17, 2016 21:37
5506065
to
dec2381
Compare
All LGTM now. Thanks @philkr! |
Any examples how to use this? |
fxbit
pushed a commit
to Yodigram/caffe
that referenced
this pull request
Sep 1, 2016
Exposing solver callbacks to python
@kli-nlpr A simple and nice example can be found at this SO thread. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR exposes the solver callbacks to python. They can be added by calling
solver.add_callback(on_start, on_gradient)
, whereon_start
andon_gradient
are python functions.