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

Extends A3d1 to "anywhere but the mat" #343

Closed
viroulep opened this issue Mar 7, 2016 · 11 comments
Closed

Extends A3d1 to "anywhere but the mat" #343

viroulep opened this issue Mar 7, 2016 · 11 comments

Comments

@viroulep
Copy link
Member

viroulep commented Mar 7, 2016

Right now A3d1 states :
A3d1) The puzzle must not rest on the timer. Penalty: time penalty (+2 seconds).

Following this thread : https://groups.google.com/forum/#!topic/wca-delegates/K0CBpf-wdTY, I believe we should extend this to handle the case where the competitor put the puzzle anywhere but on the mat (like in this video : https://youtu.be/7E6ZfCoYplA?t=163).

What do you think ?

@SAuroux
Copy link
Member

SAuroux commented Mar 7, 2016

But this is handled already by:

A3d) At the end of the inspection, the competitor places the puzzle on the mat, in any orientation.

What could be clarified however is, that the penalty also applies if the puzzle is put anywhere else.

@viroulep
Copy link
Member Author

viroulep commented Mar 7, 2016

I must have expressed myself poorly, your suggestion is exactly what I intended to suggest : literally changing "on the timer" to "anywhere but on the mat".

@Claster
Copy link
Contributor

Claster commented Mar 7, 2016

Do we want only to give +2 to such solves, or disqualify them completely?

@pedrosino
Copy link
Contributor

I believe DNFing is better.

@Laura-O
Copy link
Member

Laura-O commented Mar 8, 2016

For Clock a penalty is defined in F3). Although the main intention of this regulation is probably to penalize changing the pin positions, it also mentions that the puzzle has to be placed on the mat. Therefore, in Clock this would be a DNF:
F3) At the end of the inspection period, the competitor places the puzzle onto the mat in a standing position. The competitor must not change the positions of any pins from their scrambled positions before the beginning of the solve. Penalty: disqualification of the attempt (DNF).

@SAuroux
Copy link
Member

SAuroux commented Mar 8, 2016

Why is that? +2 is absolutely consistent with A3d1.

2016-03-08 12:27 GMT+01:00 Pedro Santos notifications@github.com:

I believe DNFing is better.


Reply to this email directly or view it on GitHub
#343 (comment)
.

@pedrosino
Copy link
Contributor

@Laura-O I didn't realise that part. It is weird that only clock has this "almost-well-defined" DNF and the other puzzles only have A3d1.
( @SAuroux maybe I subconciously knew this and wanted everything to be DNF)

@SAuroux
Copy link
Member

SAuroux commented Mar 8, 2016

Haha, Laura is techniocally correct, even though this certainly isn't the
intention of F3. The empesis here is on the standing position, not on the
mat.

2016-03-08 13:22 GMT+01:00 Pedro Santos notifications@github.com:

@Laura-O https://github.com/Laura-O I didn't realise that part. It is
weird that only clock has this "almost-well-defined" DNF and the other
puzzles only have A3d1.
( @SAuroux https://github.com/SAuroux maybe I subconciously knew this
and wanted everything to be DNF)


Reply to this email directly or view it on GitHub
#343 (comment)
.

@pedrosino
Copy link
Contributor

Indeed, I think the "correct" interpretation here is about the position and not moving any pins, but since it's all in the same sentence, the DNF applies if you didn't move any pins, set the clock in a standing position but not on the mat.
I guess this closes the case on the indian competition...

@Claster
Copy link
Contributor

Claster commented Mar 8, 2016

+2 will lead to a simpler rule: you won't need to memorize different levels, like, if a puzzle is here, it is DNF, if a puzzle is there, it is +2.
Though I would prefer DNF as a more stricter rule :-P

Claster added a commit that referenced this issue Mar 22, 2016
Claster added a commit that referenced this issue Mar 28, 2016
@Laura-O
Copy link
Member

Laura-O commented Mar 31, 2016

Fixed in #347

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

No branches or pull requests

5 participants