Refactor the trajectory pipeline
All the possible filtering modules (ascent etc.) are currently hardcoded into the MPipelineConfiguration
, so even before any trajectory actor exists. These modules are also in the pipeline, if the filters are disabled.
This makes it hard to add new filters and is also prone to bugs. It makes more sense to have the pipeline set up dynamically, so the user can enable or disable pipeline filters/modules from the UI. Then the pipeline is updated and filters are only created if they are required.