SEEK: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362003-10-03T20:44:46ZEcoinformatics Redmine
Redmine Bug #1178 (Resolved): stub actors should be editablehttps://projects.ecoinformatics.org/ecoinfo/issues/11782003-10-03T20:44:46ZChad Berkleyberkley@nceas.ucsb.edu
<p>we need to be able to edit stub actors in the same dialog that we use to create<br />them. the actor should then be recompiled and replace the existing actor.</p> Bug #1177 (Resolved): create implementation interface for stub actorshttps://projects.ecoinformatics.org/ecoinfo/issues/11772003-10-03T20:43:45ZChad Berkleyberkley@nceas.ucsb.edu
<p>There should be an interface to implement the actor stub code that is created<br />through the dynamic actor creation tool. This would basically entail<br />implementing the fire, prefire and initialize methods in the actor.</p> Bug #1176 (Resolved): allow user selected icon in dynamic actor toolhttps://projects.ecoinformatics.org/ecoinfo/issues/11762003-10-03T20:41:52ZChad Berkleyberkley@nceas.ucsb.edu
<p>The user should be able to create/select an icon to associate with the new<br />actor. Need to look into existing SVG editors. The ptolemy group has said that<br />they will not be continuing work on their icon editor for some time. We could<br />possibly continue that work for them.</p> Bug #1147 (Resolved): create agent to get data from ecogridhttps://projects.ecoinformatics.org/ecoinfo/issues/11472003-09-15T18:23:22ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to be able to access data sources from EcoGrid from within the AMS. So,<br />from within AMS (vergil) need to be able to search EcoGrid to find candidate<br />data products, and then bind those data sources to the inputs of partially<br />constructed pipelines. Eventually, we want to be able to have the pipeline<br />drive the query (e.g., from the port types), but for now the user could specify<br />an EcoGrid query to identify the data needed.</p>
<p>To close this bug:<br />1) Design a system to query and expose EcoGrid data in the workflow editor<br />2) Implement this system in conjuntion with the EcoGrid team</p> Bug #1146 (Resolved): implement GridService discovery in Ptolemyhttps://projects.ecoinformatics.org/ecoinfo/issues/11462003-09-15T18:19:40ZMatt Jonesjones@nceas.ucsb.edu
<p>Ptolemy's GUI (vergil) for creating workflows needs to be able to discover<br />GridServices on the fly so that they can be incorporated into AMS pipelines and<br />eventually executed. An initial implementation of a GridService discovery<br />component for the AMS needs to be designed and developed. There are probably<br />two principal mechanisms for this: browse and search.</p>
<p>For browsing, an "EcoGrid Services" folder could be created in the library and<br />populated by looking at the EcoGrid Registry for the list of services that are<br />available. As the Registry is not yet complete, now is a good time to specify<br />the design needs of the AMS GUI for service discovery.</p>
<p>For search, could provide a way to search for services using their metadata<br />(e.g., service name/description) as well as search by their input and output<br />port types: this is a "typed" search and could/should eventually make use of the<br />SMS services. But for now it could be a simple match based on name of the type<br />for the ports.</p>
<p>To close this bug:<br />1) Design a system for discovering and displaying EcoGrid services from within<br />the AML GUI, likely including both browsing and searching<br />2) Implement this so that grid services can be incorporated into Ptolemy<br />pipelines and executed</p> Bug #1145 (Resolved): allow execution of GridServices in AMShttps://projects.ecoinformatics.org/ecoinfo/issues/11452003-09-15T18:12:23ZMatt Jonesjones@nceas.ucsb.edu
<p>Need an agent in Ptolemy that can execute arbitrary GridServices. These are<br />basically web services with some additional, required methods that facilitate a<br />science environment, and workflow performance optimization. One thing that will<br />need to be handled is GSI authentication. To close this bug:</p>
<p>1) Develop a proposed architecture for running GridServices in ptolemy<br />2) Implement (1) for ptolemy</p> Bug #1144 (Resolved): write an agent for running R jobs in the AMShttps://projects.ecoinformatics.org/ecoinfo/issues/11442003-09-15T18:08:12ZMatt Jonesjones@nceas.ucsb.edu
<p>Need to be able to execute R from within AMS. Probably just port the monarch<br />code to do this. Later, establish a GridService that can handle this for us.</p>
<p>Close this bug by having a ptolemy agent that can execute R.</p> Bug #1064 (Resolved): create initial workflow editor from Vergilhttps://projects.ecoinformatics.org/ecoinfo/issues/10642003-05-20T16:28:44ZMatt Jonesjones@nceas.ucsb.edu
<p>SEEK participants need to be able to create and edit workflows to explore the<br />expressiveness of the language. The current version of vergil does not support<br />editing the workflow before a java wrapper class has been created. Need to<br />modify vergil to allow scientists to easily create new stub classes that<br />represent analytical steps, and then use those in a workflow. The classes can<br />be implemented later in order to execute.</p>
<p>Requirements:<br /> 1) New actors added dynamically at run time, one per analytical step<br /> 2) Actors may be only stub interface classes<br /> 3) Actors accurately reflect the I/O interface needed for the analytical task<br /> 4) Newly created actors show up in library listing<br /> 5) Newly created actors can be used in workflows<br /> 6) Serialized workflows in MoML show new actors in workflow</p>
<p>Optional but useful:<br /> 7) Person who creates the actor can set its icon</p>