CSE 260 Research Projects

One of the goals of CSE 260 is to teach you how to conduct research. A research project is a formal requirement of the course and counts for 45% of your grade. A project may be done individually or in teams of two. You should allow 5 weeks to complete it. Your project grade will be based on your successful completion of the following 3 parts:

  1. Project proposal: due week 4, Tuesday 1/29 (1/10 of the project grade)
  2. Progress report: due week 7, Thursday 2/21 (electronic, 1/10 of the project grade)
  3. In class presentation: during week 10. Bring hard copies of your slides to class. (2/10 of your project grade)
  4. Final Report: due Friday, March 14th at 5PM, in EBU3B 3244 (Hard copy and electronic).
    Be sure to read Turnin instructions (6/10 of your project grade)

Here are descriptions of some projects that I’m currently interested in. If you have an idea for a project not listed here, let me know and we can talk about what you have in mind.

Your project proposal should address the following issues.

  1. What are the goals of your project? Are they realistic?
  2. What is your hypothesis?
  3. What result(s) do you want to demonstrate?
  4. What are the significance of the results?
  5. What is your experimental method?
  6. What code will you have to implement? Briefly describe any software packages or previously written software that you will be relying on.
The proposal should also include the investigator(s) names, the title of the project, and a preliminary list of milestones—with completion dates—and possible options depending on your progress. Be realistic, but remember that your milestones are not binding and you can fine-tune them as the project is underway. (This is fine so long as you document your decisions.) If you are working in a team, describe the division of labor in your proposal.


The progress report will help keep you on a steady pace and enable you to make mid-course corrections. The report should

  1. discuss your progress to date. If you are working in a team, include a self-evaluation discussing the division of labor and other aspects of how you worked together as a team team (A copy of the form is available in html)
  2. revise any milestones and completion dates that you established previously, including an explanation.

In evaluating your proposal and progress report I will check to see if your goals are realistic. A realistic project that is completed successfully will likely receive a higher grade than one that is too ambitious and doesn't get finished. Results alone are not adequate. You need to interpret them. If you have any questions about this, be sure and see me. If you do have an ambitious design, we can work together to set realistic goals. The project should be a polished piece of work.

Submit your Final report in hard copy form and electronically (e.g. html with ASCII and other attachments). I will give you instructions on how to submit an electronic copy later in the quarter. The report should be a polished piece of work.


Sample Projects from previous years

  • A Parallel Implementation of Tensor Multiplication Bryan Rasumussen (CSE 260, Fall 2006)
  • Parallelizing LU Factorization Scott Ricketts (CSE 260, Fall 2006)
  • Parallel Particle Packing, Richard Lohwasser and Chris Schroeder (CSE 260, Fall 2005)
  • A Spatial Database Implementation for 3D Computational Fluid Dynamics, Han Kim (CSE 262, Spring 2006)
  • Adaptive Coarsening in Two and Three Dimensions, Chris Schroeder (CSE 262, Spring 2006)
  • Fast Adaptive Storage and Retrieval, Jeremy Lau and Eric Hall (CSE 260, Fall 2002)
  • A Parallel Simulation of Mobile Ad-Hoc Networks, Ted Hromadka and Johann Ammerlahn (CSE 260, Fall 2002)
  • A Parallel Simulation of Traffic, Cynthia Bailey Lee (CSE 260, Fall 2002)
  • Message passing performance, Bob Boyer and Patrick Chase (CSE 260, Spring 2001)
  • Performance Comparison of MPI vs. Titanium, Roger Bharath and Stephen Lau (CSE 260, Spring 2001)

  •  18-Jan-2008 14:04