CS4802 -- Lab 2: Histogram Equalization



->Courses
->STL Info
-->Oral Presentation
-->Lab 1
->Lab 2
-->Lab 3
-->Lab 4
->Electronic Submission
->Old Exams
->C++ Examples
->MSVC++ Info
->STL Info
->MFC/GUI Info
->Software
->Tentative Schedule
->Support Forum
->Course Policies

[Courses]
[Rich][Home][Rich]
[Author]

Winter Quarter 2000-2001

Procedures

Within the application framework developed for Lab 1, add the ability to perform a histogram equalization on the image currently being displayed. Your program should work for both grayscale and color images.

In addition, you should implement a localized histogram equalization function. This function should allow you to select the extent of the localized region.

Although not required, you may wish to develop a method of displaying the histogram of the image. This may prove useful when analyzing the before and after images.

You may work alone or with a partner.

Lab report (due 11:00pm, the day prior to week 5 lab)

The lab report should be in your own words and self-contained. By self-contained I mean that it should be possible for someone to understand what you did and why without seeing anything other than your report. Your report should include:

  • Problem Statement
  • Procedure (the steps you used to design your program, reasons for your design decisions, etc.)
  • Documented source code for your program. You may find it useful to use the code.bat and dump.bat batch files to produce one file containing all of your source code with the markup commands required by my electronic submission process.
  • Discussion (sample program output (both global and local HE) for at least these two images: haleBopp.jpg and room.png, answers to any questions, problems you encountered (and how they were overcome), etc.)
  • A list of any additional resources (e.g., libraries) with links to appropriate websites.
  • A summary of your activity log indicating how much time you spent on each phase of the assignment. Please report the time in the following categories:
    • Design
    • Coding
    • Debug (before you think it's working)
    • Test (after you think it's working)
    • Documentation
    • Other
  • If you worked with a partner, be sure to indicate what each of you did and did not do in completing this project.
  • Conclusions (what you learned, suggestions of how the assignment could be improved, things you would have done differently, etc.)

As with any report you submit, correct spelling and grammar are required. You will need to do two submissions. One submission should contain your written report in PDF format. The other submission should contain your documented source code (generated using the batch files provided above). Be sure to keep copies of all your files, in case something gets lost. It may be wise to keep a diskette backup as well.

Your grade will depend on quality of design, clarity of code and documentation, as well as whether your program produces the correct results. If you have any questions, consult your instructor.

© 2001 Dr. Christopher C. Taylor Office: CC-27C Phone: 277-7339 Last Updated: January 3, 2001
I am responsible for all content posted on these pages; MSOE is welcome to share these opinions but may not want to.