Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-07-21T19:59:44ZEcoinformatics Redmine
Redmine Bug #5100 (Resolved): Report Layout designed in a composite actor window is losthttps://projects.ecoinformatics.org/ecoinfo/issues/51002010-07-21T19:59:44ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>When you have a workflow with a composite actor, and you open the composite actor, its contents appear in a new kepler window. If you design a report layout in this window, and then close it, the parent workflow report designer does not show this layout. If you open the composite again, the report layout is not there either.</p>
<p>If you leave the composite actor window open with a report layout, no instance is generated for it after execution.</p>
<p>I'm not sure if or what the plan was for this scenario. Maybe switching to the Report Designer view should simply not be allowed when you're in a composite window. I think this would be a good first pass. An alternative is to keep the 2 (or N) report layout guis and objects for parent window and all opened composite actor windows in sync, and this will likely be more work.</p> Bug #5096 (Resolved): Reporting on a RecordToken failshttps://projects.ecoinformatics.org/ecoinfo/issues/50962010-07-15T00:49:16ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>I'm trying to report on a record token. I make a simple workflow with {{data = 1, timestamps = 2}} pasted in a Constant, and add Constant's output to my report design, but on execution get this error:</p>
<p>(Location of error unknown)org.apache.fop.fo.ValidationException: Error(Unknown location): fo:table-body is missing child elements. <br />Required Content Model: marker* (table-row+|table-cell+)</p>
<p>and a popup error.</p>
<p>I found someone w/ a similar error that garnered this response:<br /><a class="external" href="http://marc.info/?l=fop-user&m=120819139826155&w=2">http://marc.info/?l=fop-user&m=120819139826155&w=2</a></p> Bug #5094 (Resolved): reports do not display matrix or xml token datahttps://projects.ecoinformatics.org/ecoinfo/issues/50942010-07-14T18:08:43ZDaniel Crawldanielcrawl@gmail.com
<p>Reports do not display the contents of matrix tokens. I'm attaching an example kar.</p> Bug #5047 (Resolved): Rename the tagging docs tagging.pdfhttps://projects.ecoinformatics.org/ecoinfo/issues/50472010-06-11T18:29:02Zdebi staggsstaggs@nceas.ucsb.edu
<p>The tagging docs (tagging-2.0 > docs) need to be named tagging.pdf instead of kepler-tagging-ui.pdf</p>
<p>This is so that they can be displayed in the list of 'available documentation' for the modules.</p> Bug #5015 (Resolved): Export of runs contain different, and missing or extra reporting items nowhttps://projects.ecoinformatics.org/ecoinfo/issues/50152010-05-17T18:55:42ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>After the changes to roll ROML lsids with changes, the first export of a run kar contains less items than the second export of the same run. The first export no longer contains the RIOs, and the second export contains an extraneous ROML. An example export of a run from WRM:</p>
<p>1st export:<br />derik_test_wf_with_report_ROML.xml<br />derik_test_wf_with_report.urn.lsid.kepler-project.org.ns..1079.1.11.xml<br />WorkflowRun.1.xml</p>
<p>2nd export:<br />derik_test_wf_with_report_ROML.xml<br />ROML.1.xml<br />derik_test_wf_with_report.urn.lsid.kepler-project.org.ns..1079.1.11.xml<br />RIO.1.pdf<br />RIO.1.xml<br />WorkflowRun.1.xml</p>
<p>I don't think either of these contains the right items -- it used to be that you only get 1 ROML, so the second kar contents minus a ROML would seem right to me.</p> Bug #5014 (Resolved): Add documentation to resources for the Workflow Run Manager modulehttps://projects.ecoinformatics.org/ecoinfo/issues/50142010-05-17T18:11:41Zdebi staggsstaggs@nceas.ucsb.edu
<p>Add resources > documentation into svn, and then place the workflow-run-manager documentation there. Documentation needs to be named the same as your module name, i.e. workflow-run-manager .pdf. This is so that the Modules Documentation for the tagging module can be found by that menu action in Kepler.</p> Bug #5013 (Resolved): Add documentation to resources for Tagging modulehttps://projects.ecoinformatics.org/ecoinfo/issues/50132010-05-17T18:10:18Zdebi staggsstaggs@nceas.ucsb.edu
<p>Add resources > documentation into svn, and then place the tagging documentation there. Documentation needs to be named the same as your module name, i.e. tagging .pdf. This is so that the Modules Documentation for the tagging module can be found by that menu action in Kepler.</p> Bug #4980 (Resolved): Tagging a run now creates two identical tags in the GUIhttps://projects.ecoinformatics.org/ecoinfo/issues/49802010-05-06T00:44:54ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Sean is able to replicate this at r24224. If you tag a run in the WRM, two gui tag labels show up instead of one.</p> Bug #4979 (Resolved): ROML has type of ReportInstance instead of ReportLayout in kar manifesthttps://projects.ecoinformatics.org/ecoinfo/issues/49792010-05-05T02:11:35ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>E.g.:</p>
<p>Name: Unnamed1_ROML.xml<br />dependsOnModule: reporting<br />handler: org.kepler.kar.handlers.ReportLayoutKAREntryHandler<br />lsid: urn:lsid:kepler-project.org/ns/:951:2:1<br />type: org.kepler.reporting.rio.ReportInstance<br />dependsOn: urn:lsid:kepler-project.org/ns/:951:1:4</p>
<p>I believe this is because calling reportLayout.getClass().getName() in ReportLayoutKAREntryHandler saveReportLayout sometimes returns ReportInstance. I'm not sure why yet.</p> Bug #4977 (Resolved): Can't associate multiple sets of reporting artifacts in one kar with differ...https://projects.ecoinformatics.org/ecoinfo/issues/49772010-05-05T00:00:07ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Reporting artifacts from imported runs are no longer being put into provenance since reporting attributes are no longer stored in the WorkflowRun. I'll change the code to instead look for and insert all items found in the kar manifest that use handlers ReportLayoutKAREntryHandler or ReportInstanceKAREntryHandler.</p>
<p>Since reporting items dependOn the workflow and not the workflowRun, this is another tripping up point for multiple runs in one kar -- how will we know which reporting artifacts to associate with which run? I think putting multiple runs in one kar will require reporting artifacts dependOn the execution lsid.</p> Bug #4976 (Resolved): Importing run archive from a different namespace is brokenhttps://projects.ecoinformatics.org/ecoinfo/issues/49762010-05-04T21:13:27ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>When you import a run, the run's execId is set to the next available execId, and we attempt to increment the run's revision. Subsequent tag events on this run also increment the revision. However, if this run comes from a different namespace, it gets an entirely new lsid. There are a few problems with this at the moment:<br />- a subsequent export of this imported run will not contain the derivedFrom lsid. This is not currently stored in provenance. We can't tell who originally created the run.<br />- opening the kar again during a subsequent kepler session will again import the run with a different lsid even though it's already been imported, because the lookup to avoid this is based on the original lsid. So you end up with two runs that are the same in all ways but run lsid. This bug doesn't happen during the same kepler session.</p>
<p>I think the solution to these issues is to make sure WorkflowRuns are getting and storing referral list, and to then store and utilize the referral list in provenance.</p> Bug #4527 (Resolved): reports cannot be loaded when InstanceAuthNamespace changeshttps://projects.ecoinformatics.org/ecoinfo/issues/45272009-11-04T03:39:51ZOliver Soongsoong@nceas.ucsb.edu
<p>Generate a report and save the KAR. Close Kepler, clean-all, delete the configuration folder, LastObjectID, and .ptolemy-compiled (I think that's almost everything that Kepler generates). Run Kepler again, and open the KAR. The report layout should be there. Now close Kepler and delete only InstanceAuthNamespace. Run Kepler again and open the KAR. The report should not be there.</p>
<p>This makes it hard to transport a KAR file to another computer or even another build of Kepler.</p> Bug #4507 (Resolved): report designer losing content when there are too many itemshttps://projects.ecoinformatics.org/ecoinfo/issues/45072009-10-27T23:25:05ZOliver Soongsoong@nceas.ucsb.edu
<p>If I have a lot of items in the report designer, the scroll bar seems to be too short for the content. Eventually, there are figures that are above and below the scrollable area and are not accessible. They still show up in reports, though.</p> Bug #4457 (Resolved): Workflow Run Manager - past Report Layouts don't openhttps://projects.ecoinformatics.org/ecoinfo/issues/44572009-10-15T00:13:46ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If in WRP you create a report layout, run the workflow, quit and restart kepler, and then "Open Workflow in New Window" for this run, the workflow and report for will be viewable, but the report layout does not show up.</p> Bug #4161 (Resolved): Develop kepler workflow execution enginehttps://projects.ecoinformatics.org/ecoinfo/issues/41612009-06-15T22:06:25ZJing Taotao@nceas.ucsb.edu
<p>Here is the an email from matt:</p>
<p>I think the next stage would be to have you work on<br />putting together an execution engine that can, given a schedule of a<br />workflow to be run, can be called to retrieve the workflow KAR from<br />metacat, set up a proper staging directory for execution, and run<br />kepler, making sure that output and errors are handled properly. On<br />the output side, this means programatically calling the run manager<br />that Derik and Aaron are making to create a kar file that contains the<br />results, and then publish that to metacat (Kepler also should have an<br />API for this when Derik and Aaron are done).</p>
<p>We decided to use web service as the execution engine. The API will be:</p>
<p>1. execute(workflowID)::runID<br />2. getStatus(runID)::status</p>
<p>status includes:<br />SCHEDULED<br />EXECUTING<br />SUCCEEDED<br />FAILED<br />NOTFOUND</p>