[kepler-users] About the string constant component in the Ecogrid workflow example.

[ben leinfelder]

Hi Bina, 
I believe Jing is out today (UC holiday), but I looked at your workflow and you're only using a string constant to pass the data file name to the Metadata Source actor. You can provide the data file name to this actor in many other ways. An upstream actor might create the data file, for example, and one of that actor's output ports could be the file name that it created. The Metadata Source actor would then use that value when it received it on the 'dataFileNameIn' port.
Hope that helps,
-ben

On Mar 30, 2012, at 12:31 PM, Bina Philip wrote:

> Hello Jing,
> 
> In a previous email exchange you had given an example workflow which demonstrated the usage of EcogridWriter workflow. In this workflow the "string constant" was used to send the data file to the metadata source component.
> 
> I had one question about the "string constant" component -- Is this also capable of receiving a data file from a previous actor (which possibly generates this file) and supplies the same data file to the next actor which in the example case is the metadata source component. Basically I am trying to find out if the same string constant component can also receive as an input from another actor the data file? Kindly let me know.
> 
> Please find attached the workflow I am referring to.
> 
> In addition to this I would like to know how the fire method of the actor is triggered in the workflow. Does the actor get triggered after the necessary parameters are found or does it get triggered once the control shifts to the actor? (More of a data v/s control flow question)
> 
> Best
> 
> -- 
> Regards,
> Bina
> Indiana University Bloomington
> Dept Of Computer Science (Master's).
> Contact:- 812-327-4780
> 
> <EMLGenerator2.kar>_______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users