Skip to content

Conversation

@shsms
Copy link
Contributor

@shsms shsms commented Apr 8, 2024

No description provided.

shsms added 5 commits April 8, 2024 17:26
Signed-off-by: Sahas Subramanian <[email protected]>
Signed-off-by: Sahas Subramanian <[email protected]>
The EV charger manager has its own task that tracks the status of the
EV chargers and redistributes power to them as EVs are connected and
disconnected.  This approach is specific to the EV charger pool,
because the status of the components is dynamic, unlike the
BatteryPool and the PVPool.

This task needs to run only in locations where there are EV chargers,
because it expects that there be at least one EV charger in a location
and runs into issues if that's not the case.

Signed-off-by: Sahas Subramanian <[email protected]>
The API would reset power back to 0 after an interval only for
batteries.  For EV chargers and PV inverters, it will not have a reset
mechanism.

Signed-off-by: Sahas Subramanian <[email protected]>
@shsms shsms added this to the v1.0.0-rc6 milestone Apr 8, 2024
@shsms shsms self-assigned this Apr 8, 2024
@shsms shsms requested a review from a team as a code owner April 8, 2024 15:40
@github-actions github-actions bot added part:tests Affects the unit, integration and performance (benchmarks) tests part:data-pipeline Affects the data pipeline part:actor Affects an actor ot the actors utilities (decorator, etc.) labels Apr 8, 2024
@shsms shsms added the cmd:skip-release-notes It is not necessary to update release notes for this PR label Apr 8, 2024
@shsms
Copy link
Contributor Author

shsms commented Apr 8, 2024

Skip release notes because these are internal changes and bugfixes to unreleased features.

Copy link
Contributor

@llucax llucax left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, the only question is why instantiating a EVChargerManager at all if there are no EV chargers, but I assume you thought about it and have a good reason for it, so I will give the approval anyway, but I'm curious about it.

@shsms
Copy link
Contributor Author

shsms commented Apr 9, 2024

the only question is why instantiating a EVChargerManager at all if there are no EV chargers

It is just that this is where we already have the list of available component IDs. Otherwise, we'd have to get the component IDs for all component types in the _data_pipeline.py file, which feels less modular.

Also, they are lazily started, so an EVChargerManager or even a PowerDistributor instance is only started when a corresponding call is made to microgrid.ev_charger_pool().

@shsms shsms added this pull request to the merge queue Apr 9, 2024
@shsms shsms closed this Apr 9, 2024
Merged via the queue into frequenz-floss:v1.x.x with commit 6637d7f Apr 9, 2024
@shsms shsms deleted the ev-pool branch April 9, 2024 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cmd:skip-release-notes It is not necessary to update release notes for this PR part:actor Affects an actor ot the actors utilities (decorator, etc.) part:data-pipeline Affects the data pipeline part:tests Affects the unit, integration and performance (benchmarks) tests

Projects

Development

Successfully merging this pull request may close these issues.

2 participants