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

Planner should support a null planning value

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 6.0.0.Final
    • None
    • optaplanner-core
    • None

    Description

      Several users on the user mailing list have run into this, especially for task assignment use cases.

      Example use case:
      @PlanningEntity TaskAssignment assigns a Task to a @PlanningVariable Employee
      There are so many Tasks, that's better to not assign some Tasks for now.

      Current workaround:
      Make a Employee representing NONE,
      which is the only Employee instance that returns true on employee.isNone()
      and the score rules are written to deal with that.

      Technical difficulty to fix:
      The @PlanningVariable(s) of a @PlanningEntity with planning value null are considered to be "uninitialized".
      Partial uninitialized solution detection is fundamental for repeated planning (including real-time planning),
      because the construction heuristics need to detect which parts of the solution to intialize, but not everything because that takes too long.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users PLANNER-226 Chained=true should support nullable=true too, for example for overconstrained vehicle routing

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Open

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-12 NPE during benchmark when no solution found so far

          • 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 blocked by

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

          Feature Request - Feature requests from customers and/or users PLANNER-160 Support for declarative value ranges

          • Critical - To be worked on immediately following BLOCKER issues.
          • 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-206 Clearly define strict and non-strict 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

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: