Quote:
Originally Posted by H1LLIER
I think there may be an error on fielding calculations though, particularly 2B. I noticed it when sorting by wOBA and seeing Yordan Alvarez's SS WAR was over 3x higher than his 2B WAR. He'd be a terrible defender in either position so I wondered why there was such a difference. I did a bit of digging and I think IF range is being undervalued for 2B.
//
If I'm interpreting the calculations in config.py correctly it looks like IF range is over twice as valuable to 1B than it is to 2B which can't be right. Even 1B IF arm carries more weight at 75 rating
|
Hey man, thanks for this. I really appreciate thoughts on this...if you see any more 'this looks wrong' stuff please do send it my way. There are bound to be some bugs in this somewhere.
On 2B range here I think the numbers look OK / as I intended them but I ought to explain why. I'll get a video onto youtube soon to explain what I've done, but the basic idea is:
- for each position I've tried to identify what 'replacement level' fielding skills are - so the replacement level IF range for 2B is assumed to be 55, whereas for SS it is assumed to be 60 (these numbers are based on my MLB save)
- the numbers for 'runs saved per 162' are based on the testing I've done and the way I interpret the results is that for 2B there's a lot of downside to having a low-range guy but not much upside for having a high-range guy
- whereas for SS there is quite a bit of upside vs replacement level for having a high range guy, and actually less downside (which seems a bit odd, but that's what the testing results said)
- That's all based on the testing I've done - I will get organised and release all of the testing data / results so anyone interested can see all of the underlying data behind how the projections are put together
Will get that explanatory video out when I can, all being well over the next few days or so.
As I say please do point anything else out that looks weird, very much appreciate it
Thanks