CPSC448: Problem solving

Winter 2002-2003, term 2

• Course outline and syllabus
• Homework
• Marks
• The original course proposal
• Resources
  • The Tables problem and solution
  • Quiz 2 Question 1 Solution
  • Midterm preparation questions
  • Code and output for the debugging practice 1
  • Midterm 1 solutions (PDF).
  • Debugging session: Three bad implementations
  • Number theoretic algorithms in C++.
  • Stefan's Subsets Tutorial.
  • Final exam preparation questions
  • The final exam (PDF, DOC)

Judy 0.9beta

This is our new problem submission system (still in experimental stage).

February 22, 2003: Over a megabyte of source code has been submited to the judge.

• Submit a solution.
• Check the real-time status.
• The new scoreboard.
• Source code (still buggy and incomplete).

grep+

Keyword search:

Miscellaneous

• An obfuscated program and more stuff like that.
• Website access statistics

What is the scoreboard for?

The scoreboard shows who solved which problem and how many tries it took the person to get it. First of all, it is not meant to rank students in any way! Different people will start working on the problems at different times and in different order. The number of incorrect submissions is completely irrelevant in calculating the marks. The point of the scoreboard is to help you. If you are struggling with a problem, take a look at how other students are doing with it. If nobody has an accepted solution and a number of unsuccessful submissions, that probably means that it is a hard problem and you should perhaps read it more closely or work on the other ones first. If on the other hand, several people have solved a particular problem, this could mean that the problem is relatively easy, and you should perhaps start with that problem.