-
Notifications
You must be signed in to change notification settings - Fork 195
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
FileNotFoundError: [Errno 2] No such file or directory: 'player_features.p' #5
Comments
did you find a solution? I got the same error |
Hi, anyone found a solution? I get the same error :( |
it's a problem related to the pickle stuff, just try to comment out from the main those 4 code line of |
@giambe99 thank you for the help, I will give it a go. |
Actually there are some problems with this code... |
You maight need to change datetime with datetime.datetime somwhere... |
@ricciolini sei italiano anche tu? |
Admit we are here cause of kalle hallen video hahahaha |
I'm a Python newbie ahah. I just wanted to try this code out for learning. There's a lot I don't understand, including xgboost. |
@ricciolini is an italian surname. |
@giambe99 thanks for the advice :) |
It didnt work for me. I have the same error. What can I do? |
Was facing the same issue. For me, commenting the following lines (79 to 86 of main.py) worked : Let me know if you need me to check more |
@giambe99 why you think the elo feature is completely useless? |
it's good to predict matches outcomes (with a certain precision), for ex, elo 2000 vs elo 1600 ---> alomost certain, but u're not considering facts like recent injuries that could even leed to se a bookie offering a 1.80 1.90 that said the best way to exploit bookies in a market is just to find the average of a given outcome and then bet on the platform who's offering the best deal (the best, not the profitable way). |
Yeah, good point. I was thinking to look for an average of certain points without using the elo, because as you said sometimes it is useless. |
almost finishing compilation I got this error
24200/24481 matches treated.
24300/24481 matches treated.
24400/24481 matches treated.
Traceback (most recent call last):
File "main.py", line 83, in
features_player=load("player_features")
The text was updated successfully, but these errors were encountered: