EPyGrAM
Enhanced Python for Graphics and Analysis of Meteorological fields
The epygram library package is a set of Python classes and functions designed to handle meteorological fields in Python, as well as interfacing their storage in various usual (or not) data formats.
Dependencies
EPyGrAM dependencies are available from Pypi (pip install ...), and listed in pyproject.toml.
Some packages are mandatory, others are optional, only necessary for the use of specific functionalities or formats.
Formats for which the import of the according underlying package fails are deactivated at runtime.
Installation
pip install epygram
or
pip3 install epygram
To use specific functionalities which dependencies are not covered by default, you may need to manually pip install the according package(s).
You can also install all optional dependencies using:
pip install epygram[all]
or
more specifically one of the extra group of dependencies:
pip install epygram[<opt>]
with <opt> among (graphics, docs, features, extra_formats), cf. pyproject.toml.
Tests
To run tests, cf. tests/README.md.
Documentation
To generate Sphinx doc: make doc. It will be generated in docs/build/html.
Online doc of the latest release on master branch is available at https://umr-cnrm.github.io/EPyGrAM-doc
Applicative tools
Some applicative tools in command line are provided and installed by pip.
These tools are available through a single command line epygram with sub-commands:
epygram -hto list available sub-commandsepygram <sub-command> -hfor auto-documentation of each tool/sub-command.
or as epy_<sub-command> (pip should have placed them in your $PATH).
Example, to plot a field:
epygram cartoplot <file> -f <field>
or
epy_cartoplot <file> -f <field>
are equivalent to
epy_cartoplot.py <file> -f <field>in versions prior to 1.6.0
License
This software is governed by the open-source CeCILL-C license under French law, cf. LICENSE.txt. Downloading and using this code means that you have had knowledge of the CeCILL-C license and that you accept its terms.
Metadata
Release files for epygram 2.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| epygram-2.1.0-py3-none-any.whl | Python 3 | none | any | Details for epygram-2.1.0-py3-none-any.whl |
Release files / epygram-2.1.0-py3-none-any.whl
| Download URL | epygram-2.1.0-py3-none-any.whl |
|---|---|
| Size | 3.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
774f0462a10a66491678a15a9cb9d4a442d66915de477a612801c43e50c0f8e8
|
|
BLAKE2b-256 checksum How to use checksums |
10b0aeb808e88e28eda57ff521e95192d91be2b018d94bdbdefd55d72b04b68c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for epygram 2.1.0
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.