Eye-gaze: tracker matrix, calibration workflow, accuracy testing — the least-tested primary access method

Open
  • Is something wrong?
#69 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
accessibility, desktop, testing

Research direction

Start with RFC 0010 and the governance#41 test checklist gap analysis, then inventory the existing eye-gaze test entry points and available tracker APIs or drivers. Define and run tests for tracker compatibility, calibration persistence, auto-speed stability, dwell selection, and 30-minute fatigue; done means concrete test data and the RFC proposals moved to active.

Written by the indexing model from the issue text.

Description

From the governance test checklist gap analysis (governance#41).

Priority: HIGH — primary access method, least tested

Eye-gaze is the core access method for the target AAC audience on Windows, and it has:

  • No tracker compatibility matrix (which Tobii models? EyeTribe? PCEye?)
  • No calibration workflow test
  • No accuracy/stability test scenarios
  • RFC 0010's eye-gaze proposals are still open

What to test

  1. Tracker matrix: which trackers work with Dasher v6? (Tobii 4/5, PCEye Plus, EyeTribe — via what driver/API?)
  2. Calibration: does Dasher use the tracker's built-in calibration or provide its own? Does calibration state persist?
  3. Auto-speed stability: RFC 0010 mentions auto-speed adjusting based on gaze stability — does it oscillate or converge?
  4. Dwell + eye-gaze: the combination (gaze to steer, dwell to select) is the most common eye-gaze setup — is it tested?
  5. Fatigue: does accuracy degrade over a 30-minute session?

Relationship to RFCs

RFC 0010 (input & access methods) lists eye-gaze under "proposals still open." This issue should drive those proposals to active with concrete test data.

Dominant language
C#
Stars
0
Forks
1
Avg merge
1d 13h
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dasher-project/Dasher-Windows

All issues in dasher-project/Dasher-Windows

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.