Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-02-04T20:48:06ZEcoinformatics Redmine
Redmine 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 #4339 (New): build system needs to provide more information on moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/43392009-08-26T20:52:27ZChad Berkleyberkley@nceas.ucsb.edu
<p>The build system has a 'describe' task that will svn cat the description.txt file of any module. This is a good start, but only the ppod module has a description.txt file. Furthermore, the description.txt file is located in the root of the module instead of in the module-info directory where such metadata should probably reside.</p>
<p>To close this bug:<br />-The description.txt file needs to be redesigned to include the following fields (whoever works on this should evaluate and probably use the kepler documentation format for this):<br /> 1) Title<br /> 2) Description<br /> 3) Author*<br /> 4) Related Modules*<br />-The description.txt file should be located in module-info<br />-All modules should have a valid description file and all core modules must have a description.txt file<br />-Modify the list-modules task to print the description, name, etc of every module in the system.</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 #4323 (In Progress): Add the "send to back" menu to keplerhttps://projects.ecoinformatics.org/ecoinfo/issues/43232009-08-18T19:49:26ZChad Berkleyberkley@nceas.ucsb.edu
<p>Ptolemy has an appearance/send to back menu that is not in kepler. We should add this and similar menus to the kepler gui.</p> Bug #4306 (In Progress): add command line params to the configurationhttps://projects.ecoinformatics.org/ecoinfo/issues/43062009-08-12T21:19:45ZChad Berkleyberkley@nceas.ucsb.edu
<p>There's been a request to have an actor know what the command line params were when Kepler was started. It should be pretty easy to add these as parameters of the configuration upon startup. An actor could then just get the configuration and look up the params.</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 #3931 (New): Get the R actor working with JNIhttps://projects.ecoinformatics.org/ecoinfo/issues/39312009-04-02T16:58:08ZChad Berkleyberkley@nceas.ucsb.edu
<p>We need to get the R actor working with JNI instead of having it make calls to the native executable. This will simplify many aspects of R, including file handling, installation and overall cohesiveness with the rest of the system.</p>
<p>Bug 3809 needs to get fixed first.</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 #3265 (New): ascToRaw needs more error handlinghttps://projects.ecoinformatics.org/ecoinfo/issues/32652008-05-02T17:41:34ZChad Berkleyberkley@nceas.ucsb.edu
<p>There are several try/catch statements in AscToRaw.java that either have nothing in the catch statement or just a single println. this should be reworked to use better error handling.</p> Bug #3205 (New): gdalTranslate actor crashes on bad format and won't work with all gdal formatshttps://projects.ecoinformatics.org/ecoinfo/issues/32052008-04-03T16:24:25ZChad Berkleyberkley@nceas.ucsb.edu
<p>Niels Hoffman reports that the gdalTranslate actor will not work with all of the current formats supported by gdal_translate. I think this is a problem with the dll or so that we have pre-compiled. We may need to recompile the jni java classes against the newer gdal libraries and include a new dll/so.</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 #3066 (New): actor sdkhttps://projects.ecoinformatics.org/ecoinfo/issues/30662008-01-16T00:41:43ZChad Berkleyberkley@nceas.ucsb.edu
<p>We need an SDK for building actors so that it is easier for people writing new java actors. the SDK would include a build file that only compiles the actor then puts the actor and any required jars into a kar file.</p> Bug #2997 (In Progress): Icons stop working after using kepler for a whilehttps://projects.ecoinformatics.org/ecoinfo/issues/29972007-11-06T22:32:37ZChad Berkleyberkley@nceas.ucsb.edu
<p>After having kepler open for some uncertain amount of time, the icons just stop working right. When you drag an actor to the canvas, the error " Error getting kar file on actor drop: For input string: "11906637555"" is displayed in the console and the icon that shows on the canvas of the newly dropped actor is either a blank box or a generic green box.</p> Bug #2895 (New): Distributed Execution Tracking Bughttps://projects.ecoinformatics.org/ecoinfo/issues/28952007-07-23T17:31:03ZChad Berkleyberkley@nceas.ucsb.edu
<p>Chad and Lucas are developing the distributed execution system for kepler. The system is currently working in a very simplified way. This bug is a consolidation of bug 1891 and bug 1899.</p>
<p>The following items need to be added:</p>
<ul>
<li>Make sure that the JNI libraries can be accessed via the slave and that the ENM actors will work on the slave</li>
</ul>
<ul>
<li>we might have to solve the problem that kepler has where you can't run multiple instances of the application with the same user account. The problem is that the cache uses an embedded database which only allows one connection at a time. the db is stored in the .kepler directory so if you try to run kepler twice at the same time, you'll get an error on the 2nd one that the db is already in use. If we have a cluster where the slave is distributed via a single home directory, this will be a problem</li>
</ul>
<ul>
<li>Matt came up with the idea of using the ecogrid registry as a way of doing node discovery.</li>
</ul>
<ul>
<li>Get this to run on the NCEAS ROCKS cluster.</li>
</ul>
<ul>
<li>we need to deal with transferring support files to the slave(s). This includes doing the indirect transfers between slaves (instead of transferring results back to the master then to the next slave, the slaves should be able to transfer data between each other).</li>
</ul> Bug #1884 (In Progress): Enable drag and drop of ports and relationshttps://projects.ecoinformatics.org/ecoinfo/issues/18842005-01-20T17:59:21ZChad Berkleyberkley@nceas.ucsb.edu
<p>you should be able to drag and drop the ports and relations instead of clicking<br />on the toolbar button and having the port appear somewhere. this functionality<br />should be similar to dragging an actor.</p>