Excellent. The gust values will show up either on a new day, or if you hit a new wind speed max.
Thanks, Greg -tk On Sat, May 5, 2018 at 5:35 PM, Greg from Oz <[email protected]> wrote: > OK I had 5 minutes to spare so put the new accum.py in and now have > numbers. > > MariaDB [weewx]> select datetime, windgustdir from archive where dateTime > > 1525563900; > +------------+-------------+ > | datetime | windgustdir | > +------------+-------------+ > | 1525564200 | NULL | > | 1525564500 | NULL | > | 1525564800 | NULL | > | 1525565100 | NULL | > | 1525565400 | NULL | > | 1525565700 | NULL | > | 1525566000 | NULL | > | 1525566429 | NULL | > | 1525566600 | 180 | > > So I guess I have to wait for a day yo see if anything shows up in the > week stats? > > > On Sunday, 6 May 2018 00:27:47 UTC+10, Thomas Keffer wrote: >> >> It would not surprise me if there is no value for max_dir in the daily >> wind table if the max wind gust was seen earlier in the day from when you >> installed the new accum.py. >> >> More telling would be the value after running for a day or two. >> >> How about you, Greg from Oz? >> >> -tk >> >> >> >> On Sat, May 5, 2018 at 6:06 AM, Andrew Milner <[email protected]> >> wrote: >> >>> Well I tried anyway!! >>> >>> I now have values for windgustdir in the archive table! >>> I now have a value for today in the daily windgustdir table which looks >>> ok - but I suspect that this is a bogus value! >>> >>> surely windgust max and windgustdir max times should be the same?? >>> >>> I suspect windgustdir values will be min 0, max 359 for most days (like >>> winddir currently is) >>> I suspect windgust table needs additional max_dir coluimn to be >>> populated at time of max gust - which I assume to be purpose of max_dir in >>> wind table except that I do NOT have value for max_dir in the daily wind >>> table - but I do not know what this column represents anyway!! >>> >>> So it seems an improvement to me. I don't try and use the tags though, >>> so cannot comment on those!! >>> >>> >>> >>> >>> >>> >>> On Saturday, 5 May 2018 15:38:45 UTC+3, Andrew Milner wrote: >>>> >>>> Tom - before I try the new accum I need to check that I have not misled >>>> you!! I only checked the contents of the db tables - windgustdir in >>>> archive, daily windgustdir table and maxwinddir in daily wind table. Was >>>> my answer misleading or as expected? >>>> >>>> Andrew >>>> >>>> >>>> On Saturday, 5 May 2018 14:35:04 UTC+3, Thomas Keffer wrote: >>>>> >>>>> Because Andrew reported that the new accum does not make any >>>>> difference, it appears that FO stations do indeed define wind gust that >>>>> way: it's the max wind seen during a loop period, which can be greater >>>>> than >>>>> the wind speed for that period. >>>>> >>>>> I don't know if setting windGustDir to windDir is inventing data, but >>>>> we are making an assumption: that the gust is in the same direction as the >>>>> average wind. But, this is the same assumption we are making for >>>>> *every* station that uses software record generation and/or does not >>>>> emit windGust. >>>>> >>>>> Try this version of accum.py. It explicitly substitutes windDir when >>>>> windGustDir is unavailable. >>>>> >>>>> -tk >>>>> >>>>> >>>>> On Fri, May 4, 2018 at 8:51 PM, gjr80 <[email protected]> wrote: >>>>> >>>>>> Just playing a little devils advocate here; but are we bordering on >>>>>> inventing data? The FO stations provide windSpeed, windDir and windGust >>>>>> per >>>>>> loop packet. It would appear that windSpeed is some sort of average over >>>>>> the period and windGust is presumably the max wind speed seen over the >>>>>> loop >>>>>> period. It appears now that we are setting windGustDir to windDir, but is >>>>>> that necessarily correct, we are not stretching it a little are we? >>>>>> >>>>>> I also don't see any inconsistency between the Standard skin pages in >>>>>> terms on wind/speed/dir. You need to compare apples with apples not >>>>>> apples >>>>>> with oranges. index.html shows the current conditions (windSpeed/windDir >>>>>> based) in the top left pane and day max values (wind.max/wind.maxdir >>>>>> based) >>>>>> in the lower left pane. week.html shows the week max values >>>>>> (wind.max/wind.maxdir based) in the top left pane and month max values >>>>>> (wind.max/wind.maxdir based) in the lower left pane. The FO problem is >>>>>> with >>>>>> windGustDir/wind.maxdir so anywhere wind.maxdir is used will show N/A. So >>>>>> given that limitation the Standard skin pages are completely consistent. >>>>>> >>>>>> 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. >>> >> >> -- > 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.
