{"id":242,"date":"2023-04-28T17:00:18","date_gmt":"2023-04-28T21:00:18","guid":{"rendered":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/?p=242"},"modified":"2023-04-28T17:00:18","modified_gmt":"2023-04-28T21:00:18","slug":"team-status-report-for-4-29-2023","status":"publish","type":"post","link":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/2023\/04\/28\/team-status-report-for-4-29-2023\/","title":{"rendered":"Team Status Report For 4\/29\/2023"},"content":{"rendered":"<h6><b>Testing<\/b><\/h6>\n<p><strong>1. Audio to text<\/strong><\/p>\n<p><span style=\"font-weight: 400\">Due to the nature of our system, we mainly care that the speech recognition system recognizes the correct word, not its verb tense or singularness. Therefore, verbs of different tenses will be considered as the same word (e.g. \u201cwake,\u201d \u201cWoke,\u201d \u201cwaken\u201d are considered the same). Similarly, we won\u2019t distinguish between singular and plural nouns (e.g. \u201chamburger\u201d and \u201chamburgers\u201d are considered the same).<\/span><\/p>\n<p><span style=\"font-weight: 400\">The average accuracy across 10 samples was 87.9%. A more detailed report of the test results is available at \u201cNina Duan\u2019s Status Report For 4\/22\/2023.\u201d<\/span><\/p>\n<p><strong>2. Text to command<\/strong><\/p>\n<p><span style=\"font-weight: 400\">We tested the NLP system by sending it text input, simulating the parsed result of the speech recognition system by removing capitalization and punctuations. Some example inputs have already been listed in \u201cLisa Xiong\u2019s Status Report For 4\/22\/2023\u201d, and a detailed report will be included in \u201cLisa Xiong\u2019s Status Report For 4\/29\/2023\u201d. The NLP system is able to reach 100% accuracy when parsing basic commands.<\/span><\/p>\n<p><strong>3. Order upload latency<\/strong><\/p>\n<p><span style=\"font-weight: 400\">This tests the latency between the customer-side uploading an order and the staff-side receiving the uploaded order. To calculate the difference, we printed the time when the order was sent and the time when the order was received. \u201cTime\u201d is defined as the amount of time, in seconds, since the epoch (same as how Unix defines time).<\/span><\/p>\n<p><span style=\"font-weight: 400\">The average accuracy across 20 samples, collected over 2 days, was 1.638s. The median was 1.021s. A more detailed report of the test results is available at \u201cNina Duan\u2019s Status Report For 4\/22\/2023.\u201d<\/span><\/p>\n<p><span style=\"font-weight: 400\">The latency falls in an acceptable range but fluctuates depending on the latency of the network.<\/span><\/p>\n<p><strong>4. Order upload accuracy<\/strong><\/p>\n<p><span style=\"font-weight: 400\">This test checks that the order received by the staff-side is the same as the order uploaded from the customer-side. We hard-coded 10 different orders, with varying order items and quantity, and uploaded them to the database.<\/span><\/p>\n<p><span style=\"font-weight: 400\">The resulting accuracy was 100%. We found no mismatch between the order received by the staff-side and the order uploaded from the customer-side.<\/span><\/p>\n<p><strong>5. Kiosk activation latency and accuracy<\/strong><\/p>\n<p><span style=\"font-weight: 400\">This test checks how long it takes for the distance sensor to detect the presence of an approaching customer. We tested distances including 20 cm, 30 cm, 40 cm, 50 cm, 60 cm, and 80cm. For 20 &#8211; 60 cm, the resulting accuracy was 100%. For 80 cm, the accuracy was around 70% but since we are only expecting to detect customers within 60 cm away from the kiosk, we would say we achieved our goal. Latency was always under 2 seconds, and for 93% of time, it was below 1.5 seconds.<\/span><\/p>\n<p><strong>6. Latency and accuracy of distance detection for the mic<\/strong><\/p>\n<p><span style=\"font-weight: 400\">This test checks how long it takes (latency) for the distance sensor attached to our mic to detect if the person is speaking close enough (25 cm) to the mic when it is their time to speak. In addition, we tested how accurate the results are. For the latency part, it took an average of 1.3 seconds to detect that a customer was not close enough ( &gt; 25 cm). The accuracy rate was 95% on average. <\/span><\/p>\n<p><strong>7.\u00a0Integration test<\/strong><\/p>\n<p><span style=\"font-weight: 400\">We have done end-to-end testing among ourselves to make sure that the system is functioning as expected. Our next steps will be documenting the end-to-end order accuracy through thorough tests and finding volunteers to give feedback on the overall design.<\/span><\/p>\n<h6><b>Risks<\/b><\/h6>\n<p><span style=\"font-weight: 400\">Our entire system depends on the internet. Therefore, if the WiFi at the demo location fails, our system will fail. However, since we are using our laptops to run the system logic, we could use personal hotspots from our phones to keep the system up.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Another risk which we have mentioned in the 4\/22 status report is the noise level at Wiegand Gym. We hope that our demo location can be placed in one of the smaller rooms for a quieter environment.<\/span><\/p>\n<h6><b>Design Changes<\/b><\/h6>\n<p><span style=\"font-weight: 400\">We did not implement any design changes this week. We have finalized our system and are proceeding to the integration\/volunteer testing phase of the project.<\/span><\/p>\n<h6><b>Schedule<\/b><\/h6>\n<p><span style=\"font-weight: 400\">We are on track with our current schedule.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Testing 1. Audio to text Due to the nature of our system, we mainly care that the speech recognition system recognizes the correct word, not its verb tense or singularness. Therefore, verbs of different tenses will be considered as the same word (e.g. \u201cwake,\u201d \u201cWoke,\u201d \u201cwaken\u201d are considered the same). Similarly, we won\u2019t distinguish between &hellip; <a href=\"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/2023\/04\/28\/team-status-report-for-4-29-2023\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Team Status Report For 4\/29\/2023&#8221;<\/span><\/a><\/p>\n","protected":false},"author":687,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10],"tags":[],"_links":{"self":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts\/242"}],"collection":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/users\/687"}],"replies":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/comments?post=242"}],"version-history":[{"count":1,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts\/242\/revisions"}],"predecessor-version":[{"id":243,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/posts\/242\/revisions\/243"}],"wp:attachment":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/media?parent=242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/categories?post=242"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s23-teamd3\/wp-json\/wp\/v2\/tags?post=242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}