Demo1 Setup/Outcomes & Integration Moving Forward
This week, we had our first major demo to the Professor and TA! The bulk of the work we have done since our last status update focuses on first preparing for this demo, changing our development timeline to account for feedback given during the demo, and how we have since begun conducting this work.
First, in order to lead an effective demo, each member of the team had to organize their accomplishments to date in a visually-interpretable medium. For Thor, whose laptop camera does not work, this goal meant videotaping servo movement on his phone and showcasing the output alongside a schematic of the battery management system. For Diego, this goal meant recording a video of himself poorly skateboarding down his driveway, with the Perception pipeline detecting him at the start of the video and tracking his movement down his driveway. For Ike, this goal meant setting up benchmarking measures that, across multiple threads, can track the transfer of data across critical pathways of the CSM.
Then, once all accomplishments were demonstrated to the Professor and TA, the team received feedback regarding the importance of conducting software integration as soon as possible. As a result, we have modified Ike’s and Diego’s timelines to push iOS remote development, Perception speedups, and bluetooth communication back in favor of integrating software work as soon as possible. Thor will be continuing with his previously intended timeline as this work is isolated from the majority of software development.
Lastly, Ike and Diego have begun talking to integrate Perception into the CSM pathways. The largest area of concern in this case is testing the integration, as Ike still has not received his Jetson and cannot run any of the Perception code, while Diego is not as familiar with the CSM framework.
0 Comments