Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362011-01-19T23:37:30ZEcoinformatics Redmine
Redmine Bug #5275 (Resolved): Executing sensor-view workflow records provenancehttps://projects.ecoinformatics.org/ecoinfo/issues/52752011-01-19T23:37:30ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Executing a sensor view workflow isn't supposed to record data to provenance because the director is DE.</p>
<p>Replicate:<br />start kepler<br />File->Import Sensor Site->From SPAN Host: gpp.msi.ucsb.edu (ping me if it's down)<br />Note Provenance button remains green/on<br />Execute workflow, run is recorded and shown in WRM</p> Bug #5206 (Resolved): Importing or opening a sensor site doesn't open into the sensor site viewhttps://projects.ecoinformatics.org/ecoinfo/issues/52062010-10-19T00:16:48ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Importing or opening a saved sensor site doesn't necessarily change your set of views to Sensor Site and Plot Designer, they often open into the Workflow Editor. Also, if you have a workflow open, an imported sensor site will be placed into this workflow; it should probably be a new window.</p> Bug #5172 (Resolved): Exceptions are sometimes thrown during sensor workflow runhttps://projects.ecoinformatics.org/ecoinfo/issues/51722010-09-08T23:15:50ZSean Riddleswriddle@gmail.com
<p>When running a sensor workflow (importing the localhost sensor simulator site), I will intermittently encounter one of three exceptions. I haven't checked, but I suspect that any sensor names given are not consistent between instances of an exception. Kepler will intercept the exception properly, and display an error message, stopping the workflow.</p>
<p>The exceptions are attached below:</p>
<p>--Exception 1 start--<br />ptolemy.kernel.util.InternalErrorException: Failed to compute port depth for .Unnamed1.sensor8.data<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeInputDepth(CausalityInterfaceForComposites.java:696)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeOutputPortDepth(CausalityInterfaceForComposites.java:756)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeInputDepth(CausalityInterfaceForComposites.java:692)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeActorDepth(CausalityInterfaceForComposites.java:527)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites.getDepthOfPort(CausalityInterfaceForComposites.java:373)<br /> at ptolemy.domains.de.kernel.DEDirector._getDepthOfIOPort(DEDirector.java:1582)<br /> at ptolemy.domains.de.kernel.DEDirector._enqueueTriggerEvent(DEDirector.java:1541)<br /> at ptolemy.domains.de.kernel.DEReceiver.put(DEReceiver.java:162)<br /> at ptolemy.actor.AbstractReceiver.putToAll(AbstractReceiver.java:332)<br /> at ptolemy.actor.IOPort.broadcast(IOPort.java:288)<br /> at ptolemy.actor.TypedIOPort.broadcast(TypedIOPort.java:238)<br /> at org.kepler.sensor.actor.Sensor.fire(Sensor.java:323)<br /> at ptolemy.domains.de.kernel.DEDirector.fire(DEDirector.java:568)<br /> at ptolemy.actor.CompositeActor.fire(CompositeActor.java:459)<br /> at ptolemy.actor.Manager.iterate(Manager.java:749)<br /> at ptolemy.actor.Manager.execute(Manager.java:351)<br /> at ptolemy.actor.Manager.run(Manager.java:1164)<br /> at ptolemy.actor.Manager$3.run(Manager.java:1217)<br />--Exception 1 stop--</p>
<p>--Exception 2 start--<br />ptolemy.kernel.util.InternalErrorException: Because:<br />Attempt to get depth of ioPort .Unnamed1.CR800.sensors that was not sorted.<br /> at ptolemy.domains.de.kernel.DEReceiver.put(DEReceiver.java:165)<br /> at ptolemy.actor.AbstractReceiver.putToAll(AbstractReceiver.java:332)<br /> at ptolemy.actor.IOPort.broadcast(IOPort.java:288)<br /> at ptolemy.actor.TypedIOPort.broadcast(TypedIOPort.java:238)<br /> at org.kepler.sensor.actor.Sensor.fire(Sensor.java:323)<br /> at ptolemy.domains.de.kernel.DEDirector.fire(DEDirector.java:568)<br /> at ptolemy.actor.CompositeActor.fire(CompositeActor.java:459)<br /> at ptolemy.actor.Manager.iterate(Manager.java:749)<br /> at ptolemy.actor.Manager.execute(Manager.java:351)<br /> at ptolemy.actor.Manager.run(Manager.java:1164)<br /> at ptolemy.actor.Manager$3.run(Manager.java:1217)<br />Caused by: ptolemy.kernel.util.IllegalActionException: Attempt to get depth of ioPort .Unnamed1.CR800.sensors that was not sorted.<br /> at ptolemy.actor.util.CausalityInterfaceForComposites.getDepthOfPort(CausalityInterfaceForComposites.java:379)<br /> at ptolemy.domains.de.kernel.DEDirector._getDepthOfIOPort(DEDirector.java:1582)<br /> at ptolemy.domains.de.kernel.DEDirector._enqueueTriggerEvent(DEDirector.java:1541)<br /> at ptolemy.domains.de.kernel.DEReceiver.put(DEReceiver.java:162)<br /> ... 10 more<br />Caused by: ptolemy.kernel.util.IllegalActionException: Attempt to get depth of ioPort .Unnamed1.CR800.sensors that was not sorted.<br /> at ptolemy.actor.util.CausalityInterfaceForComposites.getDepthOfPort(CausalityInterfaceForComposites.java:379)<br /> at ptolemy.domains.de.kernel.DEDirector._getDepthOfIOPort(DEDirector.java:1582)<br /> at ptolemy.domains.de.kernel.DEDirector._enqueueTriggerEvent(DEDirector.java:1541)<br /> at ptolemy.domains.de.kernel.DEReceiver.put(DEReceiver.java:162)<br /> at ptolemy.actor.AbstractReceiver.putToAll(AbstractReceiver.java:332)<br /> at ptolemy.actor.IOPort.broadcast(IOPort.java:288)<br /> at ptolemy.actor.TypedIOPort.broadcast(TypedIOPort.java:238)<br /> at org.kepler.sensor.actor.Sensor.fire(Sensor.java:323)<br /> at ptolemy.domains.de.kernel.DEDirector.fire(DEDirector.java:568)<br /> at ptolemy.actor.CompositeActor.fire(CompositeActor.java:459)<br /> at ptolemy.actor.Manager.iterate(Manager.java:749)<br /> at ptolemy.actor.Manager.execute(Manager.java:351)<br /> at ptolemy.actor.Manager.run(Manager.java:1164)<br /> at ptolemy.actor.Manager$3.run(Manager.java:1217)<br />--Exception 2 stop--</p>
<p>--Exception 3 start--<br />java.util.ConcurrentModificationException<br /> at java.util.LinkedList$ListItr.checkForComodification(LinkedList.java:617)<br /> at java.util.LinkedList$ListItr.next(LinkedList.java:552)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeInputDepth(CausalityInterfaceForComposites.java:669)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeOutputPortDepth(CausalityInterfaceForComposites.java:756)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeInputDepth(CausalityInterfaceForComposites.java:692)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites._computeActorDepth(CausalityInterfaceForComposites.java:527)<br /> at ptolemy.actor.util.CausalityInterfaceForComposites.getDepthOfPort(CausalityInterfaceForComposites.java:373)<br /> at ptolemy.domains.de.kernel.DEDirector._getDepthOfIOPort(DEDirector.java:1582)<br /> at ptolemy.domains.de.kernel.DEDirector._enqueueTriggerEvent(DEDirector.java:1541)<br /> at ptolemy.domains.de.kernel.DEReceiver.put(DEReceiver.java:162)<br /> at ptolemy.actor.AbstractReceiver.putToAll(AbstractReceiver.java:332)<br /> at ptolemy.actor.IOPort.broadcast(IOPort.java:288)<br /> at ptolemy.actor.TypedIOPort.broadcast(TypedIOPort.java:238)<br /> at org.kepler.sensor.actor.Sensor.fire(Sensor.java:323)<br /> at ptolemy.domains.de.kernel.DEDirector.fire(DEDirector.java:568)<br /> at ptolemy.actor.CompositeActor.fire(CompositeActor.java:459)<br /> at ptolemy.actor.Manager.iterate(Manager.java:749)<br /> at ptolemy.actor.Manager.execute(Manager.java:351)<br /> at ptolemy.actor.Manager.run(Manager.java:1164)<br /> at ptolemy.actor.Manager$3.run(Manager.java:1217)<br />--Exception 3 stop--</p> Bug #5133 (Resolved): Authentication and authorization of GPP serverhttps://projects.ecoinformatics.org/ecoinfo/issues/51332010-08-09T18:24:26ZJing Taotao@nceas.ucsb.edu
<p>Just open this bug. We need those mechanism in GPP server. Dan can give more details.</p> Bug #5077 (Resolved): add real inputs and outputs to sensor actorhttps://projects.ecoinformatics.org/ecoinfo/issues/50772010-07-06T23:21:10ZDaniel Crawldanielcrawl@gmail.com
<p>The output port should write the latest sampled value. One or more input ports should be added to control the sensor.</p> Bug #5042 (Resolved): create span simulatorhttps://projects.ecoinformatics.org/ecoinfo/issues/50422010-06-07T23:36:56ZDaniel Crawldanielcrawl@gmail.com
<p>Create a SPAN simulator that uses the SPAN control protocol to start/stop sensors, and change sampling rates. Additionally, the simulator should generate data for each sensor that is active.</p>
<p>A simulator would allow for building and testing with larger sensor networks (i.e., larger than the number of real sensors) and aid debugging the engineering view interfaces.</p> Bug #5041 (Resolved): display recent data next to iconhttps://projects.ecoinformatics.org/ecoinfo/issues/50412010-06-07T23:31:23ZDaniel Crawldanielcrawl@gmail.com
<p>Display the most recent data value and timestamp next to each sensor icon while "running" an engineering view workflow.</p> Bug #5040 (Resolved): create views, tabs, configurationhttps://projects.ecoinformatics.org/ecoinfo/issues/50402010-06-03T20:14:25ZDaniel Crawldanielcrawl@gmail.com
<p>The view and tab panes for the engineering view need to be created (for now, they can be empty), along with a configuration.xml to load them.</p> Bug #5028 (Resolved): dataturbine overwrites recent data when frequently detachinghttps://projects.ecoinformatics.org/ecoinfo/issues/50282010-05-24T22:17:57ZDaniel Crawldanielcrawl@gmail.com
<p>When disconnecting from a DT server, a source must "detach" so that any uploaded data remain persistent. However, detaching permanently seals the currently open fileset, resulting in DT only storing a small amount of data before overwriting it (regardless of the specified archive size).</p>
<p>To fix this bug, DT needs to be modified to allow frequent detaches and allow saving data up to a specified archive size.</p> Bug #4921 (Resolved): find reports for sensor in site layouthttps://projects.ecoinformatics.org/ecoinfo/issues/49212010-03-31T22:19:28ZDaniel Crawldanielcrawl@gmail.com
<p>Make it possible to navigate from a sensor in the site layout view (fig 1) to the corresponding sensor in the workflows tree in the workflows scheduler view (fig 6). e.g., a context menu item for sensors in the site layout view. This makes it easy to find reports involving a specific sensor.</p> Bug #4762 (Resolved): create gui to control sensor from keplerhttps://projects.ecoinformatics.org/ecoinfo/issues/47622010-02-05T18:55:48ZDaniel Crawldanielcrawl@gmail.com
<p>Allow the user to turn on or off or change the sampling rate of a sensor from the engineering view.</p> Bug #4761 (Resolved): install and configure SPAN software on gumstixhttps://projects.ecoinformatics.org/ecoinfo/issues/47612010-02-05T18:54:11ZDaniel Crawldanielcrawl@gmail.com
<p>Install the SPAN software on gumstix computers and configure it to talk to the CR800 datalogger and appropriate sensors.</p> Bug #4751 (Resolved): implement "run" for site layouthttps://projects.ecoinformatics.org/ecoinfo/issues/47512010-02-05T18:35:54ZDaniel Crawldanielcrawl@gmail.com
<p>Pressing the run button in the engineering view should show the status of the sensors by changing the color of their icon: green for on, red for error, etc. The status can be retrieved from the SPAN software running on the GPP.</p>
<p>See figure 4 in <a class="external" href="https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans">https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans</a></p> Bug #4748 (Resolved): create google earth kml from component coordinateshttps://projects.ecoinformatics.org/ecoinfo/issues/47482010-02-05T18:31:08ZDaniel Crawldanielcrawl@gmail.com
<p>Metadata for components such as sensors can include their location lat/lon/alt. Export coordinates from an engineering view site to KML so that the site can be viewed in Google Earth.</p> Bug #4743 (Resolved): create gui to edit documentation metadata for componenthttps://projects.ecoinformatics.org/ecoinfo/issues/47432010-02-05T18:24:22ZDaniel Crawldanielcrawl@gmail.com
<p>Create an interface that allows the user to document various metadata for components at a site, e.g. lat/lon/alt, type, firmware, etc. It should allow user-defined metadata fields in addition to the set of standard ones.</p>
<p>See figure 2 in <a class="external" href="https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans">https://kepler-project.org/developers/incubation/kepler-engineering-view-for-reap/engineering-view-plans</a></p>