Schedule

  • Practice session

    April 25th, 2007 0:00AM - April 27th, 2007 0:00AM (GMT / UTC)
    SPOJ (CEST) is UTC +2, Beijing (CST) is UTC +8, and Hanoi is UTC +7

  • Contest session

    April 28th, 2007 0:00AM - April 30th, 2007 0:00AM (GMT / UTC)
    SPOJ (CEST) is UTC +2, Beijing (CST) is UTC +8, and Hanoi is UTC +7

    Rules

  • In order to join our contest you must have one SPOJ user, if you haven't, try to register here
  • Languages: all languages SPOJ supports.
  • Each user can submit at most 256 submissions per problem (SPOJ default constraint).
  • Memory limit for each problem is 256 megabytes (SPOJ default constraint).
  • Standard Input/Output is used for all problems.
  • Each problem you get Accepted you will receive the appropriate score noted in each problem description.
  • The ranklist is updated automatically at Ranks page.
  • Do not use more than one user for submitting or you will be considered as cheater and removed from ranklist.

    Links

    Amber's blog: http://adn.cn/blog/

    Free Pascal 1.45's blog

    Introductions to System

  • Submitting a solution Choose a problem from the problem-set and use the 'Submit' link at the top of the problem description

  • Statistic of a problem Choose a problem from the problem-set and use the 'All submissions' link at the top of the problem description

  • Best solutions for problem Choose problem from the problem-set and use the 'Best solutions' link at the top of the problem description

  • Status codes at SPOJ:

    At present SPOJ uses the following status codes:

    AC - accepted - your program ran successfully and gave a correct answer
    WA - wrong answer - your program ran successfully, but gave an incorrect answer
    TLE - time limit exceeded - your program was compiled successfully, but it didn't stop before the time limit
    CE - compilation error - your program couldn't be compiled; compilation errors can be seen from www and are sent via mail if your preferences say so; note: only some languages can give CE, syntax errors in interpreted languages can lead to WA (Python - no pre-checking syntax or Perl - CE only afer a basic syntax check)
    RE - runtime error - your program was compiled succesfully, but it exited with an error; possible codes are:

    - SIGSEGV(signal 11) - most common, "segmentation fault";
    - SIGXFSZ(signal 25) - "output limit exceeded";
    - SIGFPE(signal 8) - "floating point error", like division by zero, etc...
    - SIGABRT(signal 6) - raised by the program itself; C++ STL does it under some conditions;
    - NZEC(non-zero exit code) - helps tell a crash from WA with interpreted languages;
    - other - there are other signals which can cause the program to terminate, all remaining are shown as other.

  • Time limit Every task has a time limit. If the program doesn't end within the time limit, the solution will recieve status code TLE

  • Input and output data You should use stdin and stdout standard streams. These file streams are accessible by default for reading and writing in many languages. So, you can use scanf/printf in the C language or read/write (without a name of a file) in Pascal.

  • © Spoj.com. All Rights Reserved. Spoj uses Sphere Engine™ © by Sphere Research Labs.