Today we offer the following MeasurementType in dsgrid to describe the value associated with a timestamp: MEAN, MIN, MAX, MEASURED, TOTAL
However, other than TOTAL, the rest of the measurement types are ambiguous IMO. For example,
If a DatetimeRange Time Config representing the 8760 of CY2018 and specifies MeasurementType.MEAN, what does each value mean? That each value is the mean hourly metric of something? But the "mean" value cannot be across time because we do not have param to specify that today. Instead, the value in the example represents "total" over that hour but averaged across some other dimension, like averaged per dwelling unit. Is this the intention we have when we first make these ENUM?
Will we ever encounter the need to specify something like, peak hour value by each day of the year? If so, we'll need the MeasurementType or the TimeConfig to additionally know what the time frequency the peak represents, which is hour, while the datetime range frequency is daily.
Today we offer the following MeasurementType in dsgrid to describe the value associated with a timestamp: MEAN, MIN, MAX, MEASURED, TOTAL
However, other than TOTAL, the rest of the measurement types are ambiguous IMO. For example,
If a DatetimeRange Time Config representing the 8760 of CY2018 and specifies MeasurementType.MEAN, what does each value mean? That each value is the mean hourly metric of something? But the "mean" value cannot be across time because we do not have param to specify that today. Instead, the value in the example represents "total" over that hour but averaged across some other dimension, like averaged per dwelling unit. Is this the intention we have when we first make these ENUM?
Will we ever encounter the need to specify something like, peak hour value by each day of the year? If so, we'll need the MeasurementType or the TimeConfig to additionally know what the time frequency the peak represents, which is hour, while the datetime range frequency is daily.