feat: add forecast vs actual comparison analysis endpoint #166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
added a new endpoint as source/region/forecast/vs-actual that can compare forecasted and actual power generated values side by side, calculates error metrics (error, absolute error, percent error), also adds stats with MAE,ME,RMSE, min/max error, if include_summary=true is given in the endpoint, done by new class ForecastActualComparison in endpoint_types.py
does not affect any data processing as endpoint results are not stored, they are only returned (read only endpoint)
How Has This Been Tested?
tested with dummy backend with api testing, output is attached below

and if include_summary=true , at the end of the response summary is returned as attached below

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?
Checklist: