PageRenderTime 51ms CodeModel.GetById 20ms RepoModel.GetById 0ms app.codeStats 0ms

/proco/info.html

https://github.com/StanfordACM/stanfordacm.github.com
HTML | 158 lines | 146 code | 1 blank | 11 comment | 0 complexity | 86b1056beb206e2b1343785d17653e5b MD5 | raw file
  1. ---
  2. title: ProCo Information
  3. layout: default
  4. custom_css: proco
  5. ---
  6. <section>
  7. <h1>ProCo Information</h1>
  8. <h3>Team Registration</h3>
  9. <!-- <p>Registration is now open, and can be completed <a href="https://forms.gle/SEYFSJBdU4HwMYcN9">at this form</a>.</p> -->
  10. <p>Due to the online nature of the contest, Stanford requires a maximum of 300 participants. Thus, slots to participate are awarded on a first come first serve basis. International students are welcome but are not eligible for swag.</p>
  11. <p><strong>The contest will happen on March 5, 2022. Registration has closed.</strong></p>
  12. <p>Once you submit your registration form, we will send out a confirmation email saying if you were accepted or not to participate.</p>
  13. <p>Teams can have between one and three students. Students on a team do not need to be in the same grade, or have the same level of programming experience.</p>
  14. <p>If we reach our participation cap, any remaining teams will be placed on a wait list, and they will be notified as soon as possible if spots become available. Once you submit your registration form, you will not be allowed to replace team members, only drop them if they are unable to attend.</p>
  15. <p>We will finalize the roster exactly one week before the contest on February 26, 2022.</p>
  16. <h3>Divisions</h3>
  17. <p>There are two different divisions in the competition: Novice and Advanced. A team may compete in the Novice division only if all members have less than two years of programming experience. If a team member has competed in ProCo or some equivalent contest before, they should compete in the Advanced division. Teams with participants who are at the Silver or higher level of USACO, should compete in the Advanced division.</p>
  18. <p>If eligible for either division, teams may choose compete in the Advanced division. One incentive for doing so, is better prizes.</p>
  19. <p>The ProCo staff has the right to disqualify any team that does not follow these rules of division assignment. If you are unsure what division to compete in, please reach out to the ProCo staff at <a href="mailto:procostaff2022@gmail.com">procostaff2022@gmail.com</a>.</p>
  20. <h3>Laptops and Equipment</h3>
  21. <p>Each team member will be responsible for using their own computer and WiFi to compete in the contest. Communication among team members can be facilitated in any fashion.</p>
  22. <h3>Prizes</h3>
  23. <p>Cool prizes will be awarded to the highest-scoring teams and vary year to year. Previous first place prizes have included Raspberry Pis, iPad Minis and Nintendo 3DSes. This year, our prizes are sponsored by Citadel Securities, and Amber by LatticeWork.</p>
  24. <h1>Rules</h1>
  25. <h3>Access and Communication</h3>
  26. <ul>
  27. <li>Each team is allowed to use up to three laptops with Internet access.</li>
  28. <li>The use of the internet is allowed to access free resources. Sentient help is strictly prohibited.</li>
  29. <li>External communication is prohibited.</li>
  30. <li>The only programs allowed are IDE, editors, web browsers, and programming tools. The use of all other programs are prohibited.</li>
  31. </ul>
  32. <h3>Input and Output</h3>
  33. <ul>
  34. <li>All input will be received from console input (System.in in Java, cin in C++, stdin in C, sys.stdin in
  35. Python 2.7).</li>
  36. <li>All output should be sent to console output (System.out in Java, cout in C++, stdout in C, sys.stdout in
  37. Python 2.7).</li>
  38. <li>Each program will specify its own output format. Format all output as closely as possible to the
  39. specifications. This includes spacing, capitalization, and punctuation. See below for examples for input and
  40. output.<ul>
  41. <li>Java
  42. <img alt="Java IO" src="java-io.png" />
  43. </li>
  44. <li>C++
  45. <img alt="C++ IO" src="cpp-io.png" />
  46. </li>
  47. <li>C
  48. <img alt="C IO" src="c-io.png" />
  49. </li>
  50. <li>Python 2.7
  51. <img alt="Python 2.7 IO" src="python2.7-io.png" />
  52. </li>
  53. </ul>
  54. </li>
  55. </ul>
  56. <h3>Submissions</h3>
  57. <ul>
  58. <li>We will be accepting submissions in C, C++, Java, Python 2.7, and Python 3.6.</li>
  59. <li>Solutions will be graded using GNU C++11, Java 1.8.0, Python 2.7, and Python 3.6 on Linux machines.</li>
  60. <li>All files must be named in the format specified on your problem statement. File extensions must be the
  61. following:<ul>
  62. <li>C: problem.c</li>
  63. <li>C++: problem.cc or problem.cpp</li>
  64. <li>Java: problem.java</li>
  65. <li>Python: problem.py</li>
  66. </ul>
  67. </li>
  68. <li>Java submissions must follow these rules:<ul>
  69. <li>Name of the main class should be the task name.</li>
  70. <li>All classes should be in one file.</li>
  71. <li>Don't include a package statement.</li>
  72. <li>Avoid using scanner for efficiency.</li>
  73. </ul>
  74. </li>
  75. <li>You will be submitting your (single) code file to us using a web interface. If you are using Java and want
  76. to create multiple classes, put all of the class declarations into one file.</li>
  77. </ul>
  78. <h3>Contest Format</h3>
  79. <p>ProCo will consist of 9 - 15 unweighted problems and will last for 3 hours.</p>
  80. <p>Submissions will be run on a set of test cases which are not revealed to the teams during the contest, and they are accepted as correct if they pass on all of the test cases. Teams will be notified whether their submission is correct within about a minute. If the submission is correct, no further points can be awarded for the problem. If the submission is not accepted, teams are free to resubmit the problem. There is no limit on the number of submissions per problem.</p>
  81. <p>The submissions from a team do not all need to be in the same language. For example, the same team could solve novA in C, novD in Java, and novF in C++.</p>
  82. <h3>Contest Platform</h3>
  83. <p>This year, ProCo will be using Codeforces to host the contest. Unlike last year, some preparation will be required from participants. Participants must create a Codeforces account before filling out the registration form, and include their username in the form.</p>
  84. <p>They will also have to create their team on Codeforces, and report their team ID upon check-in the day of the contest. Stay tuned for more instructions on how to do this. After registration closes, ProCo staff members will also be able to help students do this on the day of the contest. Furthermore, we will host office hours to help students with doing this ahead of time.</p>
  85. <h3>Scoring</h3>
  86. <p>Teams are ranked according to the most problems solved. Teams who solve the same number of problems will be ranked in accordance with ICPC style penalty points. The team with the lowest number of penalty points wins the tiebreaker. The rules for assigning penalty points are below:</p>
  87. <ul>
  88. <li>For every minute it takes to solve a problem, 1 penalty point is given upon successful completion of that problem. For example, if a team solves problem C at minute 11, they will receive 11 penalty points. If the same team then solves problem F at minute 35, they will receive 35 penalty points for that problem, and have a cumulative penalty of 46 points. Thus, their score is 2 problems, and 46 penalty points.</li>
  89. <li>Furthermore, for every incorrect submission, 20 penalty points are assigned. However, these points are only tabulated upon successful completion of this problem. Thus, if a team submits to a problem 5 times, but never solves that problem, their total penalty points will not increase. However, if a team submitted 5 times incorrectly, and then solved the problem on the 6th attempt, they would receive 5 * 20 = 100 additional penalty points for incorrect submissions in addition to the time it took for them to solve it.</li>
  90. </ul>
  91. <h1>Schedule</h1>
  92. <!-- <p>ProCo 2021 will be held in the <a
  93. href="https://www.google.com/maps/place/William+R.+Hewlett+Teaching+Center,+370+Serra+Mall,+Stanford,+CA+94305/data=!4m2!3m1!1s0x808fbb2ae177cc91:0x5351ffed56456da8?sa=X&amp;ved=0ahUKEwjKs9Lmh9LTAhVHslQKHSXpAmkQ8gEILDAB">William
  94. R. Hewlett Teaching Center</a>, located at 370 Serra Mall Stanford, CA 94305.</p> -->
  95. <p>Below is the tentative schedule of events for March 5th. All times are in PT</p>
  96. <table class="table" style="width: 100%; text-align: center; margin: 20px;">
  97. <thead>
  98. <tr>
  99. <th>Event</th>
  100. <th>Time</th>
  101. <!-- <th>Location</th> -->
  102. </tr>
  103. </thead>
  104. <tbody>
  105. <tr>
  106. <td>Registration/Check-in</td>
  107. <td>9:00 AM - 10:00 AM</td>
  108. <!-- <td>Outside Hewlett Teaching Center</td> -->
  109. </tr>
  110. <tr>
  111. <td>Opening Assembly</td>
  112. <td>10:00 AM - 10:45 AM</td>
  113. <!-- <td>Hewlett 200</td> -->
  114. </tr>
  115. <tr>
  116. <td>Practice Contest</td>
  117. <td>10:45 AM -11:15 AM</td>
  118. <!-- <td>Hewlett 200</td> -->
  119. </tr>
  120. <tr>
  121. <td>Contest</td>
  122. <td>12:00 PM - 3:00 PM</td>
  123. <!-- <td>Outside Hewlett Teaching Center</td> -->
  124. </tr>
  125. <tr>
  126. <td>Sponsor Workshop</td>
  127. <td>3:15 PM - 4:00 PM</td>
  128. <!-- <td>Hewlett 200</td> -->
  129. </tr>
  130. <tr>
  131. <td>Awards/Solutions</td>
  132. <td>4:00 PM - 5:30 PM</td>
  133. <!-- <td>Hewlett 200</td> -->
  134. </tr>
  135. </tbody>
  136. </table>
  137. <h1>Past Contests</h1>
  138. <p>Past contest results and problems can be found <a href="past-contests">here</a>.</p>
  139. <h1>External Resources</h1>
  140. <p>In order to prepare for ProCo, you may want to familiarize yourself with problems from similar contests. At the
  141. following sites you can find repositories of problems of varying styles and difficulty. Most of these problems
  142. are for training purposes and will be harder than the problems given. Recommended links (similar format or
  143. similar difficulty level) are listed first.</p>
  144. <ul>
  145. <li><a href="http://usaco.org/">USACO</a> Algorithmic training and practice</li>
  146. <li><a href="http://codeforces.com/">CodeForces</a> Online programming competition</li>
  147. <li><a href="https://www.topcoder.com/">TopCoder</a> Online programming competition</li>
  148. <li><a href="http://code.google.com/codejam/contest">Google CodeJam</a> More programming practice</li>
  149. <li><a href="http://acm.pku.edu.cn/JudgeOnline/problemlist">PKU</a> Algorithmic problem set database</li>
  150. <li><a href="https://uva.onlinejudge.org/">UVA</a> More algorithmic training</li>
  151. <li><a href="https://projecteuler.net/">Project Euler</a> Math-oriented programming problems</li>
  152. </ul>
  153. <hr>
  154. <div class="footer">
  155. Information originally from Lennart Jansson and maintained by Jeremy Kim.
  156. </div>
  157. </section>