Try using different textual features about bugbug HOT 5 OPEN

Regarding fastText, see piskvorky/gensim-data#26 (comment).

from bugbug.

@marco-c I just tried using 2-gram features for the TfIdfVectorizer, here is the gist of the results:
Before:

X: (11007, 21990), y: (11007,)
Cross Validation scores:
Accuracy: f0.951746383784194 (+/- 0.0027559934918468167)
Precision: f0.9821515475460835 (+/- 0.0025632765014633823)
Recall: f0.9621308627678055 (+/- 0.002984157203642199)

After:

X: (11007, 95124), y: (11007,)
Cross Validation scores:
Accuracy: f0.9525540057386749 (+/- 0.004604483751288196)
Precision: f0.9830817914064187 (+/- 0.0035752238919424186)
Recall: f0.9621308627678055 (+/- 0.0035581451061348556)

Unfortunately the terminal crashes with terminate called after throwing an instance of 'std::bad_alloc' in the second case.

from bugbug.

Results for which model?

To avoid OOMs, you can try to reduce the number of ngrams considered.

from bugbug.

These are the results for the bug model. Should I try it out for other models too? To generalize, won't it be better to have a feature of passing the value of n from the terminal? (something like python run.py --train --model=bug --ngrams=2)

from bugbug.

These are the results for the bug model. Should I try it out for other models too?

Yes, let's try the tracking, regression and component models too.

To generalize, won't it be better to have a feature of passing the value of n from the terminal? (something like python run.py --train --model=bug --ngrams=2)

Yes, it would be nice, but not so easy.

from bugbug.