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]: BD imports are counted as generation in source #6542

Closed
VIKTORVAV99 opened this issue Mar 4, 2024 · 4 comments · Fixed by #6590
Closed

[Data Issue]: BD imports are counted as generation in source #6542

VIKTORVAV99 opened this issue Mar 4, 2024 · 4 comments · Fixed by #6590
Assignees
Labels
data Issues or PRs relating to underlying data.

Comments

@VIKTORVAV99
Copy link
Member

When did this happen?

Ongoing since start?

What zones are affected?

BD

What is the problem?

It seems like the source is including imports as generation but we do not, so where are inferring an unknown production that is almost 1=1 with the imports. The parser needs to be updated to account for this and then all data needs to be re-fetched and reprocessed.

@VIKTORVAV99 VIKTORVAV99 added the data Issues or PRs relating to underlying data. label Mar 4, 2024
@VIKTORVAV99 VIKTORVAV99 self-assigned this Mar 4, 2024
@q--
Copy link
Contributor

q-- commented Mar 4, 2024

Small thing I noticed after I pointed this out in #5381 (comment) is that, for a few data points, generation data is incomplete (e.g. a bit of gas generation appears to be unreported); in that case 'unknown' is not only imports. Otherwise it's all imports like you've described.

Screenshot

A screenshot taken on February 20, showing the issue happened at approximately 13:30 Central European Time the previous day

So the issue happened approximately 13:30-14:30 CET

(I don't know if it happens often or whether it's corrected automatically when data is re-fetched, I just wanted to point out that, sometimes, this happens.)

@VIKTORVAV99
Copy link
Member Author

VIKTORVAV99 commented Mar 4, 2024

Small thing I noticed after I pointed this out in #5381 (comment) is that, for a few data points, generation data is incomplete (e.g. a bit of gas generation appears to be unreported); in that case 'unknown' is not only imports. Otherwise it's all imports like you've described.

(I can look for a screenshot for the day I noticed this if it helps. I don't know if it happens often or whether it's corrected automatically when data is re-fetched, I just wanted to point out that, sometimes, this happens.)

Any additional information would be helpful!
I also noticed that for some datapoints there is actually unknown production but I have only seen single digits.

If it's corrected in the source it will be corrected in our data as well :)

@q--
Copy link
Contributor

q-- commented Mar 4, 2024

I've added a screenshot to my comment

@VIKTORVAV99
Copy link
Member Author

I have started refetching all the historical data now that this is deployed. But I won't re-reprocess everything because of this alone. There are some other changes that affects historical data as well coming soon though. Once those are merged (both on the contrib repo and backend) all historical data will be re-processed.

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.
Projects
None yet
2 participants