Midas PV and Wind Data Simulator
The pwdata module, provided by the midas-pwdata package, provides a simulator for PV and wind time series.
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-pwdata
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 pwdata inside of midas, simply add pwdata to your modules
my_scenario:
modules:
- pwdata
# - ...
and provide a scope and a configuration:
my_scenario:
# ...
pwdata_params:
my_grid_scope:
interpolate: True
randomize_data: True
randomize_cos_phi: True
active_mapping:
16: [[onshore_p_mw, 5]]
17: [[solar_p_mw, 0.03]]
20: [[solar_p_mw, 0.41]]
The mapping has to match to the grid that you're using.
Any Mosaik Scenario
If you don't use midas, you can add the pwdata manually to your
mosaik scenario_ file. First, the entry in the sim_config:
sim_config = {
"PVWindData": {"python": "midas_powerseries.simulator:PowerSeriesSimulator"},
# ...
}
Next, you need to start the simulator (assuming a step_size of 900):
pw_sim = world.start(
"PVWindData",
step_size=900,
data_step_size=3600,
is_load=False,
is_sgen=True,
start_date="2020-01-01 00:00:00+0100",
data_path="/path/to/folder/where/dataset/is/located/",
filename="pvwind_profiles.csv", # this is default
)
Then the models can be started:
wind = pw_sim.CalculatedQTimeSeries(name="on_shore_p_mw", scaling=5)
pv1 = pw_sim.CalculatedQTimeSeries(name="solar_p_mw", scaling=0.03)
pv2 = pw_sim.CalculatedQTimeSeries(name="solar_p_mw", scaling=0.41)
Finally, the modells need to be connected to other entities:
world.connect(wind, other_entity, "p_mw", "q_mvar")
License
The data set is taken from 50Hertz.
Metadata
Release files for midas-pwdata 2.1.0
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_pwdata-2.1.0.tar.gz | 9.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| midas_pwdata-2.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.0 kB
Release files / midas_pwdata-2.1.0.tar.gz
| Download URL | midas_pwdata-2.1.0.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c15c4d227c4d3bf34d929db1babfaafc8632ba89a290447ff87be998ea73b610
|
|
BLAKE2b-256 checksum How to use checksums |
026e26bff65105e556503558d8c130186273ba041e15bc42d9b544c9a1d90003
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Release files / midas_pwdata-2.1.0-py3-none-any.whl
| Download URL | midas_pwdata-2.1.0-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d4d7f018e2cde777acc304a8e476b2bbfb1cddc6dcaaa5b0d1b95e12aeca91c
|
|
BLAKE2b-256 checksum How to use checksums |
e51738b7ed1913d1628f899850a1051a37e271ca72132a83a0a12476a8e127ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.11
|
Security for midas-pwdata 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.