Compare quickly with MG5 real data and downsampled version: MG5 Turbinewelle

watch out: the average is heavely influenced by the system way of working -> when no new value, then no storage

Qualitatively: look at the transient with high resolution

TODO: wider on Quarto

TODO: update wrong bar to opening

TODO: * look @ non-physical outliers on dynamic resampling stack

negative current ? could be: * calibration error; precision error * could also be brake current -> freeze machine to non-moving status

Thoughts multi axis: * think about same unit but different range -> multiaxis (e.g. kV vs V) or normalize in 1 value * organize also signal picking: checkbox, or combox, or accordion tree

Depending on type of insight to show, chose right representation i.e. cumulative vs derivative.

Also saisonality bar chart would make sense (day, week, month, etc).

Additionnally, think about 0 time : start of year, custum, etc.

Check plausability variance (30 m is big...)

Smaller engines do the baseband energy while the biggest engine is designed for reacting quickly to needs.

Idle engine (maintenance). Some measures are following the outside temperature trend, particularly heatwaves are visible. However, some other curves seems to be stable and regulated. It could be that the cooling system is shared among the engines. More specific, it could be that the water flow is the same for all machines. It would be interesting to observe, whether the operation of other engines affects temperature variation in this plot.

Hypothesis stable curves: 1. shared cooling systems accross engines 2. common cooling with water from turbine water

Some ideas: * do violin plot. Watch out: pr'haps way more parametrization * group by season to see seasonal differences

The temperature on the same object "Führungslager" seems to be different depending on the circular segment. This is probably due from the calibration which should not be that precise.