{"id":1440,"date":"2019-03-09T19:14:03","date_gmt":"2019-03-09T19:14:03","guid":{"rendered":"http:\/\/blogs.discovery.wisc.edu\/projects\/?p=1440"},"modified":"2019-03-29T21:48:54","modified_gmt":"2019-03-29T21:48:54","slug":"visual-acuity-week-3","status":"publish","type":"post","link":"https:\/\/blogs.discovery.wisc.edu\/projects\/2019\/03\/09\/visual-acuity-week-3\/","title":{"rendered":"Visual Acuity, Post 3"},"content":{"rendered":"

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

Progress<\/b><\/p>\n

This week I finished off the fixed head method of what i’m calling the Landolt V(virtual) test. Both test types are complete, and record data on the actual position of the C object plane (distance, and which direction the gap is pointed). I started to work on adding hand controls to the test, and building out the rest of the architecture so that this program can run in a standalone fashion outside of unity.<\/p>\n

I also started to run tests on myself, and found a few interesting things. First, that the issue noticed in week one where the C began to render in an odd fashion doesn’t carry over into the fixed head position test. Furthermore, in that fixed head position, the C object can get much farther away from the viewer before becoming illegible (visually useless due to rendering). I’m curious to see how others interpret these findings, whether the C becomes illegible at shorter distances for others.<\/p>\n

I’m also continuing research into validation. There’s a lot of ophthalmology stuff out there, but none of it directly translates to tests administered on screens, or really talks about validation of a Landolt C test.<\/p>\n

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

The vive setup in the dev lab was being particularly uncooperative this weekend, but aside from that and minor frustration as I continue to look for papers relevant to the topic of validating a Landolt C test, progress has been smooth.<\/p>\n

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