CSE 262 Class Projects (Spring 2006)

Your class project will count toward 60% of your grade. A project may be done individually or in teams of two, and you should allow 4 to 5 weeks to complete it.

Your project grade will be based on your successful completion of the following 3 parts:

  1. Project proposal: due Friday, April 21, 2006 (electronic, 1/10 of the project grade)
  2. Progress report: due Friday, May 19, 2006 (electronic, 2/10 of the project grade)
  3. In class presentation: Last week of classes (Tuesday and Thursday June 6 and 8, 2006)
    Presentation Schedule TBA
    Bring hard copies of your slides to class. (2/10 of your project grade)
  4. Final Report: due Friday, June 9, 2006, 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 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.

Your report should be a polished piece 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 is expected in the report, along with instructions for submitting an 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 2D or 3D adaptive coarsening, a lossy compression algorithm. Here is a short 4 page description of related work in one and two dimensions. A two person team would implement a scalable (i.e. parallel) version.
  • Implement and apply wavelet compression (lossy) of 2D and 3D datasets that will be provided to you.
  • Implement a scalable threshold detection algorithm.
  • Investigate the use of SQL in handling spatial queries, including performance, on 3D datasets.
  • Apply an available workflow tool to a data centric workflow, and qualify performance. Come up with optimization strategies.
  • Implement a spatial access method for a provided 3D dataset.
  • Apply machine learning techniques to studying turbulent fluid flow using a provided dataset.
  • Investigate an efficient scheme for spatial joins in 2D and 3D. A good reference is "Multi-step processing of spatial joins," by T. Brinkhoff et al., in Proc. Intl. Conf. on Management of Data (SIGMOD '94), pp. 197-208, 1994.

    • References will be provided as background for the above projects.

    Maintained by . Last modified: Sun Apr 2 17:15:00 PDT 2006