Computational Engineering / What computational engineering is
The computer as engineering assistant
What computation does well, what it does badly, and why the division of labour matters more than the tool.
Lesson review: expert verification remains open
This lesson has received a full-context editorial review and a check of its technical explanations. Selected arithmetic has been checked separately. This is not independent engineering sign-off.
Checks needed for project use
- A computational engineering reviewer must check algorithms, convergence claims, statistical assumptions and numerical examples beyond the cases explicitly recorded.
These are educational models and exercises. Check their assumptions before using the results. The full technical content and every diagram have not yet been independently verified.
Concrete and steel calculations retain their stated first-generation Eurocode teaching basis. Use the standards and amendments specified for your project; do not mix generations without an appropriate design basis.
Read the lesson register and outstanding review notesWhy this matters
Structural analysis software calculates responses for the model it is given. The engineer must decide whether its geometry, loads, restraints and other assumptions represent the question being investigated.
This course covers those modelling decisions and the checks needed before using the results. Module 9 explains enough of the solver mathematics to help you understand what the model does.
By the end of this lesson you should be able to
- Name what computation genuinely adds
- Name what it cannot add, precisely rather than vaguely
- Explain 'garbage in, garbage out' as a statement about responsibility
- Distinguish precision, accuracy and usefulness
What computation adds
Computation makes large equation systems practical to solve. A frame with 40,000 elements still requires more work on connectivity, conditioning and checking than a four-element model. Calculation cost depends on the equation system and solver, not simply on the element count.
Repeated calculations can use the same defined procedure. This helps with load combinations and option studies, although an error in the procedure can affect every case. Modules 14 to 17 cover exploration and optimisation.
Numerical methods also allow engineers to analyse geometries and loading for which a simple closed-form solution is unavailable, such as an irregular slab with openings. Time-dependent models can represent earthquake response or construction stages. Shared models can support coordination and provide a record of the design assumptions.
Engineering decisions and checks
The engineer must establish what the model represents and what it leaves out. Software can assist with these decisions, but the result still needs assessment against the intended use. A 40 mm deflection over a 6 m span must be compared with a relevant criterion; an upward load may be intended; a material modulus must have compatible units.
Check inputs, assumptions and outputs together. A model with incorrect restraints can produce converged results and plausible contours. Review the numerical solution and the representation of the structure separately. Using software does not remove the engineer's responsibility to assess whether the analysis is suitable; this lesson does not determine contractual or legal liability.
Three things that look like evidence and are not
Convergence. A nonlinear solver that converges has found a state satisfying equilibrium — for the model it was given. If the supports are wrong, it converges beautifully on the wrong structure. Module 12 has a case built precisely around this.
No warnings. Software warns about things its authors anticipated. The most dangerous errors are the ones that produce a clean run: a pressure applied inwards, a diaphragm that also restrains vertically, a member silently dropped in an import. All three appear later in this course and all three run without complaint.
A plausible picture. Contour plots are smoothed for presentation. Deflected shapes are magnified by whatever factor makes them visible. Both are designed to look reasonable, which makes them poor evidence that anything is.
Check yourself
A nonlinear analysis of a transfer structure converges in four iterations per load step with a tight residual tolerance and produces no warnings. What has been established?
Worked example
Does this need a computer at all?
Given
- A single simply supported beam, 7 m span, uniform load
- The question is whether a 406 × 178 × 60 UB is deep enough for deflection
- A model would take about forty minutes to build and check
Find
Whether to model it
Worked example
What a computer is actually good at
Given
- Two tasks: solving a 5 000-equation system, and deciding whether a support is really pinned
Find
Which is the computer's and which is the engineer's, and why
Practice
A hand calculation takes 2 minutes and a model takes 40 minutes to build. At how many repetitions of the same calculation do the two methods take equal time, ignoring the time to run the model?
Check yourself
What is the strongest argument for building a model rather than calculating by hand?
Check yourself
Which of these is a task a computer cannot take over?
Check yourself
An engineer says 'the software does the analysis, so I only need to check the output'. What is wrong with that?
Check yourself
Why is 'the computer got it wrong' almost always the wrong description of a failure?
Summary
- Computation adds scale, repetition, exploration, reach, simulation and a shared record
- It does not add understanding, judgement about what to model, or responsibility
- The output of a wrong model is indistinguishable in presentation from the output of a right one
- Convergence, absence of warnings and plots each support limited checks; none alone validates the model
- Report precision that is justified by the inputs, model and purpose of the calculation