Replies: 28
| visibility 2
|
Orange Blooded [2423]
TigerPulse: 93%
32
|
tigers screwed by clock operator with less than a minute in
Nov 25, 2022, 9:34 PM
|
|
game,
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
How so?***
Nov 25, 2022, 9:41 PM
|
|
|
|
|
|
 |
Orange Blooded [2423]
TigerPulse: 93%
32
|
with 3 sec. the game clock started but shot clock didn't.
Nov 25, 2022, 9:47 PM
|
|
result, it should have been a shot clock violation and remained a tie game.Refs reviewed play ,didn't reverse call
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
|
|
|
 |
Hall of Famer [8208]
TigerPulse: 100%
43
Posts: 16077
Joined: 2001
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
The shot clock is synchronized with the game clock.
Nov 25, 2022, 9:57 PM
|
|
They started at the same time. The announcers were spewing gibberish, and later corrected themselves after talking with officials.
|
|
|
|
 |
Hall of Famer [8208]
TigerPulse: 100%
43
Posts: 16077
Joined: 2001
|
These were not in sync - game clock started when the ball
Nov 25, 2022, 10:08 PM
|
|
Was touched and was accurate - watch the replay and focus on the game clock. Ball was out at about 37.3-37.4
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
They were in sync ... just because the shot clock didn't
Nov 25, 2022, 10:19 PM
|
|
start moving when the game clock did does NOT mean it was not counting.
The game clock started right away because it shows 10th of seconds, therefore it immediately started counting down in 10ths. The shot clock only shows full seconds, and had over 3 seconds on it, but less than 4, so it only showed 3. When it started counting synched with the game clock, it didn't move for over a full second, so it appeared that it wasn't started, but it was, it just had to remain at 3 for over a full second before it changed to 2, all while we could see the game clock counting in 10ths. Just because you didn't see it moving doesn't not mean it was not counting - it was.
|
|
|
|
 |
Hall of Famer [8208]
TigerPulse: 100%
43
Posts: 16077
Joined: 2001
|
The shot clock had to be reset from the previous
Nov 25, 2022, 10:24 PM
|
|
play screw up - they literally had to punch in 3.0 not 3.9. Again, the game clock is all that matters - it showed 40.1. The shot was off before 37.1 so the shot is good.
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
I missed that part about resetting to 3.0. That makes a
Nov 25, 2022, 10:59 PM
|
|
difference, but the game clock still tells the tale - the guy got the shot off in less than 3.
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
In other words, the shot clock counts down without moving.
Nov 25, 2022, 10:31 PM
[ in reply to They were in sync ... just because the shot clock didn't ] |
|
It is counting in 10ths, we just don't see it - we only see it move in full seconds. It can count down a full second without changing or moving, say from 3.9 to 2.9. So, if there are actually 3.9 seconds left on the shot clock, we will see "3". As soon as it starts counting down, it will stay at 3 for a full second befor it changes to 2. It starts immediately, but we don't see it move for a full second. That's essentially what happened tonight. That caused the announcers, and a lot of other people, to incorrectly think it started late.
|
|
|
|
 |
Athletic Dir [1109]
TigerPulse: 100%
26
|
Re: In other words, the shot clock counts down without moving.
Nov 25, 2022, 11:00 PM
|
|
You’re wrong about that. When shot clock shows 3, it’s 3 or less.
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
You're right!
Nov 25, 2022, 11:30 PM
|
|
I stand erected!
On a clock that displays tenths of a second, like the game clock, when the whole number is 3, that means it's got 3 or more seconds remaining, for example 3.1, 3.2, etc.. When it goes to less that 3, the whole number changes to 2, to 2.9, 2.8, etc. BUT ...
On a clock that displays only whole numbers/full seconds, when the whole number is 3, it means 3 or less.
|
|
|
|
 |
Commissioner [1211]
TigerPulse: 100%
27
|
Re: with 3 sec. the game clock started but shot clock didn't.
Nov 25, 2022, 9:55 PM
[ in reply to with 3 sec. the game clock started but shot clock didn't. ] |
|
Watched all the numerous replays and if you look at the game clock (and ignore the shot clock) which was at 40.1, the player got the shot off just before the game clock hit 37.1 so within 3 secs.
It took forever to review but they got it correct.
|
|
|
|
 |
Commissioner [1224]
TigerPulse: 100%
27
|
Memories of the Duke clock
Nov 25, 2022, 9:52 PM
|
|
and the untimed seconds against Clemson.
|
|
|
|
 |
National Champion [7902]
TigerPulse: 100%
42
|
I was watching that. The explanation was…
Nov 25, 2022, 9:53 PM
|
|
that the game clock and shot clock were synced to start at the same time, but only the game clock shows tenths of a second; the shot clock only shows changes in one-second increments. And that is why the shot clock didn’t appear to start although the game clock was running. There was actually 3.9 seconds on the shot clock, but we could only see the 3.
Bottom line - if Clemson does a better job of rebounding and didn’t give Iowa so many extra chances, we were much more likely to win the game. We had them on the ropes at the end. Also we missed a clutch foul shot near the end.
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
Exactly. It's really not that hard to understand.
Nov 25, 2022, 9:59 PM
|
|
Don't know why so many are struggling.
|
|
|
|
 |
Game Changer [1746]
TigerPulse: 97%
31
|
Re: Exactly. It's really not that hard to understand.
Nov 25, 2022, 10:35 PM
|
|
One thing all of you are missing. The play before, the ref said “3 seconds on the shot clock”. He didn’t say 3.9, or 3.5. He said 3. 3 means 3.0. That shot clock should have immediately dropped to 2 when the ball was touched.
|
|
|
|
 |
Standout [248]
TigerPulse: 100%
13
|
Re: Exactly. It's really not that hard to understand.
Nov 25, 2022, 10:50 PM
|
|
There was 3.0. It doesn't flip to 2 until it's at 2.0. It's easy to see why when you think of when it runs out. You want it it to flip to 0 at 0.0, not 0.9.
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
Oops - hold on!***
Nov 26, 2022, 10:10 AM
|
|
|
|
|
|
 |
Athletic Dir [1109]
TigerPulse: 100%
26
|
Re: Exactly. It's really not that hard to understand.
Nov 26, 2022, 4:45 AM
[ in reply to Re: Exactly. It's really not that hard to understand. ] |
|
No, it should change from 3 to 2, one second after the ball is touched. When you start a possession with a full 30 seconds, the clock doesn’t change to 29 immediately when touched. Only after a second expires.
|
|
|
|
 |
Orange Immortal [65578]
TigerPulse: 100%
60
Posts: 49140
Joined: 2000
|
That's a big problem then.
Nov 26, 2022, 10:09 AM
[ in reply to Re: Exactly. It's really not that hard to understand. ] |
|
That means that the players only had 2 seconds to shoot, not 3. Think about it ...
As soon as the ball is touched, the clock changes from 3 to 2. Zero (or no significantly measureable amount) time has elapsed, yet one full second is gone off of the clock ... so as soon as they touch the ball, they really only have 2 seconds to shoot, not 3.
It seems to me that if the players are to have 3 seconds to shoot, then one full second would have to elapse after the ball is first touched before the clock changed to 2, where it would remain for one full second before changing to 1, where it would remain for one full second before changing to 0, thus giving 3 full seconds to shoot. That's the way the game clock, which displays 10ths of a second, works. For instance, let's say you had 3.0 seconds left on the game clock, and 3 seconds left on the shot clock, and immediately started the count as soon as the ball was touched, the game clock would change from 3.0 to 2.9, not from 3.0 to 2.0, while the shot clock would change from 3 to 2. When the shot clock eventually got to 0 (zero), the game clock would still show 0.9 seconds. The only way to avoid that disparity is to have a shot clock that also displays 10ths of a second, or allow a full second to pass on the shot clock upon initial touch before changing.
|
|
|
|
 |
National Champion [7271]
TigerPulse: 100%
42
|
Re: tigers screwed by clock operator with less than a minute in
Nov 25, 2022, 11:33 PM
|
|
If he didn’t coach from behind all of the time it wouldn’t be an issue.
|
|
|
|
 |
Tiger Titan [50729]
TigerPulse: 79%
58
Posts: 37006
Joined: 2003
|
We weren’t screwed by the clock operator
Nov 26, 2022, 12:37 AM
|
|
but we were screwed by the refs who didn’t call a foul on Iowa’s player for pushing Schieffelin down. That allowed him to get the offensive rebound and have an uncontested putback.
Considering the fact that we were called for at least 6-8 phantom fouls tonight, it’s super annoying that Ian was literally pushed down and nothing was called.
|
|
|
|
 |
Hall of Famer [8831]
TigerPulse: 100%
43
|
Blame the refs tactic? Thoughts on final play call?***
Nov 26, 2022, 12:39 AM
|
|
|
|
|
|
 |
Tiger Titan [50729]
TigerPulse: 79%
58
Posts: 37006
Joined: 2003
|
I’m not blaming the loss solely on the refs.
Nov 26, 2022, 1:05 AM
|
|
We only have ourselves to blame for:
-Allowing 17 offensive rebounds -Only shooting 40.6% from the field
But the refs played a role tonight. Lots of phantom fouls called on us that weren’t called on the Hawkeyes.
Of course, our job is to put ourselves in a position where the refs can’t influence the game like that. But when we are playing a legit top 25 team, that’s a tall order.
As I said in another thread, there were a lot of encouraging things about our performance tonight. I hope our fans can see that.
I have no issue with the final play. We didn’t have any timeouts left and only had ~1.5 seconds to work with.
|
|
|
|
 |
Hall of Famer [8831]
TigerPulse: 100%
43
|
So how do we put ourselves in a better position
Nov 26, 2022, 1:14 AM
|
|
to pull out a very probable win against a legit top 25 team in which phantom calls by the refs have no influence on the outcome of the game?
So no problem with down by 3, ~1.5 to play, and Hail Mary the ball inside the 3 point line in a crowd of players with no chance to get any kind of good look at a basket?
|
|
|
|
 |
Freshman [-74]
TigerPulse: 66%
-1
|
|
|
|
Replies: 28
| visibility 2
|
|
|