Accomplished
I presented our proposal on Monday, so a good part of my week went into the slides, rehearsing, and preparing answers for questions on our timing numbers and on why we use a scheduler rather than one shared model.
My technical task this week was writing out the equipment states and timer rules, which is the logic the rest of the application is built on. A treadmill is available, in use, or unknown, and a rack or bench is in use, free, or flagged. I also wrote down the rules the timers follow, including when a timer starts, that it only runs while nobody is at the station, that a person returning resets it, and how a flag clears once the station is reset. Getting this written down early matters because both the detection work and the scheduling work feed into it, so we all need to agree on what a detection is supposed to mean. A couple of open questions came out of it too, like how long someone has to be in a zone to count as returning so a person walking past does not reset the timer.
Progress
On schedule. The states and timer rules were this week’s task and they are written up.
Deliverables
Start on the dashboard, beginning with a version running on fake data so we can see the treadmill count and station flags before any real detections exist. Write tests for the timer rules using made up detection sequences. Help with the design presentation slides.