Skip to content

Change how missions are started #164

Description

@Rezenders
  • Remove constant distance mission and reuse "time constrained" mission with time limit set to 0 or -1
  • Remove the notion of a "time constrained" mission
  • Create two distinct mission types: suave and suave extended (maybe this is not a good long-term solution if we plan to extend suave more)
  • Refactor mission.launch.py, it is very confusing now. I think a good idea is to create a launch file for each managing system with everything it needs and just call it from mission.launch.py
  • Change how "mission_name" is defined in the saved metrics. A good idea is to add a column "mission" which could be either suave or suave extended, and a column "managing system"

Launch command: ros2 launch suave_missions mission.launch.py adaptation_manager:=metacontrol|random|bt|none mission_type:=suave|suave extended result_filename:=filename

runner: ./runner.sh false|true metacontrol|random|bt|none suave|suave extended N

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions