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

Score should keep track of the uninitialized variable count

    XMLWordPrintable

Details

    • NEW
    • NEW

    Description

      Keeping the uninitialized variable count in the Score would simplify working with uninitialized solutions - unfortunately, this would probably break backwards compatibility.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users PLANNER-361 Show intermediate results of the Construction Heuristic

          • 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
          causes

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-560 The score of the bestSolution is set before it is (fully) initialized, but from Solver.getBestSolution() it's not detectable that it's not yet initialized

          • 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

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-564 Concurrency issue when retrieving unitialized best solution

          • 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

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-510 Examples: addProblemFactChange done when not solving that causes variables to become unitialized results in wrong score in panel

          • 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

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-624 Branch and bound: Score First node exploration degraded to Depth First as a side effect of PLANNER-405

          • 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

          Task - Represents a small unit of work that is not end-user facing. PLANNER-584 Score.negate() always fails on an uninitialized score and power() maybe too

          • 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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-591 Performance regression due to PLANNER-405 because AbstractScoreDirector now tracks initScore

          • 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
          duplicates

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) PLANNER-46 getBestSolution() should be able to return partially initialized Solution (or even a completely uninitialized solution) if the CH haven't finished (or started) yet

          • 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
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-587 BendableBigDecimalScore.multiply should not affect the scale of the BigDecimals

          • 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
          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. RHDM-46 OptaPlanner Kie server: Cannot marshall best solution score

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. PLANNER-383 7.0 backwards incompatible changes for next major version

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-588 Benchmark report's standard deviation should take initScore into account and use score level labels if possible

          • 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.
          • Open

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              oskopek Ondrej Skopek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: