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

A6e: Explicitly reference A7a to make it clear what counts as inspected. #385

Closed
wants to merge 1 commit into from

Conversation

lgarron
Copy link
Member

@lgarron lgarron commented Sep 28, 2016

I have a long-standing personal note that I just came across to clarify A6e a bit.

In the real world, applications of A7e are somewhat fuzzy, so I think it's worth stating exactly what counts as "inspected".

@HippolyteM
Copy link

Hi,
Maybe the regulations should clearly specify what is already done most of the time (when cases are tricky), and choose a word, as "ok", which would be part of the judging routine and that the judge should always say before the competitor touch his cube.

@lgarron
Copy link
Member Author

lgarron commented Oct 2, 2016

Maybe the regulations should clearly specify what is already done most of the time (when cases are tricky), and choose a word, as "ok", which would be part of the judging routine and that the judge should always say before the competitor touch his cube.

They do. ;-)

In fact, that's exactly what A7a says:

  • A7a) The judge tells the competitor the result.
    • A7a1) If the judge finds that the puzzle is solved, they call "OKAY".
    • A7a2) If the judge assigns any penalties, they call "PENALTY".
    • A7a3) If the result is DNF, the judge calls "DNF".

I don't know if I used to do this consistently, but I noticed that Olivér does this very well, and make sure to do it every time now.
I think it's a small but important detail. We should include it in guides (#236), although perhaps we don't need to call too much attention to it.

@lgarron lgarron mentioned this pull request Oct 2, 2016
@Laura-O
Copy link
Member

Laura-O commented Oct 4, 2016

Same here. I used to make this calls very inconsistently in the past, but started to do it consistently about 1.5 years ago. Competitors here are definitely not used to these calls. I remember a few situations when competitors asked me something like "What do you mean?" when I said "OK". 😛

This is not relevant for this pull request, but related: I just noticed that the word "result" in A7a) might be not well-chosen. Someone correct me if I miss something, but according to the regulations a result can be the original recorded time, the recorded time with penalties, "DNF" and "DNS".
A7a) suggests that the calls are also a result. I do not have a good suggestion how to replace it, maybe "outcome"? Or "judgement"?

@HippolyteM
Copy link

I am ashamed, I didn't remember that we already had an exact wording.:/
Then, what about adding to A7a : "After the judge's call, and if the competitor agree with it, the puzzle is considered inspected."
And A6e could refer to this rule. (Even if, I agree, it would be better to find a way to define "inspected" before its first use.

As for Laura's question, I also think there is something to add, as it is not clear what we exactly want the judge to tell. According to (A7a to A7c), it is indeed the judgment, but then there is no need for the judge to tell the actual time (recorded time if okay, recorded time plus penalties if needed), which is quite important, I think we all agree on that.
Here is a suggestion:
A7a) The judge tells the competitor their judgment:
A7a1) If the judge finds that the puzzle is solved, they call "OKAY".
A7a2) If the judge assigns any penalties, they call "PENALTY".
A7a3) If the result is DNF, the judge calls "DNF".
A7b) The judge tells the competitor the final time. They specify the time displayed on the timer, the exact penalties, and the final score.
(or more simple:
A7b) The judge tell the competitor exactly what he will write on the score sheet)

Hippolyte

@AlbertoPdRF AlbertoPdRF changed the base branch from draft to Fixes-2017 October 29, 2017 17:17
@Laura-O
Copy link
Member

Laura-O commented Oct 30, 2017

I just discussed this with @AlbertoPdRF and we both think that this is a good idea, but it will not work in competitions.

Even when judges are taught to say the result after an attempt, this is still done very inconsistently. I also think competitors are used to this today. Therefore, if we add this regulation and apply it in a strict way, we would see a lot of DNFs.

We can continue to discuss this, but I am closing this for now as there hasn't been any activity since more than a year here.

@Laura-O Laura-O closed this Oct 30, 2017
@AlbertoPdRF AlbertoPdRF deleted the A6e-touch-clarification branch October 30, 2017 18:55
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

Successfully merging this pull request may close these issues.

None yet

3 participants