)]}'
{
  "commit": "19382f04608d60d124379de5a8f605da59918e46",
  "tree": "cd1aed5ddedbc48f97ad78524fbf1386e510363b",
  "parents": [
    "a9977da3eb1b87287312555ad4965fa7f8ea09e4"
  ],
  "author": {
    "name": "Sameer Agarwal",
    "email": "sameeragarwal@google.com",
    "time": "Thu Jun 29 07:28:27 2017 -0700"
  },
  "committer": {
    "name": "Sameer Agarwal",
    "email": "sameeragarwal@google.com",
    "time": "Thu Jun 29 07:34:14 2017 -0700"
  },
  "message": "Make the Evaluator statistics key strings consistent\n\nWe keep track of evaluator call and time statistics\nvia a hashmap containing magic strings. These strings\nneed to be consistent across the GradientProblemSolver\nand Solver as the LineSearchMinimizer is used by both\nof these solvers. Previously they were inconsistent\nin a manner that GradientProblemSolver was not getting\ninformation about the evaluation timing, and in the\nprocess of fixing that I made it so that the TrustRegionMinimizer\nwhen solving bounds constrained probelms will access/update\nthis information correctly.\n\nSo while I look for a more elegant solution, this CL\nis meant to fix the inconsistency by making sure that the\nsame magic strings are used everywhere.\n\nChange-Id: I120ca0bd1c2f77fde2db15edd9e33286a49dbae9\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ca49c2412a3504c7fa6205ff98f94563ebdab890",
      "old_mode": 33188,
      "old_path": "internal/ceres/gradient_problem_evaluator.h",
      "new_id": "9ccd10ee44b85bfb8db41fcd588e307dd86cdbfb",
      "new_mode": 33188,
      "new_path": "internal/ceres/gradient_problem_evaluator.h"
    },
    {
      "type": "modify",
      "old_id": "478818b349991f8314b3045a409a1a0f1439f036",
      "old_mode": 33188,
      "old_path": "internal/ceres/gradient_problem_solver.cc",
      "new_id": "ba36dd7b299a0eef4f6e1331a5108224bb6d0957",
      "new_mode": 33188,
      "new_path": "internal/ceres/gradient_problem_solver.cc"
    }
  ]
}