Hi -> I find the heavy-weight user-interface one of the limitations in Kepler. Every time I open a new workflow, it creates a new instance of Kepler rather than just opening the workflow in the existing interface. Further, if I exit from one window, all windows are closed. -> While running the web/grid services, it does not identify the methods available by parsing the WSDL and the user have to specify them, I think this capability should be easy to implement.
Regards Ketan Ilkay Altintas wrote: > > Dear All, > > I would like to collect some data to understand the current > capabilities and limitations of Kepler. > > I'd appreciate greatly if you could send me some information on your > current and past Kepler workflows in terms of: > - biggest number of actors > - longest duration of run > - data&file management and job submission capability > - technological uniqueness > - etc... > > Unfortunately, there's no Kepler badge of honor to responders, > but I'll make the interesting summary available to everyone in a few > days. ;-) > > Thanks a million on advance! > -ilkay > > > -- > Ilkay ALTINTAS > Lab Director, Scientific Workflow Automation Technologies (SWAT) > San Diego Supercomputer Center(SDSC), UCSD > 9500 Gilman Drive, MC: 0505 La Jolla, CA 92093-0505 > phone: (858) 822-5453 fax: (858) 534-8303 > web: http://users.sdsc.edu/~altintas <http://users.sdsc.edu/%7Ealtintas> > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kepler-users mailing list > Kepler-users at ecoinformatics.org > http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users >
