Installing and configuring Judge - ประวัติรุ่นแก้ไข

Jittat: /* Importing test data */

2009-10-05T17:14:08Z

Importing test data

Jittat: /* Importing test data */

2009-10-05T17:12:53Z

Importing test data

Jittat เมื่อ 04:44, 20 สิงหาคม 2552

2009-08-20T04:44:12Z

Jittat: /* Check out the scripts directory from the SVN */

2009-08-19T16:50:54Z

Check out the scripts directory from the SVN

Jittat: /* Check out the scripts directory from the SVN */

2009-08-19T16:49:48Z

Check out the scripts directory from the SVN

124.121.137.248 เมื่อ 16:50, 30 กรกฎาคม 2551

2008-07-30T16:50:12Z

Jittat เมื่อ 01:02, 23 มีนาคม 2551

2008-03-23T01:02:17Z

Jittat: /* How to grade */

2008-03-21T12:24:16Z

How to grade

Jittat: /* How to grade */

2008-03-21T12:24:00Z

How to grade

Jittat: /* How to grade */

2008-03-21T12:22:31Z

How to grade

@@ แถว 83: / แถว 83: @@
 Then you invoke the script call <tt>import_problem</tt> in the judge directory (e.g., <tt>(judge-home)</tt>).
 The following is from the script usage:
   using: import_problem_new name dir check [options]
-−
   where: name = problem_name (put '-' (dash) to use dir name)
          dir = importing testcase directory
@@ แถว 91: / แถว 92: @@
                  path_to_your_script, or
                  'wrapper:(path_to_your_wrapped_script)'
   options: -t time-limit (in seconds)
            -m memory-limit (in megabytes)
-−
   The script looks at test data files in the dir of the forms: *.in and
   *.sol and import them to the evaluation dir for their environment,
   based on their prefixes.
-−
   Currently supporting environments are:
     * grading
@@ แถว 105: / แถว 107: @@
         import to: ev-exam
         prefix with: ex.  (e.g., ex.1.in, ex.5a.sol)
-−
   For each environment, the script
     * creates a directory for a problem in ev dir of that environment,
@@ แถว 111: / แถว 113: @@
     * copies a check script for grading
     * creates a test_request template in the ev dir + '/test_request'
-−
   For wrapped checked script see comment in templates/check_wrapper for
     information.

@@ แถว 81: / แถว 81: @@
 In normal usage where every test case has the same constraint and each corresponds to a unique test run, you can use a script to import the problem test data in a simpler format: each test case i has two files i<tt>.in</tt> and i<tt>.sol</tt>, all stored in some directory.  For example you may have <tt>1.in</tt>, <tt>1.sol</tt>, <tt>2.in</tt>, <tt>2.sol</tt>, ..., and so on.
-Then you invoke the script call <tt>import_problem</tt> in the test data directory (e.g., <tt>(judge-home)/ev</tt>).
+Then you invoke the script call <tt>import_problem</tt> in the judge directory (e.g., <tt>(judge-home)</tt>).
 The following is from the script usage:
-  using: import_problem name dir num check [options]
+  using: import_problem_new name dir check [options]
-    where: name = problem_name [
-           dir = importing testcase directory
+ where: name = problem_name (put '-' (dash) to use dir name)
-           num = number of testcases
+        dir = importing testcase directory
-           check = check script, which can be
+        check = check script, which can be
-                    'integer', 'text' (for standard script),
+                'integer', 'text' (for standard script),
-                    path_to_your_script, or
+                path_to_your_script, or
-                    'wrapper:(path_to_your_wrapped_script)'
+                'wrapper:(path_to_your_wrapped_script)'
-    options: -t time-limit (in seconds)
+ options: -t time-limit (in seconds)
-             -m memory-limit (in megabytes)
+          -m memory-limit (in megabytes)
-  What it does:
-    * creates a directory for a problem in the current directory,
+ The script looks at test data files in the dir of the forms: *.in and
     * copies testdata in the old format and create standard testcase config file
     * copies a check script for grading
-    * creates a test_request template in the current directory + '/test_request'
+    * creates a test_request template in the ev dir + '/test_request'
   For wrapped checked script see comment in templates/check_wrapper for information.
 Note that you have to specify how the submission's output will be graded by specifying check script (See [[An Online Programming Judge System#Check Script|this]] for specification).  Standard checkers are available: ''integer'' and ''text''.  To decouple the development of the check script and the grading system, one can develop the checker with no direct access to problem configuration and then wrap it using wrapper check script.  The wrapping check script would call the real script with the following arguments

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 04:44, 20 สิงหาคม 2552
แถว 1:		แถว 1:
		+	{{กล่องสี\|#ffcccc\|
		+	<center>
		+	เนื้่อหาของบทความนี้ล้าสมัยแล้วและกำลังอยู่ระหว่างการปรับปรุง ขออภัยครับ.
		+
		+	The content of this article is out of date. It is being revised; please wait. Thank you.
		+	</center>
		+	}}
		+
	Judge system reads user submissions and test submissions and grades. Its sandbox software is taken from the [http://mj.ucw.cz/mo-eval/ MO contest environment] developed by [http://mj.ucw.cz/ Martin Mares].		Judge system reads user submissions and test submissions and grades. Its sandbox software is taken from the [http://mj.ucw.cz/mo-eval/ MO contest environment] developed by [http://mj.ucw.cz/ Martin Mares].

@@ แถว 37: / แถว 37: @@
 ===Check out the scripts directory from the SVN===
- svn co http://theory.cpe.ku.ac.th/grader/judge/trunk/script
+<pre>
 ===Edit config files===

@@ แถว 36: / แถว 36: @@
 ===Check out the scripts directory from the SVN===
 ===Edit config files===
 Config files are in <tt>(judge-home)/scripts/config</tt>.  In that, you will find sample config files (under <tt>*.SAMPLE</tt>).

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 16:50, 30 กรกฎาคม 2551
แถว 137:		แถว 137:

	Have fun!		Have fun!
		+
		+	==HOWTO: Interactive tasks==
		+	: to be added
		+
		+	==HOWTO: Output-only tasks==
		+	: to be added

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 01:02, 23 มีนาคม 2551
แถว 1:		แถว 1:
−	Judge system reads user submissions and test submissions and grades. It can be run with different configurations (called "environments") depending on the situations, e.g., during the exam, the judge probably grades with example test cases but while grading it grades with different sets of test cases. This multiple configurations can be done with multiple "environments" where configured so that the judge finds different sets of test data.	+	Judge system reads user submissions and test submissions and grades. Its sandbox software is taken from the [http://mj.ucw.cz/mo-eval/ MO contest environment] developed by [http://mj.ucw.cz/ Martin Mares].
		+
		+	It can be run with different configurations (called "environments") depending on the situations, e.g., during the exam, the judge probably grades with example test cases but while grading it grades with different sets of test cases. This multiple configurations can be done with multiple "environments" where configured so that the judge finds different sets of test data.

	==Basic directory structure==		==Basic directory structure==

@@ แถว 121: / แถว 121: @@
 Here are the steps.
 . Make sure that you have stopped all other running grader on the grading environment.  If you know the pid of judge, call
   grader stop (pid)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:24, 21 มีนาคม 2551
แถว 128:		แถว 128:

	2. Make sure that you have your test data ready. (You should!) Assume that you have it in <tt>grading</tt> environment.		2. Make sure that you have your test data ready. (You should!) Assume that you have it in <tt>grading</tt> environment.
		+
		+	3. Then for each problem, say (problem-name), call
		+	grader grading prob (problem-name)
		+	and iterate through your list of problems.
		+
		+	Have fun!

@@ แถว 121: / แถว 121: @@
 Here are the steps.
-# Make sure that you have stopped all other running grader on the grading environment.  If you know the pid of judge, call
+. Make sure that you have stopped all other running grader on the grading environment.  If you know the pid of judge, call
   grader stop (pid)
 or you can stop all running graders by calling
   grader stop all
 but you have to delete the stop file <tt>stop.all</tt> by yourself, otherwise you won't be able to start the grader.
-# Make sure that you have your test data ready.  Assume that you have it in <tt>grading</tt> environment.