Help--100% accuracy with LibSVM?

13
votes

Nominally a good problem to have, but I'm pretty sure it is because something funny is going on...

As context, I'm working on a problem in the facial expression/recognition space, so getting 100% accuracy seems incredibly implausible (not that it would be plausible in most applications...). I'm guessing there is either some consistent bias in the data set that it making it overly easy for an SVM to pull out the answer, =or=, more likely, I've done something wrong on the SVM side.

I'm looking for suggestions to help understand what is going on--is it me (=my usage of LibSVM)? Or is it the data?

The details:

  • About ~2500 labeled data vectors/instances (transformed video frames of individuals--<20 individual persons total), binary classification problem. ~900 features/instance. Unbalanced data set at about a 1:4 ratio.
  • Ran subset.py to separate the data into test (500 instances) and train (remaining).
  • Ran "svm-train -t 0 ". (Note: apparently no need for '-w1 1 -w-1 4'...)
  • Ran svm-predict on the test file. Accuracy=100%!

Things tried:

  • Checked about 10 times over that I'm not training & testing on the same data files, through some inadvertent command-line argument error
  • re-ran subset.py (even with -s 1) multiple times and did train/test only multiple different data sets (in case I randomly upon the most magical train/test pa
  • ran a simple diff-like check to confirm that the test file is not a subset of the training data
  • svm-scale on the data has no effect on accuracy (accuracy=100%). (Although the number of support vectors does drop from nSV=127, bSV=64 to nBSV=72, bSV=0.)
  • ((weird)) using the default RBF kernel (vice linear -- i.e., removing '-t 0') results in accuracy going to garbage(?!)
  • (sanity check) running svm-predict using a model trained on a scaled data set against an unscaled data set results in accuracy = 80% (i.e., it always guesses the dominant class). This is strictly a sanity check to make sure that somehow svm-predict is nominally acting right on my machine.

Tentative conclusion?:

Something with the data is wacked--somehow, within the data set, there is a subtle, experimenter-driven effect that the SVM is picking up on.

(This doesn't, on first pass, explain why the RBF kernel gives garbage results, however.)

Would greatly appreciate any suggestions on a) how to fix my usage of LibSVM (if that is actually the problem) or b) determine what subtle experimenter-bias in the data LibSVM is picking up on.

2
artificial-intelligencemachine-learningcomputer-visionsvmlibsvm
Mmmm, data and model analysis at arm's length. Doable, but really, really slow. This could be rather challenging. Any chance you can post the data? It's almost surely the data, but having someone else reproduce it could be helpful. Also, if you are proficient in R, that could make it easier to advise. – Iterator
the most likely -) is that you have included your test data in the training set. I know you've check, but check some more. – bmargulies
@carlosdc has a good point: are these independent samples, or are you choosing rando, train/test splits where images could be very close temporally? – Iterator
@severian: if you process the data set to a minimum, it should be far less - 2500 * 900 * 15 (assuming roughly 15 characters per feature) is about 33mb, uncompressed. My hunch is that it really is in the data - maybe the positive and negative samples where preprocessed somewhat differently, resulting in artifacts in the features that the classifier picks up on - has happened for other datasets too. As for the "RBF Kernel returning garbage" - that's likely overfitting. Varying C and sigma should help there (but why bother with RBF if a linear kernel seperates perfectly ;)) – etarion
@Sid: see the above thread--it was an issue (my fault) of not well-dividing the data set into test & training. E.g., consider a naive sort of dividing all frames 50-50 into test and training. Frame n+1 (and, to a lesser degree, n+2, n+3, etc.) looks a lot like frame n, and is generally (in my case) labeled identically to frame n. The classifier gets trained on frame n, and then sees n+1 in the "test" set and then magically gets it "right"...over and over. A more discrete partitioning (e.g., multi-second/minute/whatever subsets) into test & train was needed. – severian

2 Answers

11
votes

Two other ideas:

Make sure you're not training and testing on the same data. This sounds kind of dumb, but in computer vision applications you should take care that: make sure you're not repeating data (say two frames of the same video fall on different folds), you're not training and testing on the same individual, etc. It is more subtle than it sounds.

Make sure you search for gamma and C parameters for the RBF kernel. There are good theoretical (asymptotic) results that justify that a linear classifier is just a degenerate RBF classifier. So you should just look for a good (C, gamma) pair.

10
votes

Notwithstanding that the devil is in the details, here are three simple tests you could try:

  1. Quickie (~2 minutes): Run the data through a decision tree algorithm. This is available in Matlab via classregtree, or you can load into R and use rpart. This could tell you if one or just a few features happen to give a perfect separation.
  2. Not-so-quickie (~10-60 minutes, depending on your infrastructure): Iteratively split the features (i.e. from 900 to 2 sets of 450), train, and test. If one of the subsets gives you perfect classification, split it again. It would take fewer than 10 such splits to find out where the problem variables are. If it happens to "break" with many variables remaining (or even in the first split), select a different random subset of features, shave off fewer variables at a time, etc. It can't possibly need all 900 to split the data.
  3. Deeper analysis (minutes to several hours): try permutations of labels. If you can permute all of them and still get perfect separation, you have some problem in your train/test setup. If you select increasingly larger subsets to permute (or, if going in the other direction, to leave static), you can see where you begin to lose separability. Alternatively, consider decreasing your training set size and if you get separability even with a very small training set, then something is weird.

Method #1 is fast & should be insightful. There are some other methods I could recommend, but #1 and #2 are easy and it would be odd if they don't give any insights.