You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run roslaunch agile_autonomy simulation.launch
[ERROR] [1686655639.396501363, 3.536000000]: no kernel image is available for execution on the device 209
The details are as follows:
Ready?: 0
Ready?: 1
[INFO] [1686655639.023764265, 3.349000000]: Unity is ready!
[ERROR] [1686655639.396501363, 3.536000000]: no kernel image is available for execution on the device 209
[ERROR] [1686655639.531226480, 3.603000000]: no kernel image is available for execution on the device 209
Environment Information
Operating System: Ubuntu 20.04
GPU Version: RTX3060
CUDA Version: 12.1 and 11.0 (The above error occurs)
Steps to Reproduce
I finally catkin build successfully according to readme and other blogs, but when running roslaunch agile_autonomy simulation.launch, three windows can be successfully opened, but when the picture in the simulation is displayed in rviz, the error mentioned above occurs.
Thank you!
The text was updated successfully, but these errors were encountered:
Issue Description
When I run roslaunch agile_autonomy simulation.launch
[ERROR] [1686655639.396501363, 3.536000000]: no kernel image is available for execution on the device 209
The details are as follows:
Ready?: 0
Ready?: 1
[INFO] [1686655639.023764265, 3.349000000]: Unity is ready!
[ERROR] [1686655639.396501363, 3.536000000]: no kernel image is available for execution on the device 209
[ERROR] [1686655639.531226480, 3.603000000]: no kernel image is available for execution on the device 209
Environment Information
Steps to Reproduce
I finally catkin build successfully according to readme and other blogs, but when running roslaunch agile_autonomy simulation.launch, three windows can be successfully opened, but when the picture in the simulation is displayed in rviz, the error mentioned above occurs.
Thank you!
The text was updated successfully, but these errors were encountered: