openvinotoolkit / openvinotoolkit/open_model_zoo

[Feature Request]: Gaze Estimation Demos questions

Open
#3,856 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature
Dominant language
Python
Stars
4.4k
Forks
1.4k
Avg merge
4d 13h
Merged PRs (30d)
4

Description

Request Description

"Hello, I'm trying out the example on the official OpenVino website: Open Model Zoo Demos -> Gaze Estimation Demos. I have a few questions as follows and would like to ask your development team for assistance:

Could you describe the training dataset and the values of the feature points that determine the gaze for the 'gaze_estimation_adas_0002' model?
I would like to use this model to calculate the position on a computer screen based on the generated gaze vector. Is there a ready-made demo for this?
When testing the model, I found that the coordinate system of the gaze vector is that of the computer screen. It seems the screen needs to be vertical on the desk and parallel to the face. It's also mentioned that the camera should be at the same height as the eyes. I'm not sure if I understand this correctly."

Feature Use Case

gaze_estimation_adas_0002

Issue submission checklist
  • The feature request or improvement must be related to OpenVINO

Contributor guide

Open the contributing guide

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.

Research direction

Review the Open Model Zoo Gaze Estimation Demos and the gaze_estimation_adas_0002 model documentation first. Done means providing authoritative answers about the training dataset, feature points, gaze-vector coordinate assumptions, camera placement, and whether a screen-position demo exists.

Written by the indexing model from the issue text.

Assessment

Tech stack
machine-learning
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.