AutoRPE
(Automatic Reduced Precision Emulator)
AutoRPE is a tool designed to optimize the numerical precision of computational science models written in Fortran. Originally developed to enable the use of a Reduced Precision Emulator (RPE) ( Dawson, A. and Düben, P. D.: 2017) in large-scale codes such as NEMO, AutoRPE has since evolved into a framework for streamlining code modifications, managing precision experiments, and facilitating precision sensitivity analysis.
Features
- Automatic Code Manipulation:
Modifies Fortran source code to implement reduced precision emulation, reducing manual effort.
- Precision Sensitivity Analysis:
Identifies sensitive variables requiring higher precision using algorithms like binary search.
- Workflow Management:
Automates precision testing workflows to minimize manual intervention and ensure reproducibility.
- Code Coherency Assurance:
Detects and resolves inconsistencies in variable types to ensure code correctness.
Background
Global warming and climate change pose significant challenges to humanity due to their social, economic, and environmental impacts. Better understanding and improved capacity to forecast climate evolution can support the development of ambitious adaptation policies. Earth system models (ESMs) are crucial for simulating and predicting climate behavior, but their computational demands continue to grow with advancements such as higher resolution and ensemble forecasting. Efficient use of computational resources has become essential, and mixed-precision approaches are emerging as a way to enhance performance by reducing memory and computational costs. However, identifying variables that can safely operate at reduced precision without compromising model accuracy is complex. AutoRPE was developed to automate this process, enabling the exploration of mixed-precision configurations in full-scale models and facilitating performance improvements in computationally intensive simulations.
Documentation
For detailed documentation on installation, usage, and workflows, visit the AutoRPE Documentation.
Metadata
Release files for AutoRPE 1.0.1
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 |
|---|---|---|---|---|
| autorpe-1.0.1.tar.gz | 139.2 kB | Without provenance | Details for autorpe-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| AutoRPE-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for AutoRPE-1.0.1-py3-none-any.whl |
Total release size: 309.7 kB
Release files / autorpe-1.0.1.tar.gz
| Download URL | autorpe-1.0.1.tar.gz |
|---|---|
| Size | 139.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e108f59d13a0001401a0d20d4475c5a6d766b0179b506acb93db19503fd4954
|
|
BLAKE2b-256 checksum How to use checksums |
686c5289024491d736bc0cf056bc3bfecdd3c3ac46fbed18165daf4b82da45cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Release files / AutoRPE-1.0.1-py3-none-any.whl
| Download URL | AutoRPE-1.0.1-py3-none-any.whl |
|---|---|
| Size | 170.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b57943d95a06ef4f5fdb28b576716140b126c509da8e681f001e2af7c8eda30c
|
|
BLAKE2b-256 checksum How to use checksums |
540e067d146c7438526dbaf5010f7058fa48eee106522ca8f21fee93b1adc18f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.0.1 CPython/3.12.8
|
Security for AutoRPE 1.0.1
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.