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

Publishing FMC Solutions #125

Closed
lgarron opened this issue Dec 26, 2013 · 11 comments
Closed

Publishing FMC Solutions #125

lgarron opened this issue Dec 26, 2013 · 11 comments

Comments

@lgarron
Copy link
Member

@lgarron lgarron commented Dec 26, 2013

Competition organizers usually don't look at FMC solutions too much because it takes a lot of time -- they're just glad to have scored them once.

I still have physical FMC solutions from past US Nationals that I intended to type up and publish -- but I've been partly concerned that some competitors have an expectation of privacy in their solution. Considering that cubing is traditionally an open sport (e.g. the community is very collaborative, and filming official solves of fast cubers to learn from/reconstruct is popular), I think it would be awesome if FMC results were public data, possibly even part of the result (i.e. available on the results site). However, for now it would help to make explicit that the organizer has the right to publish an FMC solution.

(Do we have a precedent where a competition organizer published a solution after a record was set, instead of the competitor reporting it? After SF09, I put up results here but I don't know how many people have seen that.)

If we had a good mechanism, digital scoring might actually be faster than turning physical cubes (and give us data as a byproduct). The current FMC sheets came out of my attempts to make this happen, going back to 2009:

I still think digital FMC scoring is worth pursuing, but I've had other things to worry about.

@iVinshe

This comment has been minimized.

Copy link
Contributor

@iVinshe iVinshe commented Dec 26, 2013

Easier to err on the side of privacy. Would it be simple to add a simple
opt-in check box for this?

On Wed, Dec 25, 2013 at 5:58 PM, Lucas Garron notifications@github.comwrote:

Competition organizers usually don't look at FMC results too much because
it takes a lot of time -- they're just glad to have scored them once.

I still have physical score sheets from past US Nationals that I intended
to type up and publish -- but I've been partly concerned that some
competitors have an expectation of privacy in their solution. Considering
that cubing is traditionally an open sport (e.g. the community is very
collaborative, and filming official solves of fast cubers to learn
from/reconstruct is popular), I think it would be awesome if FMC results
were public data, possibly even on the results pages. However, it would be
nice if it were at least explicit that the organizer has the right to
publish an FMC solution.

(Do we have a precedent where a competition organizer published a solution
after a record was set, instead of the competitor reporting it?)

If we had a good mechanism, digital scoring might actually be faster than
turning physical cubes. The current FMC sheets came out of my attempts to
make this happen, going back to 2009:

I still think it's something worth pursuing, but I've had other things to
worry about.


Reply to this email directly or view it on GitHubhttps://github.com//issues/125
.

@lgarron

This comment has been minimized.

Copy link
Member Author

@lgarron lgarron commented Dec 26, 2013

You mean, on the FMC sheet? I think case-by-case is rather messy; one simple rule would be preferable. (Like the clear choices of "gender public" and "age private".)

I don't think anyone should have an expectation of privacy for an FMC solution, I was mainly concerned that some might have.

@lgarron

This comment has been minimized.

Copy link
Member Author

@lgarron lgarron commented Dec 6, 2018

From #660

I'd like to support better FMC grading software, including software that allows uploading solutions for computer grading or assistance from people who are not the competition (thus freeing competition staff). This allows for easier competition logistics, provides a better record for accountability, and supports the open, constructive nature of the cubing community. (If I understand correctly, practically all top competitors freely share their official solutions and approaches.)

To this end, I'd like us to clarify that FMC solutions are not secret.

@Berkmann18

This comment has been minimized.

Copy link

@Berkmann18 Berkmann18 commented Dec 6, 2018

It's definitely a good idea whether the workings behind a solution or not are published alongside said solution.
I doubt anyone wouldn't want their final solution to go public when (I'm sure) a fair amount of FMCers would learn from it, or simply want to see what a person did on a certain scramble.

@ColorfulPockets

This comment has been minimized.

Copy link

@ColorfulPockets ColorfulPockets commented Dec 6, 2018

I 100% support that the solutions should be public. Competitors are already required to explain a solution if asked, right? So if they were private, the only people who could learn their secret techniques would be people like delegates.

Obviously that’s a ridiculous thing to actually happen, but in principle I think they need to be public

@lgarron lgarron changed the title FMC Solutions: Private or Public? Publishing FMC Solutions Dec 10, 2018
@lgarron

This comment has been minimized.

Copy link
Member Author

@lgarron lgarron commented Jul 18, 2019

I would like to consider this change for 2020.

  1. The cubing community has so far been fairly open about our techniques. I'd like to encourage that by allowing everyone to learn from official solutions.
  2. It allows better accountability. If someone cheating, the public information may help detect a pattern.
  3. I'm interested in resuming a project to make it easy to grade FMC by taking pictures and transcribing them on a computer. This could be faster and more reliable than normal solution checking. Making solutions public allows volunteers from around the world help grade solutions at a given competition, potentially freeing up the organizer's resources. (Note: this still requires great care to protect the scramble before the attempt is finished.)
  • If someone receives a DNF they did not expect, a picture and transcription gives them a paper trail for what happened.
@lgarron lgarron added this to Big Ideas in [moved] Jul 18, 2019
@ColorfulPockets

This comment has been minimized.

Copy link

@ColorfulPockets ColorfulPockets commented Jul 19, 2019

A project to make it easy to transcribe? How does that work?

@maconard

This comment has been minimized.

Copy link

@maconard maconard commented Jul 19, 2019

Vision recognition and potentially AI, I would assume. I've made an AI project that could read human handwriting and transcribe it (just for Arabic numerals), but regardless of how well done it is it will never be quite perfect.

If the idea is to take 3 seconds to snap a picture and have most if not all of the solution transcribed with parts marked that it couldn't figure out (such as where the competitor scratched out a move slot and skipped it or the handwriting was drastically different from standard) and need human review, I would think that's fairly do-able. It could even check the result if it's given the scramble before a grading session.

However if the tool isn't done really well or has lots of errors, I could see it slowing down or making little to no improvement on the grading process time commitment.

@lgarron

This comment has been minimized.

Copy link
Member Author

@lgarron lgarron commented Jul 19, 2019

A project to make it easy to transcribe? How does that work?
Vision recognition and potentially AI, I would assume.

No AI!

I originally designed the FMC sheet make it easy to isolate letters for human transcription.
See https://www.speedsolving.com/threads/fcf-and-fmctyper.8090/#post-113677 for a program I wrote in 2008(!) to do this. I've learned a lot over the last 11 years, and I want to find a way to wrap up the project.

@Ivan-Brigidano

This comment has been minimized.

Copy link
Member

@Ivan-Brigidano Ivan-Brigidano commented Aug 23, 2019

I think this will be perfectly doable if the future WCA Live includes the software needed for checking and saving the solutions

@pokekrom

This comment has been minimized.

Copy link

@pokekrom pokekrom commented Aug 24, 2019

What about a Bluetooth cube? You can scramble the cube and perform the solution and you didn't have to type it yourself, just check that the solution actually works.

@lgarron lgarron moved this from Major Ideas to Minor Ideas in Regulations 2020 – Priorities Aug 30, 2019
hanwu85 added a commit that referenced this issue Oct 10, 2019
Addressing issue #125
lgarron added a commit that referenced this issue Nov 30, 2019
* Allow FMC solutions to be published

Addressing issue #125

* Update wca-regulations.md
lgarron added a commit that referenced this issue Dec 31, 2019
* Improve wording for E2c1++ and E2c1++++. Closes #727.

* Fix typo in 9g.

Thanks to Brandon Harnish for finding!

* Fix typo: aleready → already

Thanks to Wilson Alvis for spotting this!

* Update `wca-states.md`. (#747)

- Update names:
  - Macedonia → North Macedonia
  - Swaziland → Eswatini
- Fix sorting order.

* Update a few Regs to correctly refer to "solve" instead of "attempt".

Thanks to Manu Vereecken for spotting these.

* Solve instead of attempt

* Fix weird sentence

* Improve the wording of 4b3.

Suggested by Gregor Grigorjan.

4b3b to 4b3d are still a tad ambiguous, but I think it's better to keep them concise instead of 100% clear.

* Add credit section on `wca-states.md`.

* List Armenia under Europe instead of Asia. (#773)

Fixes #772.

* Remove ambiguousness from A3b1

* List project boards

* Review

* Remove references to 1c3a

* Clarify C1b

Clarifying the use of surface during one handed solve.
Issue[#718](<#718>)

* Clarify camera display

Addressing issue #721

* Update wca-guidelines.md

* Update wca-regulations.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Update wca-regulations.md

* Update wca-regulations.md

* Update wca-guidelines.md

* 6a+ fix

There is no sense of calling it a ADDITION as it doesn't refer to a regulation.

* Update wca-regulations.md

* Update README.md

* Update wca-regulations.md

* Update wca-guidelines.md

* Update wca-regulations.md

* Update wca-guidelines.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Update wca-regulations.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Update wca-regulations.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* Typo fixing

* Update README.md

* Update README.md

* Update title and introductory sentence in the `README.md`

The old intro sentence was more of a subtitle/noun fragment. This changes it into a full sentence.

* Update README.md

* Minutes Log inclusion on the README

* Update README.md

* Update README.md

* States.md punctuation fix

#774

* Update Minute log link and show it as code

* Minutes log link fix

* Update README.md

* E2c2++ WCA Delegate fixing

Thanks @hanwu85 for finding this!

* Rename "opaque object" for BLD to "sight blocker" (#864)

* Allow FMC solutions to be published (#852)

* Allow FMC solutions to be published

Addressing issue #125

* Update wca-regulations.md

* Extra attempt reason recording (#849)

* Extra attempt reason recording

* Update wca-guidelines.md

* Update wca-guidelines.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* E4: Update "WCA" in "WCA Delegate" to match document style.

* Require scramblers signatures (#854)

* Require scramblers signatures

* Update wca-regulations.md

* Update wca-regulations.md

* Update wca-regulations.md

* Update wca-regulations.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Clarify how to handle missing scramble signatures. (#883)

* Clarify how to handle missing scramble signatures.

* Update wca-guidelines.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* Turn A1c into 2j3 (#868)

* Turn A1c into 2j3

Addressing Issue #867. This way the regulation affects all events and not only speed solving events.

* Update wca-regulations.md

* Update wca-guidelines.md

* Restore A1c

* Update A6c from judge discretion to Delegate (#885)

* Allow clock pins to be distinguishable (#838)

* Allow clock pins to be distinguishable

Addressing issue  #759

* Update wca-guidelines.md

* Update wca-guidelines.md

* Update wca-guidelines.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* Update A6e to Delegate discretion (#886)

* Update A6e to Delegate discretion

Addressing [this incident](https://www.worldcubeassociation.org/incidents/23)

* Update wca-regulations.md

* Update gramma in 2k3 and 2k4 so that it's easier to read. (#734)

* Allow to re-scramble duplicate cubes at MBLD (#887)

* Allow to re-scramble duplicate cubes at MBLD

* Update wca-guidelines.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* O-rings recommendations movement from Guidelines to Regulations (#855)

* Update wca-guidelines.md

* Update wca-regulations.md

* Update wca-regulations.md

* Update wca-regulations.md

* Update wca-regulations.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Clarification for non-electric aids during FMC. (#839)

* Allow clock pins to be distinguishable

Addressing issue  #759

* Clarification for non-electric aids during FMC.

Addressing issue #815

* Update wca-regulations.md

* Update wca-guidelines.md

* 3h2a exception clarification (#832)

* 3h2a exception clarification

See Issue #826

* Update wca-regulations.md

* Update wca-regulations.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Specify that clock stands are allowed. (#890)

* Specify that clock stands are allowed.

* Update wca-regulations.md

* Update wca-regulations.md

* Minor changes to the README (#893)

* Remove a remaining "Rubik's" from the Style Guide (#892)

* README/style guide changes from the latter half of 2019.

* Change "combined rounds" to "cutoff rounds". Closes #543. (#889)

* Correct H1+ wording (#891)

* Correct H1+ wording

Thanks @Goosly for spotting it!

* Update wca-guidelines.md

* Update wca-guidelines.md

Co-Authored-By: Lucas Garron <lgarron@worldcubeassociation.org>

* Remove bracket rotations in favor of <x, y, z>. Addresses #757. (#888)

* Only allow <x, y, z> rotations. Addresses #757.

Based on feedback, removing more than this may be beneficial, but some competitors strongly prefer to keep them. However, reducing to a single rotation sytem is generally supported, and the community prefers <x, y, z> over bracket rotations.

* Update wca-regulations.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* Update wca-regulations.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* Update wca-regulations.md

Co-Authored-By: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>

* Update wca-regulations.md

* Update wca-guidelines.md

* Update wca-guidelines.md

Co-Authored-By: Han Wu <3752812+hanwu85@users.noreply.github.com>

* Revert A6c/A6e to judge's discretion. (#897)

* Revert "Update A6c from judge discretion to Delegate (#885)"

This reverts commit da52628.

* Revert "Update A6e to Delegate discretion (#886)"

This reverts commit 4c5d528.

* Improve H1+ wording (#908)

* Improve 2i2a+ wording (#909)

* Remove official status for 3x3x3 with Feet. (#912)

* Move 2j3 changes to 2k6 (#928)

* Update wca-regulations.md

* Update wca-guidelines.md

* Update wca-regulations.md

* Update wca-regulations.md

* Clarify how to handle missing scramble signatures. (#936)

* Clarify how to handle missing scramble signatures.

* Move phrase into paren to make it clear that it refers specifically to the reason.

* Update wca-guidelines.md

* Update wca-guidelines.md

* Update date for the 2020-01-01 release. (#939)

Co-authored-by: Manu Vereecken <manu.vereecken@hotmail.com>
Co-authored-by: Alberto Pérez de Rada Fiol <apdrf.94@gmail.com>
Co-authored-by: Kotaro Terada <kotarot@apache.org>
Co-authored-by: Han Wu <3752812+hanwu85@users.noreply.github.com>
Co-authored-by: Iván Brigidano Pérez <47502355+Ivan-Brigidano@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
7 participants
You can’t perform that action at this time.