|
avoid k's will be easy.
if you don't have 100% accurate ratings, it will be less clear. stick to mlb players and hopefully a good scout and budget if you don't want to use 100% accuracy.
just about everyhting is a ~normal distribution, so we cna make some assumptions.
for example, ~1/2 scale should be ~baseline average SO per player. (normal dist, so mean=median or so close it won't matter)
the max scale players will be some specific SO less based on LTM and LT of the league for SO. 3 s.d. out for max? good guess. then the >max even further... but it will be tied to these metrics mentioned... and it wil be consistent and repeatable under the same settings/context.
this particular endeavor requires absolute ratings, not relative ratings based on nonsense for nonsense reasons clouding the picture... on purpose i might add!
having relative ratings for the ai's function would be a good reason for them... making ratings more difficult to read accurately and precisely from a human's standpoint is not a good thing. context would dictate absolute for this type of data mining.
advancing runners and such.. lots of info to google... scoring % per out and base the runner is on -- just read an article in last week about that. rl will be different from your league.. but it can show you how to evaluate it for your leageu and learn how it differs.
if terminolgy is a problem, look at some lists of abbreviations to help your google search for relevant data.
Last edited by NoOne; 02-26-2018 at 04:06 PM.
|