This issue tracker is closed. Please visit UPPAAL issue tracker at Github instead.

Bug 64

Summary: the nature of symbolic traces should be explained in the doc
Product: UPPAAL Reporter: Juhan Ernits <juhan>
Component: DocumentationAssignee: Paul Pettersson <paupet>
Status: CLOSED FIXED    
Severity: normal    
Priority: P2    
Version: 3.4.1   
Hardware: All   
OS: All   
Architecture:

Description Juhan Ernits 2003-10-03 09:29:44 CEST 
it seems to be unintuitive to understand the symbolic traces Uppaal gives
especially in the case they happen to be unstable, i.e. they contain reachable
states from where there is no path to the final state.

Therefore there should be a concise note in the documentation for clarifying
that Uppaal actually uses symbolic traces in the simulator and how a symbolic
trace should be interpreted.

In the same context, it would be nice to have a reference to the command line
option to generate concrete traces using verifyta.
Comment 1 Paul Pettersson 2004-05-07 14:13:54 CEST 
Text updated.