The following module learning objectives are applicable for this assignment:
- Model signals, fifilters and processes using computer packages.
- Design signal processing systems.
- Apply signal processing systems to classify signals and extract information.
- Evaluate signals and systems using laboratory test and measurement equipment.
The focus of this assignment is Parts 2 and 3 of the module, in particular content related to digital fifiltering and signal estimation.
2 Sessions and Support
There are 2 sets of in-person lab sessions as scheduled in Tabula to be held in A2.05a/b:
- Friday 18 November and Friday 25 November 1:00pm–3:00pm
- Friday 18 November and Friday 25 November 3:00pm–5:00pm
These sessions will begin and end promptly on time and you must attend your own sessions.
If you would like to change either of your sessions: You must fifind someone to swap with and both of you must email the module leader to confifirm that you agree. Otherwise, your entry at the other session may be refused.
Extra support can be obtained during the module leader’s support and feedback sessions in D2.05:
- Mondays 1:00pm–1:50pm
- Tuesdays 3:30pm–4:20pm
Finally, there is a support forum for all Lab Assignments (link) under the “Key Module Resources” heading on Moodle. Emailed questions will generally be re-directed to the forum unless the question is truly individual.
Email/forum cutoffff: In fairness to all students, the module leader will not respond to Assignment queries (either forum or email) sent after 10pm on Wednesday 30 November until after the submission deadline, unless there is an internal (i.e., university-side) problem with submissions.
3 Academic Misconduct
Your submission must be your own. Plagiarism of any kind is not acceptable and can result in a mark of zero. We have previously identifified many cases of academic misconduct (including plagiarism) that have resulted in penalties for the assignments in this module.
It is expected that you will discuss the assignment with your classmates. However, you should keep the following best practices in mind to avoid having your work flflagged for academic misconduct:
- Write your own code, comments, and written answers. Start from the provided templates.
- You should not adapt code from external sources, but if you do then they should be cited.
- Do not write your implementation together with another student and submit it as your own work. This includes talking through your implementation line-by-line. Such cases count as academic dishonesty.
- Do not share your assignment fifiles with another student. Allowing your work to be copied,even if it is modifified, counts as plagiarism.
- Do not use the fifiles of another student or other source as a starting point for your own submission. This still counts as plagiarism and can be flflagged by our academic integrity processes, even if you make changes!
4 General Instructions
Heads up regarding names:
These instructions include precise case-sensitive guidance
regarding names of fifiles, directories, functions, and variables. These must be followed exactly so that the marking scripts run correctly. There will be points deducted for any deviations.
This may seem pedantic, but precise naming is standard practice in programming and is essential for writing code that other people can rely on.
The instructions to complete this lab assignment are as follows:
- Download the zip fifile ES3C5_2022_2023_lab_data.zip (link) from the ES3C5 Moodle Page under the Assessment Information heading. Extract four fifiles from the zip fifile:
where <ID> is your student number.
- Download your signals fifile u<ID>_lab_signals.mat from the ES3C5 Coursework Lab Assignment Signals Files page (link) under the Assessment Information heading, where <ID> is your student number.
- Note: This is a separate download so that you do not need to download everyone else’s signals (over 100 MB).
- Rename the template fifiles as follows:
- ES3C5_2022_2023_lab_template.m to u<ID>_lab.m (where <ID> is your student number; don’t forget the “u” prefifix here!) and place the fifile in your MATLAB working directory (this should be a directory where you have write privileges on your computer).
- ES3C5_2022_2023_lab_template.docx to u<ID>_lab.docx.
and rename the function title in the fifirst line from
ES3C5_2022_2023_lab_template() to u<ID>_lab() (where <ID> is your student number).
Do not change the output argument Answers or any of the code in the top-level function.
You will be entering all of your code in the subfunctions. Also, do not change the output arguments of the subfunctions or add any input arguments.
- Complete the prescribed steps in the
(ES3C5_2022_2023_lab_recording.pdf) to record the audio data that you will use to answer the problems in Question 1. This data will be stored to the fifile u<ID>_lab_Audio.mat.
- Complete the problems listed below in Section 6 and refer to u<ID>_lab.txt for the functions and parameter values that you must use. You will also need to load signals from u<ID>_lab_signals.mat and there is already a call to do this as needed in the template code. Enter the required code in the corresponding subfunctions in u<ID>_lab.m; you should not need to write your own functions. The code must calculate the answers using your as signed parameters unless otherwise indicated. Take care to use parameters with the correct units for each MATLAB function that you call. For example, you may need to do conversions between radian and Hz frequencies, or convert gains between linear and dB forms.
- When a question includes plotting a fifigure, please account for the following:
(a) Every fifigure should be initiated by creating a new blank fifigure and your code should not close any fifigures.
(b) The plot function calls must be inside the subfunction code for the question, but details such as labels can be added after your solution function runs.
(c) Carefully consider appropriate parameter ranges and axis scaling, e.g., is it better for a given axis to be linear or logarithmic?
(d) ALL submitted plots must have labelled axes.
(e) Figures must include your student number and question number at the top.
(f) Each fifigure requested should be placed in u<ID>_lab.docx as a png image.
- Include readable comments in your code that brieflfly summarise your work, especially critical steps. See the subfunction Q0 below (and in u<ID>_lab.m) as a template example:
本网站支持 Alipay WeChatPay PayPal等支付方式
E-mail: firstname.lastname@example.org 微信号:vipnxx