Open Suvodeep90 opened 5 years ago
Methods: 'ns', 'nd', 'nf', 'entropy', 'la', 'ld', 'lt', 'ndev', 'age', 'nuc', 'exp', 'rexp', 'sexp','fix' FX: commitguru: 13 attributes
FSS
CFS(https://github.com/ai-se/bellwether_community/blob/master/src/CFS.py) paper: https://www.cs.waikato.ac.nz/ml/publications/1997/Hall-LSmith97.pdf paper: https://www.cs.waikato.ac.nz/~mhall/HallHolmesTKDE.pdf thesis: https://www.cs.waikato.ac.nz/~mhall/thesis.pdf parameter:
temporal selection: https://arxiv.org/pdf/1803.05067.pdf
LEARNER: logistic regression
Hyper parameter optimizer
suggestions:
Success criteria
DATA
150 projects rows:
what's the PEEKING mechanism?
None. no zzz
Just the activity in the commit
LABELLING using keyword labelling
not yet active learning yet
TRAIN-TEST rig
suggestions:
RELATED WORK
has anyone used this data to get PD>66 nd PF < 33 before?
1) Predicting crashing releases of mobile applications - uses some metrics collected from commit guru along with other code related metrics. (recall- between .5 to .7, prec - ~0.2)
2) Just-In-Time Bug Prediction in Mobile Applications: The Domain Matters! - uses commit guru metrics with FSS - (58(p),25(R),34(F1))
3) Software Maintenance at Commit-Time - (90.75(P) 37.15(R) 52.72(F1))
TODO
Expectation from results:
FILES