There are four main tasks in this assessment; Task 1 Estimate the pathloss exponent of the given channel Task 2 Design and simulate the performance of Orthogonal Frequency Modulation (OFDM) in an Additive White Gaussian Noise (AWGN) channel Task 3 Simulate the above OFDM system in a multi-path fading channel Task 4 Design an appropriate coding scheme for the above OFDM system and simulate the coded OFDM performance in the given multi-path channel. While Task 1 can be completed independently, Task 2, code can be modified to complete the Task 3 and Task 3 code can be modified to complete Task 4. Preliminary Instructions You can extract the path loss data and the measured channel delay profile parameters by following the instructions . Each group will have a unique set of data based on your Team Number. Download the A2DataGen.p file from Canvas and place them into your working directory. Run the command ’A2GenData’ on the MATLAB command prompt to generate the data for your Team. Enter your team number when prompted. >> A2GenData >> Enter your Team’s number to generate the data: Its 9 for my group The Assessment data unique to your team will be stored in MATLAB data file called ‘channel.mat’. Use the MATLAB command ‘load’ to get the assessment data on to the MATLAB workspace. >>load ( ‘channel .mat ’ ) Note – Further details, including required content for the assessment can be found in this document: What you need to submit This assignment includes elements of written and coding assessment. The Report Component (up to 20 Pages) An outstanding report demonstrates knowledge and understanding of the subject area. It will communicate ideas clearly and logically with a combination of visual, mathematical and code assets. Correct information not articulated clearly will also attract deductions. Present the report so that it can be understood without reference to the assignment brief. Any figures or code referenced within the code should be no more than one page turn away. Document flow and coherency is to be prioritised. It is important that all relevant code and justification for each part is included in your report submission. Your report is being marked, your code is included for justification. Include a title page that states the unit name, unit code, assignment number, your name and student number. Do not include a table of contents, list of figures, nor a list of tables. Convert the report to the PDF file format before submission. This ensures document typesetting is preserved across different computers running different operating systems. The rubric that markers use to grade the assessment task is included and you should use it as a guide when working on the assessment task. The Code Component Working code is expected to be submitted alongside your report to Blackboard. The code needs to be executable (e.g. group_#.m) and without run-time error. Only include additional .m files if absolutely necessary. Code should be commented to describe intent. You may use the code provided in the weekly tutorials to check your solutions. However, you are expected to generate your own code for your assignment. Individual Reflections Each member of the group should write a reflection and appended to the end of your report. Include a short discussion (maximum 100 words) that addresses problems encountered, any lessons learned and things that you would have done differently. If you had any group concerns throughout the duration of your assignment, please address them here.
