BAPC/Jury - Revision history

Max at 14:50, 6 March 2013

2013-03-06T14:50:36Z

Jbransen: /* Problem difficulty */

2013-03-06T14:48:16Z

‎Problem difficulty

Jbransen: /* Planning */

2013-03-06T14:42:27Z

‎Planning

Jbransen: /* Planning */

2013-03-06T14:41:57Z

‎Planning

Jbransen: /* SVN repository */

2013-03-06T14:25:28Z

‎SVN repository

Jbransen at 14:22, 6 March 2013

2013-03-06T14:22:25Z

Jbransen at 14:19, 6 March 2013

2013-03-06T14:19:44Z

Tomr: Created page with "foo bar Category:BAPC"

2013-03-06T13:33:55Z

Created page with "foo bar Category:BAPC"

New page

foo bar

[[Category:BAPC]]

@@ Line 22: / Line 22: @@
 It is very important to pick problems of the adequate difficulty. As a BAPC jury member it is often much more interesting to come up with difficult algorithms than to come up with original simple problems. However, both the preliminaries and the BAPC problemset will need to have some very simple (almost trivial) problems, because there are usually many teams that compete for the first time. Keep this in mind when coming up with ideas.
-== Miscellaneous ==
+== Miscellaneous tips ==
 [[Category:BAPC]]

@@ Line 19: / Line 19: @@
 == Problem difficulty ==
 == Miscellaneous ==
 [[Category:BAPC]]

@@ Line 3: / Line 3: @@
 The following is a suggestion for a planning with enough time to finish all problems.
-  * March: form committee of about 8 to 10 jury members
+* March: form committee of about 8 to 10 jury members
-  * April-May: Create problem ideas, which can be an informal description of the problems.
+* April-May: Create problem ideas, which can be an informal description of the problems.
-  * Beginning of June: Plan a meeting to pick the problems for both the preliminaries and the contest itself. Make sure that there are enough suggestions, you will at least need 30 suggestions to be able to have some choice. Also try to make sure that the difficulty level is appropriate and that the problems are original. See below for more information.
+* Beginning of June: Plan a meeting to pick the problems for both the preliminaries and the contest itself. Make sure that there are enough suggestions, you will at least need 30 suggestions to be able to have some choice. Also try to make sure that the difficulty level is appropriate and that the problems are original. See below for more information.
-  * July-August: the chosen problems are completed with good texts, testdata, check scripts for testdata, solutions.
+* July-August: the chosen problems are completed with good texts, testdata, check scripts for testdata, solutions.
-  * Beginning of September: Proofreading of problems by native English speaker, final check of all problems.
+* Beginning of September: Proofreading of problems by native English speaker, final check of all problems.
-  * Mid September: Send preliminary problems to all preliminary organizers
+* Mid September: Send preliminary problems to all preliminary organizers
-  * Begin October: Enjoy the preliminaries!
+* Begin October: Enjoy the preliminaries!
-  * Mid October: Evaluate preliminaries, and make final changes to contest problemset when necessary.
+* Mid October: Evaluate preliminaries, and make final changes to contest problemset when necessary.
-  * Mid-End October: Make solution presentation slides.
+* Mid-End October: Make solution presentation slides.
-  * End October: The contest! Enjoy!
+* End October: The contest! Enjoy!
 == SVN repository ==

← Older revision		Revision as of 14:41, 6 March 2013
Line 1:		Line 1:
	== Planning ==		== Planning ==
		+
		+	The following is a suggestion for a planning with enough time to finish all problems.
		+
		+	* March: form committee of about 8 to 10 jury members
		+	* April-May: Create problem ideas, which can be an informal description of the problems.
		+	* Beginning of June: Plan a meeting to pick the problems for both the preliminaries and the contest itself. Make sure that there are enough suggestions, you will at least need 30 suggestions to be able to have some choice. Also try to make sure that the difficulty level is appropriate and that the problems are original. See below for more information.
		+	* July-August: the chosen problems are completed with good texts, testdata, check scripts for testdata, solutions.
		+	* Beginning of September: Proofreading of problems by native English speaker, final check of all problems.
		+	* Mid September: Send preliminary problems to all preliminary organizers
		+	* Begin October: Enjoy the preliminaries!
		+	* Mid October: Evaluate preliminaries, and make final changes to contest problemset when necessary.
		+	* Mid-End October: Make solution presentation slides.
		+	* End October: The contest! Enjoy!

	== SVN repository ==		== SVN repository ==

@@ Line 3: / Line 3: @@
 == SVN repository ==
-A simple setup can be found [https://secure.a-eskwadraat.nl/Vereniging/Commissies/escapade/Jury_svn_setup.zip here].
+In order to work together on the creation of problems it is a good idea to set up a subversion (or git) repository. A sample setup for automatically building and testing solutions and to create pdf's can be found [https://secure.a-eskwadraat.nl/Vereniging/Commissies/escapade/Jury_svn_setup.zip here].
 == Problem difficulty ==

← Older revision		Revision as of 14:19, 6 March 2013
Line 1:		Line 1:
−	~~foo bar~~	+	== SVN repository ==
		+
		+	A simple setup can be found [https://secure.a-eskwadraat.nl/Vereniging/Commissies/escapade/Jury_svn_setup.zip here].

	[[Category:BAPC]]		[[Category:BAPC]]