First and foremost, it's a very simple metric if I wasn't clear enough. I just gave weights to box score stats based on a regression. It's that simple. If you have the same data you can build it in a short time. So I don't want to call it a model as it would be shameful.
I say it again. Only simulations will be accurate enough for the prediction of complicated sports. If it's easy to accomplish 55%+ accuracy at predicting the final score margin (I think it's called spread or something like that. English is not my native language) of NBA games, I just ask you where's that metric? There are lots of money for us to earn..
You can find approx PER weights here. I wasn't the author of article btw.
http://bleacherreport.com/articles/1131 ... l-the-mess
I thought weights were not good enough and making a PER-like pure box-score stat metric based on regression would be more accurate and here it is. In fact, I searched for that kind of metric (without the implementation of +/- in any format - SPM is one of them) and I couldn't find one. So here it is.
Finally, scaling. I strongly resisted to comment on that but I'll shoot it then. It's related to how I ran the regression. As you all know box score stats do not represent a lot of things especially at the defensive end and players don't get credited for their mistakes. So that box-score ratings should be theoritically higher than +/- stats and metrics. But the margin should stay reasonably accurate since opponents' ratings will be higher too.
Then you'll point out that player-combined rating of LAC per 100 poss is 95 while WAS' rating is 64 and 31 differental definetely doesn't represent MOV. Here you should just take the half of PTR and then you'll get your MOV.
Why is it "half"? My answer is regression again. I think you should understand why I don't give the details of regression here. All I can do is reitarating the fact that Point-Opponent Points=MOV. Some people will probably guess why it's "exactly half" now.
Edit: While I was reading EZPM details (thanks DSMonK), I thought using PBP data is simply beyond awesome (I'm too lazy for such a thing) and I really liked the model. Just I spotted some minor things. For example:
Blocks: In my model, the +0.7 coefficient for blocks has real meaning, since it gives the full value of the opponent's missed field goal to the player getting the block. To me, this makes perfect sense, since the guy getting his shot blocked missed the field goal and loses 0.7 pts. Shouldn't the blocker be credited with exactly the same amount?
Simply no. This is why theoritical approach is not good enough. If your FG miss is -0.7, block should be something like 0.68. Because if Player A wouldn't block that FG and Player B missed that FG, it would be better for Player A's team. Check offensive rebound percentage of blocked shots vs unblocked field goal misses and out of bounds situation. Especially since EZPM uses PBP data, it should seperate blocked shots from field goal misses and non-steal TOs from steal-TOs (here comes fastbreak possibility. Almost 9% worse than normal turnover).