8000 BDEW SLP does not consider public holidays · Issue #84 · oemof/oemof-demand · GitHub
[go: up one dir, main page]

Skip to content

BDEW SLP does not consider public holidays #84

Open

Description

@marcus-voss

I compared the 2026 SLP G0 profile to one I obtained from my local DSO (Stromnetz Berlin) and saw that e.g. January 1st and Easter are not modelled the same.

See the screenshots where I compare the two days with the profile from DSO (blue) with the library (orange).

Image Image

Activity

  1. p-snft commented on Jan 9, 2026

    @p-snft
    Member

    Thanks for bringing this up. I see that the documentation should be improved on this point: As holidays are regional, you need to provide them as an argument. Please see https://github.com/oemof/demandlib/blob/v0.2.2/examples/bdew_slp25.py for an example.

    Do you think, we should issue a warning if none are given, or alternatively do not just assume no holidays as a default. In the latter case, you could still give an empty list for no holidays, but cannot forget to give them.

  2. marcus-voss commented on Jan 9, 2026

    @marcus-voss
    Author

    Ah, okay. Indeed, this one is then also partly on (lazy) me! Didn't see the holidays argument in the ElecSlp constructor.

    I think that a list of at least the national holidays (January 1st, Easter, May 1st, Himmelfahrt, October 3rd, Christmas) should be provided by default. I suppose that would make the default "more right" for most users, wouldn't it?

  3. marcus-voss commented on Jan 9, 2026

    @marcus-voss
    Author

    I have solved it for me now with the holidays package. Given that its so convinient you could consider integrating this to get the German holidays per default for each year and maybe even asking for the local state string (like "BE" for Berlin).

  4. p-snft commented on Jan 9, 2026

    @p-snft
    Member

    I actually dislike having a default that is silently wrong. (We have one now, though.) Thus, I can imagine the following options (just taking one profile for the example):

    1. BDEW25Profile(timeindex) warns that no holidays are given, or
    2. BDEW25Profile(timeindex) fails.

    In case 1, either no holidays or another default could be assumed. (An example might be national holidays in Germany, it's BDEW after all.)

    Independent from the decision between 1 and 2, it might be made possible to provide a regional code instead of a list. (If a default set of holidays is taken, of course it makes no sense to not expose this option.)

  5. marcus-voss commented on Jan 11, 2026

    @marcus-voss
    Author

    I would prefer 1. with the warning and a default of the German national holidays as as you mentioned it is Germany after all.
    So the ones as returned by the holidays library for Germany (here for 2026):

    {datetime.date(2026, 1, 1): 'Neujahr', datetime.date(2026, 4, 3): 'Karfreitag', datetime.date(2026, 4, 6): 'Ostermontag', datetime.date(2026, 5, 1): 'Erster Mai', datetime.date(2026, 5, 14): 'Christi Himmelfahrt', datetime.date(2026, 5, 25): 'Pfingstmontag', datetime.date(2026, 10, 3): 'Tag der Deutschen Einheit', datetime.date(2026, 12, 25): 'Erster Weihnachtstag', datetime.date(2026, 12, 26): 'Zweiter Weihnachtstag'}

    Maybe you could allow for either a list or a string, which is stilly pythonic enough for my taste.
    If it is a list of datetimes, then use them, if it is a string allow for the state strings for local holidays as provided by holidays library (States: BB (Brandenburg), BE (Berlin), BW (Baden-Württemberg), BY (Bayern), HB (Bremen), HE (Hessen), HH (Hamburg), MV (Mecklenburg-Vorpommern), NI (Niedersachsen), NW (Nordrhein-Westfalen), RP (Rheinland-Pfalz), SH (Schleswig-Holstein), SL (Saarland), SN (Sachsen), ST (Sachsen-Anhalt), TH (Thüringen); cities: Augsburg)

  6. added 2 commits that reference this issue on Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0