Team Status Update for 04/25 (Week 11)

Progress

This week, we worked on the final demo; creating videos so it is clear what we have accomplished so far. We are almost done with the engineering part of the project, and we are collecting performance metrics. We created the final presentation and planned out what we will use for the final demo vide.

Deliverables next week

Next week, we will work on the final video and report.

Schedule

On schedule.

Jerry’s Status Update for 04/25 (Week 11)

Progress

This week, I worked on the final version of the point model. To get the best performance, I included noise into the pointing dataset, used less keypoints to focus on the arms, and added location as a feature for point classification.

The best performing model on the newest dataset had a validation accuracy of 96%.

I also built a point trigger to let users choose where to activate the point in the final application. This allows the point to operate smoothly with the gesture recognition system at ~27 FPS, whereas running the point model on every frame is 28FPS.

We also planned what we needed for our demo video.

Deliverables next week

Next week, we will give our final presentation and put together our video.

Schedule

On schedule.

Sean’s Status Update for 04/25 (Week 11)

Progress

This week, I focused mainly on producing presentation/demo material. I recorded couple videos of the robot performing path-finding as well as driving to the desired location. The project is more or less complete, and I am cleaning up the codes I wrote so it is more readable to anyone who sees the code for the first time.

Deliverables next week

Next week, I plan to record more video for the final presentation. In addition, I will work on the final report.

Schedule

On schedule.

Team Status Update for 04/18 (Week 10)

Progress

Path-finding

The algorithm is complete and ready for testing. It uses A* as mentioned before, and the robot is able to arrive at the grid-cell the goal point is located in. Testing is needed to check its robustness.

Pointing

Pointing to the room is almost done. It works well on one side of the room using a multitask regression model. It needs additional data to cover more parts of the room and for hyperparameter fine-tuning.

2D to 3D Mapping

Mapping now runs at 17 fps and data is formatted properly. The map needs to be integrated with point data.

Schedule

On schedule. Next week, we will put together a video for our demo.

Rama’s Status Update for 04/18 (Week 10)

Progress

I got speed up to 17 fps by not drawing the map; tkinter was a huge bottleneck. The data is formatted and I started planning integration to display point data on the map.

Deliverables next week

I will finish the integration with the point information before working on integration.

Schedule

On schedule.