-
Notifications
You must be signed in to change notification settings - Fork 7
/
help.php
157 lines (117 loc) · 6.61 KB
/
help.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
<?php
include("config.php");
include("common.php");
?>
<html>
<head>
<?php print "<title>$g_pagetitle - Help</title>\n"; ?>
</head>
<body>
<div align="center">
<h1>Help Page</h1>
</div>
<?php navigation("help"); ?>
<hr>
<div align="left">
<h2>Introduction</h2>
<p> The UofC Programming Contest Control Centre is a tool for hosting an
<a href="http://icpc.baylor.edu">ACM ICPC</a>-style programming contest on the
web. Only a basic web browser (with cookies enabled) is required to access the
contest system.
<p> In order to participate in the running contest, you must have a valid team
ID and password. If you do not have an ID and password, please contact the
contest host to obtain one.
<h2>Contest Problems</h2>
<p> Links to each of the contest problems can be found on the main page. Note
that these links are only active once the contest has begun, and are accessible
to the general public as well. The contest date and time (with time zone) is
also posted on this page.
<h2>Contest Scoreboard</h2>
<p> The "Scoreboard" navigation tab takes you to a page displaying
the current, live standings of contest. This page is automatically refreshed
every 5 minutes.
<p> On the scoreboard, formally participating teams names are shown in
emphasized bold type, while guest and ghost teams are shown in regular typeface.
Only teams that have submitted solutions will be shown on the scoreboard.
<p> A number appearing in a cell in the scoreboard indicates the number of
minutes a team took to solve a particular problem. The number following a +
sign indicates additional penalty minutes a team incurred. A negative number
in parentheses incidates the number of failed attempts to solve a particular
problem.
<h2>Submitting Solutions</h2>
<p> The "Submissions" navigation tab will provide you with a form
you can use to submit a solution to a problem. You must be logged in to the
system with a valid team ID and password in order to submit your solutions.
<p> In the Source field, choose the file which contains the source code for
your solution. Please note that all the source code for any one solution must
be contained within the same file! Be sure to select the correct language of
the source, or you may receive a nasty compilation error. The accepted
languages are currently C, C++, and Java.
<h2>Checking Submission Status</h2>
<p> You will also be able to check the status of any solutions you submitted
at the bottom of the "Submissions" page. If you are logged in to the
system, a table displaying all submissions received from your team will
automatically be shown. Checking the judge results of your submissions is
important, as it can give you valuable information if your solution failed.
<p> The various results for a submitted solution are listed below. Note that
not all possible responses may be used by the judge for a particular contest.
<p><table cellpadding="4">
<tr> <td width="180"> "Not Yet Judged" </td>
<td> The contest judge has yet to run your solution against the test
data.</td></tr>
<tr> <td> "Accepted" </td>
<td> Your solution is correct.</td></tr>
<tr> <td> "Run-Time Error" </td>
<td> Execution of your solution on the test data resulted in a program
crash or similar behaviour.</td></tr>
<tr> <td> "Time Limit Exceeded" </td>
<td> Your program failed to terminate within the allotted execution time.
</td></tr>
<tr> <td> "Incorrect Output" </td>
<td> Execution of your solution on the test data does not produce the
correct answer.</td></tr>
<tr> <td> "Presentation Error" </td>
<td> Your solution appears to produce the correct answer to the problem,
but there is an error in the formatting, capitalization, spelling,
punctuation, etc. of the output.</td></tr>
<tr> <td> "Compile Error" </td>
<td> Your program source fails to compile on the judge system using the
compiler for the specified language.</td></tr>
<tr> <td> "Submission Error" </td>
<td> There was an unknown or unanticipated problem with your submission.
Check that you are following the right conventions for formatting
and uploading your source files, using the correct input/output, and
that you are solving the right problem. It may be necessary to
contact the contest host or judge if you cannot resolve the problem.
You are not normally penalized for a submission error.
</table>
<h2>Contest or Problem Clarifications</h2>
<p> The "Clarifications" navigation tab allows you to view any
additional clarifications or information about the problems or the contest that
the judge has posted. You may also use this page to submit a clarification
request. It is important to check this page often during a contest, especially
if you are having difficulties with a certain problem or the contest system.
<p> Note that whenever a clarification is answered, it is answered for all
teams to see. Clarifications are only intended to be used when there is some
genuine inconsistency or ambiguity in a problem that needs to be resolved, or
if certain special instructions for the contest are required but were omitted.
It is not by any means a way for you to get the judge to explain a problem if
you do not understand it.
<p> Once you submit a clarification request, you will no longer be able to
see it. Do not worry -- it has been saved! The clarification will only appear
if and when the judge has chosen to answer it.
<h2>About the UCPCCC</h2>
<p> The University of Calgary Programming Contest Control Centre was developed
beginning in 2005 for the purpose of training the University of Calgary and
other Canadian programming teams. It was designed as a super light-weight, easy
to use, and universally accessible front end for running small programming
contests.
<p> If you have any questions, comments, or suggestions about the system,
please contact the author, Sonny Chan, at <a href="mailto:sonnyc@gmail.com">
sonnyc@gmail.com</a>. The author would also like to thank Kelly Poon and Allan
Hart for their contributions to the development of the contest system, and
Chuong Do for providing a very nice automatic judging script back end.
</div>
<?php footer(); ?>
</body>
</html>