What you’re reading is a companion to two things: a piece of software, and the book that grew up beside it. The software is the Abaqus INP Comprehensive Analyzer. The book is its Learning Center Companion Reader. Over the next little while, I want to walk you through both — not feature by feature, but idea by idea. I’ll start with the why, because the why is the whole point. Then I’ll take you category by category through the Reader, so that when you open it, you already know where everything lives and how to find what you need.

This walkthrough, the Reader it describes, and the tool itself were developed in collaboration with Claude, from Anthropic. I’ll come back to what that partnership means near the end. For now, let’s begin where every good analysis begins — with a question.

The First Why — Who Gets to Read a Simulation?

Here is the question. Who actually gets to read a simulation?

A finite element model lives in a file. In the Abaqus world, that file is the input deck — the .inp. It is the single source of truth for the entire analysis. Every node, every element, every material card, every load and boundary condition, every contact definition — all of it is written down in that one text file. If you want to know what a simulation really assumed, you don’t look at the colorful contour plot. You look at the input file.

And yet, for decades, reading that file required an expensive solver license and years of practice. The people who most needed to understand the model often could not even open it. The industrial designer who shaped the housing. The program manager deciding whether to ship. The young engineer learning the craft. The reviewer on a different network, far from a license server. All of them locked out of the very document that decides whether a product survives a drop, a shock, or a lifetime of vibration.

The Abaqus INP Comprehensive Analyzer was built to remove that lock. It opens any input file. It renders the model in three dimensions. It summarizes the bill of materials and the loading. It checks the material cards against best practice. And then it explains, in plain language, what it found — all without a solver license. That is the first why: to put the truth of the analysis back into the hands of everyone who has a stake in it.

The Deeper Why — Combating Engineering Mind Blindness

But a reviewer that only reports is doing half the job. The deeper why lives in a phrase I’ve carried for years: combating engineering mind blindness.

Mind blindness is the quiet failure mode of our profession. It is not the model that crashes. A model that crashes is honest — it tells you something is wrong. Mind blindness is the model that runs cleanly, finishes overnight, produces a beautiful stress plot, and is completely, confidently wrong, because a single assumption went unexamined.

I’ve seen it take many shapes. Mass scaling that quietly multiplied the inertia of the whole model, so a drop test reported forces that could never happen. A unit system error that turned five milliseconds into five seconds, off by a factor of a thousand, with no warning at all. Quasi-static material data — measured slowly, in a lab — driving a high-rate impact event, making a brittle part look tough. A single-point fracture value standing in for a material that tears at one strain in tension and a very different strain in shear. None of these throw an error. Every one of them misleads. The simulation looks plausible. The physics is fiction.

So the tool was designed to do what mind blindness cannot survive: to surface the questions. To notice the quiet assumption and say it out loud. Not to overrule the engineer — never that — but to make sure the engineer is choosing the assumption, rather than inheriting it by accident.

The Holistic View

And that is where the holistic view comes in, because checking a model is not enough. You have to understand it. It is not enough to be told that a displacement-based damage law is mesh-sensitive, or that slow material data is unsafe for a fast event. An engineer deserves to know why — well enough to argue it, well enough to defend it in a design review, well enough to feel it in the gut before the solver ever runs.

The holistic analyst doesn’t start with the mesh. The holistic analyst starts with the material — with how it actually behaves when you bend it, drop it, freeze it, or load it a thousand times a second. Glass is not a number; it’s a population of invisible surface flaws waiting for a tensile stress to find the worst one. A polycarbonate housing is ductile at room temperature and brittle in the cold. A weld line, where two flow fronts met inside the mold, can cut a material’s strain-to-break from a hundred percent down to fourteen. If you model the material as a tidy constant, you will be precisely, elegantly wrong. The holistic view asks you to respect the nature of the thing before you trust the number.

That is the spirit the Learning Center was written in. It does not just hand you rules. It teaches the reasoning behind the rules. And this Reader gathers all of that reasoning into one place — free, and meant to be read. Whether you are a student meeting modal analysis for the first time, or a seasoned analyst calibrating a ductile damage model at impact rates, the goal is the same: to make the reasoning visible.

A Guided Walkthrough of the Five Categories

So let’s open the Reader together. It is organized into five categories, in a deliberate reading order. We move from what analyses exist, to the materials they act on, to how to do the work well, to how the tool itself reasons on your behalf, and finally to a quick reference. Each topic carries a difficulty tag — beginner, intermediate, or advanced — so you can calibrate where to start. Let me walk you through all five.

1. Analysis Types

This is the lay of the land — the families of simulation you’ll meet in structural work, and how each one is built. We begin gently, with modal analysis: finding the natural frequencies and mode shapes of a structure, the equivalent of discovering the natural notes a guitar string wants to sing. From there it broadens. Shock analysis, for transient dynamic events. The shock response spectrum, for characterizing how a structure answers a sudden jolt. Random vibration, where the loading is described by a power spectral density rather than a single history. Harmonic response, for steady-state vibration. And static analysis, the implicit, patient cousin of the explicit world.

The category closes with three short pieces on step sequences — how you actually stack the pieces of a simulation in order: for static and quasi-static jobs, for impact and drop, and for perturbation and vibration. Think of this category as the map you consult first. If you’re not yet sure which kind of analysis your problem even is, start here. The beginner topics — modal and static — are the natural front door.

2. Materials

This is the heart of the Reader, and the largest of the five, with seventeen topics, because materials are where holistic thinking pays off the most.

It opens, fittingly, with glass — beginning with the nature of glass as a lived, flawed, statistical material, then moving into thin brittle modeling, Weibull statistics and fracture criteria, and the subtle world of edge quality, the heat-affected zone, and bend-radius design. From glass it moves through the families you meet every day: plastics and how they really fail; metals — steel, aluminum, and magnesium, in wrought, cast, and die-cast forms; elastomers and silicones, modeled as hyperelastic materials rather than with a simple modulus; and foams, like Poron, for cushioning and compressible seals.

Then it turns to the cross-cutting truths. There are guides to choosing materials for drop and impact, for static and structural work, and for modal and frequency analysis. There is a deep, careful topic on damage and failure modeling — ductile, brittle, and energy-based — which I think is the most important advanced topic in the whole book, because it’s the easiest to get wrong. And there are two essential companions: strain-rate dependency and temperature dependency, each comparing how metals, plastics, and glass respond when you load them faster or chill them down. The category is crowned by the holistic materials approach itself — the philosophy that ties the rest together. If you only read one category slowly, make it this one.

3. Best Practices

If the first two categories tell you what you’re doing, this one tells you how to do it without fooling yourself. There are seventeen topics here, and many of them are the hard-won habits that separate a defensible analysis from one that merely looks finished.

This is the home of the famous traps. Mass scaling and the unit-system traps — the silent killer I mentioned earlier, where a hidden factor of a thousand or a million quietly corrupts your inertia. The millisecond time trap, where the units look right and the physics is off by orders of magnitude. Alongside the traps are the constructive skills: energy-balance validation, so you can prove an explicit run is physical and not just pretty. Hourglassing and how to control it. Bulk viscosity for shock waves. Mesh convergence studies. Element selection and element types. Contact formulations, general versus pairs. Stabilizing a static analysis that has contact. Overmold and multi-part assembly with tie constraints. And output requests and post-processing, so you ask the solver for the right data in the first place. Reach for this category when your model runs but you don’t yet trust it. The answer to “why don’t I trust it” is almost always somewhere in here.

4. Behind the Scenes

This is the most unusual category, and in some ways the most honest. With nineteen topics, it pulls back the curtain on the tool itself — how it reasons, what it assumes, and where its limits are.

Some of these are guides to specific instruments inside the tool: the output request builder, the impact and drop analysis, the projectile and ball-drop evaluator, the boundary-condition and load viewer, the interaction viewer, the contact analysis, the surface-correction tool, and the convert-for-HyperMesh path. Others explain the quiet machinery: how three-dimensional rendering works in tessellated versus actual-mesh mode, how assembly instance transforms position your parts, how the tool merges nodes and handles a flat orphan mesh, how it tells engineering stress-strain from true stress-strain, and how it detects coincident surfaces and classifies your simulation’s intent.

But the two topics I’d point a new user to first are the most candid ones: the assumptions and limitations of the tool, and the engineering judgment notice. Together they say, plainly, that everything the tool reports is advisory. The tool surfaces questions. You answer them. It does not replace verification, validation, or the responsibility that comes with signing your name to an analysis. Read those two early, and you’ll read everything else in the right spirit.

5. Reference

It’s the smallest — just two topics — and it’s exactly what the name suggests. A complete guide to every item in the Tools menu, so you always know what each command does. And a clear explanation of the Abaqus step approach — how a simulation is built up, step by step, into the sequence the solver actually runs. This is the category you’ll return to quickly, mid-task, when you just need to confirm one thing and get back to work.

How to Use This Book

So how should you actually use this book? You can read it cover to cover, and the order is deliberate if you do. But you don’t have to. Every topic is written to stand on its own, and the difficulty tags are there to guide you. If you’re new, follow the beginner topics across the categories first — modal analysis, static analysis, understanding unit systems, the assumptions and limitations. If you’re experienced, dive straight into the advanced material on damage, fracture, and contact, and use the rest as reference. And whatever your level, let the cross-references carry you. The topics talk to each other, the way the physics does.

Everything in this Reader, and every flag the tool raises, is advisory. The tool surfaces the question. The engineer answers it. Trust nothing you cannot explain. That sentence is the difference between using a tool and being used by one.

A Word on the Collaboration

This Reader, the Learning Center it compiles, and the analyzer itself were developed together with Claude, from Anthropic. I want to be clear about why that matters, because it isn’t a footnote. The method here is to combine decades of hands-on simulation judgment — the kind that only comes from watching real parts crack on real test rigs — with a tireless partner for drafting, for checking, for explaining the same idea five different ways until it lands. The judgment is human. The reach is shared. And the aim, start to finish, has been to get the reasoning into the hands of as many engineers as possible. That, in the end, is what combating engineering mind blindness really means: not smarter software, but more engineers who can see.

Thank you for reading. This has been Joe McFadden.

Combating engineering mind blindness.

Engineer. Lifelong Learner. Holistic Analyst.

www.McFaddenCAE.com · McFadden@snet.net

Have a thoughtful and wonderful day.

Joseph McFadden https://www.mcfaddencae.com

Introduction .

Contents

Introduction