Skip to content

ArWen 2.3.3

Choose a tag to compare

View all tags
@FahrenheitResearch FahrenheitResearch released this 14 Aug 21:13
· 6 commits to main since this release
v2.3.3
569bdc8

A fast follow on 2.3.2, which shipped worldwide 30 m terrain that no documented install could reach.

Fixed:

  • pip install gpuwm now carries the high-resolution terrain path. rasterio and pyproj were an optional geog extra that [all] excluded and no quickstart named, so following the terrain doc downloaded 160.7 MiB of tiles and then died on a missing import. Both are ordinary dependencies now, so every published install line reaches the feature.
  • The terrain path refuses a missing geography stack before it fetches anything, by name, with the exact command to run. The old check ran after the download and escaped gpuwm static as a raw traceback at exit 1. It is one sentence at exit 2 now, with nothing fetched.
  • on_refuse = "fallback-30s" no longer swallows that refusal. A source coverage policy must not answer an install question with 900 m terrain.
  • gpuwm doctor reports geography stack (rasterio + pyproj), so the product can say this before a run instead of after a download.
  • gpuwm static no longer requires a forcing GRIB and a Vtable it never opens. Building terrain no longer needs a forecast cycle on disk first.
  • docs/public/HIGHRES-TERRAIN.md carries an install line and a worked example that produces real terrain: one 40 x 40 km Alpine domain at 1 km, about 80 MB of tiles. Verified end to end from a PyPI install.
  • Terrain doc reproduce commands use python -m tools.<module>, which works off a wheel. python tools/<file>.py needed a source checkout that a pip install does not provide.
  • docs/install.md documents every extra, including [obs] and [dealias], which code told users to install and no document mentioned.

Known issues:

  • The geog extra is retained and empty so pip install 'gpuwm[geog]' keeps working. It adds nothing.
  • Outside the United States a high-resolution run still replaces terrain only. Land use and soil remain the 30 arc-second baseline, unchanged from 2.3.2.
  • The base install grows by about 119 MiB. rasterio ships wheels for the same platforms netCDF4 already required, so no platform loses the ability to install.

Full detail: CHANGELOG.md

Assets 5
Loading