storm-lists
This package compiles Python implementations of various geomagnetic storm lists.
Citations
When using this software, please cite the Zenodo record as well as the paper corresponding to the list you are using:
- Noora Partamies et al. (2013), Statistical properties of substorms during different storm and solar cycle phases, Annales Geophysicae, 31(2), 349–358. https://doi.org/10.5194/angeo-31-349-2013
- Maria-Theresia Walach and Adrian Grocott (2019). Superdarn observations during geomagnetic storms, geomagnetically active times, and enhanced solar wind driving, Journal of Geophysical Research: Space Physics, 124(7), 5828–5847. https://doi.org/10.1029/2019JA026816
Funding
John C Coxon was supported during this work by Science and Technology Facilities Council (STFC) Ernest Rutherford Fellowship ST/V004883/1.
Installation
To install and test the model, simply type:
pip install storm-lists
Usage
For examples of how to use the models, see the Jupyter notebooks in the notebooks directory.
Model-specific notes
Walach and Grocott (2019)
The Walach and Grocott (2019) implementation in this module is directly based on the IDL code used to generate the list for that paper.
Partamies et al. (2013)
The Partamies et al. (2013) implementation in this module is based on the description in the paper, and it makes assumptions outlined below.
- The rate of change at a timestamp is calculated between Dst at the timestamp and Dst at the previous timestamp.
- The recovery phase start is set to the last timestamp at which the rate of change is still under the threshold.
- If there is only one hour where the rate of change is below the threshold, the main phase and recovery phase are set to the same timestamp.
- When a local minimum in Dst is not associated with a rate of change below the threshold, it is ignored and the algorithm runs again neglecting that minimum Dst. (This implies that Dst can theoretically still continue to decrease during the recovery phase before starting to recover.)
- When looking back to the point at which Dst exceeded the start threshold, if that point has already been labelled as belonging to the storm, the start of the storm under consideration is set to one hour after the previous storm end and the storm type is set to 2 (as opposed to the default value of 1).
1 maintainer
Metadata
1 maintainer
Release files for storm-lists 1.0.3
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 |
|---|---|---|---|---|
| storm_lists-1.0.3.tar.gz | 8.2 kB | With provenance | Details for storm_lists-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| storm_lists-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for storm_lists-1.0.3-py3-none-any.whl |
Total release size: 18.2 kB
Release files / storm_lists-1.0.3.tar.gz
| Download URL | storm_lists-1.0.3.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
224bda88cde040e67afef17ceb93bd50b0c81c63bd54dd11e6b101573bdd89d7
|
|
BLAKE2b-256 checksum How to use checksums |
086476b0fd719432f223cd4fc8cf85de5f2cbee7f56d36f22c4c44ee54d26852
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Nov 4, 2025.
Transparency logRelease files / storm_lists-1.0.3-py3-none-any.whl
| Download URL | storm_lists-1.0.3-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a1c54139d2c3353e2a7f9ec91d759898ccbb400122703643ecc109d0f2a483a5
|
|
BLAKE2b-256 checksum How to use checksums |
66f56776e3563ace27cada1079e6dba4abb8034f6d121f1e639c00ff1288fe72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Nov 4, 2025.
Transparency logSecurity for storm-lists 1.0.3
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
Both files in this release have been uploaded with provenance metadata.
Attestation for storm_lists-1.0.3.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 Nov 4, 2025.
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.
