From 1340a73214a76dcc32eb00b2788354bd72c7e8c8 Mon Sep 17 00:00:00 2001 From: Benjamin Chase Date: Wed, 15 May 2024 20:46:36 -0400 Subject: [PATCH] Update capstone.html --- engineering/edd/capstone.html | 59 +++++++++++++++++++++++++++++++++-- 1 file changed, 57 insertions(+), 2 deletions(-) diff --git a/engineering/edd/capstone.html b/engineering/edd/capstone.html index 28321ae..ce394eb 100644 --- a/engineering/edd/capstone.html +++ b/engineering/edd/capstone.html @@ -891,13 +891,68 @@

Learning Test Results

- - +

Final Capstone Presentation

 +

+ First, we did a dry-run presentation about a week before our final presentation. + Completely honestly, we did not spend much time on the dry-run presentation since we were still finishing the building process and testing procedures. + However, we did learn from the dry-run presentation that we needed to add much more to our presentation and that we needed to practice. +

+

+ Our final capstone presentation was on Wednesday, May 15th, 2024. + Logan and I worked on the presentation during school on the previous Friday and Monday, but we were nowhere near finished. + So Monday afternoon, I added eleven more slides, speakers notes, pictures, statistics, explanations, and added a section about our design process. + In the remaining day until our official presentation, I tried to get our team together to practice. + Unfortunately, we could not meet on the following day, so we decided to meet early in the morning before our presentation to do another practice run. +

+

+ This worked, and we organized roles along with planning out the presentation mechanics more. + I had reprogrammed the Chordinator to work offline, so network issues were out of the question. + Everything was ready, and we presented first. +

+

+ Our final presentation went very well, although I skipped over the software slide. However, when judges asked questions about software, + I was able to explain how I built a web scraper and how more frets could be added easily as an improvement to the Chordinator. + Additionally, our time was 11:07, which was longer than the recommended ten minutes, so overall it went well. +

+

+ Of course I would recommend to any team that they should practice multiple times before the day of the presentation, but for us this did not work. + Also, everyone should contribute equally to the presentation and the project as a whole. + I used extra time on the weekends to do programming and solder the electronics, however this was mainly out of my passion to make this project truly useful and more than functional. +

+

+ We also made a brochure, which was given to the judges: +

+
+ Brochure Front + Brochure Back +
+ + +

Thank You

 +

+ To make this project reality, we had help from our mentor Mr. Czar Domingo, who is an Aerospace Technology Software Engineer at NASA Wallops Flight Facility. + He helped to give crucial advice on our project. + With his experience in software validation, he helped to find possible issues such as viewing angle of the guitar body attachment + and cable management for the neck attachment before they could occur. + Mr. Domingo was very supportive throughout our project, always asked the right clarifying questions, and always believed in us. + We are very thankful for his help. +

+ +

+ We would also like to thank our absolutely wonderful engineering teacher Mrs. Zienty. + She never once doubted us, was always supportive of our project, helped us along the way, and gave us critical advice. + Mrs. Zienty also helped to manage our team, keep us on track, and gave us the knowledge and resources necessary to make the Chordinator a success. +

+

+ In the past few years, we also had classes with our other engineering teachers, Mrs. Sangwan and Mrs. Gallo. + They provided us with knowledge and sparked our interest in a variety of engineering fields and teaching us their respective skills. +

+