topleft topright

View RSS Feed

qatet

Reffing Milwaukee

Rate this Entry
by , 11-28-2010 at 09:09 PM (812 Views)
I reffed Milwaukee - my first NAC in years, although I reffed at Nationals this last summer. It clarified a couple things in my head, and was overall a good experience.

On the nuts and bolts front, there are a couple calls that I was not as good at and now see pretty well, particularly "attack stops, attack arrives." I'm still not quite sure how exactly to physically phrase that when I say it to the fencers, since there's no signal for "stops." I can either say that the attack is "no" or that it turns into a preparation, I suppose. I'll need to pay attention to a few other people as they make that call and see what they do.

There were a couple other distinct touches that I didn't quite have in my head before and do now. I remember vividly a moment of attack/counterattack where I was clearly able to see all the pieces of what the counterattacker was doing that made his action a counterattack. I've never before had a moment like that, where I could specifically tell that I was in the process of chunking together disparate pieces of information to create one group of knowledge. I probably won't ever have that moment again for that touch - I'll simply see it as a counterattack and that will be that.

Moments like that are one of the things that I most enjoy about reffing. It gives me a sense of how my brain works and what the limits of my brain are. I'm aware of micro-breaks in my attention, which are growing smaller and smaller. When I got back into reffing last year I would follow the first few actions of the phrase, and then simply stop taking in information. My eyes would be open, but there were gaps in what I remembered of the action, a sense of "wait, how'd the fencers get so far apart, they were just doing crazy infighting." I suppose it's similar to inattention blindness, where the brain, focusing on something else, stops interpreting information from the eyes. Here, my eyes and brain are focused on the same thing, but too much information comes in and my eyes just shut off. I still have moments of it, but they're much rarer. I guess that that's where chunking comes in. When I don't need to do as much work to interpret the action, when I can simply chalk up the moment as "attack/counterattck," then I can move on to the next moment in time along with the fencers. It's pretty common for refs to ask themselves why on earth they put up with the bad pay and yelling and such. For me, a large part of it is this chance to see how my brain works and feel that I'm pushing at and redefining the limits of my own processing power.

I got to use the video replay system, which was a very interesting experience. I think that it allows everybody to relax a bit more and focus on their job. The fencer can just think about fencing their opponent, the coach can just think about analyzing the bout and coaching their student, and the ref can be sure that they're making the best call possible. I did find that the monitor on the floor is a focal distance that I never use and that I had a very difficult time interpreting the information from there. I can probably practice this, though - put my computer on the ground and get myself in the habit of seeing that information.
Tags: reffing Add / Edit Tags
Categories
Uncategorized

Comments

  1. Dev's Avatar
    Qatet: I think you'll find that a few referees, when faced with left stopping and right attacking, simply signal "right attack." Then they explain to the incredulous fencer on the left that they stopped. Some will call "left's first attack no" (with the accompanying hand signal), though that's more common in sabre.
  2. catwood1's Avatar
    I generally go with the "Attack no, attack touche" or "Premier attack no, attack touche" with appropriate hand signals. Granted I ref a lot of sabre these days.
  3. qatet's Avatar
    Dev - I always figure that if I can make a pre-emptive action to avoid that moment when the fencer turns to me, mouth agape and gesticulating wildly, that I should do so. Better for the overall tenor of the bout. Because of that, I definitely want to acknowledge the stopped attack.

    I've had a bit of private and off-line feedback from this post, and the general consensus seems to be "attack no, attack arrives." I've been trying that out while reffing at practice and it feels right, so I'll be sticking with it until I get different feedback.
  4. RITFencing's Avatar
    One phrase that I make heavy use of is "in the final action."

    In the final action, right attack arrives.

    In the final action, right attack is no, left counter attack arrives.

    Etc.
  5. Allen Evans's Avatar
    As foil timing for the attack gets tighter and tighter, you're going to hear "Attack, no." more often, just as in saber. I've always done it, but I hear more referees using it these days.

    A
  6. catwood1's Avatar
    I know in the Vezzeli Errigo bout in the L4 from Paris this year, Vezzeli stops, Errigo starts, then Vezzeli finishes. I'm 99% sure the verbiage used was "Attack Premier no, attack touche."
  7. Craig's Avatar
    I agree on the practice of using "attack, no ; attack, touch". Seems more common and the fencers understand what it means. There is still some use of "in preparation" but it's a lot less. Those calls now are either the attack, no type of call or simply an attack with no mention of the prep.

    Happy to see things coming together for you on following more of the phrase.
  8. Allen Evans's Avatar
    I think that in the case described, it's a mistake to use "AIP" as a call, it's misleading to the fencer about why they lost the time. For me as a fencer, it's important for me to know whether the referee is seeing my action as one that starts out having time (and loses it) or never has time to begin with. Of course, Craig, you know this.

    For the same reason, I think "Attack, no" acknowleges that the fencer hit made an action that for some reason, lost time or ended. Again, as the calls get tighter, it's going to be important to "seperate" out the time -- at least for now.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30