todo

Documentation structure:
1. Intro, team members, prerequisites - Justice
2. What is the problem, initial constraints, final videos of gazebo and real panda moving - Rowan
3. Project structure, explaining the modules' functions, how they communicate (de_msgs) - Justice
4. 3 packages (spawn_mnger - Keith, arm_master - Zach, brick_manager_server - Rowan & Sam) explained in detail
5. A) Code implementation (Zach) and problems specific to Gazebo (Keith); 😎 Code implementation (Zach) and problems specific to real Panda (Keith)
6. Hololens interfacing and next steps (Dan)


"""Short Function Summary

Longer Function Description

Args:
    param1 (int): The first parameter.
    param2 (str): The second parameter.

Returns:
    bool: The return value. True for success, False otherwise.

"""

``[x, y, z, rot_x, rot_y, rot_z]``


"""
roslaunch franka_gripper franka_gripper.launch robot_ip:=192.168.0.88
roslaunch move_to_start.launch robot_ip:=192.168.0.88

"""


+ finish documenting source code 15
+ write up 30
+ get it all on read the docs 15

y detailed documentation,
describing all theoretic and
implementation aspects of the
project. Includes not only
explanations about the successful
achievements, but also about the
failed attempts during the project
(i.e. what worked and what didn’t
work).





+ make graphics for pages
+ format
+running on gazebo
+ talk about the namespace issue with rqt_graph
+ film video
+ friction set up



Go through and format code and publish/push - Do this so I set up the team who will be getting up soon.



more content (1hr)
rest (1hr)
run()
Add dropped checked to documentation


+ go through and format all pages and add photos ect.... of going through the process and off your own screen



What matters right now?

Getting in documentation for the rest of the code base.
Editing the existing documentation to 80%
Talking about Gazebo