openego / eDisGo / 33632916784
84%
dev: 84%

LAST BUILD BRANCH: 739-task-decouple_regular_test_suite_from_live_OEP_access
DEFAULT BRANCH: dev
Ran
Jobs 1
Files 68
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 83.789%. First build
33632916784

push

github

joda9 
docs(presets): correct the spatial_reduction_opf header and cover opf_version 3

The header of `spatial_reduction_opf.yaml` described a preset that does not
exist here. It called itself "UC6", explained at length how it was ported from
`edisgo_run_edisgo`'s `uc6_spatial_reduction.yaml`, and told the reader to
"port the uc5 feature from edisgo_run_edisgo first" to get automatic timestep
selection back — a feature this branch has always had as
`select_critical_timesteps`, which `overlying_grid_opf_spatial.yaml` uses. It
also named the branch as `feat/pipeline-runner` and called
`spatial_reduction.enabled` false by default, while the preset sets it true
twenty lines below.

Replaced with what the preset actually is: the standalone sibling of
`overlying_grid_opf_spatial` that reads overlying-grid data from a CSV
directory and uses a fixed time window instead of automatic selection, i.e.
the cheap path for a smoke run — explicitly not the preset to point eGo at for
production.

Both presets also claimed eGo could inject the `spatial_reduction` block.
It cannot: `_build_run_edisgo_config` emits only `extends`, `scenario`,
`grid`, `results`, `database` and `overlying_grid`, so naming a preset that
already enables spatial reduction is the only way an eGo run gets it. Both
comments now say so, which matters because it is the reason the exemplary
scenario settings have to name `overlying_grid_opf_spatial`.

The inline note on `aggregation_mode` read "start with false; true enables
load/generator merging", as if `true` were merely the next step. It is not
usable: `apply_busmap` renames loads but leaves the flexibility input frames
(`heat_demand_df`, `flexibility_bands`, `dsm.p_min`) under the old names, so
`optimize` fails with a KeyError on a merged grid. The comment says that now.

Finally, a happy-path test for `opf_version=3`. It is the value both
overlying-grid presets ship and it was covered by no test anywhere — the
existing ones exercise 1, 2 and 4. The ... (continued)

9469 of 11301 relevant lines covered (83.79%)

0.84 hits per line

Jobs
ID Job ID Ran Files Coverage
1 33632916784.1 68
83.79
 GitHub Action Run
Source Files on build 33632916784