Marco Castelluccio

I wonder if this kind of data already exists in some dashboard that we can simply link to. CC @ahal @Archaeopteryx @jmaher @ahal

No, it's not resolved yet. It depends on #637, so that one must be fixed first before fixing this one. Once that is fixed, something similar needs to be done...

You should train a model first, so that the bugs DB will be downloaded. ``` python3 run.py --goal defect --train ```

Can you post the output of `ls -al data/`? What error pops up? Try to give as much info as possible, otherwise it'll be hard to help you :)

Yes, there is a trainer script now (see the README for updated info).

@sd1998 feel free to work on any open issue (following the rules in CONTRIBUTING.md), no need to ask.

@Divya063 all issues are unassigned until there is a PR open to fix them, so feel free to work on this if it's interesting for you.

@srajgure there is quite a few info in this issue report, just read through the comments and ask if you have specific questions.

It might be better to add an option to the already existing word2vec classes to use doc2vec instead of word2vec (in the end they're very similar).

I tried DistilBERT out of curiosity for the components model (using the [transformers](https://github.com/huggingface/transformers) library) and it looks promising.