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

Hard fail if max forecast above 100 GW #174

Open
peterdudfield opened this issue Feb 3, 2025 · 9 comments
Open

Hard fail if max forecast above 100 GW #174

peterdudfield opened this issue Feb 3, 2025 · 9 comments
Labels
good first issue Good for newcomers

Comments

@peterdudfield
Copy link
Contributor

peterdudfield commented Feb 3, 2025

It would be good to add a hard fail in the forecast is above a crazy amount like 10% above Nationla capacity

The check could happen here

if da_abs_national.max() > 1.1* national_capacity:
   raise Exepection('The maximum of the forecast is above 10% of the national capacity ({national_capacity})'
@peterdudfield peterdudfield added the enhancement New feature or request label Feb 3, 2025
@dantravers
Copy link

Maybe 30GW is enough, and would catch more possible error cases?

@peterdudfield
Copy link
Contributor Author

Perhaps it could be > 50% above national capacity, so like 17*1.5 GW. This means it wont fail in the future when capacity grows

@dantravers
Copy link

Yes, good idea if we can index to national capacity. Might only need a 10% buffer, as we never see forecasts close to MWp capacity.

@peterdudfield peterdudfield removed the enhancement New feature or request label Feb 3, 2025
@peterdudfield peterdudfield added the good first issue Good for newcomers label Feb 3, 2025
@peterdudfield peterdudfield mentioned this issue Feb 3, 2025
6 tasks
@Sukh-P
Copy link
Member

Sukh-P commented Feb 4, 2025

Great check to add in! Would it still be good to have a hard max limit constant? I guess the current check assumes that the national capacity (which I assume we get from PVLive also?) is also correct, which might not always be the case

@braddf
Copy link

braddf commented Feb 4, 2025

This is a good point @Sukh-P – either as a hard max constant or as a warning constant, maybe both make sense if we're worried about hitting a manually configured limit?
Capacity doesn't change that quickly, so could be notified when we get a number 10% below the hard limit or something.

@peterdudfield
Copy link
Contributor Author

peterdudfield commented Feb 4, 2025

Ah, so we could put in an extra limit that stops a 100 GW as well?
We can put a warning too at 90GW, but that'll be a while a way

@braddf
Copy link

braddf commented Feb 4, 2025

Still seems a little high to me – if we set the warning/limits lower and need to bump this once a year when it reaches the warning capacity, I think that's fine, so more like 25GW warning, 30GW limit? As 40-50GW would take us to 2030 ish at current estimates I think!
(There are also other things like the UI that would like to know when the capacity does meaningfully increase which would be helpful to be aware of)

@dantravers
Copy link

Great check to add in! Would it still be good to have a hard max limit constant? I guess the current check assumes that the national capacity (which I assume we get from PVLive also?) is also correct, which might not always be the case

Yes, this occurred to me also - if the capacity figures were missing for some reason, we might trigger false positives and incorrectly fall back to a lower quality forecast.

@peterdudfield
Copy link
Contributor Author

Ok, so perhaps

  • warning if forecast is above 30 GW
  • hard fail if the forecast is above 100 GW.

For missing capacity, i.e capacity is nan, then we currently fail. I think I would rather keep it like this for the moment. If it starts happening then we put in a back up capacity amount. This would raises risk of not knowing we are on a backup capacity, and therefore producing lower forecast, vs robustness of the service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants