Name changes & documentation updates#64
Name changes & documentation updates#64stefan-brus-frequenz merged 9 commits intofrequenz-floss:v0.x.xfrom
Conversation
Fixes frequenz-floss#58 Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
Fixes frequenz-floss#59 Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
Fixes frequenz-floss#60 Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
4d8c641 to
0068258
Compare
Fixes frequenz-floss#60 Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
Fixes frequenz-floss#61 Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
Fixes frequenz-floss#62 Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
Signed-off-by: Stefan Brus <stefan.brus@frequenz.com>
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] <support@github.com>
9004f5c to
727c554
Compare
|
Before merging anything I strongly recommend trying out how it is rendered doing: pip install -e .[dev-mkdocs]
mkdocs serveRemember 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.
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.
Fixes #58
Fixes #59
Fixes #60
Fixes #61
Fixes #62