-
Notifications
You must be signed in to change notification settings - Fork 529
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
Dataset extractor broken on 3.0.0 #253
Comments
Thanks for the report. You're probably right, because 3.0.0 changed the getPupilFeatures API a little bit. I'll look into it later this week. |
Hmmm was this working with WebGazer 2.1.2? And are you just using the webgazer.js from the www/ folder? I'm not exactly sure what your setup is. Generally, the video dataset was originally meant to work with a much older version of WebGazer, basically WebGazer 1.x. If it easily works with WebGazer 2.x then that's great. If you're fine with tinkering a bit, here the error is simply that estimateFaces() needs a video stream (due to the newer facemesh) and it's being passed a null one. There might be a way to remove that need for a video stream in webgazer.js completely, and revert the parameters back to what it was in 2.x. Or there can be a way to pass that into estimateFaces(). |
Thanks for looking at that so quickly. |
I can see from #253 @bbonf that dataset extractor does work on Webgazer 2.1.2 so I reverted to it using
and then nothing... So I checked the console log on my browser and it has
I'm not adept at javascript :/ What can I do to fix this? |
@Lotemn102 May be this error is caused by a missing webgazer.js.map file. Have you tried copying and pasting webgazer.js.map from /dist into www/data/src/webgazer.js.map? |
I think it has to do with the video element changes in cd26c90
The text was updated successfully, but these errors were encountered: