I'm interested in understanding wheater prediction models because accurate wind forecasts make a big difference to my personal life (sports).
Is there a good overview to learn about the current models, which all just seem like cryptic acronyms to me? in apps like Windy etc.
WRF, TRRM, IK-HRRR-3km, ECMWF-9km,...
I understand by now that small grid cells are better for local prediction and that thermic winds are mostly missing from them all.
Ask your favorite AI to give you a crash course, but to start the main models you need to know are the GFS and the ECMWF. In the US where available in high res, the HRRR is excellent, but doesn’t forecast very far out. The PWG/PWE 1km PredictWind models are also very good at picking up land based features and other more precise patterns. If you are in the US everything else is probably not super relevant.
Any advice will really depend on where you live and the dominant source of local error. These are all good options for the US and if the one main source of error is near surface winds around complex terrain then you can also look into WindNinja from the National Forrest Service.
It’s been well thought out and edited but it’s clearly written by AI, and it was obvious long before “load-bearing”. Still - it makes an important point well and is worth reading.
If every use of AI was like this, I perhaps wouldn't have this slight allergic reaction to it, but as it stands, this voice and rhythm has become associated with bad lazy grifting writing.
Parent comment has the rhythm of an AI comment. Caught myself not realizing it until you mentioned it. Seems like I am more in tune with LLM slop on twitter, which is usually much worse.
But on second sight it's clear and it also shows the comment as having no stance, and very generic.
@dang I would welcome a small secondary button that one can vote on to community-driven mark a comment as AI, just so we know.
Not working on it (yet), but I wish the jj <-> github story was a little more ergonomic.
Additionally, I am really missing support for stacked diffs, ie, easily pushing a number of commits into one PR on github each such that they all show their incremental diff.
ezyang's gh stack was pretty useful, if a little bit fragile [0]
and graphite.dev is also very nice, but paid software with a strong VC based motivation to become everyone's everything instead of a nice focused tool.
https://github.com/LucioFranco/jj-spr is one way to get stacked diffs on GitHub with jj, but also GitHub has at least claimed on X that native stacked diffs is coming so we'll see how that goes!
This stance strikes me as questionable, to use the first hunch that comes to mind to seed doubt in a topic that is researched and reported by multiple fairly reputable sources and multiple people on the ground.