Changes between Version 4 and Version 5 of ESE2015Results


Ignore:
Timestamp:
06/05/15 15:57:21 (9 years ago)
Author:
sherbold
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ESE2015Results

    v4 v5  
    77  * the experiment configurations 
    88  * the results as .csv files 
    9  * US means only undersampling is applied, i.e., the file contains the configuration/results for ALL data 
     9 * US means only undersampling is applied, i.e., the file contains the configuration/results 
    1010 * US-ENTITYKNN means that undersampling and the KNN data selection is applied, i.e., the file contains the configuration/results for the KNN data selection 
     11 * The results contain additional classifiers, i.e., a Random Forest. The results are similar to the SVN results and were omitted from the paper as to not dilute the focus.  
     12 * The results for US-ENTITYKNN also contain the combination of the KNN model with the two local models. These results are interesting, but out of scope of the paper. Moreover, they carry a similar message than the other results and also do not really beat the global model. Therefore, they were removed from the paper as to not dilute the focus.  
    1113 * The results contain additional metrics and success measures, we did not discuss in the article, but are evaluated by !CrossPare anyways. 
    1214  * the metrics error, recall, precision, f-score, g-score, MCC, AUC, AUCec (after Rahman et al.: Recalling the “imprecision” of cross-project defect prediction), true positive rate (tpr), true negative rate (tnr), number of true positives (tp), number of false negatives (fn), number of true negatives (tn), number of false positives (fp) 
     
    1618  * succG60 is 1 if g-score>0.6 
    1719 * A batch script for execution the experiments. 
    18   * Be aware the the results are overwritten and the executions will take at quite some time. Moreover, !CrossPare will grab all of your CPU cores and consume than too 100%. 
     20  * Be aware the the results are overwritten and the executions will take at quite some time. Moreover, !CrossPare will grab up to all of your CPU cores and consume than too 100%.