- When instantiating analyzer units, the sensor tree can be navigated
vertically through the "topdown N" and "bottomup N" keywords, which
respectively mean "N levels down from the top" or "N levels up from the
bottom" of the sensor tree
- This renders the "unit - X" syntax obsolete

Add isTemplate parameter to readSensorBase() and readSensorGroup() to reduce debug output for templates

- Mainly fixes to unsigned-signed comparison warnings

- Small fixes to prevent compilation warnings

- If no analyzerPlugins block is present in global.conf, initialization
of the data analytics framework will be skipped without terminating the
pusher

- Analyzers in on-demand mode now cache units that have been queried
and resolved recently, to speed up response times and reduce overhead
- Once the cache reaches its maximum size, the oldest entry is removed
upon every insertion

- When the analyzer is created, we check whether it only has the root
unit; if so, the unit is immediately resolved and instantiated even if
the analyzer is on-demand

- Auto-publish has been split in two parts: construction of the
sensor names is performed within the Configurators, whereas the MQTT
messages are sent from the MQTTPusher
- This way, sensors always have the correct names upon plugin reloads
- Will make switching to textual MQTT topics easier

- By setting the "streaming" attribute to false, users
can instantiate analyzers that are available only on-demand for requests
on the REST API
- The input/output config will be used to instantiate an unit on the fly
starting from the node queried by the user
- Computation is performed and the result is returned, no data is pushed
on MQTT or to the database

- Added basic obsolescence checks in QueryEngine
- REST API GET requests now output actual JSON when requested
- Other minor changes

- Mostly working, still under testing
- Users can define custom analyzer-specific REST PUT actions
- Support for on-demand data analytics computation via REST coming up

- Fixed a minor bug in QueryEngine that broke thread safety
- The all and all-recursive clauses for unit input sensors do not
replace all existing sensors anymore, but only add the remaining ones

- Fixed a bug in the QueryEngine that caused wrong cache
sections to be selected for sensor data
- Now AverageAnalyzer actually computes sensor averages

- Unit instantiation logic moved to UnitGenerator
- Regex-based filtering system to configure units was added
- Thread safety in QueryEngine access addressed
- Tons of bugfixes

- First working version of Data Analytics Framework
- A test plugin that performs the sum and max of its input sensors was
implemented

- Subsampling behavior with delta fixed: the deltas that
are sent over MQTT are coherent with the subsampling frequency, and are
computed separately from the local high-frequency deltas
- Added exception handling when writing to sensor file sinks
- Fixed odd ProcFS behavior that led to reading constant values from
certain files by closing and re-opening every time. Overhead seems to
be negligible