Yes, I was thinking along those lines as well. This might be the best approach since you're not continually calculating something against a steadily increasing set of data. Putting it in the database would also allow you to see these stats whenever you want, however you want (i.e., coldest night of the week, month, etc.).
On Monday, January 16, 2017 at 11:38:38 AM UTC-5, Andrew Milner wrote: > > My initial reaction is that this would become an incredibly time consuming > calculation without having a additional daily night and day tables holding > max and min like the existing daily tables, and have an associated > service updating them. Thinking aloud perhaps the same can be achieved by > designating two unused database fields as day_temp and night_temp, have a > service populate these two fields according to the time of the record, and > the database should end up with the night and day max and min values you > are seeking. > > Just a thought ......... > > > > On Monday, 16 January 2017 18:10:10 UTC+2, Jared wrote: > >> Hi, >> >> I'm still figuring things out and I'm making my way through the >> customization guide and starting to think about my own customizations. One >> all-time record I used to like from WeatherDisplay was the coldest and >> warmest day/night stats. A night was 6pm - 6am, and day was the opposite. >> I'm not a developer and only know programming basics, but I'm looking at >> the MyXSearch example in the customization guide and it seems like this is >> not a simple calculation but rather a new set of calculations and then >> taking the highest/lowest average from the set. Would this require >> modification of the database? Has anyone created something similar and >> provide some hints? >> > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
