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

Kellycriterion #230

Merged
merged 5 commits into from
May 5, 2023
Merged

Kellycriterion #230

merged 5 commits into from
May 5, 2023

Conversation

timseymour42
Copy link
Contributor

In this update, I did the following:

  • Created a Kelly Criterion class to calculate the percentage of the bankroll a bettor should use
  • Revised the NN_Runner and XGB_Runner files to indicate the correct fraction of the bankroll for each bet
  • Created a Kelly Criterion test file to ensure the calculations are accurate
  • Refactored color logic in the NN_Runner and XGB_Runner files
  • Updated the Readme to reflect the changes

KC Update

@kyleskom
Copy link
Owner

Will review this soon. One thing I'm thinking though is to have this behind a feature flag.

@fciaf420
Copy link

I am very new to this, how can I pull thos code into collab and run it to get the kelly criterion results ?

@timseymour42
Copy link
Contributor Author

I am very new to this, how can I pull thos code into collab and run it to get the kelly criterion results ?

You can replace the git clone command with this: git clone -b kellycriterion https://github.com/timseymour42/NBA-Machine-Learning-Sports-Betting.git

You can also plug the model's win probability into this calculator: The kelly criterion feature is not a part of the main code base just yet.

@timseymour42
Copy link
Contributor Author

Will review this soon. One thing I'm thinking though is to have this behind a feature flag.

Yeah, that's a great idea! I can implement this. Before doing so, I just want to be sure that my code would be used because there is another contributor that implemented the kelly criterion feature. So lmk.

@kyleskom
Copy link
Owner

Will review this soon. One thing I'm thinking though is to have this behind a feature flag.

Yeah, that's a great idea! I can implement this. Before doing so, I just want to be sure that my code would be used because there is another contributor that implemented the kelly criterion feature. So lmk.

Yup this will be used / merged if we can have this behind a feature flag.

@onlyadamscott
Copy link

Such good work. Thanks guys! I'm working on a native Sentiment agent. Still testing for accuracy.

@BG2011
Copy link

BG2011 commented May 2, 2023

Great addition man ! Small question this will work for the money line but what about the points ?

@timseymour42
Copy link
Contributor Author

Great addition man ! Small question this will work for the money line but what about the points ?

Currently, the output of the models is a percentage chance that a team will win on the ML. You could raise an issue that you would like to see predictions for the point spread.

Copy link
Owner

@kyleskom kyleskom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and verified. Works as expected!

@kyleskom kyleskom merged commit 05f71ed into kyleskom:master May 5, 2023
@kaiforsyth
Copy link

This breaks when not passing the -odds argument to use custom odds:
TypeError: '>=' not supported between instances of 'str' and 'int'

Need to convert the input to an integer.

@kyleskom
Copy link
Owner

kyleskom commented May 5, 2023

This breaks when not passing the -odds argument to use custom odds: TypeError: '>=' not supported between instances of 'str' and 'int'

Need to convert the input to an integer.

Can you open an issue.

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

Successfully merging this pull request may close these issues.

None yet

6 participants