-
Notifications
You must be signed in to change notification settings - Fork 10
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 Request mechanism #247
Conversation
do not shadow on_stop and setup methods unify usage of start_time and end_time
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #247 +/- ##
==========================================
+ Coverage 78.33% 78.44% +0.11%
==========================================
Files 39 39
Lines 4218 4259 +41
==========================================
+ Hits 3304 3341 +37
- Misses 914 918 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks fine, but could you please also add some tests for the new functionality and updated setup() function for the market operator? Just to be sure we have working features on main.
remove unit_id mapping, by adding the unit_id implicit to the order, this fixes the graph on the dashboard update grafana dashboard to include economic metrics fix ramping in example_02
@maurerle hi Florian, so are no additional tests required for this functionality? I saw a commit with fix tests, but no extra tests. Or are they a part of another commit? |
This PR implements a feed in policy, which calculates the value a special demand agent pays on top of the market prices as a feed-in-tariff. The contract is accepted on a monthly base for example, and evaluated on a weekly base. For this, the generation and market_price of the last week is requested using the data_request mechanism developed in #247 - then the resulting orderbook is created and sent to the contract participants using the already existing `clearing` process. This works in general, though the results are not correct yet. I think the volume and price is applied for the whole series and the dashboard needs some polishment too. --------- Co-authored-by: Nick Harder <[email protected]>
This adds a new data_request mechanism which can be used to request the power generation of a unit or the market price of a market.
This is needed for contracts, which are developed in a follow-up PR
This allows workflows like: