-
Notifications
You must be signed in to change notification settings - Fork 10
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
How to use this collected data in personalized calibration #2
Comments
may be use this https://github.com/pperle/gaze-tracking |
@DanielC-MST did you manage to figure this out? I'm stuck on the same problem |
@pperle Any chance you can help out here? I have the csv file same as @DanielC-MST but not sure how to use it. :( |
I'm stuck on the same. How can we use this csv in the pipeline project? @pperle |
I am in the same problem, does someone found out how to fix this? |
anyone solved the problem? i'm facing the same issue |
eval.py |
@losemankim will the eval.py do the preprocessing on my custom data or will it train another model that i can infer on for prediction? |
For preprocessing MPIIFaceGaze, download the original dataset and then run python dataset/mpii_face_gaze_preprocessing.py --input_path=./MPIIFaceGaze --output_path=./data. Or download the preprocessed dataset. To only generate the CSV files with all filenames which gaze is not on the screen, run python dataset/mpii_face_gaze_errors.py --input_path=./MPIIFaceGaze --output_path=./data. This can be run on MPIIGaze and MPIIFaceGaze, or the CSV files can be directly downloaded for MPIIGaze and MPIIFaceGaze. @kimou6055 |
Hi, did you ran the model using your calibration data? |
Hi, I would like to check after this gaze-data collection. I got a CSV file including file_name, point_on_screen, time_till_capture, monitor_mm, and monitor_pixels. But I don't know how to use these data to calibrate in the gaze-tracking pipeline (https://github.com/pperle/gaze-tracking-pipeline).
The text was updated successfully, but these errors were encountered: