| commit | 190e4bf8a434a04c7426d7ea30a8ba2171a61741 | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 15 10:56:20 2021 -0600 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Wed Dec 15 11:12:31 2021 -0600 |
| tree | 034ba61a3eedd0389cec3116db140e69c86bb5ac | |
| parent | 05b1d41788058cdf255ce1d46b2ff8041abf5656 [diff] |
README: format changes suggested by markdownlint Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I189f176f9ea6ef16603f962bbd109678edb54fb6
phosphor-virtual-sensor reads in virtual_sensor_config.json There are two types of data in this file:
See virtual_sensor_config.json in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.
For example:
{ "Desc": { "Config": "D-Bus", "Type": "modifiedMedian" } }
Sensors added this way can only use a set of restricted calculations. At this stage the only type supported is modifiedMedian.
The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.
The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json (specified in entity-manager/schemas/VirtualSensor.json).