ArWen 2.2.1
·
10 commits
to main
since this release
ArWen 2.2.1 fixes the ERA5 route for everyone it broke: the one-file config that gpuwm domain --source era5 writes now loads in every entry point, so the documented chain from wizard to rendered PNGs runs again from a fresh install.
Fixed
- The config
gpuwm domain --source era5writes is accepted everywhere a config loads:gpuwm check,gpuwm run,gpuwm fetchand the ERA5 initialization front door all consume[case_data]instead of refusing the file it sits in. - Big-domain ERA5 preparation no longer refuses the cache it just wrote; domains of 448x448 and larger prepare again.
- The composed Thompson + Shin-Hong profile no longer stops with a non-finite TKE error on real forecast cases. When its diagnostic-only TKE chain hits a legitimate zero, the value is repaired to the scheme's own floor and the run prints a one-line advisory and continues; that line is expected, not a problem to report.
- An ERA5 series that starts before the experiment start hour is trimmed with a message instead of refused.
- The fetch cache stores one copy of each downloaded object instead of two, cutting its disk use by 25 percent.
gpuwm doctorrecommends the CUDA library wheels that match the CUDA major your box actually serves, and a new check tells a missing CUDA header tree apart from a broken CuPy install and prints the remedy that fixes it.- Releases publish more reliably.
Known issues
- The HRRR native route does not expose
[tiles]. [tiles]streaming currently starts only on Linux; on Windows the memory planner refuses before the configured budget is read.- The ERA5 config route and
gpuwm downscaledo not expose[tiles].
Full detail in CHANGELOG.md.