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

Bug 614 - Guarded, not enabled edge with urgent channel enforces urgency
Summary: Guarded, not enabled edge with urgent channel enforces urgency
Status: ASSIGNED
Alias: None
Product: UPPAAL
Classification: Unclassified
Component: Engine (show other bugs)
Version: 4.1.20
Hardware: PC Linux
: P5 enhancement
Assignee: Marius Mikučionis
URL:
Depends on:
Blocks:
 
Reported: 2016-09-27 01:04 CEST by Peter Gjøl Jensen
Modified: 2017-02-20 10:26 CET (History)
1 user (show)

See Also:
Architecture:

Attachments
Model provocating the error (1.58 KB, text/xml)
2016-09-27 01:04 CEST, Peter Gjøl Jensen 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Gjøl Jensen 2016-09-27 01:04:49 CEST 
Created attachment 293 [details]
Model provocating the error

Even though a warning is produced, the engine accepts the attached model, and produces erroneous results.

It seems that urgency is enforced on all edges, even though it is only present on one - which is not enabled due to a guard.

(Has been fixed in development branch stratego_2016_ndiscrete)
Comment 1 Marius Mikučionis 2017-02-20 10:26:08 CET 
Uppaal 4.1.19 implements urgency on all edges.
Stratego 4.1.20-4 does not.