Free Trial
Free Trial
Student

Writing up simulation results in an engineering lab report

Key Takeaways

  • A simulated figure counts as evidence only when the model, the parameter values, and the solver settings are written beside it.
  • Stated assumptions and a comparison against a hand calculation turn a number into a result a marker can check.
  • A report is reproducible when a classmate can rebuild the model from the page and reach the same value.

A simulation result earns marks only when your report states what you modelled, which values you used, and why the number deserves belief.

Most weak reports share one habit. A waveform gets pasted in as a screenshot, a single number gets quoted beneath it, and the reader is left to guess the circuit, the parameters, and the solver settings that produced it. The fix is to treat every simulated figure as a claim that needs its inputs written beside it.

That standard matters well beyond coursework. A survey of working scientists found that 70% of researchers had tried and failed to reproduce another scientist’s experiments, which shows how often published work leaves out the details a second person needs. Write it so a classmate could rebuild your model from the page alone and land on the same result, and you’ve met the bar that engineering teams and journals expect.

What a good engineering lab report looks like

A good engineering lab report lets a reader who wasn’t in the lab understand what you did, check how you did it, and judge your result without asking you a single question. It states the objective, the method, the results with units, and a discussion that compares those results against theory or a hand calculation.

Picture two students who both report a converter output of 12 V. The first pastes a scope capture and writes that the circuit works. The second names the topology, lists the component values, states the time step, and shows the hand calculation the simulated value was checked against. Only the second report proves it. Knowing how to write an engineering lab report comes down to that difference. Headings such as objective, methods, results, and discussion are the easy part. The marks sit in the evidence under each heading.

What belongs in the methods section of a simulation report

The methods section of a lab report records everything a reader needs to rebuild your model and run it the same way. For a simulation, that means the circuit or system you modelled, every parameter value with units, the solver settings, the test conditions, and the point where you took each measurement.

A complete methods section for a simulation states these 5 things:

  • The system you modelled, shown as a labelled schematic or block diagram.
  • Every component value and source setting, with units.
  • The solver type, the time step, and the total simulated time.
  • The initial conditions and the operating point under test.
  • The measurement location and the window used for each reading.

Consider a student who reports inductor current ripple but never states the time step. A step that is too coarse will flatten the ripple and understate the peak, and the reader has no way to rule that out. One line in the methods settles it. Entries like this take minutes to write, and they’re what markers look for first.

How to document the assumptions behind your simulation model

Documenting simulation assumptions means writing down every simplification you made, the reason you made it, and the effect you expect it to have on the result. Ideal switches, a ripple-free source, a purely resistive load, and neglected parasitic resistance are typical entries for a power electronics lab.

Take the capacitor in a converter output filter. Modelling it as ideal removes the equivalent series resistance, which means your simulated voltage ripple will come out lower than a bench measurement on the same circuit. Stating that in advance turns a mismatch into a predicted outcome.

Assumptions are far easier to list when the model shows you what’s inside it. With open component models, you can open a block, read the values and equations it uses, and copy them into your report as written. You’ll find the assumption list is mostly a matter of reading what the model already states and deciding which entries affect your result.

“Stating that in advance turns a mismatch into a predicted outcome.”

How to present simulation results a marker will trust

How to present simulation results a marker will trust

Present simulation results as labelled figures and stated values that a reader can check against something independent. Every plot needs axis titles with units, a caption that says what was measured and under which conditions, and a comparison value from theory, a hand calculation, or a datasheet.

A waveform exported as a plot with a time axis in milliseconds and a voltage axis in volts tells the reader the scale at a glance. The same waveform captured as a screenshot of the scope window usually carries a dark background, unreadable tick labels, and no caption. Export the data and plot it properly. Then quote the number you’re claiming in the sentence that refers to the figure.

Comparison is what earns belief. A simulated ripple of 20 mV means little alone, but 20 mV against a calculated 20.5 mV shows the model behaves as the theory predicts. When the gap is large, don’t hide it, because a reasoned explanation of a 15% difference tells the marker more than an unexplained match.

One simulation result written up badly then properly

The same simulation result can be worthless or convincing depending on what surrounds it. A weak write-up gives a screenshot and a verdict. A proper write-up gives the parameter set, the solver settings, the measured value with units, and a check against a hand calculation, all in a few sentences.

Suppose you simulated a buck converter stepping 48 V down to 12 V. The weak version reads, “Figure 3 shows the output voltage. The ripple is small, so the converter works.” Nothing in those two sentences can be checked. Treat the stronger version as a lab report example for engineering courses, starting with the parameter set read directly from the SPS SOFTWARE model.

Parameter Value and the reason it is stated
Input source 48 V DC, modelled as ideal because supply ripple sits outside the scope of the lab.
Duty cycle and switching frequency 0.25 at 50 kHz, which sets the 12 V target and the ripple period.
Inductor 220 µH with no winding resistance, so conduction loss is excluded from the result.
Output capacitor 100 µF with no series resistance, so the simulated ripple is a lower bound.
Load 6 Ω resistive, drawing 2 A at the target output voltage.
Solver settings Discrete time step of 0.1 µs over 20 ms, giving 200 points per switching period.

The proper version then reads as follows. Output voltage settled at 12.0 V, with a ripple of 20 mV peak to peak measured over the final 1 ms of the run. The hand calculation for an ideal capacitor gives 20.5 mV, a gap of under 3%. Ripple on a bench circuit will be higher because the capacitor’s series resistance was neglected. Those four sentences give a reader everything needed to rebuild the model and test each claim.

What makes simulation results reproducible for another student

Simulation results are reproducible when another person can take your report, rebuild or open the model, run it with the stated settings, and get the same numbers. That requires the full parameter set, the solver configuration, the software version, and the model file itself.

Published research shows how rarely that standard is met without effort. When one research team requested the data and code behind 204 computational papers in a leading journal, they could reproduce the findings for only 26% of them. Details that feel obvious while you’re running the model vanish within weeks.

A simple test works before you submit. Hand your report to a lab partner and ask them to rebuild the result using only what’s written. Every question they ask marks a missing line.

Add the software version and the date of the run as well, since a default setting that differs between releases can shift a result without any visible cause.

“Engineers are trusted on the strength of results that others can check, and a lab report is the first place you practise writing that way.”

Why careful reporting matters beyond the final grade

Careful reporting matters because the habit outlasts the course. Engineers are trusted on the strength of results that others can check, and a lab report is the first place you practise writing that way. The habit shapes every design review and test record that follows.

Think about the person reading your work two years from now. It could be a supervisor deciding to approve a design, or you, reopening an old model to find out why a value was chosen. What they have is the page, and the page either carries the parameters, the assumptions, and the check, or it doesn’t.

SPS SOFTWARE keeps component parameters and model structure open to inspection, so documenting a result is a matter of recording what you can read. Students who need their own copy to produce the figures can use the educational offer. Whichever tool you use, write each result so a stranger could repeat it. That’s what the report markers remember.

Cart Overview