Have made this same complaint many times. As it isn't a predictive path, surely they can narrow it down to a precise point? Although maybe I'm oversimplifying as I guess depending on the angle of approach of the ball, it may be difficult to define which point on the ball touches pad first?Why does umpire's call cover impact? No one knows. But very slightly outside anyway.
Surely with a round ball first impact is a specific point?What's the rule on impact anyway? What does "in line with" mean.... Anything in line, all in line, >50% in line?
I'm going to guess whoever first drafted the law didn't give it much thought...
36.1.4. Vague. https://www.lords.org/mcc/laws/leg-before-wicketWhat's the rule on impact anyway? What does "in line with" mean.... Anything in line, all in line, >50% in line?
I'm going to guess whoever first drafted the law didn't give it much thought...
HawkEye isn't actually very good at this though. Point of impact is its weakest feature to the point of it actually being the area that causes the most uncertainty with the predictive element as well. It's extremely good at predicting the path of the ball once it knows where it start predicting from, but the determination of where that is is disturbingly manual.Surely with a round ball first impact is a specific point?
Sure, if we had an XI of Jeet Raval’sLeach could be quite a handful if we are chasing 250 on day 5.
ah but what about Santner if England are trying to see out the draw on day 5Leach could be quite a handful if we are chasing 250 on day 5.
Proven.Sure, if we had an XI of Jeet Raval’s
Yeah I have never understood why there would be a margin of error in the PREDICTION since it’s just extrapolating from the existing data, and since when were umpires supposed to account for random changes in trajectory after impact anyway? But this makes a lot more senseHawkEye isn't actually very good at this though. Point of impact is its weakest feature to the point of it actually being the area that causes the most uncertainty with the predictive element as well. It's extremely good at predicting the path of the ball once it knows where it start predicting from, but the determination of where that is is disturbingly manual.
I think it still treats the "front" of the ball to be the first point of impact even though pads aren't square and batsmen can move in three dimensions. That's why we still have umpire's call on impact.
Tbh I don't think we need umpire's call on the predictive element anymore at all. Exactly which part of the ball first hit the pad doesn't really effect where the ball is heading. It just makes people feel better, and also helps to make a massive amount of lbws not immediately change the game in a way people would be uncomfortable with. Your average cricket fan isn't really ready for the robot revolution.Yeah I have never understood why there would be a margin of error in the PREDICTION since it’s just extrapolating from the existing data, and since when were umpires supposed to account for random changes in trajectory after impact anyway? But this makes a lot more sense
13th over: New Zealand 39-1 (Raval 10, Williamson 12) The wind ruffles Williamson’s shirt, but he remains unruffled. And that’s a just lip-smackingly gorgeous common or garden jab for four off Archer. He’s your best friend’s mysterious, kind, yet untouchable older brother.