This week we focused on integrating with the board. We finalized our calibration and main software processes. We did more testing on how the lighting conditions affect our software and optimized our eye tracker by using the aspect ratio. One big risk that we are continuously looking out for is the speed of our program. On our laptops the computation speed is very quick but if it takes longer on the board our contingency plan is to use AWS to speed it up.
For the board we are now using TensorFlow 2.4 and python 3.6 which changes a few built-in functions. This is necessary for the compatibility with the Nvidia Jetpack SDK we are using on the board. There are no costs for this only minor changes in the code are necessary.
So far we are keeping to the original schedule. We will be focusing on optimization and next start working on our stretch goals.
This week my primary goal was working through and flushing out the calibration process, specifically making it more user friendly and putting pieces together. I first spent some time figuring out the best way to interact with the user. Initially I thought tkinter would be easy and feasible. My initial approach was to have a button the user would click when they want to take their initial calibration pictures. But after some initial research and coding and a lot of bugs I realized cv2 does not easily fit into tkinter. So instead I decided to work with just cv2 and take the picture for the user once their head is within a drawn ellipse. This will be easier for the user as they just have to position their face and this guarantees we get the picture and values we need. Once the calibration process is over I store the eye aspect ratio and mouth height into a text file. Adriana and I decided to do this to transfer the data from the calibration process to the main process so that the processes are independent from each other. Here is a screen recording of the progress.
2. Based on our schedule I am on track. I aimed to get the baseline calibration working correctly with simple user interface.
3. Next week I plan to start working on pose detection and possible code changes in order to be compatible with the board.
