Instructor: Kevin D. DonohueOffice: 689 FPATEmail: [email protected] Hours: Tuesday 3:00pm - 5:00pm Thursday 9:00am - 11:00amPhone: 859-257-4004TA: Mr. Yang LiuOffice: 520 CRMSEmail: [email protected] Hours:Texts:Lab Report Format: Lab reports must be prepared with a word processor and organized according to the following format:EE 422G: Signals & Systems LaboratorySpring 2008Instructor: Kevin D. Donohue Office: 689 FPAT Email: [email protected] Page: http://www.engr.uky.edu/~donohue/Office Hours:Tuesday 3:00pm - 5:00pmThursday 9:00am - 11:00amPhone: 859-257-4004TA: Mr. Yang Liu Office: 520 CRMS Email: [email protected] Hours:Wednesday 3:00 pm – 5:00pmTexts:1. EE 422G Lab Notes2. M.J. Roberts, Fundamentals of Signals and Systems, McGraw Hill, 2008. (ISBN 978-0-07-340454-7)Expected Student Learning OutcomesStudents successfully completing this course must be able to:1. Characterize random signals with correlation and probability density functions2. Analyze discrete-time signals with the (discrete) Fast Fourier transform.3. Design FIR and IIR filters based on signal and noise specifications.4. Characterize system dynamics using impulse responses, transfer functions, and state-variable representations. 5. Simulate signals and systems using modern computer software packages6. Design experiments to estimate signal and system model parameters from input and/or output data.Course SummaryLectures present new material on state variables and applications of random variables, as well as review topics from EE421G. For the transition version of this course, extra lectures will be given during lab periods to cover the material missed by the old version of EE421G. In particular, discrete-time signals will be covered starting with the sampling theorem through the Z-transform. Homework assignments and quizzes will be given over this material. 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.PrerequisitesEE 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 modulation systems and filters, Analyze discrete-time systems with the difference equations and z-transforms, Characterize input-output relationships of linear time-invariant discrete-time systems using impulse response and transfer function representations, model random variation with common 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/ee422Grading:Pre-lab assignments (9)Lab Team Plan (1)27% 2%Lab Reports (8)Demonstration (2)48% 5%Homework/Quizzes 18%Graduate students taking this course will have more difficult homework assignments and quiz questions commensurate with the analysis expected of a student with a completed Bachelor’s degree.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, 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 the 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 (withdescriptive labels) is sufficient.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 typically 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 andorganized. The pre-lab is graded on completeness, clarity, and accuracy. Lab Report Format: Lab reports must be prepared with a word processor and organized according to the following format:- 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 some design concept that was either presented to you or resulted from a design that you solved for. 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