GitLab

- querySensor does not return NULL pointers anymore, but always
the "buffer" input argument
- the previous implementation was more descriptive of error statuses,
but much more prone to leaking memory in case of improper usage
- Also fixed a warning in the MSR plugin

-Fixes and improvements to Caliper service
-Start work on Pusher plugin

Local work will be merged to branch

- Fixed a bug in the collectagent that caused the QueryEngine to not
be treated correctly, due to a missing linking flag

- Fixed a bug associated to virtual sensor queries under the new schema
- Symbol for scaling in dcdbquery is now '@'

-service stores snapshot data now in shared memory
-Caliper service finished for the moment
-Pusher plugin adaption outstanding...

- Fixed a bug in the Filesink plugin that caused occasional crashes
- Fixed a bug in the Pusher REST API that prevented plugin reloads
for operators

- Make clean might be required

-fixed symbol address calculation

- This plugin allows to write arbitrary sensor data to the local file system
- Removed the obsolete sink functionality in SensorBase
- Also fixed a minor bug concerning MQTT topic assignment in template analyzers

-implement custom symbollookup instead of Caliper service usage
-relocate lookup logic to pusher plugin
-share symbol information via shared memory

- Added shuffling of data in the training set in an attempt to improve
regression accuracy

-avoids symbollookup service but instead uses dladdr
-not fully re-entrant but does not crash
-needs huge clean-up

- The "observations" operation simply counts the number of total queried
elements over the inputs of each unit

- Fixed a bug in UnitGenerator when generating units in relaxed mode
- Added the latest reading as feature in the Regressor plugin
- Added a small delay in the scheduling of analyzers to give higher
priority to standard monitoring plugins

- Allowing users to define analyzers with inputs but no outputs
- In this case, a "sink" unit is created, which always refers to the
root of the sensor tree
- This is useful for control analyzers that tune system knobs but do
not actively produce sensor data

- For plugins that use hierarchical units (e.g., job analyzers) a
"flatten" plugin option was added. If enabled, output sensors in the
sub-units of each unit will be exposed as well, and their output values
propagated
- Minor fixes here and there