Difference between revisions of "Programming Ladder"

From LUDD - Luleå Academic Computer Society

(Created page with "The Programming Ladder is a weekly programming competition run by LUDD. It was started in April 2013 and is currently on the first year. Each week members are challenged with a p...")
 
(LOL FIXED)
Line 1: Line 1:
The Programming Ladder is a weekly programming competition run by LUDD. It was started in April 2013 and is currently on the first year. Each week members are challenged with a programming problem. Depending on how well you solve the problem you gain a set amount of points which are recorded on the ladder. At the end of the year (December) the topmost contestant wins a price (size depends on number of contestants and supporters).
+
The Programming Ladder is a weekly programming competition run by LUDD. It was started in April 2013 and is currently on its first year. Each week, members are challenged with a programming problem. Depending on how well they solve the problem, they'll gain a set amount of points which are recorded on the ladder. At the end of the year (December) the topmost contestant wins a price (the value of which depends on number of contestants and supporters).
  
 
== Current Ladder ==
 
== Current Ladder ==
Line 7: Line 7:
  
 
=== Ruling ===
 
=== Ruling ===
When a submission arrives on our systems, it will be run with the inputs and outputs mentioned on the problem sheet. If the submission is correct, you will be rewarded points according to the Scoring system.  
+
When a submission arrives on our systems, it will be run with the same format of inputs and outputs mentioned on the problem sheet. If the submission is correct, the contestant will be rewarded points according to the scoring system.  
  
A submission is regarded as correct if:
+
A submission is regarded as correct if the program:
  
* It terminates within 2 minutes
+
* Terminates within 2 minutes,
* It generates correct output stated on the problem sheet
+
* Generates correct output according to the format on the problem sheet,
* If the program needs compilation, the program has to compile.
+
* Compiles correctly, if compilation is needed,
* A submission may not use any non-standard libraries.
+
* Does not use any non-standard libraries,
  
 
=== Cheating ===
 
=== Cheating ===
While it is not against the rules to cooperate in solving the problems, it is important that you do not rely on it. Submitting a solution that is similar too another's or that is obviously copied is frowned upon. Multiple offences will result in disqualification.
+
While it is not against the rules to cooperate in solving the problems, contestants are to submit their solutions individually. Submitting a solution that is similar to another contestant's or that is obviously copied is frowned upon. Multiple offences will result in disqualification.
  
 
=== Input and Output ===
 
=== Input and Output ===
Line 24: Line 24:
 
Output will be received through STDOUT according to the problem sheet.
 
Output will be received through STDOUT according to the problem sheet.
  
In linux, if you want to test STDIN and STDOUT, do "echo 1 | your_program | cat -" and it will send 1 to your program through STDIN and print what is received throught STDOUT.
+
On linux, if you want to test STDIN and STDOUT, do "echo 1 | your_program | cat -" and it will send 1 to your program through STDIN and print what is received throught STDOUT.
  
 
=== Scoring ===
 
=== Scoring ===
Upon submitting a solution the program will be run on our machines. If a correct solution is met within 2 minutes of program execution '''AND''' the program is terminated, the contestant will be rewarded 10 points. If the program does not meet those conditions the solution will be rejected.  
+
Upon submitting a solution the program will be run on our machines. If a correct solution is returned within 2 minutes of program execution '''AND''' the program is terminated, the contestant will be rewarded 10 points. If the program does not meet those conditions the solution will be rejected.  
  
 
A contestant may choose to resubmit their corrected solution but will be deducted 1 point per failed try.
 
A contestant may choose to resubmit their corrected solution but will be deducted 1 point per failed try.
  
 
'''''For example:'''''
 
'''''For example:'''''
''Bob submits his solution to a problem. He has previously submitted two incorrect solutions. Bob's new submission is correct so he will be rewarded '''8 Points''' ('''10 Points''' for a correct solution '''- 2 Points''' because of the 2 failed tries)''
+
''Vicke submits his solution to a problem. He has previously submitted two incorrect solutions. Vicke's new submission is correct so he will be rewarded '''8 Points''' ('''10 Points''' for a correct solution '''- 2 Points''' because of the 2 failed tries)''
  
The minimum amount of points rewarded is 2, if your score deduction would lead you to receive less then 2 points, it will be adjusted up to 2 points.
+
The minimum amount of points rewarded is 2. If your score deduction would lead you to receive less then 2 points, it will be adjusted up to 2 points.
  
 
You can submit a solution to an earlier week's problem, but you can only be rewarded 2 points maximum for the solution.
 
You can submit a solution to an earlier week's problem, but you can only be rewarded 2 points maximum for the solution.

Revision as of 19:27, 4 April 2013

The Programming Ladder is a weekly programming competition run by LUDD. It was started in April 2013 and is currently on its first year. Each week, members are challenged with a programming problem. Depending on how well they solve the problem, they'll gain a set amount of points which are recorded on the ladder. At the end of the year (December) the topmost contestant wins a price (the value of which depends on number of contestants and supporters).

Current Ladder

TODO

Rules

Ruling

When a submission arrives on our systems, it will be run with the same format of inputs and outputs mentioned on the problem sheet. If the submission is correct, the contestant will be rewarded points according to the scoring system.

A submission is regarded as correct if the program:

  • Terminates within 2 minutes,
  • Generates correct output according to the format on the problem sheet,
  • Compiles correctly, if compilation is needed,
  • Does not use any non-standard libraries,

Cheating

While it is not against the rules to cooperate in solving the problems, contestants are to submit their solutions individually. Submitting a solution that is similar to another contestant's or that is obviously copied is frowned upon. Multiple offences will result in disqualification.

Input and Output

Input will be submitted through STDIN according to the problem sheet.

Output will be received through STDOUT according to the problem sheet.

On linux, if you want to test STDIN and STDOUT, do "echo 1 | your_program | cat -" and it will send 1 to your program through STDIN and print what is received throught STDOUT.

Scoring

Upon submitting a solution the program will be run on our machines. If a correct solution is returned within 2 minutes of program execution AND the program is terminated, the contestant will be rewarded 10 points. If the program does not meet those conditions the solution will be rejected.

A contestant may choose to resubmit their corrected solution but will be deducted 1 point per failed try.

For example: Vicke submits his solution to a problem. He has previously submitted two incorrect solutions. Vicke's new submission is correct so he will be rewarded 8 Points (10 Points for a correct solution - 2 Points because of the 2 failed tries)

The minimum amount of points rewarded is 2. If your score deduction would lead you to receive less then 2 points, it will be adjusted up to 2 points.

You can submit a solution to an earlier week's problem, but you can only be rewarded 2 points maximum for the solution.

Submitting

To submit a solution, head to Will be announced and choose the source code. Your solution should be packaged as a .zip, .rar, .tar.gz or .tar.bz file.

Please make sure to only send the files needed for compilation and running your program.

Current Problem

TODO

Earlier Problems

Personal tools