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

Semi-pinned: Planning variable immovability (not just per entity): A planning variable can be pinned for Planner with a @PlanningPin while another variable in the same entity is not pinned

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Major
    • None
    • None
    • optaplanner-core
    • None

    Description

      Old title: Planning variable immovability (not just per entity): A planning variable can be immovable for Planner based on a SelectionFilter while another variable in the same entity is movable

      Not simple, because:

      • entities would need to be selected, but only in move selectors that actually change one of the pinned planning variables.
      • moves selectors that change multiple variables must not change pinned planning variables

      strawman napkin design:

      @PlanningEntity
class Lesson {

   @PlanningPin(variable= {"room"})
   private boolean roomLocked;

    @PlanningVariable
    private Timeslot timeslot;
    @PlanningVariable
    private Room room;

}

      Attachments

        Issue Links

          blocks

          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-175 Don't select from variables that only have one possible value

          • 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.
          • Closed
          is blocked by

          Feature Request - Feature requests from customers and/or users PLANNER-103 Planning entity immovability (AKA Planning entity locking): A planning entity can be immovable for Planner based on a SelectionFilter

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

          Activity

            People

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

              Dates

                Created:
                Updated: