Post by Rog on Feb 15, 2014 8:21:48 GMT -5
A month and a half ago we had a pointed discussion about a play in the Warriors/Heat game in which it was stated that the Warriors committed a foul that was missed, and then the ball was thrown out of bounds, which was also missed. It was stated that it was clear that the Warriors hadn't touched the ball, so if there was no foul, the Warriors should have gotten the ball. I finally got to see the play, so please allow me to comment in a more informed way.
First, the play happened in transition, just as I had surmised was the case. How did I know that? Because that is the time it is most easy to miss calls. If one stops and thinks about, the reason becomes obvious. The referees are scrambling for position and often don't get as good a look as they do in more of a half-court situation.
So as best I could tell (and the only thing I wasn't positive about, although I agree it was highly likely, was the foul), here is what happened and why. This isn't an excuse. The call was missed -- twice -- and ideally no call would ever be missed.
When the foul was committed, the referee who would normally make the call was the center ref. He was the one who was racing downcourt almost directly at the side of the play. He's got a body in between him and any contact that was made, so he couldn't see the foul. If he thinks there was a foul, he's caught between a rock and a hard place. If he's right and does call the foul (which wasn't certain even with a better angle and slow-mo replay, but certainly appeared to be a foul), he's guilty of calling a foul he didn't see. And how many times have we heard here how bad it is for an official to call something he doesn't see?
So he's wrong if he gets the call right, and obviously he's wrong if he misses it. So essentially he's wrong in one manner or another because he's blocked on the play. Should he have been blocked on the play? Because of the quick interception of the David Lee back and cross court pass, I can see no way it was humanly possible. It wasn't because he was slow. He was keeping right up with the play, which if anything, made it harder to call because he was almost totally blocked.
Did he get a bad break on the play? No. He was actually behind the play when it started and yet was quick enough that with a slight veer by the Miami player, he had caught up to the play and was virtually horizontal from it (which as mentioned, was part of the problem he had in viewing it).
So what we've got is a play on which the referee most responsible for the play did nothing wrong -- and yet certainly did appear to miss the call.
OK, so how about the ref who called the pass out of bounds on a Warrior deflection? Because he was the trail referee becoming the lead when the ball changed hands, he probably had a better angle on the play. But there was also a player from each team who was out in front of the play. Watching those guys was his primary responsiblity.
I think when the ball went out of bounds, he was pretty darn sure something had happened back near midcourt. He wasn't sure enough of what happened to call a foul, but he knew something had happened and the Warriors didn't deserve the ball. So he called a deflection (which did appear to happen, although the ball then went right back into the hands of the Miami player but in a manner that caused him to throw the ball away). Gave the ball to the Heat.
Was the play called correctly? It certainly didn't appear that way (although the only way to be positive would have been with a camera at a different angle than either of the two shots that were shown). Did the right team wind up with the ball? Very likely it did.
So we've got one referee who couldn't see the apparent foul because he was blocked. And we've got the other referee who out of the corner of his eye saw enough of the play to know it shouldn't be a Warriors ball. So he made what was probably the judicious call. (He likely didn't even see enough of the play to know which player to call the foul on.)
The referees almost certainly missed the call, but they wound up at least not taking the ball away from the Heat. They appeared to get the spirit of the call right, even if the play wasn't called to the letter of the law. Was the call impossible to get right? No, but it was likely at least as hard as shooting a free throw.
I hope at least now we can understand WHY the call was likely missed. That still doesn't make the call right. But it does show that the person who said if the referee couldn't get it right, he shouldn't be an NBA official was at least as wrong as the result of the play. If the official shouldn't be in the NBA because he missed that play, no player who ever missed a free throw should be in the NBA either.
So what was the most ridiculous comment here IMO? It was the statement that the referee should have paid the fine for the technical foul Mark Jackson received on the play. First of all, which official should have paid the fine? The one who was blocked on the play and appeared to miss the foul? Or the one who got the spirit of the call right?
But more importantly, whether an official missed a call or not, there is no excuse for a coach to get a technical foul. Well, I actually CAN make an excuse. The coaches are under tremendous pressure in a very emotional situation. But they still should maintain their dignity. Doing enough to get a technical foul is akin to the referee's coming over during a time out and questioning the coach's strategy by cursing at him. Or worse, questioning the stategy while play is still going on.
The problem here isn't that with the aid of instant replay and slow motion we don't see most of the time when a call is missed. The problem is that we don't understand -- and don't seem even to WANT to understand -- why the call was missed.
I have made the statement here that sometimes even the easy calls are missed. Not very often, but it certainly does happen on occasion. Ever seen a player drop a routine fly ball or muff a routine grounder?
On this play, someone who understands officiating will tell you that while he HATES to see any call missed, this was a very tough play to call -- and at least the right team wound up with the ball. In fact, because the Warriors coach -- and Mark Jackson is a gentleman who rarely gets a technical foul -- got a technical, the Heat not only wound up with the ball, they also wound up with a point on the technical.
There is absolutely NOTHING that makes the calls on that play the right ones (other than the result made the result more or less proper). But I wanted to explain probably HOW the calls were missed. I realize no one gives a hoot, but they should. If a person hasn't reffed at a high enough level to know WHY those calls were likely missed, he probably shouldn't be criticizing.
Criticize that the call was missed, but don't say the referee should pay the fine for the technical foul. Even a child can understand why that is wrong. There is no reason why we, as adults, shouldn't be able to.
First, the play happened in transition, just as I had surmised was the case. How did I know that? Because that is the time it is most easy to miss calls. If one stops and thinks about, the reason becomes obvious. The referees are scrambling for position and often don't get as good a look as they do in more of a half-court situation.
So as best I could tell (and the only thing I wasn't positive about, although I agree it was highly likely, was the foul), here is what happened and why. This isn't an excuse. The call was missed -- twice -- and ideally no call would ever be missed.
When the foul was committed, the referee who would normally make the call was the center ref. He was the one who was racing downcourt almost directly at the side of the play. He's got a body in between him and any contact that was made, so he couldn't see the foul. If he thinks there was a foul, he's caught between a rock and a hard place. If he's right and does call the foul (which wasn't certain even with a better angle and slow-mo replay, but certainly appeared to be a foul), he's guilty of calling a foul he didn't see. And how many times have we heard here how bad it is for an official to call something he doesn't see?
So he's wrong if he gets the call right, and obviously he's wrong if he misses it. So essentially he's wrong in one manner or another because he's blocked on the play. Should he have been blocked on the play? Because of the quick interception of the David Lee back and cross court pass, I can see no way it was humanly possible. It wasn't because he was slow. He was keeping right up with the play, which if anything, made it harder to call because he was almost totally blocked.
Did he get a bad break on the play? No. He was actually behind the play when it started and yet was quick enough that with a slight veer by the Miami player, he had caught up to the play and was virtually horizontal from it (which as mentioned, was part of the problem he had in viewing it).
So what we've got is a play on which the referee most responsible for the play did nothing wrong -- and yet certainly did appear to miss the call.
OK, so how about the ref who called the pass out of bounds on a Warrior deflection? Because he was the trail referee becoming the lead when the ball changed hands, he probably had a better angle on the play. But there was also a player from each team who was out in front of the play. Watching those guys was his primary responsiblity.
I think when the ball went out of bounds, he was pretty darn sure something had happened back near midcourt. He wasn't sure enough of what happened to call a foul, but he knew something had happened and the Warriors didn't deserve the ball. So he called a deflection (which did appear to happen, although the ball then went right back into the hands of the Miami player but in a manner that caused him to throw the ball away). Gave the ball to the Heat.
Was the play called correctly? It certainly didn't appear that way (although the only way to be positive would have been with a camera at a different angle than either of the two shots that were shown). Did the right team wind up with the ball? Very likely it did.
So we've got one referee who couldn't see the apparent foul because he was blocked. And we've got the other referee who out of the corner of his eye saw enough of the play to know it shouldn't be a Warriors ball. So he made what was probably the judicious call. (He likely didn't even see enough of the play to know which player to call the foul on.)
The referees almost certainly missed the call, but they wound up at least not taking the ball away from the Heat. They appeared to get the spirit of the call right, even if the play wasn't called to the letter of the law. Was the call impossible to get right? No, but it was likely at least as hard as shooting a free throw.
I hope at least now we can understand WHY the call was likely missed. That still doesn't make the call right. But it does show that the person who said if the referee couldn't get it right, he shouldn't be an NBA official was at least as wrong as the result of the play. If the official shouldn't be in the NBA because he missed that play, no player who ever missed a free throw should be in the NBA either.
So what was the most ridiculous comment here IMO? It was the statement that the referee should have paid the fine for the technical foul Mark Jackson received on the play. First of all, which official should have paid the fine? The one who was blocked on the play and appeared to miss the foul? Or the one who got the spirit of the call right?
But more importantly, whether an official missed a call or not, there is no excuse for a coach to get a technical foul. Well, I actually CAN make an excuse. The coaches are under tremendous pressure in a very emotional situation. But they still should maintain their dignity. Doing enough to get a technical foul is akin to the referee's coming over during a time out and questioning the coach's strategy by cursing at him. Or worse, questioning the stategy while play is still going on.
The problem here isn't that with the aid of instant replay and slow motion we don't see most of the time when a call is missed. The problem is that we don't understand -- and don't seem even to WANT to understand -- why the call was missed.
I have made the statement here that sometimes even the easy calls are missed. Not very often, but it certainly does happen on occasion. Ever seen a player drop a routine fly ball or muff a routine grounder?
On this play, someone who understands officiating will tell you that while he HATES to see any call missed, this was a very tough play to call -- and at least the right team wound up with the ball. In fact, because the Warriors coach -- and Mark Jackson is a gentleman who rarely gets a technical foul -- got a technical, the Heat not only wound up with the ball, they also wound up with a point on the technical.
There is absolutely NOTHING that makes the calls on that play the right ones (other than the result made the result more or less proper). But I wanted to explain probably HOW the calls were missed. I realize no one gives a hoot, but they should. If a person hasn't reffed at a high enough level to know WHY those calls were likely missed, he probably shouldn't be criticizing.
Criticize that the call was missed, but don't say the referee should pay the fine for the technical foul. Even a child can understand why that is wrong. There is no reason why we, as adults, shouldn't be able to.