Problem description:
Using certain parameters from the logfile to select specific flight sections marked earlier was only available through the model configuration and sometimes even coupled to the requirement of code modifications.
Proposed solution:
This pull request adds an additional optional parameter and option to the makefile and python launch commands, which can be used to specify the manual_control_setpoint that should be used to identify the relevant parts of the flight:
Using the value setpoint for the data_selection option uses all segments of the flight log, where aux1 was triggered
Using the configuration parameters selection_variable and activations allows to overwrite the default aux1 value with any other manual_control_setpoint topic and specify, which activations of this parameter should be chosen for identification.
Problem description: Using certain parameters from the logfile to select specific flight sections marked earlier was only available through the model configuration and sometimes even coupled to the requirement of code modifications.
Proposed solution: This pull request adds an additional optional parameter and option to the makefile and python launch commands, which can be used to specify the
manual_control_setpointthat should be used to identify the relevant parts of the flight:setpointfor thedata_selectionoption uses all segments of the flight log, whereaux1was triggeredselection_variableandactivationsallows to overwrite the defaultaux1value with any othermanual_control_setpointtopic and specify, which activations of this parameter should be chosen for identification.Further developments