[kepler-dev] [Bug 5360] New: changes to a sensor parameter might not take effect until next current sample
bugzilla-daemon at ecoinformatics.org
bugzilla-daemon at ecoinformatics.org
Wed Mar 30 13:27:10 PDT 2011
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5360
Summary: changes to a sensor parameter might not take effect
until next current sample
Product: Kepler
Version: 2.1.0
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sensor-view
AssignedTo: barseghian at nceas.ucsb.edu
ReportedBy: barseghian at nceas.ucsb.edu
QAContact: kepler-dev at kepler-project.org
Estimated Hours: 0.0
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.
--
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the Kepler-dev
mailing list