PepsiCenterMagic
Food is Great
- Jul 17, 2013
- 657
- 46
Unfortunately, no.Did you end up doing the ML model in the end?![]()
At least not yet.
Like I said above, it's hard to justify the time needed. I found some data from somewhere and did some poking around, trying to see if I could create a proof of concept, and realized the tedious nature of what I wanted to do.
It became tedious quick. And I question whether or not the data I need even is available to the general populous. I say this because if this is a model that is going to update itself everyday, not only do I need season stats per player, but a snapshot of a player's stats after every single game. This way, the model hopefully would be able to find complex relationships between features and time of season, and would be able to adaptively train and predict according to the trends of a progressing season - obviously training on the trends of all progressions of past seasons
And really, that is the concept that really intrigues me. Really, you want to turn to these models because they pick up complex relationships a lot more intuitively than we ever could, and iterate through them with impressive speed. This model would be able to pick up trends of a progressing season - and of course it all depends on what features we would be able to provide as traction - i.e interactions of injuries ~ recuperation time ~ player production behaviors (fast, slower starters) ~ team's intra-season production ~et al.
Last edited: