Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Require competitors to take every attempt seriously #204

Closed
lgarron opened this issue Aug 22, 2014 · 4 comments
Closed

Require competitors to take every attempt seriously #204

lgarron opened this issue Aug 22, 2014 · 4 comments

Comments

@lgarron
Copy link
Member

lgarron commented Aug 22, 2014

Came up in the Delegate thread about FMC move limits (see #203).

We currently have:

A1c) A competitor participating in an event must be able to fulfill the event's requirements (e.g. know how to solve the puzzle). A competitor competing with expectation of a DNF result may be disqualified from the event, at the discretion of the WCA Delegate.

Given the discussion, it would be desirable for the Delegate to have a way to disqualify competitors if they are wasting competition resources (e.g. taking up timers/judges, causing FMC graders to spend more time), but without punishing competitors simply for being inexperienced.

Some Existing Suggestions

Form the Delegate list thread:

... intention of DNF, or deliberately not performing to the best of their abilities in good faith...

Or:

A competitor competing with expectation of a DNF result or intentionally poor result may be disqualified from the solve or the event, at the discretion of the WCA Delegate

Personally, I like the idea of "good faith", because it gets to the point. I have the feeling that "intentionally poor result" will result in more discussion about exactly how to interpret it. (What if a competitor finds a way to waste competition resources without getting something that is strictly a "poor result"?)

We need a much better phrase. I think most organizers aren't against fooling around per se, but something that tries to curb any such attempts that have an undesirable effect. The best notion I have right now is "wasting competition resources", but I think we can come up with something clearer. (The word "resources" is too vague for our audience.)

@lgarron lgarron changed the title Require Competitors to Take every Attempt Seriously Require competitors to take every attempt seriously Aug 22, 2014
@lgarron
Copy link
Member Author

lgarron commented Aug 22, 2014

Related: doing OH/BLD during speedsolves: https://groups.google.com/forum/#!topic/wca-delegates/YXNx-EOSpUc

@Laura-O
Copy link
Member

Laura-O commented Aug 22, 2014

In this context I want to suggest a clarification of

A3b1) When the judge believes the competitor is ready, he asks "READY?". The competitor must be ready to start the attempt within one minute of being called, else he forfeits his attempt (DNS), at the discretion of the judge.

Competitors sometimes interpret this as a minute to fool around and do unrelated things (e.g. talking into their camera) which just delay the attempt unnecessarily. It would be good to emphasize that this is meant as a timeframe to prepare for the attempt (find a good sitting position, concentrate, etc.).

@lgarron
Copy link
Member Author

lgarron commented Dec 10, 2014

In general, I think that we don't need mandate that competitors don't ever waste time/resources – i.e. we don't need to write our intentions into every relevant Regulation; we just need to give the Delegate the ability to enforce it when needed.

But I agree that any fix for this issue should make it clear that wasting time in A3b1 is covered; thanks for pointing it out.

@lgarron lgarron added this to the 2015 milestone Dec 19, 2014
@lgarron lgarron removed this from the 2015 milestone Jul 29, 2015
@Laura-O
Copy link
Member

Laura-O commented Mar 30, 2017

This was changed in 2015.

@Laura-O Laura-O closed this as completed Mar 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants