GEORGIA INSTITUTE OF TECHNOLOGY
School of Electrical and Computer Engineering
ECE2025
Introduction to Signal Processing
Format for Formal Lab Reports
The format required for the formal lab reports is detailed
below. Each report should be a well-organized document that not only solves the lab
project, but also discusses the solution in a way that demonstrates your knowledge
of the topic.
- The total length of the report should be less than 12
pages (excluding the title page). If necessary, reduce the size of figures, use the
subplot command, etc.
- The font size must be greater than or equal to 10
point.
- The title page should contain the following
information: course name and section, report title, your name, name of your grader, and
date. See the example on the next page.
- Number all pages, figures, tables, etc.
- It is strongly recommended that the report be typed.
If you choose not type your report, you must neatly print your report and write on one
side of the page only. Regardless of whether you type or print your report, it is expected
that the report is well organized, neat, and easy to read.
- In order to make a professional looking report, use CUT and
PASTE so that you will have the text and graphics on the same page (i.e., graphics
should not be included at the end of your report). Matlab (current PC version) allows you
to copy the figure window, after which you can paste the graphic directly into a Word
document (or whatever windows-based word processor you’re using). If the version of
Matlab you’re using doesn’t allow you to copy figures, you may use the
old-fashioned method (scissors and tape).
- Figures, tables, etc. are not self-explanatory! All figures,
tables, etc. must be clearly and appropriately labeled. For example: "Figure 1.
Instantaneous Frequency Plot" is not an appropriate figure caption as it is
too vague (especially if you have several plots of the instantaneous frequency for various
cases). A figure caption is too vague if it could also describe another figure/table. A
more appropriate caption would be "Figure 1. Instantaneous Frequency vs. Time for
Case 1" (assuming the reader knows what Case 1 refers to, but you get the idea). In
addition, all axes on figures should also be labeled appropriately with the quantity
measured and the units. Finally, all figures, tables, etc. should be introduced and
explained within the text of your report.
- Matlab code should be presented as a figure (not as
part of the "text" of your report). In general, code should be adequately
commented. If the code is for a function, the comment/help section that explains the usage
of the function must be included.
- The report should begin with an Introduction section.
In this section, you should describe the objective or purpose of the project you are
reporting on, as well as any background information necessary to understand the rest of
the report. After reading the Introduction, the reader should have a general idea of what
your project is about and what the goals/objectives of the project were.
- The organization of the rest of the report is left up
to you; however, it must be well organized! One way to organize your report would be to
start with a general description of the overall system in terms of the major tasks
involved in your implementation of the system. Then, for each major section of the
project, explain the methods used to perform the section’s function and show any
supporting data, graphs, etc. you feel are necessary. Finally, explain how all the
sections put together implement the system in question. If in the project you are
implementing more than one system to perform the same (or similar) function, it is then
appropriate to compare and contrast the two systems (in a Conclusion section).
- You know you’ve done a good job in your reporting if a
fellow classmate of yours (who isn’t necessarily familiar with the lab you’re
reporting on) understands what the lab was about and could possibly reproduce what
you’ve done after reading your report. Also (and perhaps more importantly from your
perspective :-), the grader should be able to easily determine whether or not you
understand the concepts presented in the lab.
EXAMPLES: Mock examples of write-ups.
Sample 2 contains useful tips for writing the lab not included in Sample 1.
GRADING: The quality of the writing will be a factor
in the grading, so take some care in the presentation of your results. The only way that
this will work is if you do the solution well before the deadline and make a rough draft
of the write-up at least 24 hours before the deadline. Then, the all-important "last
minute" can be spent polishing up the write-up!
REALITY: The work you turn is, by default, assumed
to be yours alone. Other students are all working on the same lab, so you must limit your
discussions about the solution to general ideas (only a completely na? professor would
assume there is no discussion). Sharing/copying files that implement the solution is
obviously a violation of the Institute rules related to academic honesty, so you’d
have to explain that sort of behavior to the appropriate Dean. Likewise, the write-up must
not be plagiarized from other sources or from other students.
GEORGIA INSTITUTE OF TECHNOLOGY
School of Electrical and Computer Engineering
ECE2025 A4
Introduction to Signal Processing
Lab 2
Introduction to Complex Exponentials
Submitted by:
George P. Burdell
Submitted to:
Georgette P. Burdell
Submitted on:
January 1, 1999
|
