Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
GradientProblemSolver::Options does not support update_state_every_iteration #246
Comments
bchretien
changed the title from
GradientProblemSolver::Options does not support update_state_every_variable to GradientProblemSolver::Options does not support update_state_every_iteration
Dec 21, 2016
sandwichmaker
self-assigned this
Dec 21, 2016
sandwichmaker
added the
bug
label
Dec 21, 2016
|
@bchretien thanks for reporting this, yes this is a bug in gradientproblemsolver, even though the underlying machinery actually supports this. You can either submit a patch or I can look into it soonish. |
bchretien
commented
Dec 21, 2016
|
@sandwichmaker thanks for the quick reply, I probably won't have the time to work on a patch during the next few weeks, but I'll keep you posted if that changes. |
bchretien
added a commit
to bchretien/ceres-solver
that referenced
this issue
Dec 22, 2016
|
|
bchretien |
c4a6185
|
bchretien
commented
Dec 22, 2016
•
|
I think I solved the issue (cf. this). I'll forward this to Gerrit when I find the time. |
bchretien
added a commit
to bchretien/ceres-solver
that referenced
this issue
Dec 22, 2016
|
|
bchretien |
cb04240
|
bchretien
added a commit
to bchretien/ceres-solver
that referenced
this issue
Dec 22, 2016
|
|
bchretien |
b9159fb
|
|
@bchretien that CL looks pretty good. Please do consider sending it to gerrit, I will review as soon as I can. |
|
@bchretien gentle ping :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
bchretien commentedDec 21, 2016
•
edited
While implementing a callback for
GradientProblemSolver, I realized thatupdate_state_every_iterationis not supported for that kind of solver. Yet,GradientProblemSolver::Options::callbacks's documentation hints at the contrary (here):Are there any plans to support this option, or am I missing something? Otherwise, the documentation should probably be updated. Also,
update_state_every_variableis referenced, but I'm assuming this is a typo/legacy name forupdate_state_every_iteration(it is also present in some other parts of the documentation).This was tested with Ceres 1.12.0.