Skip to content

Commit 8910e5d

Browse files
flyrevflyrev
committed
Web files added
0 parents  commit 8910e5d

File tree

126 files changed

+16752
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

126 files changed

+16752
-0
lines changed

‎NCPC-Director-HOWTO.html‎

Lines changed: 167 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,167 @@
1+
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
2+
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3+
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="no" lang="no">
4+
<head>
5+
<title>NCPC Director HOTWO</title>
6+
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
7+
<!-- <link rel="stylesheet" type="text/css" href="main.css" /> -->
8+
</head>
9+
<body>
10+
<div style="text-align: center;">
11+
<table style="margin-left: auto; margin-right: auto; text-align: justify;" width="750px">
12+
<tr>
13+
<td class="page">
14+
15+
<h1>NCPC Director HOWTO</h1>
16+
17+
<table>
18+
<tr>
19+
<td style="padding-right: 10px;"><a href="NCPC-Site-HOWTO.html">NCPC-Site-HOWTO</a></td>
20+
<td style="padding-right: 10px;"><a href="NCPC-Director-HOWTO.html">NCPC-Director-HOWTO</a></td>
21+
</tr>
22+
</table>
23+
24+
<h2>After NWERC</h2>
25+
26+
<ul>
27+
<li>Let the next NCPC director take over from here.</li>
28+
<li>Make sure you have a Head of Jury, and a Tecnical Director.</li>
29+
<li>Add news clips from NWERC to <a href="index.html#newsclips">#newsclips</a>.</li>
30+
<li>Go trough
31+
<a href="orgstatus.html">orgstatus.html</a>,
32+
set a proper schedule, and update the document.</li>
33+
<li>Go through the mailing lists
34+
<a href="http://ifi-lists.uio.no/mailman/listinfo/[email protected]">ncpc-info</a>,
35+
<a href="http://ifi-lists.uio.no/mailman/listinfo/[email protected]">ncpc-directors</a>,
36+
<a href="http://ifi-lists.uio.no/mailman/listinfo/[email protected]">ncpc-problems</a> and
37+
<a href="http://ifi-lists.uio.no/mailman/listinfo/[email protected]">ncpc-tech</a>.
38+
Send out an e-mail to each list, asking if anybody sees anybody on the
39+
list who should not be there. A trusted person from each site
40+
(typically the local head organiser), must vouch for each name from his
41+
site.</li>
42+
<li>Send out a request for problems to ncpc-problems, and inform about the
43+
schedule.</li>
44+
<li>Try to establish contact with universities not currently hosting NCPC.</li>
45+
</ul>
46+
47+
<h2>During the spring</h2>
48+
<ul>
49+
<li>Give ncpc-problems friendly reminders about the schedule. These should
50+
be frequent enough to keep the problem set at the back of peoples heads,
51+
but not frequent enough to be annoying.</li>
52+
<li>Keep on working with getting NCPC to new sites.</li>
53+
</ul>
54+
55+
<h2>August</h2>
56+
<ul>
57+
<li>Make sure the NCPC-pages are up to date:
58+
<ul>
59+
<li>Go through the front page, and the page for this years contest, and
60+
make sure everything is up to date. Be sure to check that all
61+
non-static content is updated! (References to this years this and
62+
that.) </li>
63+
<li>Check that the Rules (given an this years page) are up to date.</li>
64+
<li>Add any media references to <a href="index.html#newsclips">#newsclips</a></li>
65+
<li>Update the <a href="NCPC-Site-HOWTO.html">NCPC-Director-HOWTO</a></li>
66+
<li>Update the <a href="NCPC-Site-HOWTO.html">NCPC-Site-HOWTO</a></li>
67+
<li>Update the <a href="NCPC-PC2-HOWTO.html">NCPC-PC2-HOWTO</a></li>
68+
<li>Update the <a href="orgstatus.html">orgstatus</a></li>
69+
</ul>
70+
</li>
71+
<li>Send out an e-mail to ncpc-info, give information about this years
72+
contest:
73+
<ul>
74+
<li>Verify that all sites are in.</li>
75+
<li>Inform about how registration works.</li>
76+
<li>Make sure everybody is up to date with the technical aspects of
77+
hosting a contest (strongly coupled vs. uncoupled etc). Refer to
78+
the <a href="NCPC-PC2-HOWTO.html">NCPC-PC2-HOWTO</a>.</li>
79+
80+
<li>Make sure everybody reads the Rules.</li>
81+
</ul>
82+
</li>
83+
<li>Ask the NWERC director to schedule an NCPC meeting at NWERC.</li>
84+
<li>Ping ncpc-problems.</li>
85+
<li>Settle how scoreboards and clarifications will be handled for non-coupled
86+
sites.</li>
87+
</ul>
88+
89+
<h2>Before the contest</h2>
90+
<ul>
91+
<li>Send an e-mail to ncpc-info, letting people know the contest is up to
92+
speed.</li>
93+
<li>Set up a communication channel to use during the contest. Preferrably
94+
an IRC channel on a server which is not in a network.</li>
95+
96+
</ul>
97+
98+
<h2>During the contest</h2>
99+
<ul>
100+
101+
Kattis accounts for the contestants will be sent to you tomorrow. You will also receive 5 extra account for last minute teams or other unexpected events. Information about how to obtain a judge account for Kattis will be provided later.
102+
103+
Here are some instructions regarding Saturday:
104+
1. Make sure that each contestant account is reset and only contains
105+
the sample input and output for all problems (will be distributed
106+
with the problem set tomorrow). I suggest you create one directory
107+
for each problem. At each work station place three copies of the
108+
problem set in an envelop.
109+
110+
2. Read the rules and inform the contestants before the competition
111+
about what is allowed and what is not. For example, it is not
112+
allowed to use any other programming languages and code generation
113+
tools besides C/C++/Java. The teams are allowed to use those
114+
shells, editors and IDEs that you provide them with. However
115+
Python, Perl, lex, yacc and so on are not allowed. The contestants
116+
may use the documentation provided in Kattis (including STL and Java
117+
doc) as well as man pages if you have them.
118+
119+
3. Before the competition starts the contestants are allowed to log
120+
in, start a browser, start an editor if they want and log in on
121+
Kattis (https://ncpc12.contest.scrool.se/). Nothing else. No
122+
configuration files may be edited and the problem set is not to be
123+
touched.
124+
125+
4. All contest directors should report to me that they are ready to
126+
start the competition at the latest 10.50 Swedish time. If you have
127+
problems please report those as soon as possible. You can report on
128+
the IRC channel (irc.acc.umu.se#ncpc), through email
129+
([email protected]), or by calling me (+46-70-207 43 88). Since
130+
there are many sites this year we will probably start the contest
131+
even if one or two sites are silent. Unless something unexpected
132+
happens KTH will make a countdown on the IRC channel and at 11.00.00
133+
local KTH time the competition will start.
134+
135+
5. When the contest is started the contestants are allowed to open the
136+
problem set and start using the computer. Do your best to monitor
137+
that they do not use any illegal programs or surf the web. All the
138+
documentation that they are allowed to use is linked from their
139+
Kattis account.
140+
141+
6. All clarifications are handled through Kattis. The head judges Jon
142+
Marius Venstad and Tommy Färnqvist are responsible for answering all
143+
clarifications. They might be discussed on IRC if needed. If the
144+
answer is of general interest then an email will be sent to all
145+
directors.
146+
147+
7. When the competition is over and the final result is ready, I will
148+
announce it on IRC and to all directors by email. This is expected
149+
to be shortly after 16.00 unless something unexpected happens.
150+
151+
ncpc2012/ <li>...</li>
152+
</ul>
153+
154+
<h2>After the contest</h2>
155+
<ul>
156+
<li>Make sure the NCPC-pages are up to date again (see above).</li>
157+
<li>Make sure coaches know how to get teams to NWERC.</li>
158+
<li>Plan the NCPC meeting at NWERC. Announce it on ncpc-directors, with a
159+
preliminary list of topics.</li>
160+
</ul>
161+
162+
</td>
163+
</tr>
164+
</table>
165+
</div>
166+
</body>
167+
</html>

0 commit comments

Comments
 (0)