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
hi,
I'm trying to remove and actor from the actorLibrary model, change it,
then re-add it. For some reason, when it re-adds, you don't see the
changes that were made.
Here's the code that I'm using:
List l = actorLibrary.entityList();
for(int i=0; i
actor.setContainer(actorLibrary);
StringWri
Very interesting... Did you look at DEThreadActor? It has
some of what you do, but not all... In particular, it doesn't
have the (nice) feature that the director waits for active
actors to allow time to pass. This is similar to what we've
done in timed CSP and timed PN...
As for these specific qu