And the new 3x3x3 SINGLE WR is...

Status
Not open for further replies.
We should contact the contestant. He/she might be able to say whether it should be 6.21 or 1:06.21. If he/she says 1:06.21, then the case is closed (except for the cleanup I just mentioned in my previous post). By the way, we should not assume it was a mistake just because it seems so unlikely. Maybe the contestant was given a bad/simple scramble instead of the intended scramble... or some odd thing happened that we are unable to imagine.
 
We should contact the contestant. He/she might be able to say whether it should be 6.21 or 1:06.21. If he/she says 1:06.21, then the case is closed (except for the cleanup I just mentioned in my previous post). By the way, we should not assume it was a mistake just because it seems so unlikely. Maybe the contestant was given a bad/simple scramble instead of the intended scramble... or some odd thing happened that we are unable to imagine.
I'm pretty sure people would notice a 6.21 within a second of someone achieving it.
 
I actually have the PDFs of results (from before they were entered into the database) and the 6.21 is there too. So the mistake was made at the competition, not by the person who uploaded the results.

You will have to show me who said the error was done by the person uploading them. In fact, i stated the error occurred in the file. But great detective work, nonetheless.

rjohnson_8ball, i get the impression you really don't know how the whole process works, so perhaps you should refrain from giving directives on what to do to resolve the issue.

Bob inputted the data last night, i woke up today and found out about the errors on my way to work. I am home now, and will now work to find the correct data and give it to Bob, so he can make the correction. There will be a lapse in time before all is right in the world. Brace yourselves in the meantime.
 
Since most people will check this thread in regards to this issue, I wanted to post something for all to read.

canadianCUBING has now organized and executed 12 competitions in Canada, and one in the US. We have a pretty good track record over those competitions. Unfortunately, this last competition had erroneous data submitted, which cause quite the stir in the community as seen above. Some errors during data entry are fairly common, but this one had a bigger consequence than most.

It was ultimately my responsibility to ensure the data was correct before sending it to the WCA. I am not going make excuses, as there are none. I did my best to proof the document, but I did not catch all the errors. The correct time for the solve in question was 67.21; the difference was the missing digit of 7. The nature of the small error had a large impact.

So having said all of that, I would like to take this opportunity to apologize to the entire cubing community for this error and confusion it has caused. We will spend more time going over the results in the future. Thanks.
 
Dave. It's honestly not that big of a deal. It's like when the 'youngest cuber' on the WCA turns out to be 5 days old. Cubers know that it's too farfetched to be true, so it ultimately becomes a laughing matter.

I understand the fact that you'd like as little error as possible, but the fact of the matter is that people make mistakes. In fact, "Pennsylvania" was spelled wrongly on the Constitution, and I really don't think that really changed much.
 
Next time you guys complain about results not being ready and up on the WCA site by Sunday morning, especially when the delegate may be traveling back that day, we'll go ahead and point to this thread.
 
Dave. It's honestly not that big of a deal. It's like when the 'youngest cuber' on the WCA turns out to be 5 days old. Cubers should*know that it's too farfetched to be true, so it ultimately becomes a laughing matter.

People overreacted immensely towards this... Any with a brain would've known it was a clerical error, and that the issue would be resolved eventually. People have other things to do than check every single result thats inputted. The error was caught, and it was fixed, no harm done. Next time, have a little patience for obvious errors, instead of being irrational and assuming things that are obviously not true.
 
Dave. It's honestly not that big of a deal. It's like when the 'youngest cuber' on the WCA turns out to be 5 days old. Cubers should*know that it's too farfetched to be true, so it ultimately becomes a laughing matter.

People overreacted immensely towards this... Any with a brain would've known it was a clerical error, and that the issue would be resolved eventually. People have other things to do than check every single result thats inputted. The error was caught, and it was fixed, no harm done. Next time, have a little patience for obvious errors, instead of being irrational and assuming things that are obviously not true.

Agreed. It's silly to expect there not to be any errors, and any cuber that thought about it could easily see that this was just a typo. People need to be somewhat judicious with what they believe. When I was put down as the 6th youngest blindfold cuber I didn't believe I was instantly 10 years younger than I actually am just because the database said so. Think, people.

@Stachu- It wasn't spelled incorrectly, there was just not an accepted single way to spell it at the time. It's written that way on the Liberty Bell, too.
 
I'm not sure how anyone seemed to take this seriously or overreact, well... I didn't at least.

This thread was simply poking fun at how this specific and obviously untrue error would cause chaos if it were true... or something like that.
 
I noticed it when I uploaded the results and checked to see if any regional records were broken. I emailed Dave at night and didn't get to check for a response until I was at work. Hence, it stayed this way for a little bit. Oh well.
 
Status
Not open for further replies.
Back
Top