Saturday, December 8, 2012

tracking Dyop™ development

I was looking for a task list that I could use for Dyop™ development, and discovered the Blog feature in Chrome.

It occurred to me that I could use the Blogger feature to track Dyop™ development and create project/tasks lists since one of my ongoing difficulties is tracking what I am doing with the multiplicity of Dyop™ tests and figuring out what I am going to do next because of the breadth and depth of the Dyop™ concept.

Things to do today (or this weekend):

Consider changing the FullScreen buttons and image size buttons to put a white background behind a blue button.

Repeat the "Window of Visibility" test with my right eye as the monocular vision

Complete the series of color refraction tests and the menus for coordinating them.

Create a series of color acuity tests and the menus for coordinating them.

Contact Pedro Marin regarding dyslexia in Hispanics.

Create an automated color screening test.  Have Scott Talsma help me with the programming based upon the programming for the Dyop™ Motor Vehicle Vision Screening Test.

Revise the "Window of Visibility" to have Dyops™ rather than Hayes images and repeat the test.  Have Scott Talsma help me with creating a "Hayes Dyop™" with less than a proportional gap/segment.

Contact Dr. Jeff Rabin regarding Dyops™.

Send the Chris Chase email to Jim Irvine.

Send follow-up email to Dr. Chip Reddy with a copy to Erin Sauter.

Send comment to John Hayes and Jim Sheedy that Dyop™ use "strobic acuity" rather than spatial acuity.

Make reservation for SEMDA.

Contact Rick Dean about S3D Dyops™

Contact the 3D image guy.

Revise the Dyop™ brochure.