Problem with fastest trace in verifydtapn

[Jiri Srba]

Open the attached net and verify the query (it should find the fastest trace that has delay 12, but it instead returns a trace with delay 13). Now add a token the the place Deadline and verify again - this time it returns the correct shortest trace with delay 12.

If the place Deadline is removed and workflow analysis (Tool/Workflow analysis) is run - remember to add 17 extra tokens - it also finds as the shortest trace the one with 13 time unit delays. Probably a problem with the fastest trace search strategy.

[Jiri Srba (srba)]

This net removed an invariant and gives a difference of two time units (14) from the optimal fastest trace with delays of 12 time units.