What steps will reproduce the problem?

1.

Set up Reservoir resource problem with 4 transactions T+, T-, t-, t+:

T+ quantity +1000 at [10, INF] T- quantity -1000 at [120010, INF] t- quantity -1 at [960000, INF] t+ quantity +1 at [961200, INF]

and constraints T+ < T- and t- < t+.

('<' = 'strictly before' by some amount, e,g., (T- - T+) = 120000 and (t+ - t-) = 1200.)

2.

:SolverDecisionPoint :Solver:step :Solver:solve

in Debug.cfg

3. Run the solver.

What is the expected output? What do you see instead?

Expected:

THREAT: 960000 on Sband_Boolean.boolean_true(880) PRIORITY==200 THREAT: 961200 on Sband_Boolean.boolean_true(880) PRIORITY==200

Seen:

THREAT: 120010 on Sband_Boolean.boolean_true(880) PRIORITY==200 THREAT: 960000 on Sband_Boolean.boolean_true(880) PRIORITY==200 THREAT: 961200 on Sband_Boolean.boolean_true(880) PRIORITY==200

There should not be a flaw at 120010.

Using:IncrementalFlowProfile::calculatedLevels in Debug.cfg shows:

[IncrementalFlowProfile::calculatedLevels]Computed levels for instance at time 120010[-1000,1000]

It should be [0,1000].

Please use labels and text to provide additional information.

IncrementalFlowProfile::calculatedLevels]Computed levels for instance at time 120010[-1000,1000] [GenericFVDetector:detect]Detecting flaws and violations at time 120010 [OpenWorldFVDetector:detect]Lower limit flaw.

just before step=0. So it seems to think the +1000 transaction at time 10 could be moved beyond the -1000 transaction happening at time 12010, even though there is a temporal constraint forcing the +1000 to come before the -1000.

Certainly the +1000 transaction could be moved beyond time 120010, but then the -1000 transaction would have to move too.

It seems to be doing something like the timetable FV detector even though I am calling for the open world one.

this may be related to issue 136

I've tried recreating this problem directly (ResourceTest::testIncrementalFlowProfileIssue71) with no luck. Since there're no files attached, I'm flagging this as un-reproduceable.