paropy
Welcome! Here is my Python package to process data from PARODY-JA4.3 dynamo simulations with a stably-stratified F-layer at the base of the outer core.
Getting Started
Prerequisites
Installing
Conda:
conda install -c jnywong paropy
Pip:
pip install paropy
Git:
Find the Git repo here.
Warning: IPython issue
Please note that ipython may not be compatible with jedi release 0.18.0. Please revert to version 0.17.2 for auto-complete features to work (see here).
Package structure
paropy/
docs/
paropy/
__init__.py
data_utils.py
plot_utils.py
routines.py
scripts/
convective_power.py
diagnostics.py
diagnostic_parameters.py
filter_surface_field.py
latitude_vs_Br.py
latitude_vs_Br_with_CHAOS.py
meridional_snapshot.py
meridional_timeavg.py
rotation_rate.py
surface_snapshot.py
surface_timeavg.py
data/
CHAOS-7.7.mat
LICENSE.md
MANIFEST.in
README.md
setup.py
Examples
Diagnostics
Example scripts can be found within the module paropy.
-
Open
paropy/scripts/diagnostics.py -
Set path to simulation data by setting
run_ID = <run_ID> # PARODY simulation tag
directory = <path_to_data>
saveDir = <path_to_savefigs>
-
Run
paropy/scripts/diagnostics.py -
Admire the output:
Meridional snapshots
-
Open
paropy/scripts/meridional_snapshot.py -
Set path to simulation data and snapshot time by setting
run_ID, timestamp = 'c-200a', '16.84707134'
directory = <path_to_data>
-
Run
paropy/scripts/meridional_snapshot.py -
Admire the output:
Surface snapshots
-
Open
paropy/scripts/surface_snapshot.py -
Set path to simulation data and snapshot time by setting
run_ID, timestamp = 'c-200a', '16.84707134'
directory = <path_to_data>
-
Run
paropy/scripts/surface_snapshot.py -
Admire the output:
Links
Data
- CHAOS-7.7 (Finlay et al. 2020)
Authors
- Jenny Wong - Institut de Physique du Globe de Paris - Institut des Sciences de la Terre
License
This project is licensed under the MIT License - see the LICENSE.md file for details
Acknowledgments
- Del Duca Foundation
- ERC SEIC
:tada:
Metadata
Release files for paropy 0.0.5
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 |
|---|---|---|---|---|
| paropy-0.0.5.tar.gz | 1.3 MB | Without provenance | Details for paropy-0.0.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| paropy-0.0.5-py3-none-any.whl | Python 3 | none | any | Details for paropy-0.0.5-py3-none-any.whl |
Total release size: 2.7 MB
Release files / paropy-0.0.5.tar.gz
| Download URL | paropy-0.0.5.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
39d2573ae6bb824100b89c1360acfeda914424832e067be92f322fb37f8f40cb
|
|
BLAKE2b-256 checksum How to use checksums |
83a4b86dabf4bcea763e7a7fe2909e2525f0038d02934b83b81d094718563015
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.6
|
Release files / paropy-0.0.5-py3-none-any.whl
| Download URL | paropy-0.0.5-py3-none-any.whl |
|---|---|
| Size | 1.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
68dcf1ae812911c6040f072c923ecc211b5baf81fdee169b90010dea1001139e
|
|
BLAKE2b-256 checksum How to use checksums |
70521fbdf0a135cdf6b64673a426766e9cbc769d719e1125588600bc93863cee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.1.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.6
|
Security for paropy 0.0.5
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.