Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-03-15T20:51:05ZEcoinformatics Redmine
Redmine Bug #4883 (New): Need more command line options for kar fileshttps://projects.ecoinformatics.org/ecoinfo/issues/48832010-03-15T20:51:05ZChad Berkleyberkley@nceas.ucsb.edu
<p>right now, we can execute a single workflow contained in a kar file with the -runwf command line switch. It would be nice to have more options for working with kar files on the command line. The minimal options I would like to see are:</p>
<p>1) allow the user to specify which workflow within a kar file to execute (if there is >1). <br />2) allow the user to specify the output location. Either a server or local directory.<br />3) allow the use of a remote kar file with an https url (i.e. for a kar file stored in a repository).</p>
<p>Please add more requirements as you see fit. We will add this to the queue of post-2.0 enhancements.</p> Bug #4785 (New): move cache object from 1.0 to 2.0https://projects.ecoinformatics.org/ecoinfo/issues/47852010-02-10T23:13:31ZChad Berkleyberkley@nceas.ucsb.edu
<p>Cache kar objects from 1.0 that contain customized actors (i.e. not those shipped with 1.0) need to be migrated to the 2.0 installation. Any kars that include jars must be made into modules (see bug 4702).</p> Bug #4735 (New): Allow params to be passed to ConfigurationManager from the command linehttps://projects.ecoinformatics.org/ecoinfo/issues/47352010-02-04T20:48:06ZChad Berkleyberkley@nceas.ucsb.edu
<p>Need a mechanism for passing params to CM from the command line. This is a post 2.0 feature.</p> Bug #4341 (New): rearrange the actors module into smaller moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/43412009-08-26T22:54:57ZChad Berkleyberkley@nceas.ucsb.edu
<p>I'll create a list of proposed modules for the actors currently all lumped together in the actors module. The new module names should have a naming convention of "actors-xxx" so that they all sort together and so that it's evident that the module is primarily an actor module. Once I'm done with this list, I'll post it to the wiki and we can have an email discussion about how others think the actors should be re-modularized.</p> Bug #4328 (New): change-to command checks out across brancheshttps://projects.ecoinformatics.org/ecoinfo/issues/43282009-08-21T18:54:18ZChad Berkleyberkley@nceas.ucsb.edu
<p>If kepler is currently in a branch, the change-to command should not update from the trunk. Once a branch is selected with the -Dbranch=xxx param, the build system should keep the current workspace in the branch until the user updated to another branch or the trunk. The build system should also print a banner alerting the user that he/she is working in a branch to avoid confusion.</p>
<p>this bug arose when we added several modules to the trunk. Matt was working in a branch (unknowingly) and when he ran 'ant change-to -Dsuite=kepler' it updated the kepler/module-info/modules.txt file from the trunk, but did not update the rest of the modules to the trunk so the build failed. The build-area was also running from the branch so the excludes file was not updated and would not allow him to build ptolemy.</p> Bug #4290 (In Progress): Separate the GUI from the execution engine.https://projects.ecoinformatics.org/ecoinfo/issues/42902009-08-07T21:49:07ZDavid Welkerwelker4kepler@gmail.com
<p>The GUI needs to be separated from the execution engine so that it is easy to develop specialized GUIs for a particular domain. The path for developing a new GUI that uses the execution engine should be well defined. For example, if one wanted to develop a new GUI with a different technology (i.e. Flex) or for a very specialized domain there should be a well-defined path for proceeding.</p>
<p>This is a Kepler/CORE grant requirement.</p> Bug #4287 (In Progress): Separate user error messages from developer error messages.https://projects.ecoinformatics.org/ecoinfo/issues/42872009-08-07T21:40:03ZDavid Welkerwelker4kepler@gmail.com
<p>An error in the GUI should never display a nonsensical stack trace to the user. All stack traces involving the GUI and other errors made to be read by the developer should be logged to file (and optionally standard out).</p> Bug #4260 (New): Add a test suite for the build systemhttps://projects.ecoinformatics.org/ecoinfo/issues/42602009-07-22T18:25:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>Need to create a testing harness for the build system to ensure that all functionality remains working as new features are added. This should be run with the nightly build.</p> Bug #4246 (In Progress): Reorganize code in util, core and gui moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/42462009-07-14T18:33:12ZChad Berkleyberkley@nceas.ucsb.edu
<p>The code in the main modules still needs to be reorganized a bit. There is gui code in core that needs to be moved to gui or util. The util module itself should be disassembled into other modules that are more fitting of the nature of the code. Not sure if this should be done for 2.0 or post 2.0. will target to 2.0 for now.</p> Bug #4052 (New): Should be able to store native libraries in a kar filehttps://projects.ecoinformatics.org/ecoinfo/issues/40522009-05-04T21:50:45ZChad Berkleyberkley@nceas.ucsb.edu
<p>A kar file should be able to contain native libraries needed for a given actor. These libraries should be loaded at runtime when the kar file is imported. This is an offshoot of bug 3074. We are not yet ready to implement functionality such as this, so it will have to wait until after the 2.0 release.</p> Bug #3921 (New): Exported KAR files do not correctly export private classeshttps://projects.ecoinformatics.org/ecoinfo/issues/39212009-03-31T16:25:48ZChad Berkleyberkley@nceas.ucsb.edu
<p>When exporting a KAR file, if the actor contains private classes, the private classes are not exported and an exception is thrown saying the PrivateClass is not visible. Need to look into the export paradigm to see if we can extract the private classes or whether we need to change the documentation to say that private classes are not available for export and possibly check to see if private classes exist at export time and give the user a warning.</p> Bug #3915 (New): The error dialogue won't go away.https://projects.ecoinformatics.org/ecoinfo/issues/39152009-03-24T00:11:16Zjianwu jianwujianwu@sdsc.edu
<p>Workflow: There are two composite actors, one called CompositeActor1 on the top level, another called CompositeActor2, in CompositeActor1. There are two String Parameters: one called p1 on the top level, another called p2 with value '$p1/l', in CompositeActor1. p2 is used in actors in CompositeActor1, such as expression, file open.</p>
<p>Steps: <br />1) Open the whole workflow,<br />2) Open CompositeActor1,<br />3) Open CompositeActor2,<br />4) Close CompositeActor2,<br />5) Delete CompositeActor2,<br />6) Change the value of p1.</p>
<p>There will be an error saying that: "Error evaluating expression: $p1/l in .CompositeActor2.p2 Because The ID p1 is undefined."</p>
<p>There is no way to close the error except closing Kepler by force, which will lost all unsaved modification.</p>
<p>I found the bug with Kepler version 16865 and ptolemy version 52661, but I think this bug is always there.</p>
<p>I attached the workflow and error dialogue.</p> Bug #3194 (New): add actors to support Sun Gridhttps://projects.ecoinformatics.org/ecoinfo/issues/31942008-04-01T06:58:00ZMatt Jonesjones@nceas.ucsb.edu
<p>Chirs Zhu <<a class="email" href="mailto:chris.zhu@sun.com">chris.zhu@sun.com</a>> and others at Sun have contributed actors that allow Kepler to be used as a client for the Sun Grid. They have requested that these new actors be integrated into the release. To do so, we need to:</p>
<p>1) Test the code, including development of workflow tests and unit tests as needed<br />2) Check copyright and licensing for the contribution to be sure it can be distributed under the BSD and the authors have rights to distribute<br />3) Incorporate new actor code into Kepler CVS</p>
<p>See attachments for details.</p> Bug #3189 (New): CommandLineExec needs ability to kill spawned processhttps://projects.ecoinformatics.org/ecoinfo/issues/31892008-03-26T23:01:06ZChad Berkleyberkley@nceas.ucsb.edu
<p>Many times when authoring/debugging a workflow, the process spawned by the command line actor runs infinitely. It would be good if the CLE actor kept track of the process id and could kill the process either with a special user function or when you click the stop button. Right now the only way to do this is to either kill kepler or to figure out which process is hung and kill it manually.</p> Bug #3116 (New): Web page rendering needs to be made w3c complianthttps://projects.ecoinformatics.org/ecoinfo/issues/31162008-01-31T21:22:44ZChad Berkleyberkley@nceas.ucsb.edu
<p>The rendering engine used in ptII/kepler is about 10 years out of date. It gets confused on elements like end tags and fully relies on tables for layout. We need to add a better rendering engine for showing html if we want to continue to support html documentation.</p>