Thanks! That solved my problem. Barbara
On Oct 20, 2009, at 8:08 PM, Jianwu Wang wrote: > Hi Barbara, > > x and y could be Parameter, StringParameter or PortParameter. They > also do not need to be in top-level, which should be executed like > kepler -runwf workflow.xml -x 4 -y.z "foo" (z is a parameter in > composite actor named y). And Port Parameters are usually used in > composite actors, so that the composite actors will have input ports > defined by the port parameters. I think Parameter or StringParameter > is better choice for your requirements. > > To set values of Parameter, StringParameter or PortParameter, you > need to double-click them, not right-click. > > I've tested a sample workflow with Kepler 1.0.0 on a Mac. It works > using with Parameter, StringParameter and PortParameter. I also > used $echoString in String Constant actor with a echoString defined > outside as a port parameter, which works for me. > > Would you please test it again by changing it to Parameter or > StringParameter? Or I can help you to test if you send me your > workflow. > > > Best wishes > > Sincerely yours > > Jianwu Wang > jianwu at sdsc.edu > http://users.sdsc.edu/~jianwu/ > > Scientific Workflow Automation Technologies (SWAT) Laboratory > San Diego Supercomputer Center University of California, San Diego > San Diego, CA, U.S.A. > > > Barbara Lerner wrote: >> Hi, >> >> I would like to be able to run a Kepler workflow from a command >> line and pass in parameter values on the command line. I have >> found in the user's manual that I can say: >> >> kepler -runwf workflow.xml -x 4 -y "foo" >> >> to set parameters x and y. >> >> Am I correct in believing that x and y would be port parameters in >> my top-level workflow in the file workflow.xml? >> >> When I try to create port parameters, it behaves differently than >> the manual indicates. I can find the PortParameter component and >> place it on my workflow. When I right-click on it, I can use >> Customize Name to change its name. The window that pops up looks >> different than the one in the manual, showing an additional field >> labeled "Display name". This seems ok, but the Configure Attribute >> seems quite different than what the manual describes. The manual >> shows a single field labeled by the name set with the Customize >> Name command. Instead, I see 3 fields: class, semanticType00 and >> semanticType11. There does not appear to be a place to set a value. >> >> It seems that might be ok since I want to pass the value in on the >> command line, but if I try to reference my parameter as the value >> parameter of a StringConstant, saying $echoString (assuming that I >> named it echoString earlier), I get the message: >> >> Error evaluating expression: $echoString >> in .Echo.String Constant.value >> Because: >> The ID echoString is undefined. >> >> Please enter a new value: >> >> So, I have several questions: >> - Can I use port parameters to get parameter values from the >> command line? >> - How do I do that? >> >> I am using Kepler 1.0.0 on a Mac. The manual is dated May 12, 2008. >> >> Thanks, >> Barbara >> >> ------------------ >> >> Barbara Lerner >> "Power to the peaceful" >> Associate >> Professor -- >> Michael Franti >> Computer Science Dept. >> Mt. Holyoke College >> >> >> >> >> _______________________________________________ >> Kepler-users mailing list >> Kepler-users at kepler-project.org >> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users ------------------ Barbara Lerner "Power to the peaceful" Associate Professor -- Michael Franti Computer Science Dept. Mt. Holyoke College
