Tuesday, November 8, 2011

Terrible Tuesdays - Things I Hate About the Code




I don't miss the 10.0 scoring system... Okay, maybe I miss it a little bit, but for the most part, I like the D + E way to judge. However, there's no doubt that there are parts of the code that are causing the quality of gymnastics to decline.

Here are 3 things that I hate about the current code:

1. Vault scores are entirely too high. 

The highest score at the World Championships on Vault was a 16.033 (Maroney) while the highest floor score was only 15.133 (Afan). Thats a .9 difference! With vault and bars consistently scoring higher than beam and floor, the system really isn't fair to people like Aly Raisman whose strengths are on the lower scoring events. (Someone on the International Gymnast Forum pointed out Raisman in particular, but I can't remember who.)

 If I were rewriting the code, I might add an extra composition requirement on floor and maybe beam (adding .5 to most SVs) or I would devalue all of the Vault start values by .5.

2. A Hop up onto the beam is considered a "mount". 

There are forty five unique beam mounts in the current Code of Points. According to this report by FIG, 68% of gymnasts at 2010 Worlds used an A Mount. Yet, A skills only account for 17% of the mounts in the code. I'm not even against A Mounts, as long as they display something worthwhile. I personally think that a simple leap onto the beam is such a cop out. You're setting the stage for your whole routine! You think you'd want to do something that would impress people, rather than bore them to death.

Ideally, I wouldn't get rid of "A" Mounts, but I would eliminate mounts that don't require much skill, like the leap and hop.

3. People can cheat the Frontwards/Sidewards Requirement on floor. 

Come on, you're an Elite Athlete. You do FOUR tumbling passes and for some reason, you can fit a front layout into one of them? I HATE when gymnasts add an aerial or a side somi to fulfill the composition requirement on floor that says that each gymnast needs a backwards and a frontwards/sidewards element.

I would require that the backwards and frontwards/sidewards element be part of a tumbling pass and connected to other elements.



Those are my 3 biggest pet peeves with the code... for today. What do you dislike about the code?

No comments:

Post a Comment