Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362007-01-24T20:49:18ZEcoinformatics Redmine
Redmine Bug #2746 (Resolved): Documentation system does not work with java 1.6https://projects.ecoinformatics.org/ecoinfo/issues/27462007-01-24T20:49:18ZChad Berkleyberkley@nceas.ucsb.edu
<p>If you try to run 'ant generateDoc' using java 1.6, it will appear to work, but in reality, JavaDoc fails with the error "Error 1". You have to set failonerror="true" in the keplerJavadoc target to see the error. I'm not sure what is causing this but it will need to be fixed as java 1.6 becomes more popular.</p> Bug #2417 (Resolved): TRACKING: DOCUMENTATION - complete first draft of documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/24172006-04-13T23:26:00ZMatthew Brookebrooke@nceas.ucsb.edu
<p>complete first draft of documentation</p>
<p>Includes:<br />Actor Man Pages<br />Getting started guide (incl. tutorial chapters)<br />FAQ</p>
<p>(Use this bug to track dependent bugs)</p> Bug #2390 (Resolved): Documentation problem with derived actorshttps://projects.ecoinformatics.org/ecoinfo/issues/23902006-03-24T00:23:17ZDan Higginshiggins@nceas.ucsb.edu
<p>There is a problem that comes up when trying to document certain actors that<br />extend other actor classes like Source, Sink, or Transform. These examples<br />define ports called "input", "output", or both. It is useful to build new actors<br />by extending these base actor, but when one does so, the inherited ports do not<br />appear in the new class source files. Since they do not appear, a more<br />specialized use cannot be documented in JavaDoc comments in the new actor<br />extending these more basic actors.</p>
<p>One can, of course, get around this by extending TypedAtomicActor and defining<br />all ports of interest.</p> Bug #2384 (Resolved): Documentation display problems in Keplerhttps://projects.ecoinformatics.org/ecoinfo/issues/23842006-03-14T22:27:55ZDan Higginshiggins@nceas.ucsb.edu
<p>In adding documentation to the RExpression actor, I discoved a problem with<br />the documentation display in Kepler (and perhaps in Ptolemy, also).</p>
<p>Consider one parameter defined in the RExpression actor -</p>
<pre><code>/**
* The height of the output graphics bitmap in pixels<br /> */<br /> public StringParameter numYPixels;</code></pre>
<p>But later on, this parameter is created with the statement</p>
<pre><code>numYPixels = new StringParameter(this, "Number of Y pixels in image");</code></pre>
<p>Note that the display string "Number of Y pixels in image" is not the same as<br />the varible name 'numYPixels'</p>
<p>The doclet generated xml file has the proper association between the property<br />and value; i.e.</p>
<p><property name="numYPixels">The height of the output graphics bitmap in<br />pixels</property></p>
<p>But when I display the doc xml in Kepler using 'Get Documentation' the result is</p>
<p>"Number of Y pixels in image - No description"</p>
<p>The code to display the xml file replaces the 'numYPixels' name with its display<br />string 'Number of Y pixels in image' but it then loses the value! This seems to<br />happen whenever the parameter name is different than the display string; when<br />they agree, the descriptions are shown properly.</p>
<p>Dan</p> Bug #2351 (Resolved): Welcome Window Programmer/Scientist docshttps://projects.ecoinformatics.org/ecoinfo/issues/23512006-02-09T17:47:47ZChristopher Brookscxh@eecs.berkeley.edu
<p>The Welcome Window introProgrammer.htm and introScientist.htm documentation in<br />kepler/configs/ptolemy/configs/kepler/<br />needs to be updated.</p> Bug #2232 (Resolved): Website updateshttps://projects.ecoinformatics.org/ecoinfo/issues/22322005-10-17T18:03:34ZIlkay Altintasaltintas@sdsc.edu
<p>-- The webpages have a few different links to installation manuals. We need to<br />incorporate these under one unique text file (like Matt J. has in the cvs.) and<br />link it from various places on the website. The content of the pdf and word<br />files are great. They need to be copied into the text file also keeping what<br />Matt has. This needs to reflect the new build process after the kar files.</p>
<p>-- Developers tutorial needs to be integrated into the new kar architecture.</p>
<p>-- An email to kepler-dev to check and suggest changes to FAQ's. Not urgent.</p> Bug #2231 (Resolved): Documentation system implementationhttps://projects.ecoinformatics.org/ecoinfo/issues/22312005-10-17T17:58:12ZIlkay Altintasaltintas@sdsc.edu
<p>-- How-to manuals chapters for specific computational tasks (patterns of use)<br />(for example, how to do iteration in a workflow)<br />-- Generate a template automatically from the actor code and put it in the kar.<br />The detailed documentation should be later filled in manually on this template<br />by the doc writer.<br />-- Solidify the actor metadata format before Oct 26th 2005. Explain this at the<br />meeting that day. Detail: WE'LL UPDATE WHAT MATT HAS PUT TOGETHER AND ALSO<br />GENERATE DOC TEMPLATES FOR 3 EXAMPLE WORKFLOWS. Then we'll let Samantha and<br />Laura know to put it.<br />-- Go over the actor list and generate a web page including links to all the<br />kars and their documentation in a structured form.<br />-- Create an XSLT processor to format documentation from the metadata.<br />-- Implement a Java application to automatically create doc metaata templates<br />and list of actor for the webpage.</p> Bug #2137 (Resolved): create a docbook format for WF documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/21372005-07-05T21:14:02ZChad Berkleyberkley@nceas.ucsb.edu
<p>we need a docbook type format for workflow documentation. We agreed to look<br />into this at the june 05 kepler meeting. Ilkay agreed to take the lead.</p> Bug #2089 (Resolved): Problem with docs source code with Java 1.5https://projects.ecoinformatics.org/ecoinfo/issues/20892005-05-24T20:06:55ZDan Higginshiggins@nceas.ucsb.edu
<p>Documentation source code under the 'src/docs' subdirectory will not compile<br />under Java 1.5 (It does work under 1.4). This documentation code is under<br />development and removal does not affect other parts of the source.</p> Bug #1904 (Resolved): Nimrod implementation and templateshttps://projects.ecoinformatics.org/ecoinfo/issues/19042005-01-21T19:18:46ZIlkay Altintasaltintas@sdsc.edu
<p>Design (semi-)native Nimrod actors and/or use the remote Nimrod portal. Create<br />reusable patterns/templates for Nimrod based distributed execution.</p> Bug #1901 (Resolved): Documentation systemhttps://projects.ecoinformatics.org/ecoinfo/issues/19012005-01-21T19:05:01ZIlkay Altintasaltintas@sdsc.edu
<ol>
<li> Ilkay: Documentation system (Chad helps from SEEK side)
<ul>
<li>Includes way to serialize docs for atomic and composite actors (and<br />directors, and utilities, etc)<br /> o Possible way to put this documentation as linked annotations right<br />on the canvas</li>
</ul></li>
</ol> Bug #1900 (Resolved): Documentation systemhttps://projects.ecoinformatics.org/ecoinfo/issues/19002005-01-21T19:04:49ZIlkay Altintasaltintas@sdsc.edu
<ol>
<li> Ilkay: Documentation system (Chad helps from SEEK side)
<ul>
<li>Includes way to serialize docs for atomic and composite actors (and<br />directors, and utilities, etc)<br /> o Possible way to put this documentation as linked annotations right<br />on the canvas</li>
</ul></li>
</ol> Bug #1898 (Closed): Redesign the web service harvester and create design documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/18982005-01-20T19:56:04ZIlkay Altintasaltintas@sdsc.edu
<p>A document on how to do the harvesting to fit inn with the new dynamic actor<br />loading, annotation, etc. The harvested services should not be kept in the<br />repository, and they should be updated everytime the Kepler client is loaded. We<br />probably need to have a metarepository in the end to keep track of the<br />repositories and keywords that were searched and also collect some information<br />on the user's interest.</p> Bug #1892 (Resolved): Design an interface to optionally log inputs, parameters and intermediate r...https://projects.ecoinformatics.org/ecoinfo/issues/18922005-01-20T19:05:48ZIlkay Altintasaltintas@sdsc.edu
<p>Some users want to save experiment information and intermediate results. First<br />update the listen to director to give more information on the inputs and outputs<br />of the actors for each iteration. Also design formats to save this information<br />in different archives. Also proposed: different levels of verbosity for<br />monitoring of the execution.</p> Bug #1544 (Resolved): complete web service actorhttps://projects.ecoinformatics.org/ecoinfo/issues/15442004-04-30T17:45:55ZMatt Jonesjones@nceas.ucsb.edu
<p>Fix web service actor code --> Ilkay, Chad</p>
<p>This involves completing the code for a wider variety of data types, and making<br />sure that we support arrays.</p>
<p>1) New architecture for the class<br />2) Multiple output<br />3) Use java APIs<br />4) Add additional type support --> To support arrays of {int, short, long,<br />string, double, float, boolean}; Date</p>