Log Sheet

 This is the link to our time log sheet


https://docs.google.com/spreadsheets/d/1HNiQamZznDD-M1E6Qz5gV44jFFH0LcYTADbmO4eEHG8/edit?usp=sharing



Comments

Post a Comment

Popular posts from this blog

Week 4 Update (10/16 - 10/20)

Image
This week's progress was a continuation of the previous week's research in preparation for the Midterm Exam. Each member of the team was responsible for research, memorization, and hypothetical application of their algorithm to a specific problem related to the project. ROS2 installation on the PC is still underway, working through issues with Wi-Fi connection. Due to the nature of the research and the fact that the scheduled Wednesday meeting was set aside for the actual Midterm Exam, the total hours logged for the team this week was: 16 hours. Below are screenshots and photos documenting what was accomplished this week. Fig 1-4 document the algorithms chosen by the team to present for their midterms.  Fig 1. Otsu's Method. This algorithm is used to determine the perceived pixels into   two categories: foreground and background. Fig 2. Watershed Algorithm. Similar to Otsu's method, this algorithm is an integral part of    the image segmentation process, which w...
Read more

Week 6 Update (2/12-2/16)

Image
This week showed progress in the continued development of a script for automated movement and 3D mapping. Through lots of research, debugging and troubleshooting, we have successfully created a node "Move" written in C++, which currently publishes pre-planned movement commands to the corresponding Move topic, instead of relying on user-inputted commands from a terminal. Admittedly this does not seem like significant progress in terms of bot movement/intelligence, since that level has remained consistent from the previous week, but eliminating direct user control is actually a big step for the project.  Total hours: 22 hours. Fig 1. node list showing active Move node Fig 2. topic list showing active Move Topic (receiving from Node) Fig 3. Moving from Move Node (no logic yet)    Fig 4. Move Node publishing commands to Move Topic 
Read more

Week 7 Update (2/19-2/23)

Image
This week showed progress in the development of our existing Move cpp node, and the creation of our new MoveWithLidar.xml behavior tree. We did a bit of restructuring to organize all functionality in our node, and logic in our behavior tree, which is proving much more helpful and efficient. We now have logic implemented in place of a basic loop with repeating hard-coded movement commands. Initially, we used a "go until you see a wall, stop, reverse until you see a wall, repeat" logic tree to test out Lidar scope and limitations. Through many trials, we learned a lot about the 360 scope of the lidar, as well as some errors in the structure of our code (ie. mixing logic between our node and bt). We narrowed the scope of the Lidar to make decisions only on input from an 11-1 o'clock range, so a side parallel wall will not trigger as an obstacle.  Additionally, this Monday we also received access to the actual Lidar sensor, and will being testing and implementation during Wee...
Read more