Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

PYSTILT

Tests Documentation Code Quality codecov PyPI version Python Version License: MIT DOI Ruff

PYSTILT is a Python version of the STILT atmospheric transport model. It follows air backward in time from a measurement with HYSPLIT and computes a footprint, a map of which upwind surface areas influenced the measurement and by how much.

Status

PYSTILT is alpha software. There are no backward compatibility guarantees before v1.0, and the public API may still change.

The transport core is stable. The test suite covers HYSPLIT runs, trajectories and footprints, agreement with STILT-R, and runs on a local machine and on Slurm.

Installation

pip install pystilt

For plotting, projected grids, aggregation over shapefiles, and downloading meteorology from NOAA, install everything:

pip install "pystilt[complete]"

Quickstart

Describe a measurement, follow particles back from it through the meteorology, and calculate its footprint:

import stilt

receptor = stilt.PointReceptor(
    time="2023-07-15 18:00",   # UTC
    longitude=-111.848,
    latitude=40.766,
    altitude=10,               # meters above ground
)
met = {"directory": "/data/hrrr", "file_format": "%Y%m%d_%H", "file_tres": "6h"}
grid = stilt.Grid(xmin=-113.0, xmax=-110.5, ymin=40.0, ymax=42.0, xres=0.01, yres=0.01)

particles = stilt.run_trajectories(receptor, met, n_hours=-24, numpar=100)
foot = stilt.calc_footprint(particles, receptor, grid)

particles is a pandas DataFrame, one row per particle per step, and foot an xarray DataArray, one map per hour.

For many receptors, a project runs each one and keeps the results:

project = stilt.Project.init(
    "./my_project",
    receptors=[receptor],
    mets={"hrrr": met},
    variants={"hrrr": {}},
    n_hours=-24,
    numpar=100,
    grid=grid,
)
project.run()   # returns when the run is done

sim = project.simulation(receptor.id, "hrrr")
sim.particles, sim.footprint

Everything is saved in ./my_project. Later, open it again with stilt.Project("./my_project"). A second run() only runs what is missing. To change a setting, edit config.yaml.

Command line

stilt init ./my_project          # write a starter config.yaml and receptors.csv
stilt run ./my_project           # run every receptor that is not done yet
stilt run ./my_project --cpus 8  # the same, eight receptors at a time
stilt status ./my_project        # what has finished, and the settings folders

stilt run exits with 0 when every simulation it ran is complete, 1 when some failed, and 3 when it was stopped before they finished. Every command exits with 2 when its command line is wrong.

Variants

A variant is a named set of settings. Every receptor runs once under each variant. The top-level settings in config.yaml are the defaults, and a variant lists only what it changes. The variants section declares them all; hrrr: {} runs the defaults.

variants:
  hrrr: {}                                  # the defaults
  hrrr-zi08: {ziscale: 0.8}                 # mixed-layer height scaled by 0.8
  hrrr-err:                                 # wind-error ensemble for transport_error
    siguverr: 2.6
    tluverr: 260
    zcoruverr: 450
    horcoruverr: 14
    realizations: 4                         # realizations 0 to 3 of hrrr-err
    grid: null                              # particles only, no footprint
  hrrr-ak:                                  # another footprint from the hrrr particles
    transforms: [{kind: averaging_kernel, table: kernels}]

Each receptor under each variant is one simulation. Results go to the output directory (./output by default), in a folder named for the settings they were made with. Variants whose transport settings match share one HYSPLIT run and differ only in the footprint, as hrrr-ak does here. Adding a variant runs only what is new, and changing a setting writes to a new folder beside the old one.

On a cluster

Add an execution section to config.yaml and run the same command. PYSTILT splits the unfinished receptors among the tasks of one Slurm job array and submits it:

execution:
  backend: slurm
  n_workers: 200          # array tasks
  account: my-account
  partition: my-partition
  time: "02:00:00"
  mem: 4G
stilt submit ./my_project       # submits and returns; stilt run waits
stilt status ./my_project

Each task runs stilt run --task I/N, so a task is a command line you can read and rerun. A task that is preempted or nears its time limit requeues itself and skips the receptors it finished. Whether a simulation is finished is always decided by its files in the output directory. The same --task runs a project as a Kubernetes indexed Job.

Column and satellite soundings

Read the soundings into a table with one row per sounding, then make a receptor for each. Each sounding has its own averaging kernel, which goes into the project as a table:

import stilt
from stilt.observations import read_tropomi_ch4, receptors_from_soundings

df = read_tropomi_ch4(path)                      # or read_oco2, read_tccon, or your own reader
receptors, kernels = receptors_from_soundings(df[df.good], "slant", top=3000)

project = stilt.Project("./my_project")         # a project with a config.yaml
project.add_receptors(receptors)
project.add_table("kernels", kernels)
project.run()

Then name the table in config.yaml:

grid: {xmin: -114.0, xmax: -111.0, ymin: 39.0, ymax: 42.0, xres: 0.01, yres: 0.01}
transforms:
  - kind: averaging_kernel
    table: kernels
    coordinate: pres
  - kind: pressure_weighting

"column" makes vertical columns in place of slant lines of sight. The satellite tutorial goes from an orbit to modeled and observed enhancements.

Particle transforms

A transform changes how much each particle counts before the footprint is calculated. List them in config.yaml, as a default or for one variant:

transforms:
  - kind: averaging_kernel
    levels: [0.0, 1000.0, 2000.0]
    values: [1.0, 0.8, 0.5]
  - kind: pressure_weighting
  - kind: first_order_lifetime
    lifetime_hours: 4.0
  - kind: mypkg.transforms.BoundaryLayerOnly   # your own pydantic class with an apply() method
    max_height: 1200

A transform is any object with an apply(particles, receptor=None, directory=None) method. The transforms guide covers the column-weighting science and how to write your own.

Loading results

import pandas as pd

import stilt

sims = project.simulations                       # one row per receptor and variant
january = sims[(sims.variant == "hrrr") & sims.time.between("2023-01-01", "2023-01-31")]

project.status(january)                          # which results exist
footprints = project.footprints(january)         # one dataset: receptor, hour, lat, lon
mean = footprints.foot.sum("hour").mean("receptor")

windows = stilt.Mesh.from_windows([(-111.9, 40.7), (-111.8, 40.8)], size=0.05)
time_bins = pd.interval_range(
    start=pd.Timestamp("2022-12-31 00:00"),  # backward footprints reach a day back
    end=pd.Timestamp("2023-02-01 00:00"),
    freq="1h",
    closed="left",
)
H = project.jacobian(january, windows, time_bins)  # sparse: receptors by (hour, window)

If a simulation's particles never reach the grid, PYSTILT writes a footprint file with no cells and the reason. The simulation counts as finished, and project.footprints() lists it in attrs["empty"].

STILT-R parity

PYSTILT footprints match the STILT-R footprints to a relative tolerance of 1e-7 in every grid cell. The test suite checks this against a pinned STILT-R commit. The NetCDF files are laid out differently from STILT-R's, so read them as standard CF-1.8 NetCDF. The STILT-R parity section of the development docs has the details.

Roadmap

What is implemented and what is planned is on the roadmap page of the documentation.

Use of AI coding agents

This project is developed with the help of AI coding agents, directed and reviewed by the maintainer, who owns the design and the science.

Documentation

The full documentation is at https://jmineau.github.io/PYSTILT/.

Contributing

Contributions are welcome. See CONTRIBUTING.md for how to set up and submit changes.

License

PYSTILT is released under the MIT License. See the LICENSE file.

Author

James Mineau - jmineau

Metadata

Release files for pystilt 0.1.0a23

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pystilt 0.1.0a23
File Size Uploaded Provenance
pystilt-0.1.0a23.tar.gz 995.0 kB With provenance Details

Built distributions (wheels)

Table of built distributions (wheels) for pystilt 0.1.0a23
File Interpreter ABI Platform
pystilt-0.1.0a23-py3-none-manylinux_2_17_x86_64.whl Python 3 none Linux glibc 2.17+ x86-64 Details
pystilt-0.1.0a23-py3-none-macosx_11_0_x86_64.whl Python 3 none macOS 11.0+ x86-64 Details

Total release size: 3.2 MB

Release files / pystilt-0.1.0a23.tar.gz

Download URL pystilt-0.1.0a23.tar.gz
Size 995.0 kB
Tags Source
SHA-256 checksum
How to use checksums
105b7757a92bf4dd782dd288781275a2569f935e6e69e63862a0a06d00787b71
BLAKE2b-256 checksum
How to use checksums
fcce7657d4a36a60a0eee06d8ad154b88c7d753c1779c212d9d0624e113bf495
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 Oct 9, 2026.

Transparency log

Release files / pystilt-0.1.0a23-py3-none-manylinux_2_17_x86_64.whl

Download URL pystilt-0.1.0a23-py3-none-manylinux_2_17_x86_64.whl
Size 1.5 MB
Tags Linux glibc 2.17+ x86-64 Python 3
SHA-256 checksum
How to use checksums
e537586ecd6c131310dac9ed8bb9bf826a538fa9d1c0b74ea7f5cd20e68477f4
BLAKE2b-256 checksum
How to use checksums
cf5886ed5e1311e04cc20c5fceba26f5cd0b8a97af49672133435b2eb95a6851
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 Oct 9, 2026.

Transparency log

Release files / pystilt-0.1.0a23-py3-none-macosx_11_0_x86_64.whl

Download URL pystilt-0.1.0a23-py3-none-macosx_11_0_x86_64.whl
Size 688.0 kB
Tags Python 3 macOS 11.0+ x86-64
SHA-256 checksum
How to use checksums
0a1d257ae90541de140a31f4b308e123d7bd2cc76b4a771a9d4fb565b855a7f7
BLAKE2b-256 checksum
How to use checksums
bd66a1edc63f249525dc967957c64ed2d7b44a2559cacc2fd0befdf96bde7c50
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 Oct 9, 2026.

Transparency log

Security for pystilt 0.1.0a23

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.

Full provenance

All 3 files in this release have been uploaded with provenance metadata.

Select from 3 files

Attestation for pystilt-0.1.0a23.tar.gz

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 Oct 9, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page