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.
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:
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.
At the contest, all teams have a similar working environment:
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:
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:
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.
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.
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.
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 ...).
|| Home | News | Info | Regulation | Contest | Porto | Links ||
last update: |
Copyright © 2002 - Universidade do Porto
Html & Design by Pedro Ribeiro ; Comments to Regional Contest Director