You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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).
The text was updated successfully, but these errors were encountered: