Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change how missions are started #164

Open
5 tasks
Rezenders opened this issue May 29, 2024 · 0 comments
Open
5 tasks

Change how missions are started #164

Rezenders opened this issue May 29, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Rezenders
Copy link
Collaborator

  • 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

@Rezenders Rezenders added the enhancement New feature or request label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant