gpuwm-data
Physics reference tables for gpuwm.
Install gpuwm and this arrives with it:
pip install gpuwm
You do not install this package by hand and you do not choose it. gpuwm
declares gpuwm-data==<its own version> as a hard dependency, because a
gpuwm that cannot run radiation or Thompson microphysics is not an
install. There is no extra to remember and no post-install step.
Why it is a separate distribution
PyPI rejects any file over 100 MiB. The 2.5.0 gpuwm wheel measured
103.62 MiB. These two directories of pure reference data were 64.21 MiB of
that, so they ship here and gpuwm ships at 39.41 MiB.
What is in it
| Directory | Contents |
|---|---|
gpuwm_data/data/rrtmgp/ |
RTE+RRTMGP k-distribution and cloud-optics NetCDFs, the RFMIP clear-sky input profiles, and the license and provenance texts that document them |
gpuwm_data/data/thompson/tables/ |
The Thompson microphysics lookup tables generated by WRF v4.6.1's thompson_init, plus CCN_ACTIVATE.BIN for the aerosol-aware variant, under MANIFEST.sha256 |
Every byte is a table. There is no compiled code and no platform coupling,
so one py3-none-any wheel serves every platform gpuwm runs on.
Two of the Thompson tables are not here: freezeH2O.dat (243 MiB) and
qr_acr_qg_V4.dat (71 MiB) are each over the same PyPI limit that split
this package out. They are published as GitHub release assets and staged
by gpuwm fetch-tables, byte-verified against the pins in
gpuwm.core.thompson_contract. Only mp_physics=8/28 runs need them.
Reading it
gpuwm resolves these paths through gpuwm.data_assets, which is the only
supported way in. If you want the directory yourself:
import gpuwm_data
gpuwm_data.data_root() / "rrtmgp" / "rrtmgp-gas-lw-g256.nc"
Provenance and licensing
The code here is Apache-2.0. The data is not uniformly so, and each
directory carries its own texts: see data/rrtmgp/PROVENANCE.md with its
LICENSE, LICENSE-CC-BY-4.0 and LICENSE-CC-BY-SA-4.0 files, and
gpuwm's own gpuwm/data/thompson/PROVENANCE.md for the WRF-derived
Thompson tables. The four CC-BY-NC-SA-4.0 RFMIP reference-result NetCDFs
are deliberately excluded from this wheel so a non-commercial restriction
never attaches to it; they remain in the source repository as test
fixtures.
Source and issues: https://github.com/FahrenheitResearch/arwen
1 maintainer
Release files for gpuwm-data 2.7.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gpuwm_data-2.7.7.tar.gz | 67.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gpuwm_data-2.7.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 134.7 MB
Release files / gpuwm_data-2.7.7.tar.gz
| Download URL | gpuwm_data-2.7.7.tar.gz |
|---|---|
| Size | 67.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0d2b583fdcd16d296860f092905cd2c3ca32b0ece664cf04f086a70135c7eee2
|
|
BLAKE2b-256 checksum How to use checksums |
a101b2d1f5d19e07a5a3c67d5370284780e10e69b1baa48a6e973ca3c6bee590
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / gpuwm_data-2.7.7-py3-none-any.whl
| Download URL | gpuwm_data-2.7.7-py3-none-any.whl |
|---|---|
| Size | 67.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8a8a2f6dc157dc262e5e40225c6389411523c850725b2225b0bffe1d9d6cf717
|
|
BLAKE2b-256 checksum How to use checksums |
7f347c202487d946f6e6822e805a6d401d5b16fb883c2a92769d1ee71dc69b25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log
