-
Notifications
You must be signed in to change notification settings - Fork 815
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
unvalid xml file and other basic questions about SVM trainers #463
Comments
Hm not sure if the actual error is related to this package, rather then being an issue with OpenCV not being able to load your xml file. To your second question, when using trainAuto, shouldn't you be able to get all the updated properties by logging the svm object: |
thank you for your answer.
it's as simple as that!? shame on me...
But average prediction results with test datas is 0.8208955223880597 so WTF*$#?!
If you see something wrong, please tell me. I continue my investigation. |
Uhm 0.82 is pretty good, that's overall about what I achieved in the example, isn't it? |
yes. but with my own data.
I think i find my mistake: our train pictures must be on THRESH_BINARY (or THRESH_BINARY_INV) for to be readable by the HOG? |
no, it still does not work. I'm stalling!
and My HOGAndSVMTrainer.js
... without errs module, saveConfusionMatrix etc... |
Odd, could you upload the xml file here, which is being produced from svm.save? |
sure! or |
I just tryed with a copy/paste of haarcascade_eye.xml and it's work perfectly. |
Hello guys, hello Vincent,
I ask noob questions, sorry about that.
My xml file for a very simple detection set return that common error :
It is probably the SVM trainer that gets me an invalid XML file.
So, I have a lot of questions before I can to be on my own:
At first; how to get settings chosen by the computer if we use the trainauto mode ?
Is there a command for console.log theme? even in python, this command is hard to find.
The code of my SVM trainer is almost the same as @justadudewhohacks 's one.
Thank you all.
The text was updated successfully, but these errors were encountered: