CALPUFF access inquiry โ€” draft, not sent

Prepared 5 September 2026. The recipient is listed on the provider's Version 7 download page. Sending this inquiry and accepting software licence terms are separate decisions. No agreement has been accepted and no inquiry submitted.

To: calpuff@webLakes.com
Subject: CALPUFF Version 7 access and reproducible research use โ€” Howe Sound

Hello,

I am developing a public-facing research project about possible flare dispersion around Woodfibre LNG in Howe Sound, British Columbia. The work is currently exploratory. It does not claim validated exposure predictions or regulatory acceptance.

Your download page identifies CALPUFF 7.2.1, level 150618, as available by request. Could you provide access to the appropriate current standard distribution, its Fortran source, matching documentation and a small reference case with expected outputs? A case exercising the flare source and changing winds would be especially useful. Please identify the matching CALMET and CALPOST versions and any known requirements for building on macOS arm64 with GNU Fortran.

I would also appreciate clarification of permitted reproducibility practices under your licence. The intended public materials are source citations, configuration descriptions, our own inputs and processing code, validation results and derived maps. We would like to understand which model input/output examples may be shared, what restrictions apply to redistributing your program files, and whether any platform-only source adaptations would need submission to you. Please identify any additional component terms, including those relevant to chemistry options.

We have ECCC HRDPS GRIB2 fields and local observations. If you maintain or recommend a documented input pathway from those fields to CALMET, please point us to it; we understand CALWRF is specifically a WRF netCDF converter.

Thank you.


Before sending, the sender may add their name and preferred contact details. No affiliation, professional certification or licence acceptance is implied by this draft. The access-readiness record preserves the checked versions and unresolved access requirements.