ITQC/gls_docs
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Option to define mapping aggregations.

Browse Source
This commit is contained in:
Fabian Märki
2018-10-30 09:28:34 +01:00
parent 206bc63879
commit 980ddc2098
4 changed files with 217 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
Readme.md
View File

@ -523,12 +523,15 @@ It is possible to map values based on their pulse-id/global time. Setting this o
```json
"mapping":{
"incomplete":"provide-as-is"
"incomplete":"provide-as-is",
"alignment":"by-pulse",
"aggregations":["count","min","mean","max"]
}
```
- **incomplete**: Defines how incomplete mappings should be handled (e.g., when the values of two channels should be mapped but these channels have different frequencies or one was not available at the specified query range (values: **provide-as-is**|drop|fill-null). *provide-as-is* provides the data as recorded, *drop* discards incomplete mappings, and *fill-null* fills incomplete mappings with a *null* string (simplifies parsing).
- **alignment**: Defines how the events should be aligned to each other (values: **by-pulse**|by-time|none). In case alignment is undefined it will be selected based on the query type (query by pulse-id or by time). _none_ will simply add one event of a channel after the other (independent of other channels).
- **aggregations**: In case several events are mapped into the same bin (e.g. due to activated binning or duplicated pulse-ids) the values will be aggregated based on this parameter (in case it is undefined it will use the global/default aggregations).
<a name="value_transformations"/>