IAL expertise
Expert tools to analyse the outputs of IAL configurations.
Each expert is addressing a different kind of output, being able to parse or read these outputs, and compare them to a reference output.
This package has been developped primarily for the needs of Davai which uses these experts to state on the outputs of tests conducted on a code contribution to IAL or other associated source repositories.
Currently implemented experts (non-exhaustive list)
Experts currently are implemented for the following metrics:
- Norms (spectral, gridpoint)
- Fields in FA/GRIB output files
- Jo-tables
- DrHook profiling
- OOPS observation operators, direct and adjoint test
- OOPS model adjoint test
- Bator obscounts, Canari statistics
- Gmkpack build
- Variables printed in model setup
Expert Board
The analysis and comparison are processed through the use of an ExpertBoard object, whose class is provided in the package.
Experts doc generation
Using Vortex's tbinterface.py:
tbinterface.py -f json -c outputexpert -n ial_expertise
1 maintainer
Metadata
1 maintainer
Release files for ial-expertise 1.3.4
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 |
|---|---|---|---|---|
| ial_expertise-1.3.4-py3-none-any.whl | Python 3 | none | any | Details for ial_expertise-1.3.4-py3-none-any.whl |
Release files / ial_expertise-1.3.4-py3-none-any.whl
| Download URL | ial_expertise-1.3.4-py3-none-any.whl |
|---|---|
| Size | 49.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1339f1fb73721ebc41993162e9eee8ef6abfda639658342a9cb684c24ee5fd3
|
|
BLAKE2b-256 checksum How to use checksums |
ea1a907a25fca539415e71e466a72803a75c16713251bbf64749444fe0188f51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.3
|
Security for ial-expertise 1.3.4
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.
