Sorry about the 403 Forbidden error. That is a test domain and public access is often blocked. I opened access a few hours ago when I saw your message, but didn't have time right then to post a response or upgrade. I have since upgraded to v0.2.9. You should now be able to see it working here:
http://www.lablibrary.com/ss/newport.php This area recently had a several-day period of unusually light winds. The 'wgust" value anomalies occurred at those unusually low wind speeds. I don't know why functionality would be different at different speeds, but whatever the reason, v0.2.8 'wgust' anomalies occurred far less frequently today at higher speeds and I haven't seen them at all since upgrading to v0.2.9. Weather forecasts are not very reliable in this area, but there may be an opportunity to check higher-speed functionality tomorrow, because the National Weather Service has issued this High Wind Watch: "*South wind 30-40 mph with gusts to 65 mph, strongest near beaches and headlands but also possibly affecting coastal communities. Winds spreading northward late Tuesday morning, with peak winds from about noon to 4:00pm or 5:00pm. These winds could cause tree damage that could lead to power outages, and will cause hazardous driving conditions.*" My anemometer is 33-feet (*10 meters*) above ground, 204 feet (*62 meters*) above mean-sea-level, and line-of-sight to the sea, so it should be spinning rather quickly if the forecast is correct. The time here is 8 hours behind UTC. -Bob On Monday, March 6, 2017 at 2:26:22 PM UTC-8, gjr80 wrote: > > > On Sunday, 5 March 2017 06:11:53 UTC+10, tempus wrote: >> >> I have been traveling for a few days with only a SmartPhone to watch >> data. However, based merely on wind-speed-gauge indications there seem to >> be "wgust" value anomalies. The pink gust-area sometimes disappears even >> though there have been recent gusts into that speed-range. Furthermore, >> gusts above the indicated upper-gust-limit often do not cause the indicated >> gust-range to expand. >> > > I have been closely observing my wind speed gauge over the last few days > during various windy periods. I did notice periods where the red gust > 'wedge' would disappear for a short period. I observed several occasions > where the indicated wind speed went higher than the existing 10 minute gust > value, on all occasions the ten minute gust value was immediately increased > and the red gust wedge similarly increased in size immediately to match the > indicated wind speed. > > >> It is my understanding that the value of "wgust" is supposed to be the >> speed of the highest gust over the last ten-minutes. If so, the ten-minute >> time-window should include recent "wlatest" values. >> > > That is my understanding as well and that is exactly what rtgd does. The > issue in this case was the method in which the ten minute wind gust value > was derived from the ten minute wind speed list. This has been fixed in > v0.2.9. > > I have no solution for the gusts you observed that did not update the ten > minute gust value. I have not been able to replicate this issue and I have > reviewed the code and am confident it is correctly capturing windSpeed data > and calculating 10 minute gust values. I suggest you upgrade to v0.2.9 and > see if the issue remains, if so we need to determine the conditions under > which the issue occurs. If this is not possible visually then I have some > wind speed debug code that will dump the windSpeed history list and other > key values to log and we will need to wade through the figures to determine > the issue. > > I did go to your previously posted link to try to observe the issues you > describe myself but the link now gives me a 403 Forbidden error. > > 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.
