-
Notifications
You must be signed in to change notification settings - Fork 21
Seperate ComponentMetricRequests from Resampling Actor #301
Copy link
Copy link
Open
Labels
part:actorAffects an actor ot the actors utilities (decorator, etc.)Affects an actor ot the actors utilities (decorator, etc.)part:data-pipelineAffects the data pipelineAffects the data pipelinepart:microgridAffects the interactions with the microgridAffects the interactions with the microgridpriority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the tabletype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Milestone
Description
Metadata
Metadata
Assignees
Labels
part:actorAffects an actor ot the actors utilities (decorator, etc.)Affects an actor ot the actors utilities (decorator, etc.)part:data-pipelineAffects the data pipelineAffects the data pipelinepart:microgridAffects the interactions with the microgridAffects the interactions with the microgridpriority:lowThis should be addressed only if there is nothing else on the tableThis should be addressed only if there is nothing else on the tabletype:enhancementNew feature or enhancement visitble to usersNew feature or enhancement visitble to users
Type
Projects
Status
To do
What's needed?
The
ComponentMetricResamplingActorshould accept a receiver of samples instead of aComponentMetricRequest.Furthermore after this change we can rename it to
ResamplingActor.Proposed solution
The actors
subscribeshould simply accept aReceiverofSamplein order to make it usable in every stage of the data pipeline. Setting up a stream from the data sourcing actor should happen outside of the actor.Use cases
The actor can then be used e.g. for second stage resampling (e.g. to further reduce the amount of data).
Alternatives and workarounds
No response
Additional context
No response