Closed sjschlapbach closed 10 months ago
I was just thinking that our generate_parametric_model.py contains quite a lot of logic and code. What do you think if we start modularizing some of the logic related to interactive and setpoint data selection into their own python modules to make the overall logic a bit more readable? Can be a different PR though.
I was just thinking that our generate_parametric_model.py contains quite a lot of logic and code. What do you think if we start modularizing some of the logic related to interactive and setpoint data selection into their own python modules to make the overall logic a bit more readable? Can be a different PR though.
Obviously, yes please :)
Problem Description: Until now, it was only possible to select data based on one of the 6 available
manual_control_setpoint
topicsaux1
toaux6
when using thedata_selection=setpoint
option. It was requested that this mechanism should be more flexible and also accept other variables more flexibly.Proposed Solution: In addition to the
data_selection
attribute, the user can now provide aselection_var
variable to themake
command (with the syntaxtopic_name/variable_name
- e.g.manual_control_setpoint/aux1
). The corresponding variable will then be added to the topics that are loaded from the log file and used to identify relevant sections of the provided log.Test command: