commit | 14ef874265884320e4a31f5f39d6e964b2ef9b7b | [log] [tgz] |
---|---|---|
author | Lei YU <yulei.sh@bytedance.com> | Sat Oct 07 17:50:28 2023 +0800 |
committer | Lei YU <yulei.sh@bytedance.com> | Sat Oct 07 17:52:22 2023 +0800 |
tree | 05976586578fe3a572f587400666033a03b8888b | |
parent | c77b6b3f91030c54bb5dd73076e10dfbd2d213a9 [diff] |
Add UT cases for exprtk functions related to nan Add unit test cases for below exprtk functions: * maxIgnoreNaN * sumIgnoreNaN * ifNan Signed-off-by: Lei YU <yulei.sh@bytedance.com> Change-Id: I4a9ea4b1f88ad1fd76295f88778a5bfc6b4defd1
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).