-
Feature Request
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
NEW
-
NEW
Read docs chapter 5.5 "explaining the score" entirely first, especially the ARM (= try(...) {}) code.
- Then add the new method SolverFactory.explainScore(Solution_), implemented in DefaultSolverFactory.
- Make use of SolverFactory.getScoreDirectorFactory()?
- Be inspired by Solver.explainBestScore().
- relates to
-
PLANNER-1892 If Solver.explainBestScore()'s has a total score that differs from the current best score, due to score corruption, throw exception that says do FULL_ASSERT
-
- Resolved
-
