{"id":225,"date":"2024-04-28T02:10:08","date_gmt":"2024-04-28T02:10:08","guid":{"rendered":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/?p=225"},"modified":"2024-04-28T02:10:08","modified_gmt":"2024-04-28T02:10:08","slug":"team-status-report-for-4-27","status":"publish","type":"post","link":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/2024\/04\/28\/team-status-report-for-4-27\/","title":{"rendered":"Team Status Report for 4\/27"},"content":{"rendered":"

Risk Mitigation\u00a0<\/b><\/p>\n

Our biggest risk this week is being able to test enough and fine tune our system for accuracy. We want to collect a variety of data in order to make sure our system is robust and we are able to include the relevant information in our final poster and report. We plan on going to test at Salem\u2019s almost every day this week, going at different times (sometimes in the morning to get data for when there are fewer people around, and sometimes at night from around 5-8 PM, where traffic is greater). This way we will have a variety of different tests to show for when it is time to write about testing in the final report.\u00a0<\/span><\/p>\n

Design Changes\u00a0<\/b><\/p>\n

We are exploring another way to measure throughput, instead of using our original camera angle which some cashiers were uncomfortable with, we are looking into a different camera angle (instead of overhead, we are looking into an angle that is on\/near the conveyor belt). However, this change is not final yet.\u00a0<\/span><\/p>\n

Schedule Changes\u00a0<\/b><\/p>\n

We have no schedule changes as of this week.\u00a0<\/span><\/p>\n

Tests\u00a0<\/b><\/p>\n

Below are some results from testing the upload and download time when recording different length videos. Interestingly, there is a spike in upload time from 2 to 3 seconds, but the internet that this was tested on (Brian\u2019s) is spotty, so that might have to do with the abrupt increase. Also, upload and download times remain quite stagnant from 5 second to 6 second videos. Based on these results, we figured it would be best to use 2 second videos, as the upload and download time seem to work best for meeting our latency constraints (< 5 seconds to compute a result after initially processing the video feed). It would be possible to go up to 4 second videos, but the spike from 2 to 3 second videos is a deterrent.\u00a0<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Duration<\/b><\/td>\nUpload Time (Averaged over 10 trials)\u00a0<\/b><\/td>\nDownload Time (Averaged over 10 trials)<\/b><\/td>\n<\/tr>\n
1 second<\/span><\/td>\n0.61s<\/span><\/td>\n0.32 s<\/span><\/td>\n<\/tr>\n
2 seconds<\/span><\/td>\n0.92 s<\/span><\/td>\n0.47 s<\/span><\/td>\n<\/tr>\n
3 seconds<\/span><\/td>\n1.35 s<\/span><\/td>\n0.53 s\u00a0<\/span><\/td>\n<\/tr>\n
4 seconds<\/span><\/td>\n1.52 s<\/span><\/td>\n0.55 s\u00a0<\/span><\/td>\n<\/tr>\n
5 seconds<\/span><\/td>\n1.61 s\u00a0<\/span><\/td>\n0.57 s<\/span><\/td>\n<\/tr>\n
6 seconds<\/span><\/td>\n1.65 s<\/span><\/td>\n0.59 s<\/span><\/td>\n<\/tr>\n
7 seconds<\/span><\/td>\n1.80 s<\/span><\/td>\n0.68 s\u00a0<\/span><\/td>\n<\/tr>\n
8 seconds<\/span><\/td>\n1.92 s<\/span><\/td>\n0.72 s<\/span><\/td>\n<\/tr>\n
9 seconds<\/span><\/td>\n2.21 s<\/span><\/td>\n0.76 s<\/span><\/td>\n<\/tr>\n
10 seconds<\/span><\/td>\n2.3 s<\/span><\/td>\n0.88 s\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\"\"<\/p>\n

In terms of testing relative fullness, we have tested with various different pictures and footage from Salem\u2019s in order to check the accuracy of the module. From these results, we determined that fullness calculations need a bit of tweaking in order to increase the accuracy. The module performs especially poorly with a very full cart as shown below. We have tried to decrease the Gaussian blur, which has increased the accuracy for these very full carts to a degree, but the calculations are still a bit unreliable, so we will need to adjust accordingly. <\/span><\/p>\n

\"\"

<\/p>\n","protected":false},"excerpt":{"rendered":"

Risk Mitigation\u00a0 Our biggest risk this week is being able to test enough and fine tune our system for accuracy. We want to collect a variety of data in order to make sure our system is robust and we are able to include the relevant information in our final poster and report. We plan on … <\/p>\n

Continue reading “Team Status Report for 4\/27”<\/span><\/a><\/p>\n","protected":false},"author":883,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4],"tags":[7],"_links":{"self":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/posts\/225"}],"collection":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/users\/883"}],"replies":[{"embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/comments?post=225"}],"version-history":[{"count":1,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/posts\/225\/revisions"}],"predecessor-version":[{"id":226,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/posts\/225\/revisions\/226"}],"wp:attachment":[{"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/media?parent=225"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/categories?post=225"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/course.ece.cmu.edu\/~ece500\/projects\/s24-teamc3\/wp-json\/wp\/v2\/tags?post=225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}