A token that is a condition tied to a goal can be dispatched even though other
preceding conditions are not observed.
This is es-ecially true in the case where one condition is not dispatched (e.g
on an Observed timeline) and starts before another condition which is
dispatch-able. In such case one can often see the diapatch-able condition being
sent even though the observable condition was not yet met.
We need to implement guarding mechanisms in order to protect from such
situation.
This bug was seen in the lsts.nddl model from revision r1388
It can be resolved by protecting the dispatched token within an if guard that
tests the start time against TREX_CLOCK but should be handled in a more natural
way in the future.
Original issue reported on code.google.com by fre...@gmail.com on 6 May 2013 at 8:05
Original issue reported on code.google.com by
fre...@gmail.com
on 6 May 2013 at 8:05