Seismic Hazard Analysis
This is a copy of the sha_calc package in the gmhazard repository. Since the release of the new NZ NSHM the gmhazard workflow is outdated and is no longer used. However, the sha_calc contains lots of useful functions and models relevant for seismic hazard analysis.
The aim of this repository is to contain core functionality for performing simple (i.e. no logic tree support) probabilistic seismic hazard analysis (PSHA) `based on both parametric and non-parametric ground motions predictions. Additionally, it contains core functionality for computing PSHA-based extensions, such as disaggregation, uniform hazard spectra (UHS), ground motion selection (GMS) and other related functionality such the computation of spatial IM realisation.
Metadata
Release files for seismic-hazard-analysis 2026.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| seismic_hazard_analysis-2026.6.1.tar.gz | 6.9 MB | With provenance | Details for seismic_hazard_analysis-2026.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seismic_hazard_analysis-2026.6.1-py3-none-any.whl | Python 3 | none | any | Details for seismic_hazard_analysis-2026.6.1-py3-none-any.whl |
Total release size: 7.4 MB
Release files / seismic_hazard_analysis-2026.6.1.tar.gz
| Download URL | seismic_hazard_analysis-2026.6.1.tar.gz |
|---|---|
| Size | 6.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8562100350986a6e1d4ccb2a954e68a82f7bc47e3882dec08cec141e5f5a17a7
|
|
BLAKE2b-256 checksum How to use checksums |
884fd972f8458100a588c0eccec76530fc9b090163e51ddb21d9c7e72936e8a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 19, 2026.
Transparency logRelease files / seismic_hazard_analysis-2026.6.1-py3-none-any.whl
| Download URL | seismic_hazard_analysis-2026.6.1-py3-none-any.whl |
|---|---|
| Size | 529.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bef7fc25c142157328969b5125ae839a137ad8d18da775ffa8216b24c54701a8
|
|
BLAKE2b-256 checksum How to use checksums |
33ca68730d80647bcd867bd9d0b968587334dcec0d1000e339d4626844b73651
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 19, 2026.
Transparency logSecurity for seismic-hazard-analysis 2026.6.1
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 2 files in this release have been uploaded with provenance metadata.
Attestation for seismic_hazard_analysis-2026.6.1.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 Jun 19, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.