This release is a pre-release and may not be stable for production use.
fetchAZA
Repository for reading pressure data from the Sonardyne Fetch AZA into netCDF (xarray) format.
During the reading of files, there is an intermediate step where logging event lines in the *.csv data file are separated into individual netCDF files. In the processing step, the hourly data are combined into a single netCDF file (comprising PIES, DQZ, KLR, etc events, into *use.nc) and the AZA sequence events that fit a valid sequence of AZS-AZA-AZA-AZA-AZS patterns are merged into a second netCDF file (*AZAseq.nc*)
This is a work in progress as part of the EPOC project.
Install
Install from PyPI with
python -m pip install fetchAZA
Documentation
For documentation, see http://eleanorfrajka.github.io/fetchAZA.
Check out the demo notebook notebooks/demo.ipynb for example functionality.
As input, fetchAZA takes Sonardyne Fetch AZA *.csv files. See 8318-FS Issue06.pdf for details of the data format, or check out the snippet in data/sample_data.csv.
Contributing
Contributions welcome!
To install a local, development version of fetchAZA, clone the repo, open a terminal in the root directory (next to this README.md file) and run these commands:
git clone https://github.com/eleanorfrajka/fetchAZA.git
cd fetchAZA
pip install -r requirements-dev.txt
pip install -e .
This installs fetchAZA locally. -e ensures that any edits you make in the files will be picked up by scripts that import functions from fetchAZA. You can run the example jupyter notebook by launching jupyterlab with jupyter-lab and navigating to the notebooks directory.
All new functions should include tests. You can run the tests locally and generate a coverage report with:
pytest --cov=fetchAZA --cov-report term-missing tests/
Metadata
Release files for fetchAZA 0.0.3.post1.dev0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| fetchaza-0.0.3.post1.dev0.tar.gz | 1.6 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fetchaza-0.0.3.post1.dev0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 MB
Release files / fetchaza-0.0.3.post1.dev0.tar.gz
| Download URL | fetchaza-0.0.3.post1.dev0.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0a999db479539df4bece3fb8323dcf8b4f203b58165eab54f600172703c46d5
|
|
BLAKE2b-256 checksum How to use checksums |
34ca3ee404f5173e894ef0879efeda3f04f176234cc67ba2988c6819ca2f3874
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 19, 2025.
Transparency logRelease files / fetchaza-0.0.3.post1.dev0-py3-none-any.whl
| Download URL | fetchaza-0.0.3.post1.dev0-py3-none-any.whl |
|---|---|
| Size | 38.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96f204ca4165b14b3bb80c2c12e6eca89b8a888e93ab5bb80a96883b72577536
|
|
BLAKE2b-256 checksum How to use checksums |
8c48a3cd46a58a6fc622bb119a7ef3dd24343ad9e98292b00e2a1f0f05fc1041
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 19, 2025.
Transparency log