Pat's new .py file seems to fix some of the charts. But, I think not all. I'm gathering details and will send them to him to check and see if there is still an issue to address. I'll post what I find here. phil
On Saturday, September 29, 2018 at 9:47:24 PM UTC-4, Pat wrote: > > Hi everyone, I think this has been resolved in a latest commit. In 0.6 I > was using timespan but also highcharts was packaged as 1 skin. The > timespans were giving me some problems, so I reverted to time.time and that > was causing the problems you see. Thanks Gary for taking the time to check > my code! > > I've pushed an updated commit here > <https://github.com/poblabs/weewx-belchertown/commit/5ac7b8d7165737c2f3ffd7dcfb22fa6fbcb0801d>and > > you can view the new file in full here > <https://github.com/poblabs/weewx-belchertown/blob/5ac7b8d7165737c2f3ffd7dcfb22fa6fbcb0801d/bin/user/belchertown_highchartsSearchX.py>. > > Those here are welcome to try it. If I don't hear back it'll be rolled into > my 0.8 update when I release that. > > > On Tuesday, September 25, 2018 at 9:48:21 PM UTC-4, Philip Kutzenco wrote: >> >> Yes, same for me. The week.json datafile has the last point for each >> measurement associated with the beginning of the 60 minute period following >> the current time. So, it is the same cause. As you say, it's likely related >> to the timestamp Pat chose to use. >> >> Phil >> >> On Tuesday, September 25, 2018 at 7:12:57 PM UTC-4, Colin Larsen wrote: >>> >>> I've just noticed that the end of the Week chart is an hour ahead of my >>> current time - probably all related >>> >>> On Wed, Sep 26, 2018 at 7:40 AM Colin Larsen <[email protected]> >>> wrote: >>> >>>> Thanks Gary and Phil for finding and sorting this :) >>>> >>>> On Wed, 26 Sep 2018, 04:19 Philip Kutzenco, <[email protected]> wrote: >>>> >>>>> Gary, >>>>> >>>>> Excellent. Thanks for sussing this out! I'll look forward to Pat's >>>>> next release. >>>>> >>>>> Phil >>>>> >>>>> On Tuesday, September 25, 2018 at 10:04:07 AM UTC-4, gjr80 wrote: >>>>>> >>>>>> OK, I think I have handle on what is happening here. The cause is as >>>>>> Phil has noted, the last timestamp in each data series in month.json >>>>>> is midnight at the end of the current local day. A commit by Pat on 4 >>>>>> September changed that timestamp from being the last timestamp in the >>>>>> archive to being the midnight timestamp. Looking at the releases that >>>>>> Pat >>>>>> has made I think 0.7 will exhibit this behaviour but 0.6 does not. I >>>>>> will >>>>>> drop Pat a line with the details. >>>>>> >>>>>> Gary >>>>>> >>>>>> On Tuesday, 25 September 2018 22:14:20 UTC+10, Philip Kutzenco wrote: >>>>>>> >>>>>>> So, looking at the data in the json file, the last epoch date in the >>>>>>> series is 1537934400000 and translates to September 26 at 4:00 AM UTC. >>>>>>> So >>>>>>> that is midnight on September 26 EDT (my time zone). So it sounds like >>>>>>> the >>>>>>> aggregated temperature data displayed is for the period prior to that >>>>>>> date/time. But it definitely makes the plot seem inaccurate, especially >>>>>>> when you look at past dates. You'd expect that the aggregated data >>>>>>> point to >>>>>>> correspond to the data gathered from the start of the date to midnight >>>>>>> just >>>>>>> before the next date starts. I hope that is clear (and that I'm not >>>>>>> confused). >>>>>>> >>>>>>> Phil >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tuesday, September 25, 2018 at 7:59:03 AM UTC-4, Philip Kutzenco >>>>>>> wrote: >>>>>>>> >>>>>>>> Gary, >>>>>>>> >>>>>>>> I think this is the file you want me to post. It is timestamped >>>>>>>> September 25, 2108 at 7:46 AM. I am in the US Eastern Time Zone >>>>>>>> currently >>>>>>>> observing Daylight Saving Time. So my time zone is EDT. I checked the >>>>>>>> date >>>>>>>> and time with the date command on my Raspberry Pi running running >>>>>>>> weewx and >>>>>>>> it is correct. >>>>>>>> >>>>>>>> Let me know if you wanted a different file. >>>>>>>> >>>>>>>> Thanks. I appreciate the help. >>>>>>>> >>>>>>>> Phil >>>>>>>> >>>>>>>> On Monday, September 24, 2018 at 11:33:58 PM UTC-4, gjr80 wrote: >>>>>>>>> >>>>>>>>> I suspect the issue will be related to how highcharts is >>>>>>>>> interpreting timestamps in the plot data rather then the wrong data >>>>>>>>> being >>>>>>>>> in the plot data files. I have seen something like this before but it >>>>>>>>> was >>>>>>>>> related to the timezone of the client computer viewing the plots, >>>>>>>>> would >>>>>>>>> seem that is not the issue here though. I am rather pushed for time >>>>>>>>> at the >>>>>>>>> moment but will have a look when I can, though it's been a while >>>>>>>>> though >>>>>>>>> since I have delved into highcharts. >>>>>>>>> >>>>>>>>> Phil, can you post one of the generated highcharts data files >>>>>>>>> that is displaying the issue. Would help to know your timezone and at >>>>>>>>> what >>>>>>>>> time the file was generated as well. >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
