Repository navigation
Conversation
|
Actually this fix only targeted the MASTR data. For the aggregated data across all data sources it produces undesired side effects. E.g. for Neurath, the DateOut is with all sources enables is currently infered as 2033 and the opposite problem arises, all 4 GW remain operational: Snippet from the Copilot report: Run Capacity DateIn DateOut Main source association What improved: using the comparison’s retirement convention, Neurath capacity available in 2026 falls from 4211 MW to 2120 MW, as desired. What remains problematic: The two retired rows describe overlapping Neurath blocks from different sources. They were not consolidated, so final historical capacity rises from 4211 to 6435 MW. |
The Problem
Decomissioning is too aggressive, when DateOut is missing for some units, consider e.g. the Neurath powerplant which has several blocks recorded in MASTR:
So, it's a 4 GW PP out of which around 2 GW have been decommissoned before 2024.
However, aggregation turned this into:
Which means that all 4 GW get registered as decomissioned in 2024.
This PR
Instead of aggregating all matching units into one plant, this change distinguishes the units based on the given DateOut.
This PR distinguishes based on the new config option
grouping_years_dateoutand keeps a separate row for units with DateOut = NaNChanges proposed in this Pull Request
Checklist
docs.docs/release_notes.mdof the upcoming release is included.docs/contributors.md.