-
Notifications
You must be signed in to change notification settings - Fork 11
Add trading-cli tool to query DA prices from entsoe API #94
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
Conversation
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.
LGTM, just nox is still failing
pyproject.toml
Outdated
| dynamic = ["version"] | ||
|
|
||
| [project.scripts] | ||
| trading-cli = "frequenz.client.electricity_trading.__main__:main" |
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.
should this file be located in src/frequenz/client/electricity_trading/cli/__main__.py instead?
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.
Can do, was thinking that this prevents to create another main, but not sure if we should do this.
daniel-zullo-frequenz
left a comment
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.
I have a few questions and comments to check for. LGTM otherwise, it is really simple to use the entsoe API and library but I wonder where is the catch :D
Rate limits ;-) And I am still not convinced about robustness from my first impression looking at it. |
The new CLI tool is intended to be used for interaction with the trading API. However, this initial version only provides functionality to list day-ahead prices from the entsoe API. Signed-off-by: cwasicki <[email protected]>
daniel-zullo-frequenz
left a comment
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.
LGTM!
I can see a disadvantage when using CET. There will be a "missing" timestamp record when time changes from CET to CEST for that day, and on the other hand an extra timestamp when changing from CEST to CET. This might lead to issues if the user not properly take care of time changes in trading apps.
|
But the timestamps are tz-aware, so it's not a duplicate or a missing timestamp, but the offset is included. See: I deliberately chose this timezone because this is used for EPEX trading. |
Initial version of trading CLI tool, which for now can only query DA prices from the entsoe API. Will be extended to support the real endpoints of the trading API later.
Example: