openego / eDisGo / 41803348028

87%

Build Type

push

github

Committed by web-flow

Commit Message

feat(timeseries): unify calendar-year handling via a single reference year (#769)

* feat(timeseries): unify calendar-year handling via a single reference year

Replace hardcoded `2011` throughout the timeseries-import subsystem with a
single configurable `reference_year` (config [timeindex] section, default
2011); unsupported leap years are now uniformly shifted onto it with a
warning instead of being handled inconsistently across call sites.

Decouple scenario (eGon2035/eGon100RE) from calendar year: the scenario now
only determines which data is loaded, never the index year. Replace
tools.get_year_based_on_scenario with tools.validate_scenario, keeping the
old function as a deprecated backward-compat wrapper.

Introduce align_to_edisgo_timeindex to consistently year-align raw data
(overlying grid CSVs/eTraGo, SimBEV flexibility bands, HeatPump/DSM data,
user-provided feed-in/load DataFrames) onto TimeSeries.timeindex instead of
silently producing NaN or raising KeyError. Move this alignment into the
library (OverlyingGrid.from_csv/from_etrago) so the run-pipeline task
contains no calendar logic of its own; fixes dispatchable_generators_active_power
from eTraGo never being aligned (unlike renewables_potential).

Add a TimeSeries.check_integrity warning for non-worst-case attributes
indexed in a different year than timeindex.

* route the constructor's timeindex through set_timeindex so a leap year is normalized before anything else is indexed by it

* Relabel every time index to the reference year via one helper

set_timeindex and _timeindex_helper_func relabel any time index to the
reference year, not only leap years. 29 February is always dropped, also
for a leap reference year, and the full-year index is built by date. A
time index across the year boundary raises a ValueError.

* Relabel user-provided time series to the reference year

set_time_series_manual, the predefined dispatchable generator and charging
point setters, HeatPump.set_cop/set_h... (continued)

Coverage Stats

144 of 146 new or added lines in 12 files covered. (98.63%)

3 existing lines in 1 file now uncovered.

10248 of 11817 relevant lines covered (86.72%)

0.87 hits per line