-
Notifications
You must be signed in to change notification settings - Fork 687
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
Image based ML models trained on TeachableMachine V2 show 'NaN' prediction on Chrome and Firefox (Windows OS v 7) #112
Comments
I have the same problem. |
Even I have the same problem |
Hi, we've heard complaints about this on the Pose models as well. Would you be able to provide the specific computer model and browser you were using? We believe it is a hardware specific problem so need to know what specific models you are using. We've heard this reported from HP Elitebook 840 G-1 using all browsers for now. |
Hi, I am facing this same issue, but on a different platform. When I try this from a website that holds the exact same JavaScript code as the webview, it works perfectly fine. But if I attempt to use TensorflowJS and the tensorflow model (attribute within the Teachable Machine Model), to get the classification for a TM Image model, I keep getting "NaN". Model being Used: https://teachablemachine.withgoogle.com/models/LDsdxzd1H/ System Info: |
Hello, Hope this helps someone. |
I have same problem in pose detection. NaN% problem happens even before I import the model. After I train the model and test it on Teachable machine website, it keep giving me NaN% for every value. System Info: If I use F12 to see the error message, it says index.bundle.js:2214 Model disposed so nothing to render with hook |
My computer info (microsoft exel .csv file): |
Image based models trained on TeachableMachine V2 do not work on Chrome and Firefox (Windows OS v 7)The predictions show "NaN" only and no numeric prediction is made and the models are trained.No error come at the time of training.What could be the problem?
The text was updated successfully, but these errors were encountered: