You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be an easy way to get damages per event and region_id.
There are many ways to implement this, but all of them come with a price on calculation and/or memory. From a discussion on Slack a vague plan emerged to
introduce an additional method in Impact that provides this kind of aggregation
introduce an additional argument in the ImpactCalc.impact method that indicates how/whether to persist the aggregation result within the Impact object.
The text was updated successfully, but these errors were encountered:
introduce an additional argument in the ImpactCalc.impact method (e.g., at_region_id_event) and the current at_event becomes at_region_id_event.sum(0) or something
There should be an easy way to get damages per event and region_id.
There are many ways to implement this, but all of them come with a price on calculation and/or memory. From a discussion on Slack a vague plan emerged to
Impact
that provides this kind of aggregationImpactCalc.impact
method that indicates how/whether to persist the aggregation result within theImpact
object.The text was updated successfully, but these errors were encountered: