I would agree, but why is the forecast data drawn fine and only the measured data not? My change to scaletime only calculates the time range - and that looks fine to me (see the included image within my first post). scaletime does return a triple of data - start, stop, and stepwidth. Works fine for forecast. AND works fine if there is no change of the year. I assume furthermore that scaletime does not use any global variables. But your program is very clean designed, thus I do not expect, that scaletime could create sideeffects. Tomorrow I'll know more...
Tom Keffer schrieb am Sonntag, 31. Dezember 2023 um 16:40:55 UTC+1: > Your modified version of scaletime() is surely causing the problem. Its > semantics were never clear to me, and now it appears we're discovering the > side effects. > > If you have a debugger, use it to step through running wee_reports. It > will probably become evident what the problem is. > > On Sun, Dec 31, 2023 at 7:17 AM 'Michael Waldor' via weewx-user < > [email protected]> wrote: > >> And since now I encounter the same problem with my day images. And the >> timescale is extended into the first hours of next year. Thus I'm quite >> confident that my problems will disappear as soon as the next year starts. >> >> To me it looks as if the access to weewx.sdb searches at a wrong time. >> Sadly I can't look deeper to debug that. There are no error messages within >> journalctl. >> >> I'm using two sqlite DBs - the original weewx.sdb of course and a second >> one with forecast data. Maybe if the border of a year is crossed the >> weewx.sdb becomes unavailable? I can even report the time - it happens >> exactly at 14:00. Afterwards the timeaxis starts to go till 3 o'clock in >> the night (till 14:00 it goes till midnight). And only forecast data is >> drawn (but containing data from today and tomorrow - no problem with year >> boundary). Even dayUV is no longer updated despite not using forecast data >> at all (but with the same timeaxis crossing the year boundary). >> >> Michael Waldor schrieb am Samstag, 30. Dezember 2023 um 10:20:05 UTC+1: >> >>> Since (today?) all week images contain no measured data, only the >>> forecast data are visible. >>> [image: weektempdew.png] >>> I have to admit that I've patched utilities.py to shift the right border >>> of the timescale into the "future". It works fine all over the year. To my >>> surprise all (measured) data is missing. If I drop my shift the data >>> re-appears. But - as you see from the image above - the timescale looks >>> fine and is exactly as intended. I've even debugged my modification for the >>> current date, and everythind works as intended. But why are there no data >>> from the past? Even from the above image one can see that imagegenerator.py >>> can cross the year boundary perfectly. >>> >>> And there IS data available within the past (I've checked this by >>> dropping my change, and I've got a plot between 23. and 31.). >>> >>> Why does weewx don't see the missing data? Images without forecast data >>> aren't generated at all, e.g. weekUV. >>> >>> For more details on my patch see >>> https://groups.google.com/g/weewx-user/c/76qdbSy3bbQ/m/oIlk3sKrBgAJ >>> >>> Regards, Michael >>> >>> -- >> 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]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/b4d802ee-c929-4ebb-aee9-e52c040a24c0n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/b4d802ee-c929-4ebb-aee9-e52c040a24c0n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2f363b20-7d08-4db2-9a0b-b890d0e962dcn%40googlegroups.com.
