| commit | 19382f04608d60d124379de5a8f605da59918e46 | [log] [tgz] |
|---|---|---|
| author | Sameer Agarwal <sameeragarwal@google.com> | Thu Jun 29 07:28:27 2017 -0700 |
| committer | Sameer Agarwal <sameeragarwal@google.com> | Thu Jun 29 07:34:14 2017 -0700 |
| tree | cd1aed5ddedbc48f97ad78524fbf1386e510363b | |
| parent | a9977da3eb1b87287312555ad4965fa7f8ea09e4 [diff] |
Make the Evaluator statistics key strings consistent We keep track of evaluator call and time statistics via a hashmap containing magic strings. These strings need to be consistent across the GradientProblemSolver and Solver as the LineSearchMinimizer is used by both of these solvers. Previously they were inconsistent in a manner that GradientProblemSolver was not getting information about the evaluation timing, and in the process of fixing that I made it so that the TrustRegionMinimizer when solving bounds constrained probelms will access/update this information correctly. So while I look for a more elegant solution, this CL is meant to fix the inconsistency by making sure that the same magic strings are used everywhere. Change-Id: I120ca0bd1c2f77fde2db15edd9e33286a49dbae9
Ceres Solver is an open source C++ library for modeling and solving large, complicated optimization problems. It is a feature rich, mature and performant library which has been used in production at Google since 2010. Ceres Solver can solve two kinds of problems.
Please see ceres-solver.org for more information.
Ceres development happens on Gerrit, including both repository hosting and code reviews. The GitHub Repository is a continuously updated mirror which is primarily meant for issue tracking. Please see our Contributing to Ceres Guide for more details.
The upstream Gerrit repository is
https://ceres-solver.googlesource.com/ceres-solver