Ecoinformatics Redmine: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-03-12T18:53:40ZEcoinformatics Redmine
Redmine Kepler - Bug #4881 (New): RExpression outputs [false] for any matrix of booleanshttps://projects.ecoinformatics.org/ecoinfo/issues/48812010-03-12T18:53:40ZOliver Soongsoong@nceas.ucsb.edu
<p>In an RExpression, add an output port "out" and use this R script:</p>
<p>out <- matrix(c(TRUE, FALSE, TRUE, FALSE), 2)</p>
<p>I get [false] as the output token, which seems to be because RExpression.java on line 1108 says:</p>
<p>mt = new BooleanMatrixToken();</p>
<p>instead of:</p>
<p>mt = new BooleanMatrixToken(valS);</p>
<p>or something similar. I'm not actually sure such a constructor exists, but it seems like it should given the other constructors in the lines before.</p> Kepler - Bug #4880 (New): RExpression cannot output matrix of stringshttps://projects.ecoinformatics.org/ecoinfo/issues/48802010-03-12T18:45:03ZOliver Soongsoong@nceas.ucsb.edu
<p>Create an RExpression with the output port "out" and for the script, use:</p>
<p>out <- matrix(letters, 2)</p>
<p>Looking at the code, it seems as if a matrix of strings was never really considered. Commas in the strings would likely cause problems, and I don't actually know if there's a StringMatrixToken.</p> Kepler - Bug #4879 (New): RExpression replaces ) in string vectors with } when outputting to a porthttps://projects.ecoinformatics.org/ecoinfo/issues/48792010-03-12T18:37:49ZOliver Soongsoong@nceas.ucsb.edu
<p>In an RExpression, create the output port "out" and in the R script, use:</p>
<p>out <- c("(", ")")</p>
<p>Hooking this to a Display actor, I get {"(", "}"}. This is because RExpression.java line 1139 (I think) has:</p>
<p>temp = temp.replace(')', '}');</p>
<p>which replaces all occurrences of ), even within the string.</p> Kepler - Bug #4872 (Resolved): listen to director throws errorhttps://projects.ecoinformatics.org/ecoinfo/issues/48722010-03-05T22:14:10ZOliver Soongsoong@nceas.ucsb.edu
<p>Add an SDF Director and the Tools->Listen to Director. An error pops up on the console:</p>
<p>Error creating action for class: org.kepler.gui.RunWithFeedbackChkBoxAction : null<br />Error creating action for class: org.kepler.gui.RunWithFeedbackChkBoxAction</p>
<p>I'm not sure if this causes problems or not.</p> Kepler - Bug #4870 (New): searching for packages with the same name from multiple sources sometim...https://projects.ecoinformatics.org/ecoinfo/issues/48702010-03-04T22:23:52ZOliver Soongsoong@nceas.ucsb.edu
<p>I have packages soong.4.14 and soong.28.5 on DEV and soong.4.15 and soong.28.9 on KNB. They all have the same title. The DEV packages require authentication to access the data but not to search. The KNB packages require authentication to search and access the data. If I search authenticated KNB or authenticated DEV individually, I see 2 entries. If I search authenticated KNB and authenticated DEV at the same time, I only see 3. I think this is caused by the way search records are "uniquely" named.</p> Kepler - Bug #4869 (In Progress): changes made to workflows during dialogs before committing (Edi...https://projects.ecoinformatics.org/ecoinfo/issues/48692010-03-04T19:04:24ZOliver Soongsoong@nceas.ucsb.edu
<p>When I make changes to an actor through the dialog, it seems like the changes are made to the workflow immediately, before the "Commit" button is clicked.</p>
<p>For example, create a workflow with an EML 2 Dataset actor. Make sure Kepler has not already authenticated with KNB. Now edit the EML 2 Dataset actor to reference a data package that requires authentication. The KNB login window will immediately pop up, even though no changes have been committed. Dismiss the window in some way. Now click the Help button and close the help window. The dialog will have disappeared. Open the actor dialog again, and the change will be there.</p>
<p>I should point out that the "Cancel" button does seem to work, but I suspect (based on debugging comments and comments in code) that this acts by reverting the changes already made.</p>
<p>I've seen this for sure on EML 2 Dataset and RExpression, since changes to one trigger visual feedback and I've mucked around in the code of the other. I suspect this is a general problem, though, and it may be a result of the underlying ptolemy design.</p> Kepler - Bug #4764 (New): ProvenanceRecorder.changeExecuted slow after workflow runhttps://projects.ecoinformatics.org/ecoinfo/issues/47642010-02-06T02:19:48ZOliver Soongsoong@nceas.ucsb.edu
<p>If I run any of the tpc workflows (e.g., tpc09), any subsequent changes to Kepler (say changing workflow parameters) cause Java to peg one of my CPU cores. This includes canceling changes to RExpression. I've seen this behavior on Windows XP and 7. While I haven't seen it under linux or OS X, I haven't tested those as extensively. I have tried small test workflows, and haven't seen a particularly noticeable slowdown, so it may be related to the size of the workflow run. I have to restart Kepler to get things back up to speed, and it's bad enough that I'm actually restarting Kepler after every run.</p>
<p>I'm not sure it's a memory thing. java.exe is about maxed out on memory (~0.5 GB) in the Task Manager, but the Check System Settings window says I have 46% free. I was watching jstat, and changes don't seem to trigger a flurry of garbage collection.</p> Kepler - Bug #4655 (Resolved): data packages are suddenly unusablehttps://projects.ecoinformatics.org/ecoinfo/issues/46552010-01-08T02:23:01ZOliver Soongsoong@nceas.ucsb.edu
<p>For some reason, EML 2 Dataset actors are not outputting any tokens for most output formats. The data exists at .kepler/cache/cachedata, as expected. If I set the EML 2 Dataset Data Output Format to As ColumnBased Record, then I get an error message, "The data cloumn (sic) didn't match head column". If I set the EML 2 Dataset Data Output Format to "As All Cache File Names", then things seem to work as expected. All other output formats don't seem to work.</p>
<p>Things were definitely working as of Dec. 8 and possibly Dec. 10.</p> Kepler - Bug #4633 (Resolved): LSID conflictshttps://projects.ecoinformatics.org/ecoinfo/issues/46332009-12-15T01:04:31ZOliver Soongsoong@nceas.ucsb.edu
<p>Create a workflow and save a KAR (KAR1). Note the LSID. Change the workflow in some recognizable fashion and save a KAR (KAR2). The LSID bumps as expected. Close the workflow and open KAR1. Make a different change (so it's obviously not the workflow in KAR2) and save the KAR (KAR3). Notice that when the workflow reopens, it looks like KAR2 because it is KAR2 down to the MOML in KAR3.</p>
<p>I'm observing this at r22183 right now.</p> Kepler - Bug #4632 (Resolved): problems when loading a KAR, changing the workflow, then re-saving...https://projects.ecoinformatics.org/ecoinfo/issues/46322009-12-14T23:07:12ZOliver Soongsoong@nceas.ucsb.edu
<p>Create a workflow and report and save the KAR. Next, change the workflow (i.e., bump the MOML LSID), save the KAR (overwrite or not doesn't seem to matter), and run it. The report should be blank. Sometimes, the ROML still exists in the KAR, so closing and re-opening works fine. In this case, the run archive contains the correct workflow_ROML.xml entry and a different ROML.#.xml that doesn't match the workflow_ROML.xml entry. Other times, the ROML seems to be lost from the KAR, in which case the run archive has no workflow_ROML.xml entry and a blank ROML.#.xml.</p> Kepler - Bug #4608 (Resolved): ROML in KAR files not being shown at allhttps://projects.ecoinformatics.org/ecoinfo/issues/46082009-12-08T20:10:55ZOliver Soongsoong@nceas.ucsb.edu
<p>ROML in KAR files is not being loaded. This happens regardless of the LSID in the workflow and ROML matching the InstanceAuthNamespace. This happens regardless of opening from a local repository or not.</p>
<p>This is happening at 22117, but I think I also saw it at 22111. I'm guessing it has something to do with 22083, although I can't be sure.</p> Kepler - Bug #4559 (Resolved): local repositories not showing up in components treehttps://projects.ecoinformatics.org/ecoinfo/issues/45592009-11-19T22:25:52ZOliver Soongsoong@nceas.ucsb.edu
<p>Summary says it all. I'm at r21772, and the default workflows repository isn't in the components tree. Adding repositories doesn't do anything. I'm not even getting prompts to sign into KNB or DEV to cache data.</p> Kepler - 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> Kepler - Bug #4521 (Resolved): KNB data error checking is overly aggressivehttps://projects.ecoinformatics.org/ecoinfo/issues/45212009-11-04T01:03:36ZOliver Soongsoong@nceas.ucsb.edu
<p>On r21314, I can no longer access the Kruger data. I believe this is due to some overly aggressive error checking on the data. The data packages (which are not directly under my control) have thrown errors on the console. I think this is due to negative numbers and zeroes in columns that are nominally whole numbers. In the past, there were non-fatal, but this is now major problem.</p>
<p>This change happened somewhere between r21218 and r21310.</p>
<p>The error message is specifically "Unable to parse the MetaData: Error parsing the eml package: Exception in DataTypeResolver"</p> Kepler - 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>