1 # Configuration file for the MO Evaluator
2 # (c) 2001--2007 Martin Mares <mj@ucw.cz>
4 # The root of the whole directory hierarchy
7 # User and group used by the evaluator itself
11 # Test user for the sandbox. You can let mo-setup create more test users
12 # and then run several evaluators in parallel, each in its own sandbox.
13 # For testing, you can also leave TEST_USER undefined and run the sandbox
14 # with EVAL_USER privileges, but beware, this is INSECURE.
15 #TEST_USER=${TEST_USER:-mo-test1}
16 TEST_USERS="mo-test1 mo-test2"
19 # These values are used when creating logins for eval and contestants
20 # (group id's are from the same range)
25 # Sometimes we need to get a list of all contestants (not in the evaluator
26 # itself, but in various auxiliary scripts). In such cases we call mo-get-users,
27 # which either uses an explicit list of contestants CT_USER_LIST (username<tab>fullname),
28 # or (if undefined) scans /etc/passwd for users with UID between CT_UID_MIN and CT_UID_MAX.
31 # (optional) Use remote submitting
33 REMOTE_SUBMIT_USER=mo-submit
34 REMOTE_SUBMIT_GROUP=mo-submit
36 ### Per-task configuration variables (default values, override in per-task config)
40 # Known source file extensions
41 EXTENSIONS="c cc C cpp p pas"
43 # Extra compiler flags for C (null, but can be overriden)
46 # Extra compiler flags for Pascal
49 # For each source extension, we must give compiler command
50 COMP_c='/usr/bin/gcc -std=gnu99 -O2 -g -o $EXE $EXTRA_CFLAGS $SRC -lm'
51 COMP_C='/usr/bin/g++ -O2 -g -o $EXE $EXTRA_CFLAGS $SRC -lm'
54 COMP_p='/usr/bin/fpc -Ci -Cr -Ct -g -O2 -Sg -o$EXE $EXTRA_PFLAGS $SRC'
57 # Sandbox options used when compiling
58 COMP_SANDBOX_OPTS='-m262144 -w60 -e -i/dev/null'
60 # Sandbox initialization commands for compilation
63 # List of extra files needed for compilation. They are copied to the compiler
64 # sandbox from the problem's directory.
65 #COMP_EXTRAS="extras.h"
67 ## Tester settings (most can be overriden in per-test config):
69 # The following variables are automatically set by the evaluator:
70 # PROBLEM name of the problem
71 # HDIR home directory of the evaluator (i.e., this file is $HDIR/config)
72 # PDIR directory containing problem data
73 # SDIR directory containing contestant's solution
74 # TDIR directory containing testing results
75 # TMPDIR directory containing temporary files
76 # TEST name of the current test
79 # offline off-line task
80 # interactive interactive task communicating via stdio with a testing program
81 # open-data open-data task (i.e., we don't submit program, but output files)
84 # I/O type (IO_TYPE sets defaults for IN_TYPE and OUT_TYPE)
85 # file input from $PROBLEM.in, output to $PROBLEM.out (possible even for interactive tasks)
86 # stdio input from stdin, output to stdout
87 # none no input/output
93 TESTS="1 2 3 4 5 6 7 8 9 10"
95 # A list of public tests (executed by submit and check scripts)
98 # Number of points per test
101 # Time limit in seconds (can be fractional, but beware of noise)
104 # Memory limit in kilobytes
107 # Command used for filtering of program output (optional)
108 # If turned on, program output (*.raw) is ran through this filter and the
109 # checkers are applied to the output of the filter (*.out).
110 # Can exit with code 1 if there is a syntax error in the output.
111 #OUTPUT_FILTER='tr -d '\''\r'\'' <$TDIR/$TEST.raw >$TDIR/$TEST.out'
113 # Command used to check output syntax (optional)
114 # Returns exit code 1 if syntax is wrong, 0 if correct
115 # fd1 is connect to evaluator log, feel free to log anything
116 # fd2 is an optional one-line verdict
117 #SYNTAX_CHECK='grep -v -- - $TDIR/$TEST.out'
119 # Command used to check output correctness
120 # Returns exit code 1 if output is incorrect, 0 if correct
121 # fd1 is connect to evaluator log, feel free to log anything
122 # fd2 is an optional one-line verdict
123 # The checker can generate $TDIR/$TEST.pts to assign points irregularly
124 OUTPUT_CHECK='diff -bBu $TDIR/$TEST.ok $TDIR/$TEST.out'
126 # Checker for interactive tasks
127 # Returns exit code 1 if test failed, 0 if passed
128 # fd0 and fd1 are connected to fd1 and fd0 of the program tested
129 # fd2 is an optional one-line verdict
130 # The checker can generate $TDIR/$TEST.pts to assign points irregularly
131 #IC_CHECK='$PDIR/checker $PDIR/$TEST.in $PDIR/$TEST.chk'
133 # Sandbox options used when testing
134 TEST_SANDBOX_OPTS='-a2 -f -m$MEM_LIMIT -t$TIME_LIMIT'
136 # Sandbox initialization commands
139 # Translate FreePascal exit codes to names of well-known runtime errors
142 # DEBUG: Let `ev' run sample tests, too.
145 # DEBUG: Run `pedant' on all input data. Set either to `1' or to pedant's options.
148 # DEBUG: Skip checks (useful when generating output files by running model solution)
151 # DEBUG: Skip output filters (if you suspect they are buggy)