Assessing performance for different learning algorithms about ppscore HOT 2 CLOSED

Hi Rui, thank you for reaching out. We did not compile further performance tests yet but went with a basic but reliable algorithm.

There are many papers and articles out there comparing the performance of machine learning algorithms on various datasets.
I guess there are 3 takeaways:

• The best algorithm always depends on the exact data and underlying relationship. There usually is not the one winner
• Usually, all of the algorithms pick up some signal if the data has been preprocessed correctly
• The effect of the algorithm is more important if there is a lot of data and some algorithms might extract more information. In our case, we only have 1 feature so the performance differences should be less extreme

Since the intention of the PPS is to get a quick understanding of some hidden patterns I don't think that it is critical to always choose the perfect learning algorithm as long as there are no massive differences. E.g. a massive difference would be a score of 0.05 vs 0.9 or 0.5.

Nevertheless, I would be happy to provide more performance comparisons and will share them on the repo and maybe it turns out that the DecisionTree should not be the standard algorithm going forward.

If you make some further tests on your data, I am curious to hear about the results!

Best,
Florian

from ppscore.

Hi Florian,

Thanks so much for your very quick response!

I was precisely thinking on how these might do if we have thousands of features in a n >> p setting. In this case, and just like what happens if you were computing pairwise correlations, there will be a lot of false positives. So in addition to capturing non-linear relationships, as you so well highlight in your towards data science post, I was wondering if leveraging the asymetrical property of the PPS would be helpful or actually makes your life harder since it doubles the computational cost, and whether having other strategies (including bagging in RF) could help boost F1 scores.

I'm aware that it is this situation where you can easily test millions of associations that you want to avoid RF as they can become too slow for you then. Of course, one obvious solution is to do some preliminary feature selection and only compute the PPS from the reduced feature set :)

I'll pay attention to your posts here (or if you post these results on TDS I'd really appreciate if you could link it here). I will close this issue for now in any case.

Thanks once again!

from ppscore.