Wanted to start this thread so we can have a place to organize entries for Team Cup 2017 over at hwbot.org. The main competition is broken up into 4 sub-competitions with each sub having multiple stages. All stages require multiple entries but only one submission per competitor is allowed for each stage (so if you have a socket 1171 motherboard and you happen to have an i5 and an i7 you can't submit two entries - only one submission per stage).
This is a big event that will require team work. Should be fun!
This competition is going to be great as well - I hope the ASUS Republic of Gamers team is going to do well! To help out a bit I listed below the different benchmarks / restrictions for each of the 4 sub competitions and stages. Quite a lot to do! I wish good luck to the team.
You have until September 30th to submit your scores. Please click on the Stage to see more restrictions detail and download the latest version of the benchmarks.
Stage6 - X265 1080P -> 3 submissions with 3 different Haswell Movibe CPUs -> Mobile Celeron (Haswell), Mobile Pentium (Haswell), Core i3 Mobile (Haswell), Core i5 Mobile (Haswell), Core i7 Mobile (Haswell) processor
Stage2 - 3DMark03 -> 1 submission with HD 3000 series GPUs -> Only 1 GPU -> Only use Socket AM2 processor
Stage3 - Cinebench R11.5 -> 3 submissions with 3 different Sandy Bridge Mobile processors -> Mobile Celeron (Sandy Bridge), Mobile Pentium (Sandy Bridge), Core i3 Mobile (Sandy Bridge), Core i5 Mobile (Sandy Bridge), Core i7 Mobile (Sandy Bridge) processor
Stage4 - Fire Strike -> 1 submission with a GeForce 400 series GPU -> Only 1 GPU -> Only use socket LGA2011 processors
Stage5 - 3DMark Vantage -> 2 submissions with 2 different HD 6000 series GPUs -> Only 1 GPU -> Only use LGA 1155 processors
Also, I think for right now we should just go ahead and do as many as we can from whoever is qualified to do any of the stages - especially some of the more obscure ones. As we fill in each stage we can then start to figure out our strategy - although I'm not if some of these stages has the score based on the top 1 - 5 submissions or if it applies to the first 1 - 5 in order of submission... not sure I'm explaining what I mean but does it make sense?
The number of submissions are taken from highest scores, complicated by consideration of only one submission per hardware model and one submission per competitor.
Say I submit two GPUPI scores with a GTX 1080 and one with a GTX 1060 (which I am very likely to do.) Also say ttOne submits one with a GTX1080 ti. One of my 1080 scores will be higher that the other and higher than the 1060 score. The higher 1080 score will count regardless of which was submitted first. The other can't count because there is a higher 1080 score. The 1080ti score will surely be higher than the 1080, but both count because those are different GPU models and were submitted by different competitors. The 1060 score will not count because I already count the 1080. When someone beats my 1080 score, the 1060 score could count if it is the team's top 1060 score and in the team's top five scores for the stage. None of that has anything to do with the order of submissions as long as they are in before the contest closes.
All this selecting of higher scores, one representative of a hardware model and one submission per competitor is done by HWBOT programming as the scores are submitted.
The stages I can do: XTU 5GHz with 6700K, 7700K andd7350K -- M9A HWBOT Prime with 4970K, 4770K and G3258 -- M6E GPUPI 32B with GTX 1080 and GTX 1060 -- M9A? 3DMark Vantage with GTX 980 -- R5E10 Memory Frequency with DDR4 and DDR3 -- M9A and M6E 3DMark11 Physics with 5820K (Haswell, not Broadwell) -- R5E10 GPUPI for CPU 100m with 6950X and 5820K -- R5E10 Geekbench3 with 4970K, 4770K and G3258 -- M6E
I can submit more than once in many of these stages, but only one will count. That's one reason I'm glad this is a team contest. The other is that I can't cover even half of the stages. It'll be fun watching teammates come up with scores for stages I can't touch.
Thanks for the explanation, Jab. I just wanted to make sure that someone couldn't submit an entry and lock us into a situation where a better score couldn't be submitted but I see now that is not the case.