Simon said: > I'd suggest you want a DS for heating which is either 0 (off) or 1 > (on), and update this as often as you can. And have a separate DS for > cooling, again 0 or 1.
I strongly agree; otherwise this makes higher-granularity graphs very awkward, unless there is a 1cdp=1dp RRA that goes on forever to avoid averaging, which would have other problems, of course. If you cannot do the calculation before storage, then maybe define two calculated DSs that that the status DS (0,1,2) and convert to on calculated DS that is heating 0/1 and one that is cooling 0/1 ? Once you have this, then it is easy to get percentage use time -- just create an RRA that is 1cdp=1day and the average of the heating DS x100 is the percentage time the heating is on that day! Much simpler to do all the necessary calculations. Steve Steve Shipway ITS Unix Services Design Lead University of Auckland, New Zealand Floor 1, 58 Symonds Street, Auckland Phone: +64 (0)9 3737599 ext 86487 DDI: +64 (0)9 924 6487 Mobile: +64 (0)21 753 189 Email: [email protected] Please consider the environment before printing this e-mail
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
