-
Notifications
You must be signed in to change notification settings - Fork 6
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
Name changes & documentation updates #64
Name changes & documentation updates #64
Conversation
Fixes frequenz-floss#58 Signed-off-by: Stefan Brus <[email protected]>
Fixes frequenz-floss#59 Signed-off-by: Stefan Brus <[email protected]>
Fixes frequenz-floss#60 Signed-off-by: Stefan Brus <[email protected]>
4d8c641
to
0068258
Compare
Fixes frequenz-floss#60 Signed-off-by: Stefan Brus <[email protected]>
Fixes frequenz-floss#61 Signed-off-by: Stefan Brus <[email protected]>
Fixes frequenz-floss#62 Signed-off-by: Stefan Brus <[email protected]>
Signed-off-by: Stefan Brus <[email protected]>
Signed-off-by: Stefan Brus <[email protected]>
Bumps [pytest](https://github.com/pytest-dev/pytest) from 7.4.0 to 7.4.2. - [Release notes](https://github.com/pytest-dev/pytest/releases) - [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pytest@7.4.0...7.4.2) --- updated-dependencies: - dependency-name: pytest dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
9004f5c
to
727c554
Compare
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
Before merging anything I strongly recommend trying out how it is rendered doing: pip install -e .[dev-mkdocs]
mkdocs serve Remember Markdown is used, so probably things like You can also download the generate site from the CI job artifacts ( |
It seems like the file header is not rendered at all 😢 |
Any suggested fixes before merging this? |
// Frequenz gRPC API to propagate dispatches to microgrids | ||
// Overview: | ||
// The API serves to automate the process of electricity dispatches for microgrids. | ||
// In the context of the energy industry, a 'dispatch' refers to the act of routing electrical power | ||
// between different components within a microgrid or between a microgrid and the main grid. | ||
// This could be for the purpose of supply (sending electricity to the grid or components within the microgrid), | ||
// or demand (drawing electricity from the grid or from other components like batteries and solar arrays). | ||
// | ||
// Objective: | ||
// The primary objective of this API is to streamline and automate the complex task of electricity dispatching, | ||
// making it easier to manage local electricity supply and demand efficiently. | ||
// | ||
// Key Features: | ||
// - Dispatching Electricity: Comprehensive CRUD operations for dispatching microgrid components. | ||
// - Automation: Support for one-time as well as recurring dispatches based on flexible recurrence rules. | ||
// - Fine-grained control: Dispatch individual microgrid components or entire component categories. | ||
// | ||
// Example Use Cases: | ||
// - Charging or discharging a battery based on optimal time-of-use rates. | ||
// - Limiting the output of a Photovoltaic (PV) array during periods of low demand. | ||
// - Invoking Frequency Containment Reserves (FCR) or Automatic Frequency Restoration Reserves (aFRR) to | ||
// support grid operations. | ||
// - Adjusting the output of electric vehicle charging stations to match grid availability or to avoid peak pricing. | ||
// | ||
// Target Audience: | ||
// This API is designed for application developers in the energy sector who focus on the tasks of optimizing microgrid | ||
// electricity flows. Its design aims to be as developer-friendly as possible, requiring no prior knowledge in | ||
// electrical engineering and systems. |
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.
Just to emphasize this, sadly the file-level documentation is not rendered at all. Since this is very important info it would be nice to include it somewhere else. Maybe as part of the service MicrogridDispatchService
block documentation?
@thomas-nicolai-frequenz FYI for when you create new issues with specs for new APIs.
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.
Created a separate issue for this: #67
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.
Cool, thanks!
Fixes #58
Fixes #59
Fixes #60
Fixes #61
Fixes #62