CSE 262 Class Projects (Spring 2007)

The class project will count toward 60% of your grade. A project may be done individually or in teams of two, and you should allow about 6 or 7 weeks to complete it. Your project grade will be based on your successful completion of the following 3 parts:

  1. Project proposal: due Thursday, April 26, 2007 (electronic, 1/10 of the project grade)
  2. Progress reports: weekly project reports are due each Friday by 5pm (electronic, 1/10 of the project grade). You’ll be asked to make brief presentations (5-10 minutes) in class introducing the project, and charting progress.
  3. Project presentations: Last week of class, Tuesday and Thursday June 5 and 7, 2007)
    Bring hard copies of your slides to class. (2/10 of your project grade)
  4. Project Report: due Friday, June 8, 2007, 5PM, in EBU3B 3244 (Hard copy and electronic)

A list of projects appears below. If you have your own project in mind, discuss it with me first.

Your project proposal should identify the investigator(s) and the title of the project. You should present a preliminary list of milestones –with completion dates – and possible options depending on your progress. Your milestones are not binding, so be realistic. You may need to fine-tune your goals 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. If you are proposing your own project, include a description of the project that is roughly one double spaced page long. I will give you feedback once I've read over you proposal.

All of your proposals should address the following issues:

  1. The goals of your project. Be sure to address why you think that the goals are realistic. (This is why I've asked you to provide milestones.)
  2. The result(s) you want to demonstrate.
  3. The significance of the results.


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

  1. discuss your progress to date. If you are working in a team, discuss the division of labor and other aspects of how you worked together as a team team (This need not be as formal as the Team evaluation that you will submit in your final project at 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.

Project Presentation and Report

During the last week of class, you’ll give a 25 minute presentation. Your project report is due at the end of the week. The presentation and report should be polished pieces of work. Submit hard copy as well as an electronic version, e.g., html with ASCII and other attachments. Here is a discussion about what I am expecting in the your presentation and report, along with instructions for submitting electronic copy.


Projects

Here is a tentative list of projects, but if you have a project of your own that you'd like to work on, let me know. Most of these can be formulated as one or two investigator projects. This list will grow over time, so please check accordingly.

  • Implement Ray Tracing on the STI Cell. If you want to use Cell, we should start early on (first week of classes) to set up the testbed and to accommodate the learning curve of the system.
  • EM3D is a microbenchmark that solves a partial differential equation using finite element meshes. Code is available in the Titanium programming language. Convert the code to Uniform Parallel C, studying language performance issues, including scalability.
  • Poisson's equation is ubiquitous in many area of science and engineering, and there are many approaches to solving it, depending on the initial data. Implement two methods--an FFT method and multigrid-- and asses scalability and other performance issues on thousands of processors. For this project you will use SDSC's DataStar and Blue Gene/L systems.
  • References will be provided as background for the above projects.


    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)

  • Maintained by baden @ ucsd.
    edu   [Tue Feb 6 21:47:40 PST 2007]