-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add video tutorial of autoware installation #270
Comments
@cyn-liu cc @mitsudome-r @xmfcx
Sure. FYI, there is a Japanese tutorial video by @yukkysaito. (recorded about a half year ago) I think a similar composition is good.
Do you mean you want to put the tutorial video on the documentation page? |
I am actually preparing such video series. Here is some docs as I'm working on it: https://gist.github.com/xmfcx/aeee631ea819ddfc734da26f98c6ee0e So far I've recorded till planning simulator demo and will publish tomorrow. And start working on the rest. I've only covered the source installation for this series but maybe if you want to cover the docker installation, we can add it too, what do you think @cyn-liu ? |
Yes, but I only want record video of |
@xmfcx Good job! |
Thanks, sure, go ahead and create a tutorial video, we can put it to the place you've proposed. |
I think the document of Docker installation should be divided into two branches. One is to use the The second method is very friendly for beginner to run Autoware. I wrote a draft about Autoware docker installation use Autoware installationDocker installation (prebuit version)Install dockercurl -fsSL https://get.docker.com -o get-docker.sh Install nvidia container toolkitdistribution=$(. /etc/os-release;echo $ID$VERSION_ID) sudo apt-get update sudo systemctl restart docker Install rockersudo apt update && sudo apt install curl gnupg lsb-release echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/ros-archive-keyring.gpg] http://packages.ros.org/ros2/ubuntu $(source /etc/os-release && echo $UBUNTU_CODENAME) main" | sudo tee /etc/apt/sources.list.d/ros2.list > /dev/null sudo apt update Pull imagedocker pull ghcr.io/autowarefoundation/autoware-universe:humble-latest-prebuilt (Autoware Foundation registry) Create the autoware_map directory for map data later.mkdir ~/autoware_map NOTE: Please put your map files in this directory. run containnerrocker --nvidia --x11 --privileged --user --volume $HOME/autoware_map -- ghcr.io/autowarefoundation/autoware-universe:humble-latest-prebuilt run autowaree.g., running planning simulator: NOTE: The Autoware code located in the Build the workspacecolcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release |
@cyn-liu I agree. I think that should be like a quick start and can be on the introduction or README. |
@kenji-miyake |
@cyn-liu Sorry for my unclear sentence. I meant just putting the link to a quick start there. |
Here I think installing the dependencies is common for both methods. I think you should improve existing dependency installation methods instead of rewriting them. And I agree that you can split the So user goes: Is this ok with you @cyn-liu ?
@kenji-miyake I think it's better to keep them together as they are 2 branches of a common source. |
@xmfcx Thank you for your comments. The reason why I said we should split pages is that the target readers of the pages are different. |
@kenji-miyake I think developers can use prebuilt version to edit & compile autoware too,
And our docker documentation also have:
It would be confusing to have these 2 pages in different sections since they both achieve the same result. |
@xmfcx The prebuilt version will be simplified in the future by autowarefoundation/autoware#2922. After that, developers cannot use it for development because the image has only runtime dependencies. I imagined that. |
@kenji-miyake I will comment there to separate |
I think Autoware documentation should deliberately avoid any suggestion or recommendation to install Autoware on the local system. Let's put our effort to prepare an Autoware Let the user pull the development image and mount Autoware source folder. The current image comes with source as far as remember. Encourage the developer as much as possible to work inside the container. |
@doganulus There are many core developers of the project who uses native installation method exclusively due to performance and simplicity reasons. Not everyone wants the overhead and added complexity of dealing with containers. We have a docker image and instructions to use it, if you have an issue with how it works, how it is constructed or how it can be improved, please create a separate issue for it. |
An experienced user can always install Autoware on their local system. I do not think we can prevent that. But this issue is about everyone else, especially the newcomer. Therefore let's focus on the people who want to start developing Autoware. Still developing inside the container is very valuable for experienced core developers, I believe. |
I agree that. |
@xmfcx @kenji-miyake I plan to divide the |
@cyn-liu I've created this training video series: https://github.com/orgs/autowarefoundation/discussions/3141 I didn't cover docker parts, I hope you will cover them here (`・ω・´) |
This pull request has been automatically marked as stale because it has not had recent activity. |
Checklist
Description
I plan to add the Autoware installation video tutorial in here, but the Autoware installation tutorial document is relatively complex. Even the Docker based installation tutorial requires a lot of additional dependencies, which is very unfriendly to beginners.
Autoware Universe now mostly provides images of the
prebuilt
version (image link). Based on this image, you do not need to download the source code of Autoware, and you can run Autoware without compiling. So can I record Autoware installation videos based on theprebuilt
version images?Autoware installation documentation (here) needs to be updated?
@kenji-miyake Do you have any suggestion?
Purpose
Add video of Autoware installation tutorial.
Possible approaches
Add video of Autoware installation tutorial.
Definition of done
TO DO.
The text was updated successfully, but these errors were encountered: