2018 Computing and Judging Environment

Note: you are encouraged to bring hardcopies of this page or any other pages from our web site to the Regional Contest.

Each team will be assigned a work area that includes a computer workstation, a small table desktop, and three chairs.

Each team will have a machine of its own to use during the contest. During the contest, contestants are to use the network only to submit contest problems or questions and get responses from the contest officials. Connecting to any other computer on the LAN or Internet, either before or during the contest, with telnet, FTP, Web browser, email, or any other network application is grounds for expulsion from the contest.

This year the Southern California Regional Contest will be using Fedora 28 as the host OS for the environment. We will be supplying Eclipse as an IDE along with the JetBrains IDEs (IntelliJ IDEA, CLion, PyCharm), but will include Geany, vim, emacs and other standard command line editors.

The contest will be providing one USB flash drive per team that you will be able to copy your code to and take with you at the end of the contest. This will not include the practice session. Please do NOT remove the USB drive until the end of the contest.

Lastly, the contest will use the web based judging environment called DOMJudge. Please download and read the Team Manual for information on how to use the DOMJudge interface.

If you have any questions about the Contest Environment, send them to <systems@socalcontest.org> .

For more information regarding UNIX or the editors that will be available, see our Guide to UNIX and Editors.


You will have all the tools that accompany a rather standard installation of Linux: AWK, Python, perl, and many others. These tools simply tag along with the installation process. Any languages or programs beyond the tagalongs, the compilers, and the tools stated below are installed at the convenience and discretion of the environment manager, <systems@socalcontest.org> .

Programming Languages

The judges accept problem submissions only in the following programming languages.

C gcc 8.1.1
C++ g++ 8.1.1
Java jdk SE 1.8.0_181 from java.oracle.com
Python 3 Python 3.6.6 standard release, no external libraries

The execution time limits set for each problem will NOT be scaled based on the language. It is the contestants' responsibility to select the appropriate tool (language and algorithm) to produce correct output within the allotted time limits.


Programs will be compiled and linked using the Standard C++ Library included by default with g++.


Regional judges will accept solutions coded in Python 3.


The following development tools and documentation will be available:


For additional information on the editors, please see the Guide to UNIX and Editors.

emacs 26.1 character based (emacs -nw) and mouse based (emacs)
vim 8.1.408 Vi IMproved, character based (vi, vim)
Mousepad 0.4.1 Fast text editor for the XFCE desktop environment
ed 1.14.2 line-oriented text editor

Note: jed and pico are not supported.


After you have submitted a source file for judging, your submission will be run with one or several sets of input data and the results reviewed. It is the judges' intent never to reveal directly or indirectly the specific input data the judges use to test contestant programs. The judges will respond to your submission with one of the following messages. If a submission contains more than one type of error, the response will still contain only one message. The judges will report only the first error seen, which may not necessarily be the error that occurs first or most frequently in the output.

Your program generated more output than the allowed limit. The output was truncated and considered incorrect.

The output of your program was incorrect. This can happen simply because your solution is not correct, but remember that your output must comply exactly with the specifications of the judges.

Although we do use robo-judge where possible, we verify every response before returning it to the team to ensure accurate, quality responses. The effect of this is that, depending on solution traffic and other factors, it may take longer to respond.