Test setup of mobile lab and simulation system
Inputs
Mobile Lab
In order to test your prototype during Milestone 3 you have the option to use a physical test setup at the Science Park 2. Therefore, while Milestone 3 is running, we will provide you with a dedicated room, that contains a Walkolution treadmill as well as a step tracking device that counts the steps being walked on the treadmill. The room will be locked with a smart lock from Nuki that you can access using lock's the companion app on your personal smartphone.
Step Tracker
The device is an ESP32 microcontroller with a Time of Flight sensor, that triggers a step event each time the left leg of a walking person crosses the ToF sensor. You will therefore not receive a uniform pulse comparable to the walking pattern, but only the pulse of the left leg going back and forth. We will however, provide you with a code snippet that converts those non-uniform left-leg events into uniform two-leg events so that you can kickstart your motion game coding more conveniently from there.
Slow motion of a treadmill walk with the step tracker device in the background.
The device's white LED blinks and triggers a step event each time the left leg passes by.
Software Simulation
Please note, that using the physical mobile lab for testing is not a prerequisite to accomplish the exercises of the seminar with full grading. You can also write your motion game against a simulation environment that simulates step events via manual touch events. So don't worry! We will not judge your game according to its quality in terms of graphics, user experience or longterm motivation but only in terms of the activities and reasonings you have taken to get to your implementation results as well as the testability of your prototype. That being said, you are flexible to use one of the following testing options:
- Simulation only
- Mobile lab only
- Simulation and mobile lab combined
We will provide you with template repository on GitHub that let's you kickstart your motion game by forking the repository.
Outputs
We expect you to have implemented a testable MVP prototype. We consciously use the term "prototype" as we do not expect 100% working or productive software. However, we expect the prototype to be as functionally complete to test a single usage scenario with a potential target user. Therefore: try to minimise features where you can from the start! The more mechanics or options to include in your motion game, the higher the risk that you will not end up with a coherent testable prototype.
For example, it is okay to create a prototype that is only capable of counting and visualising the number of steps the user had been taken as long as this function is counting correctly while being tested with potential external test users. However, it would not be okay to create an epic landscape that looks cool but is not in sync with the steps of the user and therefore unusable.
Please commit and push your code frequently into your group's GitHub repository and document non obvious parts of your code right in place.
More or updated information coming soon.