Right now, the number of phases worth of historical LB data that the system retains is based on how many the installed load model says it wants to use. We should add a configuration parameter to set a minimum retention, independent of the load model. This will support later programmatic use of historical data, like outputting based on some trigger event/observation, with historical data before activation for context.
Is your feature request related to a problem? Please describe.
What Needs to be Done?
Right now, the number of phases worth of historical LB data that the system retains is based on how many the installed load model says it wants to use. We should add a configuration parameter to set a minimum retention, independent of the load model. This will support later programmatic use of historical data, like outputting based on some trigger event/observation, with historical data before activation for context.
Is your feature request related to a problem? Please describe.
Describe potential solution outcome
Describe alternatives you've considered
Additional context