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 7 Update (11/6 - 11/10)

Image
 This week's progress centered around updating the droid's simulated dimensions. Accuracy is integral in creating as realistic an environment as possible to minimize any hiccups in the ultimate transition from the simulation to the actual droid itself. Droid specs were acquired from MEs and reflected in our updated code. A new GitHub repository was also created, due to technical difficulties with parent folder permissions with our previous directory. Gazebo was successfully installed and now runs smoothly, the team also created a shortcut/wrapper file to run repetitive launch commands more efficiently. Motion tests were conducted in Gazebo as well, the droid now can move in a simulated environment using keyboard commands as input. The current challenges at this stage are as follows: The simulated droid currently in development only moves using it's back two tires (for forward/backward/turning) and pushes "frictionless" front tires that do not turn. In addition to ...
Read more

Week 9 Update (3/4-3/8)

Image
This weeks work focused on the feedback we received from the non-CS/SE team. With the physical robot nearing completion they now want to begin integrating code into it, so our focus for the week was to begin the process of getting the Pi setup and transferring/modifying our code onto it. There were some issues such as the Pi not being able to update software which required a fresh install of Ubuntu. From there, we began to gut our code of anything that would be related to Gazebo or the simulation itself. Since the Pi will be in charge of sending the controls over to the Arduino, there is no need for the simulation to be running while inside of the physical robot. Before doing this, we wanted to get the LiDAR to still be able to connect to the code that we are intending to keep but ran into an issue where it wasn't appearing in the list of connected USB devices. Additionally, we also setup an SSH in order to send over commands. Total Hours: 24 hours Pictures: Figure 1: Physical Mous...
Read more

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