Midas Default Load Profiles Data Simulator
The dlpdata module, provided by the midas-dlpdata package, provides a simulator for the default load profiles provided by the BDEW set.
Version: 2.1
Installation
This package will usually installed automatically together with midas-mosaik, if you opt-in the bh extra.
It is available on pypi, so you can install it manually with
pip install midas-dlpdata
Usage
The intended use-case for the time simulator is to be used inside of midas. However, it can be used in any mosaik simulation scenario.
Inside of midas
To use the dlp data inside of midas, add dlpdata to your modules
my_scenario:
modules:
- dlpdata
# - ...
and provide a scope and a configuration:
my_scenario:
# ...
dlp_data_params:
my_scenario:
meta_scaling: 1.5
interpolate: True
randomize_data: True
randomize_cos_phi: True
active_mapping:
15: [[G4, 262.8]]
17: [[H0, 1038.06]]
The numbers 15 and 17 stand for the bus number which depends on the used grid.
Any Mosaik Scenario
If you don't use midas, you can add the dlpdata manually to your mosaik scenario_ file.
First, the entry in the sim_config:
.. _mosaik scenario: https://mosaik.readthedocs.io/en/latest/tutorials/demo1.html
sim_config = {
"DLPSimulator": {
"python": "midas_powerseries.simulator:PowerSeriesSimulator"},
# ...
}
Next, you need to start the simulator (assuming a step_size of 900).
Since it uses a custom data model, you have to specify it here:
dlpdata_sim = world.start(
"DLPSimulator",
step_size=900,
model_import_str="midas_dlp.model:DLPModel",
use_custom_time_series=True,
start_date="2020-01-01 00:00:00+0100",
data_path="/path/to/folder/where/dataset/is/located/",
filename="bdew_default_load_profiles.csv", # this is default
)
Then the models can be started:
houshold = dlpdata_sim.CalculatedQTimeSeries(name="H0", scaling=1038.06)
trade = dlpdata_sim.CalculatedQTimeSeries(name="G4", scaling=262.8)
Finally, the models need to be connected to other entities:
world.connect(trade, other_entity, "p_mw", "q_mvar")
License
The data is taken from BDEW.
Metadata
Release files for midas-dlpdata 2.1.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 | |
|---|---|---|---|---|
| midas_dlpdata-2.1.1.tar.gz | 642.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| midas_dlpdata-2.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.3 MB
Release files / midas_dlpdata-2.1.1.tar.gz
| Download URL | midas_dlpdata-2.1.1.tar.gz |
|---|---|
| Size | 642.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f162d2655b9e4057b4ae3ab1989a4a908e885d2dfcf9064a9cbb9d4f48f33908
|
|
BLAKE2b-256 checksum How to use checksums |
217591a9a66319945435526eae6986a413d7e0d5c9ae0d8df88cf2d3b4d030f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / midas_dlpdata-2.1.1-py3-none-any.whl
| Download URL | midas_dlpdata-2.1.1-py3-none-any.whl |
|---|---|
| Size | 638.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e878b888cf22297251f455d117e1c0f65f0e52f414040228e95d79cd4f745cff
|
|
BLAKE2b-256 checksum How to use checksums |
670e5f7bdb0e113701d11c6572bfcff89ce99a82350ef27c4056f1d0349407c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for midas-dlpdata 2.1.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.