Uwe,
The expression actor requires that its inputs are both present before it is executed.
In Ptolemy's DE domain, it is up to the model designer to guarauntee this.
If you don't guarauntee this, then unconsumed inputs are queued for later consumption (The behavior you describe)
Our approach has been that this aspect of the coordination between components is part of the model of computation,
and not is not something that a component cares about, except for specifying what is required of the component's
environment.
So, another approach is to change the model of computation. In particular, the HDE
(hardware discrete event) represents the communication between components as
a state variable, instead of a queue of events. In this domain, inputs to a component
are always present.
The same behavior can be created in DE using a couple of samplers and a merge, although
it is more explicit. Alternatively, you might want events to be thrown away, unless both are present, which could
also be built explicitly in DE.
Steve
------- Forwarded Message
From: Uwe Daemmrich <[EMAIL PROTECTED]> Subject: PTII3.0.2 - expression actor Date: 21 Nov 2003 14:09:50 +0100
How does expression actor behave in the DE domain, if one uses multiple input expressions and the inputs are fed with different data rates? Consider an example: in1 > in2 (boolean expr.) an in2 is fired rarely compared to in1. It appears output is fired at times of in2 (as expected intuitively) but the expression is evaluated not with in1 at the time of in2 but with some in1s before in the sequence. In fact it seems under DE expression is evaluated like under SDF but the output is fired at the times expected. Is there any simple way to let the expr. be evaluated with two input tokens of the same time?
Many thanks Uwe
------- End of Forwarded Message
---------------------------------------------------------------------------- Posted to the ptolemy-hackers mailing list. Please send administrative mail for this list to: [EMAIL PROTECTED]
