... | ... | @@ -169,7 +169,7 @@ To use the power profiling service, define a `<powerProfilingConf>` block with t |
|
|
| `obsIds`* | One or more observer IDs for which this service should be used. Note that all IDs used here have to have a target configuration as well. | ID(s) of the observer(s) to use |
|
|
|
| `offset`* | Defines the start of the power measurement relative to the test start (offset in seconds). | |
|
|
|
| `duration` | Duration in seconds of the power measurement. | |
|
|
|
| `samplingRate` | Sampling rate [Hz] for the power measurement. | possible values: 1, 10, 100, 1000, 2000, 4000, 8000, 16000, 32000, 64000. default: 1000 |
|
|
|
| `samplingRate` | Sampling rate [Hz] for the power measurement.<br />**Note:** For sampling rates below 1000Hz, the measurements will be averaged over *1000 / samplingRate* samples (i.e. internally, the min. sampling frequency is always 1kHz and the downsampled results are average values). | possible values: 1, 10, 100, 1000, 2000, 4000, 8000, 16000, 32000, 64000. default: 1000 |
|
|
|
| `fileFormat` | File format. The csv format is more convenient (text), but results in large files. If you want to parse the data manually, you can use the rld format (binary). Parsing tools are available [here](https://pypi.org/project/rocketlogger/).<br />**Note:** The chosen file format must be the same for all observers. | possible values: csv, rld. default: csv |
|
|
|
|
|
|
\* mandatory elements
|
... | ... | |