summaryrefslogtreecommitdiff
path: root/report/instructions.md
blob: 7fe7f7e8505d110604f041c7fbe6a03fa051cb94 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
## Email 1
There have been a lot of questions about the format/content of the report. This should include:

1) All the code, well commented/explained. That means explain how the algorithm works and how it solves the given ODE/PDE, or how error the analysis is carried out and what it means.

2) All plots, with brief comments explaining the physical significance of the solutions in the plots, e.g. things like resonance, transient/steady-state, corner frequency.  In Q1-3, that is in the context of the circuit. In Q4 you may use the idea of heat distribution in a rod.

Above all, you should write as if for one of your peers: your audience is someone with your level of knowledge of Mathematics and Circuits, but who doesn't know this particular topic, and you are explaining it to them. 

This report is what you submit as paper copy on 13 March by 4pm. On Blackboard there will be a link to submit the report and, separately, the program files, before 22:00 on 13 March. Please do not submit zip-files: each file report.pdf and code.m needs to be submitted. One team member to submit on behalf of group. Please include group number in the filename.

## Email 2
You should aim to explain your results to someone at your level of Mathematical maturity: your audience is your peers. Don't repeat what I did in lectures, but make sure you explain what YOU did: in the code, the figures, etc. You should explain the behaviour of the solutions in terms of the behaviour of the underlying circuits. Above all, the report should be easy to read: put the plots where they belong: in the text where you first discuss them.