Rhode Island State Final

[BatteryPowered]

Originally Posted by Rich

I think putting 1.0 seconds on the clock was a bit generous.

From what I can see on the clock in the background I tend to agree. However, isn't a timeout technically granted when acknowledged by the official and not when he hits the whistle? That may be why the put a full second back on the clock.

[Rich]

Originally Posted by BatteryPowered

From what I can see on the clock in the background I tend to agree. However, isn't a timeout technically granted when acknowledged by the official and not when he hits the whistle? That may be why the put a full second back on the clock.

He didn't even catch the ball until there's 0.7 seconds left. The coach does immediately call time -- on first watching I had 0.5 seconds as an estimate and I'm happy with that -- still enough time for the winning play. But 1 second was too much.

They should use a monitor in that situation everywhere if it's available.

[BatteryPowered]

Originally Posted by Rich

He didn't even catch the ball until there's 0.7 seconds left. The coach does immediately call time -- on first watching I had 0.5 seconds as an estimate and I'm happy with that -- still enough time for the winning play. But 1 second was too much.

They should use a monitor in that situation everywhere if it's available.

Well, since the release at the end was at 0.7 (meaning 0.3 ran off) then it is a moot point

[Camron Rust]

Originally Posted by Rich

He didn't even catch the ball until there's 0.7 seconds left. The coach does immediately call time -- on first watching I had 0.5 seconds as an estimate and I'm happy with that -- still enough time for the winning play. But 1 second was too much.

They should use a monitor in that situation everywhere if it's available.

Originally Posted by BatteryPowered

Well, since the release at the end was at 0.7 (meaning 0.3 ran off) then it is a moot point

Agree.

The player first made contact with the ball at 1.0. Control, for all practical purposes, doesn't begin until some point after that. The coach signaled timeout at 0.6. The player turned towards an official at that same time....presumably saying timeout while doing so. At most, I've got 0.6 on the clock given that it takes some amount of time to control the ball before a timeout can be granted.

But, we have video to review it, they didn't. Still, I don't think I could have come up with 1.0 if I were there.

But, as also noted, 0.6 would have still been enough for that shot to have counted.

[BoomerSooner]

My first thought was that that earliest the timeout could have come was with 0.5 to 0.6 seconds remaining. After reading Rich's comment, I could possibly agree to 0.7 seconds, but timing the request and granting of the timeout to precisely coincide with calling at the exact moment the player gains possession is unlikely at best. That said, the ball was easily off of the shooter's hand in 0.3 to 0.2 seconds (I think the clock may have started a little slow), so the basket would have been good either way.

I am curious if anyone else noticed that the LED lights on the backboard appear to light up with 0.1 second remaining during the portion of the video where the timeout is called and the clock continues. It was a little blurry, but while trying to pause the video frame-by-frame to see how much time should have been put on the clock, I thought I saw 0.1 on the clock with the light on. Usually it seems like you'll get 0.0 without the light or horn, but never time left with a horn/light.

[BoomerSooner]

Originally Posted by BoomerSooner

I am curious if anyone else noticed that the LED lights on the backboard appear to light up with 0.1 second remaining during the portion of the video where the timeout is called and the clock continues. It was a little blurry, but while trying to pause the video frame-by-frame to see how much time should have been put on the clock, I thought I saw 0.1 on the clock with the light on. Usually it seems like you'll get 0.0 without the light or horn, but never time left with a horn/light.

Ignore this...I went back and looked at it 3 more times and realized that it was 0.0 on the clock.