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

Apollo 9.0 scripts/planning.sh bug #15264

Open
YuqiHuai opened this issue Jan 9, 2024 · 0 comments
Open

Apollo 9.0 scripts/planning.sh bug #15264

YuqiHuai opened this issue Jan 9, 2024 · 0 comments
Labels
Apollo 9.0 Module: Planning Indicates planning module related issue Type: Bug Indicates an unexpected problem or unintended behavior

Comments

@YuqiHuai
Copy link
Contributor

YuqiHuai commented Jan 9, 2024

Describe the bug
The script scripts/planning.sh is no longer useable given launch file for the planning module moved from module/planning/launch to module/planning/planning_component/launch

To Reproduce
Steps to reproduce the behavior:

  1. Go to the root directory in the docker container
  2. Compile Apollo with bash apollo.sh build
  3. Use the command bash scripts/planning.sh
  4. See error "[ERROR] Could not launch module planning. Is it already built?"

Expected behavior
The planning module is launched.

Additional context
Shell function run_module calls start_customized_path which then attempts to execute cyber_launch start ${APOLLO_ROOT_DIR}/modules/${MODULE_PATH}/launch/${MODULE}.launch so under the current implementation attempts to start ...modules/planning/launch/planning.launch. Command start_customized_path planning/planning_component planning would work correctly to launch the planning module.

@lykling lykling added Module: Planning Indicates planning module related issue Apollo 9.0 Type: Bug Indicates an unexpected problem or unintended behavior labels Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Apollo 9.0 Module: Planning Indicates planning module related issue Type: Bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

No branches or pull requests

2 participants