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

ConstraintStream API: reward/penalize don't accept negative matchWeights. Add impact() (?) that does.

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • 7.34.0.Final
    • None
    • None
    • None

    Description

      Is there a better name than "impact()"?

      impact() is basically the same as reward() without the fail-fast on negative numbers and without giving optaplanner more insight on the initializingTrend (something we don't harvest yet)

      Apply on Uni, Bi, Tri,Quad for all overloaded variants.

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. PLANNER-1803 Add test coverage for Constraint Streams' penalize()/reward()

          • 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

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

              Dates

                Created:
                Updated:
                Resolved: