Skip to content

aggregate_logger: fix bug with timestamp at beginning of the new year

Alexander Hinz requested to merge (removed):master into master


The problem was, that a a aggregated year should start with the timestamp 00:30 when aggregated to 30 minutes and with the 01.01. when aggregated to a whole day.
The new solution seems to be a bit hacky.
In the writeData function a freq is needed (I renamed is to change_freq) for the iterDataFreq(data, change_freq) function in Until now change_freq=y, that isn't even listed in freqs dictionary in the iterDataFreq function in , but it works only for aggregation for 1d, not for the 30min aggregation.
For the 30min it works with change_freq=yearly.
Maybe you have an idea how to solve this better.

Merge request reports