Home News Info Regulation Contest Porto Links

 

   Here you will find info about the contest itself, such as the team roster, the final schedule, the computer environment and, during the contest, photos and results.

Tentative Schedule

Friday (15/11/2002)
17:00-19:30 Teams Registration (Hotel entrance hall)
 
Saturday (16/11/2002)
08:30 Transportation Hotel/Contest-site
08:45 Last Minute Teams Registration
09:30 Opening Ceremony
9:45 Invited talk 1: Smart Sketches - from Design to Engineering
by Prof. Joaquim Jorge, IST, Portugal.
10:45 Coffee Break
11:15 Invited talk 2: Technology and Citizenship
by Prof. JosÚ Manuel Valenša, Univ. Minho, Portugal.
12:15 Lunch: buffet
13:45 Introduction to the Practice Session
14:20 Practice Session
16:00 Coffee Break
16:15 Questions and Answers session
16:30 Transportation
17:00 Cultural/Touristic activity:
visit to Port Wine Cellars (Porto Ferreira)
19:15 Transportation
19:45 Dinner at Hotel Ipanema
22:30 Short walk to hotels (5 min.)
 
Sunday (17/11/2002)
08:30 Transportation Hotel/Contest-site
09:00 Last minute announcements
09:30 Teams head to laboratories
10:00 Contest begins
11:00 Lunch: brunch
15:00 Contest ends
16:30 Contest statistics; Questions and Answers Session
17:00 Awards ceremony
18:00 Transportation back to hotel

[go up...]

Computer Environment

Judging System

  SWERC'2002 will use the Mooshak system developed at the Computer Science Department, University of Porto. This software is web-based and behaves as a full contest manager as well as an automatic judge for contests. It includes four main views:

  • contestants view: allows contestants to
    • visualize the problems descriptions;
    • load a source program and submit it as an intended solution for a given problem;
    • ask questions to the judges;
    • read a FAQ page with answers to common questions;
    • access to the full list of questions and corresponding answers from the judges;
    • access the list of submissions that have been made since the beginning of the contest;
    • access the current classification.
  • administration view: allows the administrators to
    • setup a new contest, by defining the teams, the passwords for the teams, the set of problems, the test cases and time limits for each problem, the languages used and corresponding compilation commands and flags, duration for the contest, etc.
  • judges view: allows the judges to
    • assist in the judging process by validating the results of the automatic judge, thus making the evaluation final. Using this interface, judges can easily re-evaluate submissions if necessary;
    • answer to questions posed by teams;
  • public view: allows the general public to:
    • follow the progress of a contest;
    • access the list of submissions;
    • access the current classification;
    • access the contest statistics.

  Access to the system is through login/password authentication. The system has builtin safety measures to prevent users from interfering with the normal progress of the contests. Submissions sent by teams are evaluated by having the corresponding programs compiled and run in a safe-process environment. Programs are only allowed a certain ammount of resources in terms of main memory, disk space and execution time. If a program exceeds any default limit, it is cancelled and a submission message error is produced.

Working enviroment

  At the contest, all teams have a similar working environment:

  • Hardware: Pentium III 730 MHz with 128MB RAM and 17'' monitor; Keyboards have the portuguese layout, however teams are allowed to bring and setup their own keyboards during the coffee break on Saturday morning. You can bring PS/2 or USB keyboards.
  • Software: Linux Mandrake 9.0 with all usual goodies of Linux: Kde and Gnome window manager; mozilla browser; emacs, xemacs, vi, jove, ..., text editors; same compilers as used in the automatic evaluation system server.

    The browsers are pre-configured to be used with the submission system (14 points font size). The default profile is for mozilla, however you have to confirm its automatic profile conversion.

    Internet http access is restricted just to the automatic evaluation system server.

  The automatic evaluation system (Mooshak) will run on two servers, both are duals AMD-Athlon MP 2000 with 1GB of main memory, with Linux Mandrake 9.0 distribution. The compilers and compilation commands will be the same on teams machines and automatic judging servers.

  There is a backup server (an AMD-Athlon 1600) that will be used by the contest judges to confirm the automatic evaluation made by Mooshak.

  There will be another server (dual AMD-Athlon 1600) for the public online contest that will take place at same time as SWERC.

Using the Mooshak system

  All teams are given a login and password to access the contestants view of the system. Teams must, first:

  1. access to page: http://swerc.up.pt/contest;
    you need to go through the authentication process, in principle, just once;
  2. select the problem the team is going to solve (A, B, C,..., I);
  3. load the source code of your program that solves the problem you selected, and then click on Submit.

  Once you have made a submission, the result of the automatic judge should appear almost instantaneously. This result is initially marked as in pending state to indicate that it has to be confirmed by a judge person. Once confirmed, the submission result is marked final.

  In about 99% of the cases the automatic judge makes a correct evaluation. We made a great effort to make everything consistent and robust, but problems may arise unexpectedly, such as a system resource failure, a mistake in a test case, etc. You shouldn't worry too much because the system is highly flexible in allowing the judges to re-evaluate submissions without a team beeing penalised for it, and thus undoing whatever went wrong first.

  Please note: any attempt in sending too many adhoc submissions near the end of the contest will be interpreted as misconduct by the judges.

  Compilation commands and file extensions: all machines provide an alias for each language compiler with the flags already set as used in the judging server. Next, we list for each language the compilation command, corresponding alias and source file extension that shoud be used:
Language Compiler Command Alias Extensions
C gcc 3.2 gcc -ansi -lm file.c mygcc .c
C++ g++ 3.2 g++ -ansi -lm file.cpp myg++ .cpp or .C
Java jdk 1.4.1 javac file.java myjava .java
Pascal freepascal 1.0.6 fpc -v0w file.pas myfpc .pas

  The filename you use for your programs is irrelevant for the system. However, file extensions are crucial. The system won't recognize other extensions and won't try to guess the programming language you are using. It assumes that the file extension you give correctly identifies the programming language.

Manuals:

  The system includes the usual man-pages in Linux as well as the Gnu-Emacs info. To use info just type info on your shell, or type ``Ctrl-h i'' if you are using emacs. The java documentation can be accessed locally in /usr/local/java/doc.

Printing your programs:

  To print a copy of one of your programs, load it first and then press the button Print. Please do not leave your place to collect the printout from the printer, someone will bring it to you. You are only allowed to print your programs not the problem descriptions.

Problem descriptions:

  Even though each team member receives a paper copy of the problem set, the judging system allows you to access the problem descriptions through your browser. Please select the problem and then press on the View button.

Asking questions:

  In case you need to ask a question to the jury, please select the problem to which the question is related and then press Ask. Once you have submitted the question, every team will have access to it as well as the answer given by the judges. Some questions may not be answered directly, because they have been already answered or because the judges feel it cannot be answered without giving away relevant information.

  Please be considerate to other teams and avoid questions that simply can not be answered (e.g. what is the output of judge's solution for the following input ...).

[go up...]

 
 
| Home | News | Info | Regulation | Contest | Porto | Links |