[kepler-users] Using IterateOverArray with SSH2Exec

[Edward A. Lee]

I suspect that SSH2Exec creates the identity port in its
constructor, so removing it at runtime will have no effect...
But actually, removing a port that is defined in the constructor
should not be allowed... The ports dialog should show this in
red, and should not enable the remove button.  If you were able
to remove this port, then there is a bug somewhere.

Is this actor doing something funny when it creates this port?

A workaround would be to provide an array for the identity port.
The Expression actor with a repeat() call might be useful.  E.g.,
in the Expression Evaluator:

 >> repeat(10, true)
{true, true, true, true, true, true, true, true, true, true}

Edward

At 11:58 AM 5/19/2006, Mohana Ramaratnam wrote:
>Hello,
>
>I wanted to "batch" execute a series of commands and so I designed a
>workflow with the  ptolemy.actors.lib.hoc.IterateOverArray and SSH2Exec.
>The problem that I face is with SSH2Exec.identity port. IterateOverArray
>requires every input port to be set as an array and the way I got things
>working was by removing the identity port. I clicked on apply and
>commit. I expect that commit would save my settings so that when next
>time I load the workflow xml or the compositeActor created these
>settings will be applied. This doesnt seem to be the case.
>
>So my question is how is commit different from apply in the configure
>ports dialog box?
>
>Mohana
>_______________________________________________
>Kepler-users mailing list
>Kepler-users at ecoinformatics.org
>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users

------------
Edward A. Lee
Professor, Chair of the EE Division, Associate Chair of EECS
231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
phone: 510-642-0253 or 510-642-0455, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://ptolemy.eecs.berkeley.edu/~eal