|
Post by n00b on Nov 20, 2014 19:24:26 GMT -5
I didn't previously know that an out of rotation call on the receiving team results in the server being credited with an ace serve. That's interesting. And an out of rotation call on the serving team is a Service Error.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Nov 20, 2014 19:27:31 GMT -5
Worse yet, it's a service error for the person who was supposed to serve.
|
|
|
Post by mikegarrison on Nov 20, 2014 19:42:46 GMT -5
Worse yet, it's a service error for the person who was supposed to serve. Two different kinds of rotation errors. If the team is out of rotation and the wrong player serves the ball, the SE goes to the player who was supposed to serve. But if the team is just in the wrong overlap, the SE goes to the player who did make the serve.
|
|
|
Post by Wolfgang on Nov 20, 2014 21:16:06 GMT -5
Rotations also confuse me. I know the basics. Where I get confused is when teams employ the more complex zone formations. This could've been remedied if I investigated further, but I always forget. Plus, I'm sometimes lazy. For example, I often see the setter at RB, just behind or to the right side of the RF player. In this same formation, I often see the LF player at a position behind the RB (setter), albeit on the left side of the court.
So, two problems:
1. Why is the RB player legal? She's standing next to the RF player! I thought all the front row players had to be in front of the back row players. 2. Why is the LF player legal given that she's actually standing behind the RB player albeit on the left side of the court?
|
|
|
Post by n00b on Nov 20, 2014 21:30:01 GMT -5
Rotations also confuse me. I know the basics. Where I get confused is when teams employ the more complex zone formations. This could've been remedied if I investigated further, but I always forget. Plus, I'm sometimes lazy. For example, I often see the setter at RB, just behind or to the right side of the RF player. In this same formation, I often see the LF player at a position behind the RB (setter), albeit on the left side of the court. So, two problems: 1. Why is the RB player legal? She's standing next to the RF player! I thought all the front row players had to be in front of the back row players. 2. Why is the LF player legal given that she's actually standing behind the RB player albeit on the left side of the court? 10.3.1.1 In the front or back row, the right-side player must have at least part of one foot closer to the right sideline than the feet of the center player in the corresponding row, and the left-side player must have at least part of one foot closer to the left sideline than the feet of the middle player in the corresponding row. Each front-row player must have at least part of one foot closer to the center line than the feet of the corresponding back-row player. There's the language of the rule. To answer your questions... 1. In theory, RF must just be closer to the net than the RB. That means RB can't be touching the court closer to the net than whatever part of RF's foot is CLOSEST to the net. Note, RB isn't required to be "behind" RF, just that RF must have "at least part of one foot closer to the centerline" than the feet of RB. 2. RF must be in front of RB, CF must be in front of CB, and LF must be in front of LB (that's what they mean by "the corresponding back-row player". It doesn't matter where RB is in relation to LF. It's also worth noting that refs are directed to give a bit of leeway in this call. If a team is out of rotation by a small amount or the players leave their positions slightly before the server contacts the ball, they will not make the call.
|
|
|
Post by fiffer on Nov 20, 2014 21:31:39 GMT -5
Rotations also confuse me. I know the basics. Where I get confused is when teams employ the more complex zone formations. This could've been remedied if I investigated further, but I always forget. Plus, I'm sometimes lazy. For example, I often see the setter at RB, just behind or to the right side of the RF player. In this same formation, I often see the LF player at a position behind the RB (setter), albeit on the left side of the court. So, two problems: 1. Why is the RB player legal? She's standing next to the RF player! I thought all the front row players had to be in front of the back row players. 2. Why is the LF player legal given that she's actually standing behind the RB player albeit on the left side of the court? Overlap rules only apply to player directly in front/behind or directly beside. So the RB player only has to be behind the RF player. MB player only has to be behind MF player, LB has to be behind LF. Similarly, MF must be between RF and LF, but the back row players' positions are irrelevant (left to right, anyway)
|
|
|
Post by Wolfgang on Nov 20, 2014 22:54:13 GMT -5
Okay, some other things I'm curious about:
1. If a hitter hits the ball for an otherwise successful kill but the ref calls net violation on the opposing blocker, does the hit count as a kill for the hitter? 2. Conversely, if an opposing hitter hits the ball but a blocker blocks it for an otherwise successful block but the ref calls net violation on the opposing hitter, does the block count as a block for the blocker?
I'm guessing "no" for both questions.
|
|
|
Post by n00b on Nov 20, 2014 23:24:20 GMT -5
Okay, some other things I'm curious about: 1. If a hitter hits the ball for an otherwise successful kill but the ref calls net violation on the opposing blocker, does the hit count as a kill for the hitter? 2. Conversely, if an opposing hitter hits the ball but a blocker blocks it for an otherwise successful block but the ref calls net violation on the opposing hitter, does the block count as a block for the blocker? I'm guessing "no" for both questions. 1. This is a kill. Even if the ball is dug, it is a kill. Even if the ball is hit out of bounds, it is a kill. " Section 1, Article 2. A kill (K) is awarded to a player any time an attack is unreturnable by the opposition and is a direct cause of the opponent not returning the ball, or any time the attack leads directly to a blocking error by the opposition." 2. Not a block, just a hitting error. The hitter going into the net before the ball hit the ground is what led to the point, not the block. However, if the net violation was called on the attacker who was trying to cover the blocked ball and hit the net, then it WOULD be a block Section 5, Article 1.A block is awarded when a player(s) blocks the ball that comes off an attack into the opponent’s court, leading directly to a point. fs.ncaa.org/Docs/stats/Stats_Manuals/VB/2013easy.pdf
|
|
|
Post by Wolfgang on Nov 30, 2014 1:35:01 GMT -5
Why don't they keep stats on "touches"?
|
|
|
Post by kwyjibo13 on Nov 30, 2014 2:21:44 GMT -5
Coaches probably keep them but they do not matter in the boxscore for stats. And, if you ever have ever sat near the people on the computer doing stats for volleyball (like me), there is a good reason touches are not kept
|
|
trojansc
Legend
All-VolleyTalk 1st Team (2022, 2021, 2020, 2019, 2018, 2017), All-VolleyTalk 2nd Team (2016), 2021, 2019 Fantasy League Champion, 2020 Fantasy League Runner Up, 2022 2nd Runner Up
Posts: 28,139
|
Post by trojansc on Nov 30, 2014 4:27:21 GMT -5
Why don't they keep stats on "touches"? It should be counted as a "dig assist". You are assisting the digger by getting a touch. lol. at least at major D1 universities (and I suppose quite many below) , there are various different stats kept by the team that aren't published. Here's examples: (1) Points per Serve (by player) (2) Points in a specific rotation (3) Passing (i.e passing a 2.7 or 2.8 is REALLY good!) (4) Covering Block attempts (not sure how useful) (5) Hot/Cold Serving/Hitting Zones (6) Dig to transition options (this is complex, and measured differently, but when you are digging, how many transition hitters are available? 0-3. Sure there's more I'm leaving off.
|
|