- Homework #9: Assignment - Matlab - Solutions
- Homework #8: Assignment - Matlab - Solutions
- Homework #7: Assignment - Matlab - Solutions
- Homework #6: Assignment - Matlab - Solutions
- Mini-Project #2: Assignment - Matlab - Solutions
- Homework #5: Assignment - Matlab - Solutions
- Homework #4: Assignment - Matlab - Solutions
- Homework #3: Assignment - Matlab - FourierSynthesisSquareWave.m - Solutions
- Mini-Project #1: Assignment - Matlab - Solutions
- Homework #2: Assignment - Matlab - Solutions
- Homework #1: Assignment - Matlab - Solutions

*Amount of work to show:*

- An explanation should be given for every single answer. Answers written without explanation will lose two-thirds of the points allotted for that part.
- Only "standard" formulas (like Euler's formula, trigonometric formulas, etc.) can be used without a reference. If you're using something non-standard, then please put a reference to the formula number in the book, or whatever source you got it from. Just using the final result of a similar problem done in the class, and omitting the intermediate steps, is not okay. You have to show show your work.
- There should not be big jumps in logic from one step to the next.
- For everything, expect to show at least one intermediate step between the first line and the answer. Even if it seems unnecessary to you, please err on the side of caution. Things that seem obvious to you when you're writing the solution are not quite so obvious for someone reading it.
- If you're in any doubt about how much work to show, please ask the instructor or the teaching assistant.

*MATLAB source code guidelines:*

- Put a comment before the solution of each part, telling the question number of the solution.
- If you’re using complicated logic, leave a comment telling what that block of code is supposed to do.
- Use variable names that related to their meaning/use.
- Avoid using two different variables for the same thing.
- Don’t overuse variables. It makes the code extremely difficult to read.
- Try to avoid using “magic numbers” in the code. If you’re using a number, write a comment telling me how you derived it.
- Make sure that your code will compile & run in a clean workspace; i.e., one without any variables present. Use a clear all; at least once before submitting it.
- No marks will be deducted based on the efficiency of the code unless the problem asks you to write efficient code.

*Technical points:*

- Merge all the files together into one PDF file.
- Ensure that the page orientation (after scanning) is correct.
- Please adjust the contrast, exposure etc., to get a good scan quality so that the TA can easily read what you write. Take extra care to get a good scan for parts written in pencil.
- For the MATLAB assignments, please copy the code into Word or include a screenshot showing the code. Do not submit handwritten code.

- All plots must have axis labels, with units.
- Final answers must be boxed, or underlined or otherwise differentiated from the rest of the solution.
- All final answers must have units, if they exist.
- Read the questions carefully.
- Try to answer all parts of a question together. If the solution to some parts of a question is written elsewhere, then leave a note telling me where to find it.

Last updated 12/12/17. Send comments to bevans@ece.utexas.edu.