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

Details

    • Bug
    • Resolution: Unresolved
    • 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

    Description

      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).

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-1940 Construction heuristic does not update best solution until it finishes

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          relates to

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-2459 UnimprovedTimeMillisSpentScoreDifferenceThresholdTermination: init score improvement should reset threshold (regression?)

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated: