[kepler-dev] [kepler-users] SDF Firing Order

[Edward A. Lee]

I have checked in a change to ptolemy.actor.lib.io.LineWriter
so it now uses a FilePortParameter instead of a FileParameter.
I checked in a MoML filter so the change should be entirely backward
compatible.  I presume this is the class that is masquerading as
org.geon.FileWrite.  Let me know if there are any problems.

Edward

At 09:38 AM 11/16/2007, you wrote:
>>> Looks to me like org.geon.FileWrite should be providing a PortParameter
>rather than a parameter to specify the file name...
>
>That would be nice and would fix this problem.
> 
>>> SDF uses data precedences to determine firing order.
>
>Does that mean I should not have to worry about the order?  I seem to be
>finding other examples where the order is wrong (i.e. not what I want).  The
>SDF precedence mechanism doesn't seem to be capable of handling this
>situation (with the actor as is).  In fact, it really has no way of knowing
>which order you want.  Either could make sense.  It would probably be a
>major change to add a feature that could be used to specify the desired
>order in cases of ambiguity.  Or maybe there is reason not to?
> 
>BTW in Kepler even though the description says it is org.geon.FileWrite, it
>is really in ptolemy.actor.lib.io.
>
>Thanks,
>
>        -Ken
>
>-----Original Message-----
>From: Edward A. Lee [mailto:eal at eecs.berkeley.edu] 
>Sent: Thursday, November 15, 2007 4:36 PM
>To: Kenneth Evans
>Cc: Kepler Mailing List
>Subject: Re: [kepler-users] SDF Firing Order
>
>
>SDF uses data precedences to determine firing order.
>Looks to me like org.geon.FileWrite should be providing a PortParameter
>rather than a parameter to specify the file name...
>
>Edward
>
>
>At 04:11 PM 11/14/2007, Kenneth Evans wrote:
>>Hi,
>> 
>>In SDF if two actors have their input ports connected to a relation, what
>determines which fires first?  Since the order may be important, is there a
>way to insure the order you want.
>> 
>>In particular, the attached example, which uses a File Writer actor with
>the fileName determined by a workspace parameter that is set by the same
>relation that determines the File Writer input, does not work correctly
>because the parameter is set after the File Writer fires.
>> 
>>Maybe there is a better way to specify a variable fileName to a File Writer
>in the first place (in which case I would appreciate some guidance), but
>this is not the only workflow in which I am having a firing-order problem.
>> 
>>Thanks,
>> 
>>        -Ken
>> 
>>
>>_______________________________________________
>>Kepler-users mailing list
>>Kepler-users at ecoinformatics.org
>>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users
>
>------------ 
>Edward A. Lee
>Chair of EECS and Robert S. Pepper Distinguished Professor
>231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
>phone: 510-642-0253, fax: 510-642-2845
>eal at eecs.Berkeley.EDU,
>http://www.eecs.berkeley.edu/Faculty/Homepages/lee.html  
>
>
>_______________________________________________
>Kepler-users mailing list
>Kepler-users at ecoinformatics.org
>http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users

------------ 
Edward A. Lee
Chair of EECS and Robert S. Pepper Distinguished Professor
231 Cory Hall, UC Berkeley, Berkeley, CA 94720-1770
phone: 510-642-0253, fax: 510-642-2845
eal at eecs.Berkeley.EDU, http://www.eecs.berkeley.edu/Faculty/Homepages/lee.html