-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wind thresholds changed recently #20
Comments
Hullo there! Let me make a branch for you for testing and observations: v2-webhook-rawrbooks Most of 2021 I myself got a lot of unexpected wind, and it was pretty accurate, but then winter happened (when we normally get a lot of wind IRL) and neither the game nor the bot has said it'd be windy. It's very rare here, so I'm glad you're looking into it again. I'll give you edit access to the branch, but you an also tell me what changes to the current thresholds or formula you want to make to start with and I'll edit it in. |
hi!! thank you! I actually am in the very beginning stages of learning to code, so not sure that I'd be able to help with edits, but I can certainly track my weather and in-game responses to try and get an idea of where the pull formula might have changed. I'll tap a few friends to try and come up with hypotheses of what's happening too! I'll make a note to follow up in a couple weeks and see what data I can gather in the meantime, but I had some phantom wind yesterday where it was supposed to be partly cloudy and was windy instead lol. |
Hi!
I have been a little delinquent with gathering data but will start doing so
again this week and next week.
Do you know how to calculate local pull times (like the in-game ones rather
than the ones we set with the bot)? I'm still not totally clear and
sometimes the time period when the weather matches the bot's predictions
varies. I can send an example if that would help clarify my question!
|
Honestly, I gave up trying to estimate the pull times completely... In my region I've never noticed the pulls update more than once in an hour on the hour. But AJ has observed them changing within the hour more than once, and so much of it is still in the air 🥲 In my case, the updates happened anything from 10 to 15 minutes after the hour. Which I found out by querying every five minutes for an hour, and noting when they actually updated. Since they update only once, even that fuziness of when the data actually shows up in a query wasn't enough to worry about. I just let the bot pull in the middle of the hour. |
Hahaha yeah it seems like the hour of the day that they happen changes here
too (I have a notes section in my server and it's littered with weather
observations where I've been noting when the weather predictions are
accurate (assuming there's one hour where they are after that, I've been
assuming that's the pull time and others are 8h after and 16 after
respectively)). :'(
My friend who also noticed the wind changes theorized that it might have
had to do with gust vs constant wind speed. I've had wind in game today
almost the whole evening, with none of it predicted by castform. If I
recall correctly, AccuWeather had a constant wind speed of under 25km/h but
gusts of 40km/h, so maybe they're going by gust speed instead of constant
wind now? Or maybe the threshold was lowered 🤔 I'll try to gather some
more observations RE predicted constant speed vs gusts.
Hannah Madsen, MA, MBA, MLIS
Email: ***@***.***
Cell: 780-940-8765
LinkedIn: hbmadsen
…On Sun., Feb. 13, 2022, 00:47 Sayantan Chaudhuri, ***@***.***> wrote:
Honestly, I gave up trying to estimate the pull times completely...
In my region I've never noticed the pulls update more than once in an hour
on the hour. But AJ has observed them changing within the hour more than
once, and so much of it is still in the air 🥲
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR7F6K2M4KREL4XCW6NKRILU25OZDANCNFSM5LWX7KNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Yes I have done an experiment before where I have observed the wind speed predictions changing within the hour that has the possibility to affect the forecast, but I'd be surprised if this was a consistent problem. I gave up a while ago now trying to predict the actual pull time, I notice now and then that the forecast still lags behind by a number of hours (rain is very helpful with that as it overrides the wind). But that combined with the minute of the pull, the uncertainty that we are actually using the correct Accuweather location etc etc makes it pretty painful to try and nail down. I settled on It's interesting that you have no wind prediction at all though and wind in game. I haven't monitored much myself in recent times but I always had the problem the other way around - predicting wind when it never came. There was always a feeling that there was an upper gust limit that would trigger it but I was never able to see this in my own data conclusively. But yes this was all a while ago now so it absolutely could have changed! |
I have phantom wind today (I'm based out of Edmonton Alberta, and it's both
flat and gets airflow from polar vortexes etc, so we get loads of wind all
the time), so I'm doing some hourly tracking. do we know what the current
bot formula is for constant vs gust speed that triggers a wind prediction?
H
…On Sun, 13 Feb 2022 at 06:50, Adam Stewart ***@***.***> wrote:
Yes I have done an experiment before where I have observed the wind speed
predictions changing within the hour that has the possibility to affect the
forecast, but I'd be surprised if this was a consistent problem. I gave up
a while ago now trying to predict the actual pull time, I notice now and
then that the forecast still lags behind by a number of hours (rain is very
helpful with that as it overrides the wind). But that combined with the
minute of the pull, the uncertainty that we are actually using the correct
Accuweather location etc etc makes it pretty painful to try and nail down.
I settled on :35 for the pull and left it at that.
It's interesting that you have no wind prediction at all though and wind
in game. I haven't monitored much myself in recent times but I always had
the problem the other way around - predicting wind when it never came.
There was always a feeling that there was an upper gust limit that would
trigger it but I was never able to see this in my own data conclusively.
But yes this was all a while ago now so it absolutely could have changed!
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR7F6K4AMOL66F5HDOGPHNLU26ZJJANCNFSM5LWX7KNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
The relevant logic is here: discord-bot-castform/model-ajstewart.js Lines 155 to 182 in adcef34
Line 173 is the windy decision. However on my instance I run the gust threshold as |
interesting! a friend coded it to my server for me, so I've asked him for
the code he used (just to double check the wind thresholds are the same).
Here's what I got so far today:
[image: image.png]
As silly as it is, I wonder if they lowered the constant wind speed to 19
or 18 km/h and that's what's creating the issue. I'm going to keep tracking
and see if I get the same thing again, assuming that I have more days with
medium wind instead of crazy wind.
Cheers,
…On Mon, 14 Feb 2022 at 11:17, Adam Stewart ***@***.***> wrote:
The relevant logic is here:
https://github.com/5310/discord-bot-castform/blob/adcef34a015466c1f22a5b1bd97d20a8561db742/model-ajstewart.js#L155-L182
Line 173 is the windy decision.
However on my instance I run the gust threshold as 29.6, not 30 as is
used here in line 158.
—
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AR7F6KZ5652XI74N7674KF3U3FBM5ANCNFSM5LWX7KNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
Hello!, so I've been trying to run this on my discord server, but I can't quite seem to be able to grasp how to is there any way you can make a video tutorial on how to do it? |
Hi,
I and others in my discord server have noticed that the game has changed how it accounts for gusts -- either pulling wind based solely on gust speed or something else about how it relates to overall wind speed. Regardless, I'm now getting lots of "phantom wind", wind that shows up in-game but not in the bot. I'm down to do some documentation in order to figure out exactly what has shifted, if y'all could change the code so that it uses a more accurate variable. Could someone partner with me for it?
The text was updated successfully, but these errors were encountered: