Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-1872

Using an Unimproved Time Spent Termination crashes the Solver if the Solution is not fully initalized after the Construction Heuristic Phase

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • optaplanner-core
    • 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25)
    • 3
    • Hide

      Use the following solverConfig for any "big enough" problem (example: Scrabble with jbossProjects):

      <solver>
  <termination>
    <unimprovedMillisecondsSpentLimit>50</unimprovedMillisecondsSpentLimit>
  </termination>
</solver>
      Show
      Use the following solverConfig for any "big enough" problem (example: Scrabble with jbossProjects): <solver> <termination> <unimprovedMillisecondsSpentLimit> 50 </unimprovedMillisecondsSpentLimit> </termination> </solver>
    • NEW
    • NEW

      Only occurs now if the single CH step takes longer than the configured termination threshold.

      If the Unimproved Time Spent Termination Duration is less than the time needed for the Construction Heuristic to finish, the Solver crash on the Local Search phase (if one is configured).

      Expected behavior:
      Solver terminates without starting the Local Search phase

      (Per the Optaplanner docs, the Unimproved Time Spent Termination should not be applied to Construction Heuristics as they only update the best solution at the end. This provides an issue for the Spring Boot auto-configure, since it can only set global termination options).

              Unassigned Unassigned
              cchianel Christopher Chianelli (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: