Bug 595 - simulation trajectory filtering drops too many points
Summary: simulation trajectory filtering drops too many points
Status: ASSIGNED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: Engine (show other bugs)
Version: 4.1.19
Hardware: All All
: P5 minor
Assignee: Marius Mikučionis
URL:
Depends on:
Blocks: 589
  Show dependency treegraph
 
Reported: 2015-05-14 15:13 CEST by Marius Mikučionis
Modified: 2015-06-01 12:21 CEST (History)
1 user (show)

See Also:
Architecture:


Attachments
model demonstrating the problem (2.55 KB, text/xml)
2015-05-14 15:13 CEST, Marius Mikučionis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marius Mikučionis 2015-05-14 15:13:19 CEST
Created attachment 278 [details]
model demonstrating the problem

the trajectory filtering algorithm has some dramatic effects for very long traces with many changes: at some point it just drops almost all points.

the demonstrating example is attached.

consider the following queries:

simulate 1 [<=50000] {e,  f + 100 } // works fine, albeit trajectory appears as a solid rectangle

simulate 1 [<=100000] {e,  f + 100 } // no rectangle for f anymore, looks strange

Some higher values for trace resolution parameter can postpone the problem, but I think it should still not drop all most of the values.