Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-06-18T22:45:59ZEcoinformatics Redmine
Redmine Bug #5630 (New): See about removing one set of ColorTableCellEditor and ColorTableCellRender classeshttps://projects.ecoinformatics.org/ecoinfo/issues/56302012-06-18T22:45:59ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>There are two versions of ColorTableCellEditor and ColorTableCellRenderer, one pair in Plotting, the other in Runtimemonitor. They're almost identical; there's basically one main difference, the ones in Plotting make use of an override of Color: org.kepler.sms.Color. There are 42 references to this version of Color in Plotting. Ideally we don't replicate code or override classes, so see about removing this Color class and let both modules use one set of the ColorTableCell* classes, moved into the Gui module.</p> Bug #5600 (New): Import Site Layout performance is poor for many connections at oncehttps://projects.ecoinformatics.org/ecoinfo/issues/56002012-05-07T23:11:48ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>During a recent workshop I had ~25 people at once try to Import Sensor Site from one SPAN host running on my macbook. I believe the Site Layout appeared eventually for everyone, but there was a very long wait until they began to appear -- I'd say it may have taken 5 minutes before everyone's layout appeared.</p> Bug #5400 (New): User can specify the interval of data chunk in the workflow archiving dataturbi...https://projects.ecoinformatics.org/ecoinfo/issues/54002011-05-12T21:05:06ZJing Taotao@nceas.ucsb.edu
<p>In the current workflow, it chops the data from the last archiving time to latest data stamp if there is no metadata change.</p>
<p>However, the workflow should have a feature that let user to specify the interval of dataset. For example, user can specify the interval to be month. So one dataset will have the all data generated in one month, such as March. The next dataset will contain the data in April.</p> Bug #5364 (New): DataTurbine server memory errorhttps://projects.ecoinformatics.org/ecoinfo/issues/53642011-04-04T18:11:30ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Sometimes my gumstix DT server gives a memory error, and then stops working -- the process keeps running, but I cannot connect to it. The most recent time this happened i had been running span and spanToDT for a little under a day. I think for most of this period i sampled 1 sensor every 5s, and 2 every 30s.</p>
<p>Startup:<br />----------<br /><01-Apr-2011 Pacific Daylight Time 11:56:36.927> <dataturbine><br /> RBNB (Ring Buffered Network Bus) V3.2B5 build 2953 (built Tue Aug 31 05:47:41 Pacific Daylight Time 2010)<br /> Copyright 2006 Creare Inc.<br /> Started at address tcp://gpp.msi.ucsb.edu:3333.<br /> Archive home directory: "/var/rbnb_archive" <br /><01-Apr-2011 Pacific Daylight Time 12:50:54.179> <KeplerClient><br /> Started for sink running V3.2B5 build 2953 from Tue Aug 31 05:47:41 Pacific Daylight Time 2010.<br /><01-Apr-2011 Pacific Daylight Time 12:51:41.568> <gpp><br /> Started for source running V3.2B5 build 2953 from Tue Aug 31 05:47:41 Pacific Daylight Time 2010.<br /><01-Apr-2011 Pacific Daylight Time 12:51:41.622> <gpp><br /> Set up cache with 2 framesets of 1 frames/set (total frames = 2).<br /> Set up archive with 10 filesets of 100000 framesets/set (total frames = 1000000)<br />-----</p>
<p>Error, at the very end of log:<br />------<br />Exception in thread "gpp" java.lang.OutOfMemoryError<br /> <<No stacktrace available>><br /><02-Apr-2011 Pacific Daylight Time 10:53:49.549> <RCO com.rbnb.api.TCPRCO@40d55860><br /> java.lang.IllegalStateException: Cannot reconnect to existing client handler /dataturbine/gpp.<br /> at com.rbnb.api.RCO.login(RCO.java:1373)<br /> at com.rbnb.api.SerializingRCO.login(SerializingRCO.java:351)<br /> at com.rbnb.api.TCPRCO.login(TCPRCO.java:461)<br /> at com.rbnb.api.RCO.process(RCO.java:1653)<br /> at com.rbnb.api.RCO.run(RCO.java:2210)<br /> at java.lang.Thread.run(Thread.java:743)<br />--------</p> Bug #5362 (New): Create a GUI so user can easily archive a senosr's data from a dataturbine to a ...https://projects.ecoinformatics.org/ecoinfo/issues/53622011-03-31T21:39:54ZJing Taotao@nceas.ucsb.eduBug #5347 (New): DataTurbine actor should support Start Time with sub-second accuracyhttps://projects.ecoinformatics.org/ecoinfo/issues/53472011-03-10T01:15:13ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>DT actor Start TIme parameter should support sub-second accuracy. It would be nice if it accepted dates specified in a variety of formats, including [milli]seconds since epoch, and made apparent at least one of these formats - currently the user has no clue.</p> Bug #5313 (New): fix Import Sensor Site and Export Site to KML menu item issueshttps://projects.ecoinformatics.org/ecoinfo/issues/53132011-02-17T22:13:47ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>These menu items are currently at the bottom of the File menu. Import Sensor Site should probably be beneath 'Open...', and Export Site to KML should be beneath 'Export...'. IIRC there's an issue with this not being easy to do.</p>
<p>Also, these menu items get added to gui's uiMenuMapping config each time sensor-view starts up. The plan is to wait until <a class="issue tracker-1 status-2 priority-2 priority-default" title="Bug: adding and removing configuration properties could be made easier (In Progress)" href="https://projects.ecoinformatics.org/ecoinfo/issues/5129">#5129</a> is fixed for this issue.</p> Bug #5171 (New): link workflow in components tree to workflow in scheduler viewhttps://projects.ecoinformatics.org/ecoinfo/issues/51712010-09-03T19:54:15ZDaniel Crawldanielcrawl@gmail.com
<p>Once a workflow has been uploaded to a repository, a user might want to schedule it for execution. To make this process easier, it'd be nice if the user could quickly navigate from the workflow entry in the components tree to the workflow entry in the scheduler view (see Figure 7). One way to do this is add a context menu entry for the workflow in the components tree that changed views and automatically selected the same workflow.</p>
<p>It would also be nice to have a link in the reverse direction: scheduler view -> workflow editor / site layout.</p> Bug #5116 (In Progress): add lat/lon to sensor metadata and use during importhttps://projects.ecoinformatics.org/ecoinfo/issues/51162010-08-02T23:19:25ZDaniel Crawldanielcrawl@gmail.com
<p>The site layout in engineering workflows can reflect the physical layout of sensors at a deployment site. If lat/lon metadata were stored on the sensor server, this location information could be used when importing a workflow into Kepler.</p>
<p>The tasks for this bug are:</p>
<p>1. see if SPAN allows lat/lon metadata per sensor<br />2. if not, try to add it<br />3. use lat/lon metadata during import</p> Bug #4773 (New): Data processing on the GPPhttps://projects.ecoinformatics.org/ecoinfo/issues/47732010-02-08T23:51:25ZIlkay Altintasaltintas@sdsc.edu
<p>Do we allow data processing on the GPP unit? Could it be a Kepler workflow, e.g., for quick QA?QC.</p> Bug #4763 (New): create gui to access datalogger programhttps://projects.ecoinformatics.org/ecoinfo/issues/47632010-02-05T18:57:27ZDaniel Crawldanielcrawl@gmail.com
<p>Provide an interface within engineering view to download, view, upload, and install the program running on the datalogger. Note: this may not be possible when using the SPAN software.</p> Bug #4758 (New): search for site components in kepler's data tabhttps://projects.ecoinformatics.org/ecoinfo/issues/47582010-02-05T18:50:36ZDaniel Crawldanielcrawl@gmail.com
<p>Archive site layouts stored in dataturbine to metacat so that sensor components may be searched from Kepler.</p>
<p>See figure 8 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 #4750 (New): create wiring table guihttps://projects.ecoinformatics.org/ecoinfo/issues/47502010-02-05T18:34:25ZDaniel Crawldanielcrawl@gmail.com
<p>Create a wiring table interface that can describe all the connections between sensors and datalogger(s) at a sensor deployment. Note that this table is for documentation purposes only.</p>
<p>See figure 3 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 #4747 (New): import & export site layout to SensorMLhttps://projects.ecoinformatics.org/ecoinfo/issues/47472010-02-05T18:30:11ZDaniel Crawldanielcrawl@gmail.com
<p>Import & export engineering view site to SensorML.</p> Bug #4741 (New): create icons for engineering view componentshttps://projects.ecoinformatics.org/ecoinfo/issues/47412010-02-05T18:18:45ZDaniel Crawldanielcrawl@gmail.com
<p>Create icons for engineering view components in Kepler. This includes: sensor, datalogger, dataturbine, etc. Also, need to have different colors of the icons to show status: green, red, yellow.</p>
<p>See figures 1 and 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>