-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
No package mactching ros-galactic-desktop available for AWSIM-stable branch in Ubuntu 22.04 #3165
Comments
@shmpwk Could you tell me the right branch we should use for Humble? |
@anilbommareddy For Ubuntu 22.04, try work in progress version which includes our individual repos but will be officially supported soon: Try the following command
Note that when launching AWSIM, you need its binary. But currently we have only Galactic version of binary. |
hii @shmpwk |
@patelabhay-12 |
@patelabhay-12
|
I firstly doubted this issue but it seems you have different error 🤔 |
yes I succeeded in following without any error. Yes, I built the other Autoware branch under our ~/autoware folder |
In that case you might mixed the previous build cache. Could you once |
@patelabhay-12
Have you manually installed PCL in Ubuntu22.04? (should be automatically installed with our Autoware setup) |
We don't use |
It seems Could you try this under
and then colcon build again? |
@patelabhay-12 (For my memo: the status looks good https://repo.ros2.org/status_page/ros_humble_default.html) |
In your error log, I found your build depends |
@patelabhay-12
FYI, I have experienced the similar situation and I was taught to do that before (japanese issues ). After remove it, be sure not to exist pcl-1.13.
without output. |
OK, in that situation, you have to execute |
rm build install log -rf |
YES! |
You need After remove it, be sure not to exist pcl-1.13.
without any output. |
Your pcl under home directory is basically not depended and do not have to remove them. |
But you have to remove pcl 1.13 at system area such as |
I removed all the folders, and i will try from scratch, if I face any issue will let you know. thanks |
resolved, thanks |
Yes, build succeed!!! 👍 You can ignore stderr output. |
@anilbommareddy How's it going? |
Thank you @shmpwk for launching autoware, that last command asking for map path location, from where to get that map file?? awsim_sensor_kit map_path:=<your mapfile location?? |
map is given on AWSIM tutorial. For more question about AWSIM, please post AWSIM issue. |
@patelabhay-12 |
It seems the way to load map or the map itself is wrong. |
how to give absolute path?? |
Absolute path is |
ros2 launch autoware_launch e2e_simulator.launch.xml vehicle_model:=sample_vehicle sensor_model:=awsim_sensor_kit map_path:=/home/mytsp01065/Downloads |
If your directory is like this,
|
Thank you @shmpwk |
Could you follow the tutorial? There is an instruction of operation. |
not yet, but wil try |
@shmpwk with your provided steps able to build successful on AWSIM-Ubuntu 22.04. |
@anilbommareddy Sounds great! I close the issue since the original problem as stated in the title seems to have been resolved. |
thank you @shmpwk could you plz tell me how to generate the sensor data ?? |
@patelabhay-12 |
thank you @shmpwk |
Checklist
Description
https://tier4.github.io/AWSIM/GettingStarted/QuickStartDemo/
git clone https://github.com/autowarefoundation/autoware.git /humble branch-Ubuntu 22.04/
cd autoware
git checkout awsim-stable
./setup-dev-env.sh */enter Y and install cuda-Y.
got an error No package matching ros-galactic-desktop.
And continued with below steps got an error in PCL lib's.
mkdir src
vcs import src < autoware.repos
vcs import src < simulator.repos.
rosdep update
source /opt/ros/humble/setup.bash
rosdep install -y --from-paths src --ignore-src --rosdistro $ROS_DISTRO
Build-workspace:
colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release
Expected behavior
ros-humble-desktop. download
Actual behavior
got an error No package matching ros-galactic-desktop.
Steps to reproduce
steps are update in the description.
Versions
No response
Possible causes
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: