carla-autoware icon indicating copy to clipboard operation
carla-autoware copied to clipboard

setting up with docker [still not working]

Open jS5t3r opened this issue 5 years ago • 1 comments

My setup:

Carla

#download docker image (e.g. version 0.9.6)
docker pull carlasim/carla:0.9.6

#extract the Carla Python API from the image
cd ~
mkdir carla-python
docker run --rm --entrypoint tar carlasim/carla:0.9.6 cC /home/carla/PythonAPI . | tar xvC ~/carla-python

Carla Autoware Bridge

cd ~
git lfs clone https://github.com/carla-simulator/carla-autoware.git
cd carla-autoware
git submodule update --init

cd docker
./build.sh

Run

Terminal 1:
nvidia-docker run -p 2000-2001:2000-2001 -it --rm carlasim/carla:0.9.6 ./CarlaUE4.sh

Terminal 2:
<in docker directory> ./run.sh
autoware@lh:~/Autoware$  roslaunch $CARLA_AUTOWARE_ROOT/devel.launch

Terminal 3:
<in docker directory> ./run.sh
rviz

https://gitlab.com/autowarefoundation/autoware.ai/autoware/-/wikis/ROSBAG-Demo Launch RViz through the RViz button in the bottom-right corner of the ARM and load the default.rviz config provided with Autoware. To do this got to File -> Open Config and navigate to autoware.ai/src/autoware/documentation/autoware_quickstart_examples/launch/rosbag_demo/default.rviz

When I start, roslaunch $CARLA_AUTOWARE_ROOT/devel.launch, I get the following error:

terminate called after throwing an instance of 'std::runtime_error'
  what():  Time is out of dual 32-bit range
Failed to find match for field 'intensity'.
Failed to find match for field 'intensity'.
[ndt_matching-26] process has died [pid 5809, exit code -6, cmd /home/autoware/Autoware/install/lidar_localizer/lib/lidar_localizer/ndt_matching __name:=ndt_matching __log:=/home/autoware/.ros/log/0b4e2286-5175-11ea-a5ab-00d861527c29/ndt_matching-26.log].
log file: /home/autoware/.ros/log/0b4e2286-5175-11ea-a5ab-00d861527c29/ndt_matching-26*.log
Failed to find match for field 'intensity'.
Failed to find match for field 'intensity'.

BTW:

sudo apt install ros-kinetic-desktop-full in the autoware docker fixed the joint_state_publisher error

jS5t3r avatar Feb 17 '20 11:02 jS5t3r

Hi, I have met the same problem, have you managed to find a solution for the runtime_error. BTW, the joint_state_publisher error can also be solved to install that package alone, it seems it is missing from the ros share directory.

Felix-Feng-90 avatar Jun 08 '20 10:06 Felix-Feng-90