This week I worked on testing, refactoring our code to allow for faster testing and verification, and drafting a user survey to guide some of our design decisions. In addition, I soldered and created another “base station.”<\/p>\n
(User Survey:\u00a0https:\/\/docs.google.com\/forms\/d\/1YM4OFE08eWwsJJnDHzXr_HDfEiTtsAuOjxWQ_ADB7e0\/edit)<\/p>\n
The testing I completed involved our first requirement: to turn on the lights within 2 seconds of a person entering a section. This ensures our computation and communication latency from signal detection to computation to signaling the lights is fast enough for our user. In order to capture times, I recorded myself on video, and timed from first movement to the lights turning on for five trials. I obtained the following results. The average time is 1.028s and each trial is below 2s.<\/p>\n
Trial,Time
\n1,\u00a0 \u00a01.2s
\n2,\u00a0 \u00a00.81s
\n3,\u00a0 \u00a01.11s
\n4,\u00a0 \u00a00.97s
\n5,\u00a0 \u00a01.05s<\/p>\n
To assist with further testing, I refactored our code and began developing a script to modify and adjust our weights given values captured and written to a test file along with a desired light behavior. The script uses a gradient descent-like algorithm for adjusting weights and validating defined test cases. Weights will be slightly modified until (hopefully) the desired light behavior is correct for all test cases.<\/p>\n
This coming week I will continue testing, send out the survey to collect responses after it is finalized and create another base station.<\/p>\n","protected":false},"excerpt":{"rendered":"
This week I worked on testing, refactoring our code to allow for faster testing and verification, and drafting a user survey to guide some of our design decisions. In addition, I soldered and created another “base station.” (User Survey:\u00a0https:\/\/docs.google.com\/forms\/d\/1YM4OFE08eWwsJJnDHzXr_HDfEiTtsAuOjxWQ_ADB7e0\/edit) The testing I completed involved our first requirement: to turn on the lights within 2 seconds … <\/p>\n