[kepler-users] The most impressive thing you've done with Kepler

[Chad Berkley]

Hi Ketan,

That document is very old now.  All of the documentation is now in the 
actor moml files in the src/actors directory and can be accessed via the 
canvas of kepler.  I would recommend you try one of our nightly builds 
available here: http://www.kepler-project.org/nightly/zip/

We're hoping to have a release in the next couple months but we don't 
have a definite date yet.

chad

Ketan Maheshwari wrote:
> Hi Chad
> Is this the latest version of documentation:
> http://rainbow.polytech.unice.fr/~ketan/files/Actor_Docs_for_Users_In_Progress.pdf 
> 
> If so, I find many actors description ambiguous or not available. It 
> will surely be useful if some example for unconventional actors' usage 
> is provided.
> As for version: the about dialog  says this: beta1 May 2006
> However, last I heard from one of the developers that this dialog was 
> not updated with version and does not show correct version.
> Regards
> Ketan
> 
> Chad Berkley wrote:
>> Hi Ketan,
>>
>> What version of Kepler are you using?  We've spent the last year and a 
>> half reworking all of the actor documentation.  You should be able to 
>> right click on any actor and view the documentation for that actor.  
>> Are you not seeing that documentation?
>>
>> chad
>>
>> Ketan Maheshwari wrote:
>>> One more limitation, I feel is with the documentation of actor's. 
>>> There are many actors available, however, the information related to 
>>> their usage is limited. I am sure it is quite a lot of work but that 
>>> will certainly add a lot of value to Kepler's usability.
>>> Regards
>>> Ketan
>>>
>>> Ketan Maheshwari wrote:
>>>> 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 
>>>>>
>>>>>       
>>>> _______________________________________________
>>>> Kepler-users mailing list
>>>> Kepler-users at ecoinformatics.org
>>>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users 
>>>>
>>>>   
>>> _______________________________________________
>>> Kepler-users mailing list
>>> Kepler-users at ecoinformatics.org
>>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-users 
>>>