feat: time range KPIs #92
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
merged DurationKPI into KPI class
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added an option for generating KPIs on time profiles instead of evaluating accumulated values over the whole simulation.
This option can be enabled using the new simulation parameter "kpi_time_profile". This parameter can either be a boolean (default is False) or a list defining time intervals (example: [0, 25200, 28800, ..]).
Time profiling will apply to all KPIs that are compatible (see PROFILE_COMPATIBILITY class attribute).
Simulation will crash if KPIs with mixed compatibilities are mixed in a same KpiOutput.
KPIs evaluation methods have been adapted to provide correct evaluations on the time intervals.