Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different Prediction 1v2 & 2v1 #7

Open
Tplhardy opened this issue Mar 20, 2019 · 3 comments
Open

Different Prediction 1v2 & 2v1 #7

Tplhardy opened this issue Mar 20, 2019 · 3 comments

Comments

@Tplhardy
Copy link

I'm getting different predictions depending on whether which team I put in first and second position. Any fixes?

@Tplhardy
Copy link
Author

My thought was to normalize each column in MM Data each year to avoid having to do a-b with negative numbers.

@adeshpande3
Copy link
Owner

adeshpande3 commented Mar 20, 2019

Hmm that's a good point you bring up, I didn't really check for that, but yeah I tried it myself and a couple times the results are similar, but sometimes there is quite a bit of difference.

I think it also kind of depends on what ML model you're using since they are each different in the ways that they handle high dimensional data. But yeah, I think normalizing would be a good first step to try.

At some level I'm not sure what we can do. We conceptually know these two training examples should be "equivalent" to each other.
Example # 1: Input: 17 dimensional game vector X, Label: 1
Example # 2: Input: Negative of X, Label: 0

But the problem is that a machine learning model won't necessarily pick up on that. Wonder if there's a way to hard code that constraint. Not sure rn, but thanks for bringing it up!

@Tplhardy
Copy link
Author

Thanks! So I tried absolute values, and it just resulted in some overfitting (was getting 99% accuracy and predictions with 99% probability).
I think to solve for this in the short term (brackets due tomorrow) is, in case the two predictions are conflicting, take the difference of the two:

  • team a beats b with prob 0.55 (b beats a with prob 0.45)
  • team b beats a with prob 0.56
  • take the average -> b beats a with prob 0.505

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants