Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-05-07T23:15:32ZEcoinformatics Redmine
Redmine Bug #5601 (Closed): Can still lose report design when saving to KARhttps://projects.ecoinformatics.org/ecoinfo/issues/56012012-05-07T23:15:32ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>It's still possible to lose your report design when you save to a KAR -- there's at least one scenario where you can see your report design in the Designer, save to KAR, and the ROML does not end up in the KAR.</p> Bug #5594 (New): use input and output port icons in Items of Interesthttps://projects.ecoinformatics.org/ecoinfo/issues/55942012-04-28T23:29:58ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Currently actor ports have a "generic file"-ish icon in the Items of Interest panel. From a user's point of view this doesn't make sense, and you can't tell the difference between in and output ports, which would be very useful.</p> Bug #5434 (Resolved): run-kar result from headless kepler.sh execution doesn't contain report art...https://projects.ecoinformatics.org/ecoinfo/issues/54342011-06-30T02:03:01ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>This thread:<br /><a class="external" href="http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2011-June/002541.html">http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/2011-June/002541.html</a><br /> prompted me to look into headless usage, esp wrt passing in workflow parameters. It's unclear to me if passing in parameters is supported by ant tasks like ant run-workflow-no-gui-server. So I began focusing on usage like:<br />./kepler.sh -runwf -nogui -myparam 7 /Users/derik/KeplerData/workflows/MyWorkflows/testwf.kar</p>
<p>If this testwf.kar contains a reportlayout (ROML), the reporting artifacts do not end up in the run-kar (or in provenance associated w/ the run) after execution if you specify parameters on the command line. If you don't pass in parameters, the run-kar contains everything it should.</p>
<p>I tracked this down to the WorkflowManager changeListener not hearing the change events on the model when it's changed for the parameter passed in. This is because the NamedObj this listener gets added to is a different instance than the one used a little bit later for execution. This is because the model can't be found in the ModelDirectory at the execution point, because it's not put in until that moment.</p>
<p>A solution to this bug is to call _openModel with the url to the temporary unzipped workflow.xml file immediately after it's created in KeplerConfigurationApplication(String[] args). Then the same NamedObj is utilized, and the WorkflowManager listener doesn't get lost.</p>
<p>I want to look at this a bit more before checking in the fix, e.g. to see if there's a better spot(s?) at which to put the model into the directory...</p> Bug #5433 (Resolved): use 1024m instead of 512m for reporting suitehttps://projects.ecoinformatics.org/ecoinfo/issues/54332011-06-28T22:28:19ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Kepler has a max memory setting of 512m by default. Increasing this to 1024m when using the reporting suite enables us to increase the hsqldb.cache_scale setting to 18 (which greatly improves workflow execution time performance when provenance is on by using more memory). Without making this change kepler will lock up with heap space errors after a few executions of data intensive workflows.</p> Bug #5337 (Resolved): NPE from WorkflowManager when configuring actor within compositehttps://projects.ecoinformatics.org/ecoinfo/issues/53372011-03-04T01:59:05ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Sometimes when you right-click Configure Actor an actor within a composite, and actually make a change, you'll get an Exception Change Failed message. This is due to an NPE from WorkflowManager.changeExecuted. oldLayout is null.</p> Bug #5307 (New): Report designer - fix drag and drop outline sizeshttps://projects.ecoinformatics.org/ecoinfo/issues/53072011-02-14T22:31:31ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>When you drag report items around, from the left out to the design, or rearranging instantiated items, the outline sizes don't match the item's size.</p> Bug #5306 (New): Report designer - make dynamic report item label textfields smallerhttps://projects.ecoinformatics.org/ecoinfo/issues/53062011-02-14T22:24:20ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If the 4 textfields on dynamic report items were slightly smaller, it'd be more apparent that they're textfields.</p> Bug #5305 (New): Report designer - make north and south dynamic item labels left justifiedhttps://projects.ecoinformatics.org/ecoinfo/issues/53052011-02-14T22:20:42ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>In the report designer, the north and south labels on a dynamic report item are centered, which does not match how the instance is rendered - left justified. Change the label positions to better reflect what gets rendered. Ideally also let these labels take up more space by spanning what are currently 2 columns in a gridlayout.</p> Bug #5304 (New): Report designer - make "+ Get Image..." button much smallerhttps://projects.ecoinformatics.org/ecoinfo/issues/53042011-02-14T22:16:44ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>On the report designer, when you drag out an Image static item, the "+ Get Image..." button on the item takes up the entire line. You can't really tell graphically that this is the case, and this makes it difficult to rearrange an Image item.</p> Bug #5301 (Resolved): clicking on Image item Scale Property Value sometimes gives ArrayIndexOutOf...https://projects.ecoinformatics.org/ecoinfo/issues/53012011-02-10T01:31:29ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Clicking on Image item Scale Property Value sometimes gives ArrayIndexOutOfBoundException, seems to happen after changing the scale of another report item.</p> Bug #5299 (New): can't drag using report designer item iconshttps://projects.ecoinformatics.org/ecoinfo/issues/52992011-02-09T20:25:54ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>You can't drag an item from its icon, and this is the first place I think a user will try, especially since it's the largest static area.</p> Bug #5298 (New): rendered west and east dynamic item label problemshttps://projects.ecoinformatics.org/ecoinfo/issues/52982011-02-09T20:16:39ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Some problems with using west and east labels on a dynamic report item:<br />1) the west and east label text wraps way too much -- with a series of four letter words, each comes out on a separate line. <br />2) the west label text can easily overlap the dynamic report item (e.g. String Constant output), a string 8 chars long will overlap<br />3) if the west label contains more than one word, the north and south text wrapping changes to also be only 1 word per line</p> Bug #5295 (Resolved): Report designer panel gui simplification and spacinghttps://projects.ecoinformatics.org/ecoinfo/issues/52952011-02-05T01:02:10ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>'Items of Interest' doesn't get enough room, and 'Report Formatting Items' gets too much.</p>
<p>The checkboxes (Show Ports, Show Attributes, Show Relations) probably take up too much room too. Also should Show Ports just always be on, and not shown? And should Show Relations even be an option? Relations can't be reported on, and don't seem very useful to me in list form.</p> Bug #5293 (Resolved): Deleting a report item scrolls you to top of designhttps://projects.ecoinformatics.org/ecoinfo/issues/52932011-02-04T01:12:58ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>This is really annoying when you're trying to delete items from a long report design; with each delete you lose your place.</p> Bug #5289 (In Progress): Change report instance margins from transparent to whitehttps://projects.ecoinformatics.org/ecoinfo/issues/52892011-02-02T02:21:41ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>At some point some months ago, I noticed report pdfs having transparent, instead of white, backgrounds, which make them hard to read. With certain viewers you can't tell, but with Photoshop and os x's Preview you can. I see they're transparent in trunk and 2.1.0. I'm not sure if they've always been this way and it's just that Preview was updated, or if it's due to a change in reporting.</p>