Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Data Issue]: Remove EE, LV, LT<->RU-1 & BY Exchanges (placeholder issue for future event) #7480

Open
brandongalbraith opened this issue Nov 28, 2024 · 4 comments
Labels
data Issues or PRs relating to underlying data. needs triage Issues that need to be triaged and manually labeled.

Comments

@brandongalbraith
Copy link
Contributor

When did this happen?

2025-02-08 (future event)

What zones are affected?

EE, LV, LT, RU-1, BY

What is the problem?

On February 8th, 2025, the Baltic states intend to disconnect from zones RU-1 and BY and syncronize with the EU power grid. This issue is a stub to remove those exchanges after that transition occurs.

Sources:

https://apnews.com/article/baltics-russia-belarus-europe-electricity-transmission-a42f86ca20b7d878dc17c7cafed861bc

Utility operators Elering of Estonia, AST of Latvia and Litgrid of Lithuania said that the exit notice was signed in the Latvian capital of Riga on Tuesday. The joint agreement with Moscow and Minsk will end Feb. 7, and the Baltic systems will be disconnected from the grid the next day.

“We will disconnect and dismantle the last physical connections with Russian and Belarusian grids,” Litgrid CEO Rokas Masiulis said, calling the move an “ambitious energy independence project.”

https://spectrum.ieee.org/baltic-power-grid

image

@brandongalbraith brandongalbraith added data Issues or PRs relating to underlying data. needs triage Issues that need to be triaged and manually labeled. labels Nov 28, 2024
@VIKTORVAV99
Copy link
Member

I actually don't know if we can this without messing up the historical data. It's something we'd have to look into (even if we don't currently aggregate exchange data (we still want to do this though)).

Maybe we have to figure out some solutions that keeps them logically but removes them from the app after a certain date.

We'll also double check what nordpool and entso-e does as we want to keep parity between those when possible.

Regardless, thanks for raising the issue in due time!

@brandongalbraith
Copy link
Contributor Author

Disconnection complete.

https://apnews.com/article/lithuania-baltics-russia-estonia-latvia-electricity-2d07e4849895dbceac260a9d3ce36f33

Is it possible perhaps to keep everything as is in the backend and simply hide the exchanges on the frontend perhaps?

@VIKTORVAV99
Copy link
Member

VIKTORVAV99 commented Feb 8, 2025

Disconnection complete.

https://apnews.com/article/lithuania-baltics-russia-estonia-latvia-electricity-2d07e4849895dbceac260a9d3ce36f33

Is it possible perhaps to keep everything as is in the backend and simply hide the exchanges on the frontend perhaps?

Yeah that is most likely what we'll do.

What I had in mind is switching to versioned capacities like for the zones, and then set these to 0 and hide them in the frontend if they are 0 for all events series shown in the graphs. (This check would likely be in the backend to avoid sending 0 values for the data for no good reason.)

We just need to decide exactly how this will be implemented so we can adjust the internal projects if need be.

I have opened the discussion about improving how we treat exchanges. It don't just have this issue in mind though so I'm not sure how much we can prioritize it for this case in particular.

But given this is a pretty significant event, and given it's not the first time (FI and NO-NO4 seems to already have done it) I'll see what we can do about it!

But the versioned capacities is something we would need to implement first!

@brandongalbraith
Copy link
Contributor Author

brandongalbraith commented Feb 8, 2025

No worries, certainly low value as it is presentation vs other higher value data work. Thanks for the time and consideration!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Issues or PRs relating to underlying data. needs triage Issues that need to be triaged and manually labeled.
Projects
None yet
Development

No branches or pull requests

2 participants