autonomous-racing-pg / ar-tu-do Goto Github PK

This could be done as a text file in the arpg-archive repo

• make list with time slots for all pg members

• make doodle for time slots

• reserve room(s)

Everyone should document the topics they created.

We should establish a meeting with our PG-supervisors every few weeks and show them our progress

• steering (tires rotate)

• all-wheel drive

• Nonlinear steering with Ackermann.
• Curve radius <-> steering angle lookup table

• ros interaction, receiving data

Check what can be reused or built upon: https://github.com/f1tenth/F110CPSWeek2018

mpc ->CPU
mppi ->GPU

• keyboard control
• controller control
• "dead man's switch"

• save data of normal Position
• correct data stream?

• reverse proxy

• doxygen configuration file
• doxygen auto build with travis
• bind doxygen startpage to GitHub.io

• collect Information About FocBox and how to Access it.
• Inspect ROS package to get Topics and Information.
• Inspect ROS package to Change configuration of the FocBox depending on driving Situation

We decided on unsing the MIT license for our project. However, in order to win a price money at the f1/10 events our code needs to be under the GPL license.

• everyone has to approve it

• Investigate Doxygen vs Github Wiki
• Create wiki for the Autonomous-Racing-PG page

calibrate track rod/ steering rod in order to drive forward

• Autonous driving PG from last semester (@marian42 knows morw)

Drive the car with a gamepad and record data (IMU, LIDAR, camera, gamepad,...) to a rosbag

• Create github repositories @marian42
• Set up travis @Dadie

kp, kI, und Kd gains should be identified.

• All PG members should have a fuctional development environment installed, that can run ROS and Gazebo

• In best case a Docker solution or a Ubuntu VM

Travis makes two new doxygen documentation commits on the gh-pages branch for each an every commit.
Instead it should only rebuild the doxygen documentation when a commit/merge happens on the master branch.

• Fix bug

• clean up gh-pages branch, as it looks very ugly right now

find solution for WiFi Problems.
! low priority !

Automatically brake when LIDAR detecs a close obstacle

• Implement minimal ROS package that maps keyboard inputs to steering commands
• Check out the tutorial: http://f1tenth.org/assignment1
• Couldn't finish test without car, test package on the real car

• Connect car to internet with ssh access

• Flash / Install Ubuntu Linux & Nvidia Jetpack
• Wireless Network Setup (Connect Car and PC to the same access point)
• Establish SSH access via wifi
• Install ROS
• Install git and checkout PG repository
• Optional: Set up VNC Server on the car
• Set up LIDAR so that data can be displayed on the terminal

• Create a virtual model of the car
• Place virtual LIDAR, that scans the track and sends scanning data to ROS
• Keyboad inputs (left and right arrow) from ROS, should make the steering move left and right