Core: revise incremental vs single time/monitor values
From Github issue:
"combine" factor makes use of Metadata::computeAverage, which works properly only if mon/time are incremental, which is the case for scanning experiments
TODO:
- prevent combine>1 for non-incremental (regular) measurements
- consequence for normalization choice??
- new YAML format should ensure unambiguous semantics of mon/time fields