Support for evaluation of scenario execution
Describe the feature
I want to model scenarios in a way that their execution is robust towards changes in my testbench setup. E.g. I do not want to re-implement scenarios whenever I update vehicle dynamics or scenario interpretation in a simulator. However, it is unlikely, that scenario execution will remain exactly the same, regardless of which component is updated. Therefore, I would like to be able to model criteria in my scenario that can be evaluated to determine if the original intent of my scenario is still in tact.
Describe the solution you would like
A class, similar to parameters or variables, that allows me to instantiate one or multiple (boolean) objects that can be set based on conditions during execution of the scenario. Similar to the "keep" keyword from OSC2, I would like to be able to evaluate if all my boundary conditions are kept during the scenario execution.
Describe alternatives you have considered
The desired feature could also be achieved by using variables in OSC1.2. However, creating a dedicated class would allow dedicated implementations for scenario modeling and execution.
Describe the backwards compatibility
Given, if a new class is created.