Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362014-09-12T17:03:26ZEcoinformatics Redmine
Redmine Feature #6594 (New): cannot download from a taghttps://projects.ecoinformatics.org/ecoinfo/issues/65942014-09-12T17:03:26ZDaniel Crawldanielcrawl@gmail.com
<p>"ant change-to" downloads either from the trunk or branches. It'd be nice to also work with tags.</p> Feature #6587 (New): summarize missing actorshttps://projects.ecoinformatics.org/ecoinfo/issues/65872014-08-21T16:52:36ZDaniel Crawldanielcrawl@gmail.com
<p>If a workflow is opened that contains actors that are not present in the class path, an error dialog is displayed for each actor. It would be nice if a list of all the missing actors were displayed.</p>
<p>Attached is a modified MoMLParser.java (based on ptolemy-kepler-2.4 sources) from Philippe Huyhn that displays the missing actors. The list of missing actors is written to stdout. Using MessageHandler would be preferred since it displays a dialog, but MessageHandler appears to not allow copy and paste.</p> Feature #6575 (New): reference parameters in R actor's scripthttps://projects.ecoinformatics.org/ecoinfo/issues/65752014-07-09T21:40:18ZDaniel Crawldanielcrawl@gmail.com
<p>It would be nice if the script in the R actor could reference parameters that were added to the R actor. Currently the R actor only converts tokens read on input ports to the R script.</p> Feature #6434 (New): add workflow execution time and other metadata to report designerhttps://projects.ecoinformatics.org/ecoinfo/issues/64342014-02-28T21:11:23ZDaniel Crawldanielcrawl@gmail.com
<p>It would be nice if the report designer had drag and drop items for metadata stored in provenance such as the execution timestamp, who ran the workflow, etc.</p> Feature #5666 (New): Build system needs a target to build all common or blessed non-core moduleshttps://projects.ecoinformatics.org/ecoinfo/issues/56662012-08-07T18:07:33ZChristopher Brookscxh@eecs.berkeley.edu
<p>There should be a way to easily build all the common or "blessed" <br />non-core modules.<br />For example, "ant change-to -Dsuite=kepler" does not check out <br />reporting or tagging.</p>
<p>We should have notion of "blessed" modules, which I would say at a minumum<br />must meet two requirements:<br />1) There is someone on kepler-dev who is actively maintaining the module<br />2) There is at least one automatic test that at least does a smoke test<br />to ensure that the module works. More tests are better, but "ant test-blessed" <br />or something should do something with each module.</p>
<p>Having blessed modules would help in refactoring the tree because we<br />would have a better idea about what will break.</p> Feature #5626 (New): interacting with kepler.sh to know the status and other information in batch...https://projects.ecoinformatics.org/ecoinfo/issues/56262012-06-15T19:43:39Zjianwu jianwujianwu@sdsc.edu
<p>When we run kepler in batch mode, it's good to know its status and other information.</p>
<p>CAMERA has done something for it. Jianwu will check it.</p> Feature #5343 (New): Add optional Console viewhttps://projects.ecoinformatics.org/ecoinfo/issues/53432011-03-09T00:35:48ZSven Koehlerskoehler80@gmail.com
<p>When Kepler is not started from the command line, messages to standard output will not be visible. An optional panel on the bottom of the GUI should show the default and error output of Kepler during and after execution of a workflow.</p>