Actually your input was just what I needed to figure it out Gary. Like you said I was using the start time when I wanted the end time. Thus instead of forcing things to start at 12:15 all I needed was to use the end time of the span instead. With a span of 15 minutes, the end time of the span is the 12:15 when the days start a midnight for the first span and the closest 15th minute when outputting the last span. That way i'm always on time in the report with automatically generated reports.
Thanks again. On Thursday, May 7, 2020 at 10:46:11 PM UTC-4, gjr80 wrote: > > I have taken you skin/code and run under WeeWX v4/python2/simulator. I am > not seeing anything unusual but then again I am not 100% certain on what it > is that you are believe is not working. Perhaps you could illustrate with > some (abbreviated) actual output captures? > > Assuming the issue is the final row in downld02.txt and downld08.txt. The > final few (abbreviated) rows from downld02.txt generated during the 1225 > report cycle are: > > 08/05/20 11:45a 0.0 0.0 0.0 0.0 0.0 0.0 > 08/05/20 12:00p 0.3 0.4 0.3 80 -2.7 0.0 > 08/05/20 12:15p 0.1 0.2 -0.0 80 -2.9 0.0 > > After the 1230 report cycle it looked like: > > 08/05/20 11:45a 0.0 0.0 0.0 0.0 0.0 0.0 > 08/05/20 12:00p 0.3 0.4 0.3 80 -2.7 0.0 > 08/05/20 12:15p 0.1 0.2 -0.0 80 -2.9 0.0 > > and after the 1235 report cycle this: > > 08/05/20 11:45a 0.0 0.0 0.0 0.0 0.0 0.0 > 08/05/20 12:00p 0.3 0.4 0.3 80 -2.7 0.0 > 08/05/20 12:15p 0.1 0.2 -0.0 80 -2.9 0.0 > 08/05/20 12:30p -0.1 -0.1 -0.1 80 -3.2 0.0 > > To me this is all expected output. The final 15 minute span on the 1225 > and 1230 report cycles is from 1215-1230. In the 1235 report cycle the > final span is from 1230-1245. The 1230 archive record belongs in 1215-1230 > span so since you are printing the start date-time of the span as the first > column of your report the 1225 and 1230 reports quite correctly have > '08/05/20 12:15p' as the date-time for the last row. It is not until the > 1235 report cycle that '08/05/20 12:30p' shows and its sole data point will > be from the 1235 archive record. > > As I said I am not certain what problem you are seeing but at present I do > not see anything that is not correct. > > Gary > > On Friday, 8 May 2020 09:06:52 UTC+10, Hyrules wrote: >> >> There is definitely something I don't understand here. Run the report >> every 15 minutes with archive interval of 5 minutes the latest 15th minute >> value is not there when Weewx generates the report automatically. Check the >> database... archive value of the lastest 15 is there. If I run wee_report 1 >> minute later I get my line in my report. Print my timespan in the syslog or >> on screen, the timespan seems to be ok. For example if my timespan is from >> 00:15 today to 19:00 today I only get 00:15 to 18:45... in incremets of 15 >> minutes. I have added the skin and the python files if anyone should feel >> willing to try. I will continue on my side to try to find what is >> happening. The script is really not complicated. The skin folder should go >> in the skin folder and the user should go in weewx user folder. thanks. >> >> -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b45f755c-1090-49ec-856f-502b93362983%40googlegroups.com.
