I get an error in runtime_manager.launch

asked 2020-04-11 02:01:13 -0500

dandelion1124
21 ●2 ●5 ●6

updated 2020-04-11 23:43:34 -0500

Required information:

Operating system and version:
- Ubuntu 18.04
Autoware installation type:
- From source
Autoware version or commit hash
- 1.13.0
ROS distribution and version:
- ROS Melodic
ROS installation type:
- From binaries

Description of the bug

$ roslaunch runtime_manager runtime_manager.launch

In this time, the following error message was displayed in Terminal.
Is this a bug?

bash: ./../../../setup.bash: No such file or directory

There is this operation in runtime_manager/scripts/run.
https://gitlab.com/autowarefoundation...

Comments

@dandelion1124 Please provide some screenshots.

omkard ( 2020-04-11 14:29:41 -0500 )edit

@omkard Thank you for your reply. I shared screenshot.

dandelion1124 ( 2020-04-11 23:56:30 -0500 )edit

I will see if I have same the issue @dandelion1124 and let you know.

omkard ( 2020-04-12 16:33:20 -0500 )edit

Hi @dandelion1124 ,

I am getting the same error too. But, I don't have trouble due to that.

image description

omkard ( 2020-04-13 09:31:11 -0500 )edit

add a comment

answered 2020-04-15 23:12:18 -0500

Josh Whitley

1766 ●4 ●72 ●24

It is a bug (because the file is not in the correct location) but, fortunately, one that does not affect operation of the Autoware Runtime Manager. That line in the script is meant to source your Autoware.ai workspace but, depending upon how you built your workspace, the location of the setup.bash file will be different. However, it isn't really needed so it failing has no negative consequences.

edit flag offensive delete link

Comments

However, it isn't really needed so it failing has no negative consequences.

Thank you for your reply. Should I remove source ./../../../setup.bash from runtime_manager/scripts/run? https://gitlab.com/autowarefoundation/autoware.ai/utilities/-/blob/1.13.0/runtime_manager/scripts/run#L53

dandelion1124 ( 2020-04-18 09:04:47 -0500 )edit

The problem with using this method to try to source the workspace is that it is relying on the location of the installed runtime manager folder to be static. However, depending on how you build or configure your workspace, this may not be true. That being said, the majority of users will either:

Source their workspace as part of their ~/.bashrc file; or
Source their workspace before running runtime_manager.

So, there are two "fixes" for this:

Remove it.
Assume that most people built their workspace using the from-source instructions and replace it with source ./../../../../setup.bash (one more level than the current one).

I'm fine with either but please make a pull request to change this in the official repository.

Josh Whitley ( 2020-04-20 15:52:26 -0500 )edit

add a comment

I get an error in runtime_manager.launch

Required information:

Description of the bug

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

I get an error in runtime_manager.launch edit

Required information:

Description of the bug

Comments

1 Answer

Comments

Question Tools

Stats

Related questions

I get an error in runtime_manager.launch