Skip to content

ValueRangeProvider: inconsistent Problem Scale reporting. #2075

@TomCools

Description

@TomCools

Describe the bug
I have used valueRangeProvider to reduce the problem scale, but this isn't shown in that metric.

Context:

  • 240 vehicles (10 vehicles, planned for 24 days, so i made separate entities for each day)
  • 6874 visits
WITH ValueRangeProvider on ENTITY (soft filter): 
Problem scale: entity count (240), variable count (240), approximate value count (1414344), approximate problem scale (1,210169 ? 10^23848).

WITH ValueRangeProvider on ENTITY (more in depth filter): 
Problem scale: entity count (240), variable count (240), approximate value count (341902), approximate problem scale (1,210166 ? 10^23848).

WITH ValueRangeProvider on SOLUTION: 
Problem scale: entity count (240), variable count (240), approximate value count (6874), approximate problem scale (1,210166 ? 10^23848)

As far as i grasp it, on Entity (soft/depth) has 1414344/341902 possible values. (the sum of all vehicle value ranges)
But on the solution, it should be 240 vehicles * 6874 visits = 1649520, which is a lot higher.

Shouldn't the approximate problem scale with ValueRangeProvider on Entity be smaller than the one on Solution?

Expected behavior

I would expect that the approximate problem scale for ValueRangeProvider on Entity would be smaller , not larger than the one on Solution.

Actual behavior

Problem scale is larger when placed on Entity, which doesn't make sense because that one is filtered on which values would be allowed on which vehicles.

To Reproduce

Environment

Timefold Solver Version or Git ref: 1.30

Output of java -version: 21

Output of uname -a or ver:

Additional information

Provide any and all other information which might be relevant to the issue.

Metadata

Metadata

Labels

No labels
No labels

Type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions