-
Notifications
You must be signed in to change notification settings - Fork 11
Update cumulative cutoff rules #307
Comments
Friendly hint: There is no "cumulative cutoff", but a "cumulative time
|
Thanks @SAuroux. I keep forgetting that its a combined time limit, not a combined cutoff. Do you happen to know why that is? It seems simpler to me to think of this as a cutoff in a combined round, and then the regulations tweak wouldn't have needed to happen. |
Hm, I think I just disagree with you, since for me that is a clear type of Combined rounds need to be basedf on two WCA-official format, usually with 2016-04-17 4:18 GMT+02:00 Jeremy Fleischman [email protected]:
|
I understand how you think of combined rounds, but AFAIK, the regulations about combined rounds don't say that a combined is comprised of 2 phases, where each phase is a WCA-official format. See 9g, which just says there are two phases. I'd rather not get hung up on the semantics of what exactly the regulations currently say, though. From a data perspective, I don't like the new regulation clarification, because it won't be possible to tell if someone legitimately DNFed their solves, or just didn't get to do them because of a combined time limit. If we decided to clarify the regulations as you described them (the first phase of a combined round must be a valid wca format), then I think results team should be keeping track of what format the first phase of the round was. Right now, the database just says "this was a combined round", or "this was not a combined round". Changing that would be a lot of software work, though, and I believe a clean and simple solution would be to leave the leftover solves blank. Then someone looking at results gets a very clear visual indicator from the blank cells that this was a combined round, and they can even guess what the timelimit/cutoff/whatever you want to call it was. |
Under the new regulations, solves after not making the cumulative cutoff should be DNSs: https://github.com/cubing/wca-regulations/pull/353/files. Unfortunately, this is different than the handling of other cutoffs, where the remaining solves are just left blank.
The text was updated successfully, but these errors were encountered: