commit | 9b9b8a79e09eb68fe1b7b3fd168a759aa78901cd | [log] [tgz] |
---|---|---|
author | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 15 12:59:30 2023 -0600 |
committer | Patrick Williams <patrick@stwcx.xyz> | Wed Feb 15 12:59:32 2023 -0600 |
tree | cd4df3be7c3dfb257e09d2422cd54ca551758502 | |
parent | 32dff21bf5ec860a359b70b9d9dcae656b40578e [diff] |
service: remove obmc-mapper dependencies Mapper is dbus-activated now and this target is removed. Remove the dependency as it performs no function. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I2a61198ae29bcd5b98f9f88c5ecbfce677dc7b82
phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json
from one of three locations:
/var/lib/phosphor-virtual-sensor
/usr/share/phosphor-virtual-sensor
By default the repository will install a sample config into (3).
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. Currently 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).