{"id":1476,"date":"2019-04-20T21:01:19","date_gmt":"2019-04-20T21:01:19","guid":{"rendered":"http:\/\/blogs.discovery.wisc.edu\/projects\/?p=1476"},"modified":"2019-04-20T21:01:19","modified_gmt":"2019-04-20T21:01:19","slug":"visual-acuity-week-7","status":"publish","type":"post","link":"https:\/\/blogs.discovery.wisc.edu\/projects\/2019\/04\/20\/visual-acuity-week-7\/","title":{"rendered":"Visual Acuity, Week 7"},"content":{"rendered":"

\"\"<\/a> \"\"<\/a><\/p>\n

Progress:<\/strong><\/p>\n

The application is done and ready for testing. I’ve run it on myself and a few friends thus far with consistent enough results to merit further tests. I’ve finished the UI finally, and the rest of the code needed to make the different components communicate. A user is now able to transition between tests, and return to the start screen \/ abort tests as desired.<\/p>\n

While the application will calculate a Snellen letter score, and it seems to put out something close to physical tests, I’m not sure I’m sizing the letters right (which for me means adjusting the distance the C object moves each time).<\/p>\n

Struggles:<\/strong><\/p>\n

The actual letter size still alludes me. Mostly because all of the information out there on sizing Snellen letters for a LogMAR test pertains to physical tests, where the actual size of the letter is first measured, then scaled to append 5 minutes of arc at different test distances.<\/p>\n

Next Week<\/strong><\/p>\n