shlokgoel's profile - activity

I am trying to use ROS1 Bridge to work with ROS1 nodes from within ROS2 (Dashing) inside the docker environment (ADE).

PS. I want to use ROS2 inside the docker environment and communicate with ROS1 nodes outside the docker.

I am using Ubuntu 18.04

Is there a good documentation available for enabling the use of the ROS bridge inside the docker environment?

Thank you.

I am trying to install rqt_graph for ROS2 to visualize the ROS nodes and the computation graph. I have ROS2 dashing installed in the docker (using the Autoware.Auto class/tutorial) After entering ade and sourcing the setup.bash in Autoware.Auto, I use the following command:

sudo apt-get install ros2-dashing-rqt_graph

and I get the following error:

Unable to locate package ros2-dashing-rqt-graph

Could anyone help me out here? Thank you!

I am trying to follow the documentation to use the LGSVL simulator with Autoware.AI from here:

https://www.lgsvlsimulator.com/docs/a...

PS. I have followed the steps for the installation of docker and the shared-directory from the above link as well.

I navigate inside the Autoware folder by typing

cd Autoware.AI/docker/generic

Then I run the "run.sh" script by typing ./run.sh and I get inside the autoware docker container. I then source the install/setup.bash file and start the run-time manager by typing roslaunch runtime_manager runtime_manager.launch

After starting the run-time manager inside the docker, I am trying to load the files from autoware-data for the LGSVL simulator. However, the run-time manager is not able to locate any of these files from the shared-dir inside Autoware. (I have even tried to check the option for hidden files)

When I try to navigate to the folder "share-dir" from the command terminal, I can see the folder autoware-data and it contains all the files.

See the screenshot below for reference.

PS. The only files that the run-time manager cannot locate and use are from the below specified path:

/home/autoware/Autoware/src/autoware/documentation/autoware_quickstart_examples/launch/rosbag_demo

Any suggestions on why the run-time manager is not able to locate these files?

Thanks!

I have already put files in the host ~/shared_dir and I am able to locate them inside the docker container from the comm

I have already put files in the host ~/shared_dir and I am able to locate them inside the docker container from the comm

I have already put files in the host ~/shared_dir and I am able to locate them inside the docker from the command line t

Yes, I have the dir ~/shared_dir on the host machine as well, but I am unable to access that directory from within the r

Yes, I have the dir ~/shared_dir on the host machine as well, but I am unable to access that directory from within the r

Cannot Locate files inside Runtime Manager for Autoware.AI I am trying to follow the documentation to use the LGSVL simu

Cannot Locate files inside Runtime Manager for Autoware.AI I am trying to follow the documentation to use the LGSVL simu

You might want to modify the param (.yaml) file for the Point Cloud Filter node as well. That file contains the static t

Hi,

I currently have ADE docker installed on my Linux machine that is running Autoware.Auto. I now want to use Autoware.AI on the same machine.

Is it okay to have both Autoware.Auto and Autoware.AI on the same Linux machine? If yes, do I need to install a separate docker container or I can install Autoware.AI inside the same docker that I used for Autoware.Auto?

Machine Specifications:

Linux Ubuntu 18.04

I think the problem has something to do with the ray ground classifier node. This node is responsible for segregating th

Autoware.AI and Autoware.Auto on Same Machine Hi, I currently have ADE docker installed on my Linux machine that is run

Hi,

I was trying to use the 3D Perception Stack in Autoware.Auto to generate bounding boxes and I was facing some errors. Below is the attached rviz2 visualization alongside the simulation.

In the picture above, the blue circle represents the bounding box and the red circle represents filtered point clouds. There are two issues that I am trying to resolve:

1. The bounding boxes appear to be fish-tailing (rotating inconsistently). I have tried to change the parameters inside the .yaml configuration (param) files for the point_cloud_filter node as well but it does not seem to fix that. I have tried to look at the .urdf for the Lexus vehicle for the robot state publisher and manipulate the parameters according to how the lidar is configured, but that does not seem to fix it either. This can also be seen in the bounding boxes on the right (trees) which constantly keep changing orientation.

2. The bounding boxes appear to NOT line up longitudinally with the filtered point clouds. I have NOT changed anything in the .yaml config file for the Euclidean cluster, so I am confused why the bounding boxes do not line up with the filtered points. I would understand if the filtered points do not line up with the actual object in the simulation (since they can be calibrated using the sensor_height_m and the static transform parameters) but that is not the case.

The filtered points (output of thepoint_cloud_filter node) seem to lineup with the simulation meaning that the translation parameters are somewhat correct.

Let me know why these issues are happening!

Thanks, Shlok

Hi Nikolai, Thanks for getting back to me. I am not sure if this is due to the computational load. My simulation envir

Hi Nikolai, Thanks for getting back to me. I am not sure if this is due to the computational load. My simulation envir

Hi Nikolai, Thanks for getting back to me. I am not sure if this is due to the computational load. My simulation envir

Bounding Box Error in 3D Perception Stack of Autoware.Auto Hi, I was trying to use the 3D Perception Stack in Autoware

Bounding Box Error in 3D Perception Stack of Autoware.Auto Hi, I was trying to use the 3D Perception Stack in Autoware

Hi,

I am trying to execute/implement the trajectory following example as listed on the tutorial at Autoware.Auto website (https://autowarefoundation.gitlab.io/...)

I have been following the autoware class 2020 provided by Apex.AI.

I am able to run the tutorial for trajectory following using the LGSVL simulator, but I would like to modify the plant environment (LGSVL) and replace it with a different plant environment (that provides it the required sensor [lidar - front and rear] data .

I have gone through the the ROS2 launch.py file that launches the ROS nodes in detail to understand how the nodes are initialized and how they work. If I do not start the simulation (LGSVL) and directly run the ROS2 launch command line to start the trajectory following examples, all ROS2 nodes are generated EXCEPT for the UNITYROS2 node. After further inspection, I found that this node publishes lidar data and subscribes to data from the vehicle etc.

Is there any way that someone could provide me some help as to what needs to be changed (in the python launch file, .yaml configuration file etc. ) in order to run this example using a different simulation platform (plant environment).

PS. I can publish ROS topics from my plant/simulation for the lidars with any name - just need to know what needs to change on the autoware.auto side.

Thanks,

Shlok

@ bekirbostanci - I was able to solve this issue, it was indeed related to sourcing the ros2 environment. I just have to