Kepler: Issueshttps://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362012-05-17T21:09:46ZEcoinformatics Redmine
Redmine Bug #5610 (Resolved): check that build system can handle a "0.9.0" releasehttps://projects.ecoinformatics.org/ecoinfo/issues/56102012-05-17T21:09:46ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>We discussed releasing sensor-view as sensor-view-0.9.0 initially to signify beta status. Check if this is currently possible.</p> Bug #5606 (Resolved): move plotting classes to sensor-viewhttps://projects.ecoinformatics.org/ecoinfo/issues/56062012-05-10T22:07:34ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>THere are plotting classes in runtimemonitor and sensor-view, it seems to me they should all be in one place, sensor-view.</p> Bug #5605 (Resolved): Kepler scheduler doen't work for local workflows in windows oshttps://projects.ecoinformatics.org/ecoinfo/issues/56052012-05-09T22:30:44ZJing Taotao@nceas.ucsb.edu
<p>Before the sensor-view workshop, derik found that the Kepler scheduler doen't work for local workflows in windows. It works in mac and linux.</p> Bug #5602 (Resolved): Timezone confusion using the schedulerhttps://projects.ecoinformatics.org/ecoinfo/issues/56022012-05-07T23:52:44ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>It appears at least some parts of the Workflow Scheduling system don't account for different timezones. When you schedule a workflow in Kepler, you don't specify timezone, so presumably this is local time. I think the server also uses local time, and so this requires you to know where the server resides, and schedule using its time. Instead we should probably translate to GMT, and expose timezone codes in the gui.</p> Bug #5580 (Resolved): create sensor-view module documentationhttps://projects.ecoinformatics.org/ecoinfo/issues/55802012-03-26T20:52:03ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>Write sensor-view module documentation.</p> Bug #5417 (Resolved): changes to a sensor's serial-number param do not get written to config filehttps://projects.ecoinformatics.org/ecoinfo/issues/54172011-05-31T20:20:54ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>If you Configure Actor a sensor actor and change it's serial-number, this change is lost on SPAN restart because it is not written to the config file.</p> Bug #5408 (Resolved): dataturbine actor should reuse connectionhttps://projects.ecoinformatics.org/ecoinfo/issues/54082011-05-21T00:43:51ZDaniel Crawldanielcrawl@gmail.com
<p>When running the archival workflow, the dt actor reconnects to the dt server many times. Since the same dt server is used, the actor should reuse the same connection until the workflow finishes.</p> Bug #5404 (Resolved): change-sampling.kar demo no longer workshttps://projects.ecoinformatics.org/ecoinfo/issues/54042011-05-13T19:06:10ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>This demo seems to get stuck at preinitializing.</p> Bug #5403 (Resolved): Improve the performance of the workflow archiving data from dataturbine to ...https://projects.ecoinformatics.org/ecoinfo/issues/54032011-05-12T21:29:26ZJing Taotao@nceas.ucsb.edu
<p>Now the workflow iterates each sensor sequentially to archiving data. Probably we can parallel the process.</p> Bug #5390 (Resolved): EML created by DataTurbineToMetacat workflow should have the spatial coveragehttps://projects.ecoinformatics.org/ecoinfo/issues/53902011-05-03T22:29:33ZJing Taotao@nceas.ucsb.edu
<p>Current EML document generated by the worklfow only have the temporal coverage. We need to add spatial coverage as well.</p> Bug #5378 (Resolved): add rety logic to SpanTodt, attempt to recover if RBNB goes downhttps://projects.ecoinformatics.org/ecoinfo/issues/53782011-04-13T22:45:16ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>We've found that requesting a large amount of data from RBNB on a gumstix, at least via rdv (1.9.0 and 2.2.1), can get the server into a messed up state, requiring a restart, and the RBNB files written to disk will become corrupt such that a restart of rbnb fails to load the old data (yikes - we'll work on a replication procedure and submit these bug(s) to the rbnb list). When this happen SpanTodt locks up. Even when rbnb is successfully restarted (e.g. by deleting rbnb files on disk and starting fresh), SpanTodt stays locked. We should add some retry logic so spanToDT can attempt to persevere through tough times.</p> Bug #5360 (Resolved): changes to a sensor parameter might not take effect until next current samplehttps://projects.ecoinformatics.org/ecoinfo/issues/53602011-03-30T20:27:10ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>if you change e.g. the sampling rate of a sensor, the sensor won't immediately change to the new rate, it will change the next time it samples. This can mean having to wait a long time to see the change. Also, we're not sure if you actually have to wait for the next sample to come through for the change to actually take effect.</p> Bug #5321 (Resolved): sensor settings made by kepler user lost on SPAN restarthttps://projects.ecoinformatics.org/ecoinfo/issues/53212011-02-23T20:26:50ZDerik Barseghianbarseghian@nceas.ucsb.edu
<p>To start SPAN you</p>
<p>generate a config file from a CRBasic program:<br />./cr_parser.py conf/sq110_and_bps.CR8 span.cfg</p>
<p>and then start SPAN using it:<br />./cr1k_d CR800 span.cfg<br />./dcd_mgr span.cfg</p>
<p>Currently SPAN crashes periodically, requiring restart. Even if that weren't the case, we still need to function smoothly when the gumstix power cycles (thus restarting SPAN). If a user makes sensor changes via Kepler, and then SPAN is restarted, since the CRBasic program is never updated, the user sensor settings are lost.</p>
<p>Possible solutions, neither of which are currently supported afaik, seem to be:<br />1) download from the logger the CRBasic program whenever changes are made, thus keeping it in sync.<br />2) simply start SPAN without overwriting existing settings on the logger, e.g. with a mostly blank config.</p> Bug #5286 (Resolved): Remove the override of EntityTreeModelhttps://projects.ecoinformatics.org/ecoinfo/issues/52862011-01-31T22:37:49ZSean Riddleswriddle@gmail.com
<p>Currently, the class ptolemy.vergil.tree.EntityTreeModel is being overridden in sensor-view. This is to allow it to selectively ignore certain change requests. In this case, it needs to ignore the change requests through which Sensor actors are fired.</p>
<p>At the moment, this is accomplished by the following two part mechanism. The description of the change request in question (which was unused before, I think) is now '<group name="IGNORE_THIS_CHANGE"></group>'. EntityTreeModel is changed to ignore all change requests that contain the substring 'IGNORE_THIS_CHANGE'.</p>
<p>This is clearly imperfect. A cleaner method of marking certain change requests as 'to be discarded' by the EntityTreeModel class is needed. Alternatively, a refactoring so the plotting component does not use the EntityTreeModel class would also work.</p> Bug #4744 (Resolved): load & save site layout to local kar filehttps://projects.ecoinformatics.org/ecoinfo/issues/47442010-02-05T18:26:19ZDaniel Crawldanielcrawl@gmail.com
<p>Load and save a site deployment (including wiring, sensor workflows, etc.) to a KAR file.</p>