Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Store user input #6

Open
svjharris opened this issue Aug 21, 2013 · 1 comment
Open

Store user input #6

svjharris opened this issue Aug 21, 2013 · 1 comment
Labels

Comments

@svjharris
Copy link
Contributor

Make sure that user input on the location of eye structures can be set and interpreted properly. Since the code isn't very accurate right now, most pictures will probably be processed by the code but structures will be identified by normal human vision, not computer vision (at least in the first release).

@svjharris
Copy link
Contributor Author

This is being implemented in the resetEyes and resetPupils methods in controller. These methods have yet to be working properly/fully tested. Also resetWhiteDot and resetCrescents need to be made.

Steven made a good point:

If the first detection is wrong all the subsequent detections should be redone.
For example, if the user resets Eye a new Eye object should be made so that findPupil and the methods it calls can be run again
If they reset pupil, findWhiteDot and findCrescent should be run again.

We'll need to change the reset code to be in line with Steven's point because now it just blindly resets the data it is given without making any new objects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant