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

Support for declarative value ranges

    XMLWordPrintable

Details

    Description

      We want to be able to specify a PlanningVariable value range of <X,Y> without enumerating all of the elements, where

      • the values aren't necessarily a continuous series,
      • or even numeric.

      I intend to implement this using a new value range type, referencing an interface of generic type T with following properties:

      • T getMinimum();
      • T getMaximum();
      • T getNext(T);
      • boolean hasNext(T);
      • T getRandom(Random random);
      • int getSize();

      Furthermore, I intend to provide default implementations for all number types in Java 6.

      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-211 Beta distribution (Guassian/gauss distribution) in random selection on a ValueRange

          • 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-213 ValueRangeBuilder for more complex declarative value ranges. For example every int in the range [10-100, 200-300].

          • 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

          Bug - A problem that impairs or prevents the functions of the product. PLANNER-183 @ValueRange annotation not inherited

          • 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

          Feature Request - Feature requests from customers and/or users PLANNER-60 Planner should support a null planning 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.
          • Resolved

          Feature Request - Feature requests from customers and/or users PLANNER-71 Construction heuristics should be able to scale to many planning variables with many planning values by supporting selectionCountLimit

          • 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

          Feature Request - Feature requests from customers and/or users PLANNER-190 ValueRangeProvider from a custom factory class (not Solution or entity)

          • Optional - The request should be considered desirable but is not an immediate necessity.
          • Open

          Activity

            People

              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              lpetrovi@redhat.com Lukáš Petrovický (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: