As noted here, the ordering of the selections can cause other selection parameters to be over-riden. In the example I linked here, the original code would cause the time slice for selections to be overriden to the default time slice (1980, 2015) because the historical scenario had changed, but that is not what the user may want, since they may input their own custom time slice.
So, we need to have a way to make sure that user-instantiated selections are not overriden when they are instantiated in a valid combination.
As noted here, the ordering of the selections can cause other selection parameters to be over-riden. In the example I linked here, the original code would cause the time slice for selections to be overriden to the default time slice (1980, 2015) because the historical scenario had changed, but that is not what the user may want, since they may input their own custom time slice.
So, we need to have a way to make sure that user-instantiated selections are not overriden when they are instantiated in a valid combination.