https://github.com/frequenz-floss/frequenz-reporting-python
High level interface to Frequenz's Reporting API
https://github.com/frequenz-floss/frequenz-reporting-python
Last synced: about 1 year ago
JSON representation
High level interface to Frequenz's Reporting API
- Host: GitHub
- URL: https://github.com/frequenz-floss/frequenz-reporting-python
- Owner: frequenz-floss
- License: mit
- Created: 2024-09-11T11:52:19.000Z (almost 2 years ago)
- Default Branch: v0.x.x
- Last Pushed: 2025-04-09T15:12:59.000Z (about 1 year ago)
- Last Synced: 2025-04-09T16:24:05.617Z (about 1 year ago)
- Language: Python
- Size: 1.48 MB
- Stars: 0
- Watchers: 6
- Forks: 2
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# Reporting Highlevel Interface
[](https://github.com/frequenz-floss/frequenz-reporting-python/actions/workflows/ci.yaml)
[](https://pypi.org/project/frequenz-reporting-python/)
[](https://frequenz-floss.github.io/frequenz-reporting-python/)
## Introduction
A highlevel interface for the reporting API
## Supported Platforms
The following platforms are officially supported (tested):
- **Python:** 3.11
- **Operating System:** Ubuntu Linux 20.04
- **Architectures:** amd64, arm64
## Contributing
If you want to know how to build this project and contribute to it, please
check out the [Contributing Guide](CONTRIBUTING.md).
### Installation
```bash
# Choose the version you want to install
VERSION=0.1.0
pip install frequenz-reporting-python==$VERSION
```
### Initialize the client
```python
from datetime import datetime
from frequenz.client.common.metric import Metric
from frequenz.client.reporting import ReportingApiClient
from frequenz.reporting._reporting import cumulative_energy
# Change server address if needed
SERVICE_ADDRESS = "reporting.api.frequenz.com:443"
API_KEY = open('api_key.txt').read().strip()
client = ReportingApiClient(service_address=SERVICE_ADDRESS, key=API_KEY)
```
### Calculate cumulative energy for a single microgrid and component:
If the component does not measure `Metric.AC_ACTIVE_ENERGY`, set `use_active_power=True`
to utilize `Metric.AC_ACTIVE_POWER` instead.
A resampling period can be set that alters how NaNs are handled, resulting in varying
results. NaN values are ignored in sums, which may lead to significant data loss
if many are present in the raw data. There is no universally correct method for
handling NaNs, as their causes can vary.
```python
energy_reading = await cumulative_energy(
client=client,
microgrid_id=1,
component_id=100,
start_time=datetime.fromisoformat("2024-09-01T00:00:00"),
end_time=datetime.fromisoformat("2024-09-30T00:00:00"),
use_active_power=True,
resampling_period=timedelta(seconds=10),
)
print(energy_reading)
```