EE 422G (Sections 01 02)
Signals & Systems Laboratory, Fall 2009
Instructor: Kevin D. Donohue |
Office: 689 FPAT |
Email: donohue@engr.uky.edu |
|
Web Page: http://www.engr.uky.edu/~donohue/ |
Office Hours: Mon.
2:00pm - 4:30pm
|
Phone: 859-257-4004 |
TA: Mr. Jian Zhao |
Office: 591 FPAT |
Email: jzhao4@uky.edu |
Office Hours: Mon. 12-2PM |
EE 422G Lab Notes
Signals and Systems, 3rd ed., CT Chen, Oxford Press, ISBN-13: 9780195156614 (same texts as used in EE421G)
Expected Student Learning Outcomes
Students successfully completing this course must be able to:
Characterize random signals with correlation and probability density functions
Analyze discrete-time signals with the (discrete) Fast Fourier transform.
Design FIR and IIR filters based on signal and noise specifications.
Characterize system dynamics using impulse responses, transfer functions, and state-variable representations.
Simulate signals and systems using modern computer software packages
Design experiments to estimate signal and system model parameters from input and/or output data.
Course Summary
Lectures present new material on state variables and applications of random variables, as well as review topics from EE421G. Laboratory exercises provide opportunities for student to apply and implement concepts used in signals and systems to solve problems using modern engineering methods. Topics include noise models, filter design, modulation techniques, sampling, discrete Fourier Transforms, state variable models, and feedback design with an emphasis on using computer software for analysis and simulation.
Prerequisites
EE 421G and MA320. Students taking EE 422G must be able to: apply convolution and Fourier methods to determine the output of linear time-invariant systems; analyze continuous-time and discrete-time systems with appropriate transforms; characterize input-output relationships of linear time-invariant discrete-time systems using impulse response and transfer function representations; model random variation with distribution functions. Also it is helpful to have a background in matrix algebra and experience with programming languages such as Matlab and C++.
Class Email List:
To receive relevant communications and homework assignments for this class you must register for the list at the following web site: http://lists.engr.uky.edu/mailman/listinfo/ee422
Grading Undergraduate:
|
|
Pre-lab assignments (9) |
27 % |
|
|
Lab Team Plan (1) |
1 % |
|
|
Lab Reports (8) |
48 % |
|
|
Demonstration (2) |
4 % |
|
|
Laboratory Presence |
8 % |
|
|
Final Exam |
12 % |
Grading Graduate:
|
|
Pre-lab assignments (9) |
27 % |
|
|
Lab Team Plan (1) |
1 % |
|
|
Lab Reports (8) |
48 % |
|
|
Laboratory Exercise Design |
4 % |
|
|
Laboratory Presence |
8 % |
|
|
Final Exam |
12 % |
Undergraduate Students: Grades will be assigned using a10-point scale (A: 90+% of total points assigned, B: 80+%, C: 70+%, D: 60+%, E: Less than 60%.
Graduate Students: Grades will be assigned using a10-point scale (A: 90+% of total points assigned, B: 80+%, C: 70+%, E: Less than 70%.
Laboratory Reports: Each laboratory assignment is made up of two parts; the pre-lab (analysis and programming) and corresponding lab exercise (implement, measure, discuss, and interpret). The lab report will be due at the beginning of the next laboratory section meeting. Late assignments will be accepted with a 0.25 point per day penalty. You may work in groups up to 3 students in the laboratory; where each group turns in a single pre-lab assignment and a single lab report. The report is graded on organization, completeness, clarity, and accuracy. All lab reports must be prepared in a word processor and printed out. Programs written for the lab must be commented and placed in an appendix of the lab report. In the case of LabVIEW and Simulink programs, a screen shot of the block diagram (with descriptive labels) must be taken and included as figures in the lab report. (6 points per assignment)
Pre-Lab Assignments: Pre-lab assignments typically involve an analysis/synthesis of the system used in the experiment, or the development of a program template to be used in the lab assignment. The responses to the pre-lab questions must be handed in at the end of the lab period where the lab assignment was performed. You can hold on to the pre-lab assignment during the lab to use as a reference. There will NOT be enough time to do the pre-lab and the lab exercise in the 3 hour allotted period. If you do not finish the experiment in the 3 hour time period, you will not be allowed extra time. The pre-lab assignments can be handwritten, but must be legible and organized. The pre-lab is graded on completeness, clarity, and accuracy. (3 points per assignment)
Title Page: This includes your name, lab partner's name, title of lab experiment, date of experiment, and date of completing the final write up.
Objectives: Restate (copy) objectives from the lab assignment.
Solution/Procedure Description: For each lab you need to implement a design that was either presented in the lab assignment or the result of a pre-lab exercise. The reader should be able to repeat your results based on the description provided (without reference to the original lab assignment document). Solutions or implementation strategies for each lab assignment will have multiple procedures and you need to describe each one. If a program was written to implement a solution, do not copy and past the program in the text. Describe what the program does (functional description) and include the actual code in an appendix. A flowchart may help clearly explain the program. The "how" questions for obtaining the results are answered in this section. When grading this section the reader will ask the question, "Can I repeat these measurements from the information given?" If it is not clear (as a result of missing, poorly organized, or ambiguous information), then points will be lost (2 points).
Presentation of Results: For each solution/procedure efficient methods and statistics must be used for presenting the results. This typically includes performance metrics presented in tables and/or waveforms in figures. All axes must be labeled as well as columns and rows of tables. All figures and tables should be numbered and referred to in the text. Do not include a table or figure without introducing and explaining it within the text. The actual data generated/recorded must be presented in this section along with any analysis (formula or code description) used to estimated parameters or functions of the original data. The “what” questions concerning the results are answered in this section (2.5 points).
Discussion of Results: This section primarily makes reference to the results to explain them relative to the underlying theories presented in the systems and systems course and/or limitations of the experiment/simulation. It typically includes a comparison of results between the implementation and the pre-lab predictions. There are discussion questions in the lab assignment to help direct your writing. Make sure you address these questions in your report, in addition to whatever other issues you as an engineer consider significant or important. It should NOT simply be a questions-answer format but a narrative that addresses these questions in coherent stream of ideas. The "why" questions concerning the results are answered in this section. (1 point)
Conclusions: Summarize your results relative to the lab objectives. Assess how well the lab met the objectives. If applicable, suggest ways to improve the experiment, or how you may do things differently if experiment was repeated. (.5 point)
Lab Team Plan: The first lab group activity is to determine how the workload should be divided up with agreed-on expectations for each member. The main tasks are programming, storing, processing, and presenting data, completing the pre-lab assignment, organizing and writing the lab report, and proofreading and editing the lab report. For each lab (1 through 8) clearly delineate responsibilities. Also indicate scheduled times outside of the lab and lecture meetings to work on the pre-lab and lab reports. Since this is a 2 credit hour lab, 4-6 hours per week should be scheduled outside of class time to complete pre-lab and lab write-up assignments. A good lab plan lists the major components for each lab assignment, the person responsible, and the tentative time in the week that will be devoted to it over the whole semester. Make sure all 8 labs are covered by this plan. This will be handed in at the lecture following the first lab, so some modification can be made after doing the first lab. This is a tentative plan and can change with mutual agreement between lab partners. (2 points)
Laboratory Presence: All team members must be ready for work at the beginning of class. There will be a sign in sheet when you enter the laboratory. You will put the time at which you arrived next to you name and sign in. If you are less than 15 minutes late you will loose 0.5 points from the laboratory presence sore. If you are over 15 minutes late you will loose 1 point. If you are over an hour late you will not get credit for the lab assignment. You can loose up to 8 points by being late over the course of the semester.
Lab assignments can be made up only in the case of excused absences. The lab reports are due in the next lab meeting after the lab where measurements are made.
EE422G Topics:
Labs will be implemented in Matlab, Simulink, and Labview. Some extra labs and lecture time will be given to some of the more involved topics.
Lab1. Sampling and Quantization (Aliasing and Noise)
Lab2. Signals and Noise Characterizations (Correlation and Spectrum)
Lab3. FIR Filter Design
Lab4. IIR Filter Design
Lab5. Filter Application using signal and noise models
Lab6. Digital communication channel (Distortion and Noise)
Lab7. Correlation receiver simulation and performance (Matched Filter)
Lab8. Modulation
Lab 9. PID control
Unethical behavior (cheating): The following activities are unethical:
Using data you did not measure
Recording values you did not observe
Copying a portion of work belonging to someone else
Any of these will result in the consequences described in the university’s policy on academic dishonesty. (see http://www.chem.uky.edu/research/grossman/acadoffenses/index.htm ).
|
Tentative Course Schedule EE422G |
||||
|
Week |
Lecture Dates |
Lecture Topics |
Laboratory Sessions |
Assignments |
|
1 |
8-26 (Intro) |
Lab and course policies, Course overview, Laboratory Software |
(no lab session meetings)
|
|
|
2 |
9-2
|
Review of signal and system concepts |
(no lab session meetings)
|
|
|
3 |
9-9
|
Review of signal and system concepts |
9-14,15 (Tutorials on Software)
|
|
|
4 |
9-16 |
Sampling and Quantization |
9-21,22 |
|
|
5 |
9-23 (Lab 2) |
Noise and Signal Characterizations |
9-28,29
|
Lab 1 due
|
|
6 |
9-30 (Lab 3) |
Finite Impulse Response (FIR) filters Noise Models |
10-5,6
|
Lab 2 due and Lab Plan |
|
7 |
10-7 (Lab 4) |
Infinite Impulse Response (IIR) filters |
10-12,13
|
Lab 3 due |
|
8 |
10-14 (Lab 5) |
Filter Application using signal and noise models |
10-19,20
|
Lab 4 due |
|
9 |
10-21 (Lab 6) |
Digital communication channels |
10-26,27
|
Lab 5 due |
|
10 |
10-28 (Lab 7) |
Correlation receiver simulation and performance estimate |
11-2,3
|
Lab 6 due |
|
11 |
11-4 (Lab 8) |
Modulation |
11-9,10 |
Lab 7 due |
|
12 |
11-11 (Program ) |
Modulation LabVIEW Program |
11-16,17
|
Lab 8 Due, Lab Demonstration |
|
13 |
11-18 (Lab 9) |
PID Control, State Space Models |
11-23,24
|
|
|
14 |
11-25 (No Lecture) |
|
11-30,12-1
|
Lab 9, Pre-lab and Lab Demonstration |
|
14 |
12-2 Review |
PID Control, State Space Models |
12-7,8
|
Lab 9 Lab Demonstration |
|
15 |
12-9 Review
|
|
|
|
|
|
12/14/09 |
Final Exam 8:00 AM |
|
|