Part 5

May 28

Written By Joseph McFadden

ABAQUS INP COMPREHENSIVE ANALYZER

Under the Hood — A Deep-Dive Series

PART 5

The Learning Center

Topics, Analysis Types, and the Example INP Generator

Joseph P. McFadden Sr.

McFaddenCAE.com | The Holistic Analyst

Setup — Why a Tool Has a Learning Center

The first four parts of this series have described a tool for analyzing Abaqus input files. Every capability covered — parsing, geometry extraction, material analysis, export — serves an engineer who already has a model and wants to understand or improve it.

The Learning Center is different. It is for the engineer who is still building their understanding of what the model should be doing in the first place.

This distinction matters. A tool that only analyzes existing models assumes that the analyst already knows what a good model looks like. In practice — especially in organizations where simulation has grown faster than training — that assumption does not always hold. People inherit models, copy templates, follow procedures, and run analyses without fully understanding what each keyword does, why it is there, or what happens if it is wrong.

The Learning Center is the explicit acknowledgment that the tool has a responsibility beyond analysis. It should also teach. It should explain the underlying engineering so that the analyst builds the critical thinking framework to evaluate their own work, not just execute a procedure.

It is also the bridge between this tool and the McFaddenCAE.com audiobook series — four volumes of FEA best practices content covering unit systems, element selection, contact, mass scaling, energy balance, modal analysis, and more. The Learning Center inside the tool is the companion reference that points back to that deeper material.

Section 1 — Architecture: Topics, Categories, and Difficulty Levels

The Learning Center tab is built with a two-panel layout that mirrors the other analytical tabs. On the left, a topic list with filter controls. On the right, a content display area with a Generate Example INP button that activates for specific topics.

The topic list is populated from two sources. The first is a set of built-in analysis type topics — five analysis workflows defined directly in the main program. The second is the best practices module, imported at startup, which contributes a library of engineering best practice topics built from the same module architecture described in Part Three.

If the best practices module is not available — for example, on a minimal installation where only the core analyzer file is present — the topic list falls back gracefully to just the five analysis type topics. No error, no crash. The content that is available is shown; the content that requires the external module is silently absent.

Difficulty Levels

Each topic carries a difficulty rating: Beginner, Intermediate, or Advanced. A row of radio buttons — All, Beginner, Intermediate, Advanced — filters the list by level. Green circle icons mark beginner topics, yellow mark intermediate, red mark advanced.

The difficulty ratings are honest. Modal analysis is labeled Beginner not because it is simple to do well, but because the conceptual entry point — what is a natural frequency, how do you extract one — is accessible without extensive background. Shock Response Spectrum is labeled Advanced because it requires understanding of modal superposition, damping, and the convolution mathematics behind the spectrum concept before the analysis result means anything.

This level tagging serves a navigation purpose. A new hire encountering FEA for the first time should start with Beginner topics. An experienced analyst looking to fill a specific gap can jump directly to Advanced without sifting through foundational material they already know.

Section 2 — Modal Analysis: Natural Frequencies and What They Mean

The modal analysis topic is the recommended starting point for anyone who has not worked with dynamic analysis before. It covers one of the most fundamental concepts in structural mechanics: the natural frequency.

The opening metaphor in the topic content is the guitar string. A string under tension has a set of frequencies at which it naturally vibrates — the fundamental tone and its harmonics. A structural component has the same property: it has frequencies it prefers, and if it is excited at those frequencies, it responds with amplified motion.

This is resonance. And avoiding resonance — or designing for it — is the primary reason you run modal analysis.

The governing equation of modal analysis is: the stiffness matrix times the mode shape vector equals ω² times the mass matrix times the mode shape vector. ω is the natural circular frequency in radians per second. Frequency in hertz is ω divided by 2π. The mode shape vector, called the eigenvector, describes the relative displacement pattern of every node in the structure at that frequency.

This is an eigenvalue problem — the same class of mathematical problem that appears in quantum mechanics, principal component analysis, and image compression. The word eigen is German for characteristic. Natural frequencies are the characteristic frequencies of the structure's stiffness and mass distribution.

The Perturbation Restriction — Non-Negotiable

The topic content includes a section labeled CRITICAL: PERTURBATION LIMITATION, and it deserves the emphasis. Modal analysis is a linear perturbation procedure in Abaqus. This means two things that are absolute.

First, contact elements cannot be used. Full stop. A contact pair introduces nonlinearity — the stiffness depends on whether surfaces are touching or separating. Linear perturbation procedures assume the stiffness is constant. Abaqus will either error out or produce meaningless results if contact is present in a perturbation step. Bolted joints, press fits, gaskets, and any interface that uses contact pairs must be replaced with tied constraints or merged nodes before running modal analysis.

Second, material nonlinearity and large deformations are not captured. Modal analysis computes the linearized dynamic response around the current state. If your structure is pre-stressed — compressed by a bolt load, for example — you would need a preload step followed by the perturbation step to capture the stress-stiffening effect correctly.

The same perturbation restriction applies to every frequency-domain analysis in the Learning Center: harmonic response, random vibration, and Shock Response Spectrum all share this limitation. The topic content states this explicitly for each analysis type, not just for modal, because the mistake of leaving contact elements in a perturbation model is common enough that it deserves repetition.

Mode Shapes Are Relative, Not Absolute

Mode shapes show relative displacement patterns, not absolute physical displacements. A mode shape tells you which nodes move and in what pattern relative to each other. It does not tell you how far they actually move during a real event.

To get actual displacements, stresses, and strains from modal data, you must run a response procedure — harmonic analysis for sinusoidal excitation, random vibration for broadband stochastic excitation, or Shock Response Spectrum for shock environments. Modal analysis alone cannot give you those results, no matter how many modes you extract or how accurate your model is.

This is one of the most persistent misunderstandings in the use of modal analysis, and the Learning Center content addresses it directly rather than assuming the analyst will discover it through painful experience.

Section 3 — Shock Analysis: Time Domain, Pulse Shapes, and MIL-STD

Shock analysis — labeled Transient Dynamic in Abaqus — simulates the time-domain structural response to a sudden impact or rapid acceleration event. Unlike modal analysis, which finds the structure's inherent character, shock analysis asks how the structure responds to a specific input.

The input is defined as a base acceleration time history — the ground motion applied to the support points of the structure. The structure is typically fixed at its mounting interface, and the analysis drives that interface with the prescribed acceleration pulse. The solver integrates the equations of motion forward in time, capturing how the structure deforms, where stresses develop, and how energy distributes through the assembly.

Pulse Shapes and Their Physical Meaning

The topic content covers three standard shock pulse shapes with their physical contexts, because the choice of pulse shape is not arbitrary — it reflects the nature of the physical event being simulated.

The half-sine pulse has the form: acceleration = peak × sin(πt/T), where t is time and T is the pulse duration. The acceleration starts at zero, rises smoothly to the peak, and returns smoothly to zero. This shape closely approximates what happens when a product drops onto a relatively compliant surface — a rubber pad, a carpeted floor. The smooth onset and offset produce a pulse with moderate high-frequency content. The classic benchmark is 100 G at 11 milliseconds, which is the standard for much consumer electronics drop qualification.

The terminal peak sawtooth pulse ramps linearly from zero to peak, then drops abruptly to zero at the end of the pulse. The abrupt termination introduces high-frequency content in the spectrum — more energy at higher frequencies than the half-sine of the same peak and duration. This shape is representative of pyroshock events: the firing of explosive bolts, stage separation in a launch vehicle, or any event with a sharp termination. More severe than the half-sine at the same nominal parameters.

The square wave pulse holds constant acceleration for the full duration, then drops instantly to zero. It is the most conservative of the three shapes — for a given peak G and duration, the square wave delivers the maximum velocity change, which is the time integral of acceleration. Used for worst-case analysis when the actual pulse shape is uncertain or when the specification demands the most demanding achievable input.

Velocity Change — The Physical Quantity

The topic content introduces velocity change — ΔV — as the physical quantity that characterizes shock severity more completely than peak G alone. Two shocks with the same peak G but different durations deliver different velocity changes and produce different structural responses.

Velocity change is the area under the acceleration-time curve — the integral of acceleration. A 100-G half-sine at 2 milliseconds delivers a smaller velocity change than a 100-G half-sine at 11 milliseconds, even though both have the same peak. The 11-millisecond pulse has five and a half times more area. This means it excites lower-frequency modes more strongly and produces larger structural deformations in flexible assemblies.

Understanding velocity change as the governing severity parameter — not just peak G — is the conceptual shift that separates engineers who can reason about shock environments from those who can only follow a specification number.

Section 4 — Shock Response Spectrum: From Time History to Frequency Summary

The Shock Response Spectrum topic is labeled Advanced for good reason. Understanding it requires synthesizing several concepts: natural frequencies from modal analysis, transient response from shock analysis, and the idea of a single-degree-of-freedom oscillator as a measuring instrument.

Here is the concept. Imagine a simple spring-mass system — one mass, one spring, and some damping — attached to a moving base. Subject the base to a shock pulse. The mass responds. Measure the maximum absolute acceleration experienced by the mass. Now change the spring stiffness so the system's natural frequency is different. Subject the base to the same pulse. Measure the new maximum acceleration. Repeat for many different natural frequencies.

Plot those maximum accelerations as a function of natural frequency. That plot is the Shock Response Spectrum (SRS) of the input pulse. It tells you: for a structure with a given natural frequency, what is the worst acceleration it will experience when subjected to this shock?

The SRS is not a measurement of the shock pulse itself — it is a summary of the shock pulse's effect on structures with different natural frequencies. Two shock pulses with very different time histories can produce very similar SRS curves if they are equally damaging to structures across the frequency range of interest. Conversely, two pulses that look similar in time can be dramatically different in the SRS domain if one has more high-frequency content.

In Abaqus, SRS analysis is a two-step procedure. Step one is modal analysis: extract the natural frequencies and mode shapes of the structure. Step two is the response spectrum step, which applies the spectrum loading and uses the modal superposition principle to compute peak responses. The response to each mode is computed from the spectrum value at that mode's frequency, then the modal responses are combined using a combination rule — typically SRSS (Square Root of the Sum of Squares) or CQC (Complete Quadratic Combination).

Because step two is a perturbation procedure — it uses linear superposition of modal responses — the contact restriction applies here too. All the warnings from the modal analysis topic carry over.

The topic content flags a specific practical issue for consumer electronics applications: the SRS is the standard method for qualifying equipment under MIL-STD-810 Method 516 shock and for analyzing pyroshock environments in aerospace. If you are working on hardware that needs to survive these environments, understanding the SRS is not optional.

Section 5 — Random Vibration: Statistical Energy in a Frequency Band

Random vibration analysis addresses a different class of loading than shock. Shock is a deterministic event — it has a specific time history, even if you have to approximate it. Random vibration is inherently statistical: the loading is described by its power spectral density (PSD), which gives the average energy content per unit frequency as a function of frequency, rather than as a time trace.

The physical scenarios that produce random vibration are environments where the driving source is stochastic: road surface roughness driving vehicle vibration, jet engine noise driving aircraft structure, rocket motor combustion driving launch vehicle structure, fans and pumps driving equipment enclosures. None of these have a fixed repeating waveform. They have statistical properties — a characteristic PSD — that remains roughly constant over time.

The Power Spectral Density is expressed in units of G²/Hz. The area under the PSD curve over a frequency band gives the mean square acceleration — the statistical average of the squared acceleration — in that band. The square root of the total area is the root mean square (RMS) acceleration, which is the single most commonly reported metric for random vibration severity.

In Abaqus, random vibration analysis is a linear perturbation procedure that uses the modal superposition framework. The structure's natural frequencies and mode shapes, extracted in the modal step, are combined with the input PSD through a mathematical operation called the frequency response function. The output is the PSD of the structural response — stresses, displacements, accelerations at every location in the model — as a function of frequency.

The results are statistical. A peak stress output from random vibration analysis is not the actual stress at a given instant — it is a one-sigma value, meaning it is exceeded with a probability determined by the statistical distribution of the response. For fatigue life prediction, you typically work with three-sigma values — three times the RMS stress — as the effective peak stress, based on the assumption of Gaussian response statistics.

This statistical nature is one of the reasons random vibration analysis is labeled Advanced. The numbers require interpretation through a probabilistic framework, not just a direct comparison to a yield strength. An analyst who reads a peak stress output from random vibration as if it were a deterministic result will draw incorrect conclusions.

Section 6 — Harmonic Response: Steady-State Under Sinusoidal Excitation

Harmonic response analysis — called Steady-State Dynamics in Abaqus — computes the structural response to a continuous sinusoidal excitation as a function of excitation frequency. The result is a frequency response function: amplitude and phase of the structural response at every frequency in the sweep range.

The physical scenario is a structure being driven by a sinusoidal source at a constant amplitude as that source's frequency is swept through a range. A motor with an imbalance. A fan blade at a harmonic of the rotation frequency. An acoustic cavity resonating a panel. These are the environments where harmonic response analysis is appropriate.

The analysis identifies resonance peaks — frequencies where the response amplitude is amplified — and shows whether any of the structure's natural frequencies fall within the operating frequency range of the excitation. It also shows the phase relationship between input and response, which matters for active vibration control design.

Damping plays a critical role in harmonic response in a way that it does not in modal analysis. In modal analysis, damping slightly shifts natural frequencies and affects the rate of decay in transient response, but the undamped natural frequencies are the primary output. In harmonic response, damping determines the peak amplification at resonance. Without damping, resonance produces infinite amplitude — a mathematical singularity. With damping, the amplification at resonance is limited to 1/(2ζ), where ζ is the damping ratio.

Defining damping correctly — and knowing where your damping values came from — is therefore critical for harmonic response analysis in a way it is not for modal extraction. The topic content addresses this and cross-references the modal analysis audiobook, which covers damping estimation in depth including how to derive damping without test data.

Like all perturbation procedures, harmonic response cannot use contact elements. The same tied-constraint substitution required for modal analysis is required here.

Section 7 — Jerk and Fragility: Beyond Peak G

The jerk and fragility topic is labeled Best Practices and Advanced. It extends the shock analysis framework to include a quantity that standard analysis ignores: jerk, the time derivative of acceleration.

Acceleration describes force per unit mass at a given instant. Velocity change describes the impulse — the integrated effect over the pulse duration. Jerk describes how rapidly the acceleration is changing.

Jerk matters because components with finite stiffness at their mounting interfaces respond to rates of change in the acceleration environment, not just to peak values. A connector, a solder joint, a delicate MEMS sensor — these components see stress proportional not just to the peak G but to how quickly the G reaches its peak. A sharp-onset pulse with high jerk is more damaging to fragile components than a smooth pulse with the same peak G.

Fragility in the engineering context refers to the maximum G-level a component can withstand without functional failure — a threshold, not a strength in the structural sense. Fragility assessment is the process of determining whether the input shock environment exceeds the fragility threshold of the most sensitive component in the assembly.

The topic content covers the relationship between velocity change, jerk, and fragility in terms of product drop height analysis. Given the drop height, you can estimate the velocity change at impact. Given the impact surface compliance and the system's mass, you can estimate the pulse duration and shape. From those, you can estimate peak G and jerk. From those, you can assess whether the fragile components in the assembly will survive.

This is a systems-level analysis, not just a finite element analysis. The value of including it in the Learning Center is that it places the FEA work in a broader engineering context. The simulation result — a peak stress or a peak acceleration at a component location — only has meaning when interpreted against the fragility threshold of that component. A simulation that produces an acceleration value without the analyst knowing the fragility limit of the device being assessed is technically complete but practically useless.

Section 8 — Output Requests and Post-Processing: What to Ask For and Why

The output requests and post-processing topic covers a practical gap that is surprisingly common: analysts who know how to run a simulation but do not fully understand what they are requesting in their output definitions, or who request too much and fill their ODB files with data they cannot use, or too little and miss the results they actually needed.

Field output is written to the ODB file at specified time intervals or increments. It captures the state of the entire model — stresses, strains, displacements, velocities, accelerations at every node and every element integration point — at those moments. For a long explicit dynamic analysis, requesting field output too frequently produces enormous ODB files. Requesting it too infrequently misses the peak stress state.

The guidance in the topic is to identify the temporal window of interest — for a drop event, the first contact and peak response period — and concentrate field output requests there. If the drop event is a 20-millisecond simulation and the structural peak response occurs between 5 and 15 milliseconds, there is no reason to write field output for the first five or the last five milliseconds at the same frequency.

History output is written at every increment and captures time traces of quantities at specific locations — a node's displacement, a section's reaction force, an element's stress component. History output is essential for the energy balance monitoring described in Part Three. ALLKE, ALLIE, ALLSE, ALLPD, and ETOTAL over the full simulation time are the minimum energy outputs for quality assessment.

The topic content also covers which variables to request and why. S — the Cauchy stress tensor — is the primary structural result. E and PE — total strain and plastic strain — are needed to identify yielding. U is displacement. V and A are velocity and acceleration — needed for dynamic response assessment and for validating that the shock input was applied correctly.

Post-processing guidance covers what to look at first — energy balance, then deformation, then stress distribution — and how to interpret results that are physically unreasonable. Stresses that exceed the ultimate strength by a factor of ten do not mean the part failed ten times over; they mean the mesh is too coarse in that region, or the boundary condition is causing a stress singularity, or the result is from a single highly distorted element that should be interrogated separately.

Section 9 — The Example INP Generator: Making Concepts Executable

The Generate Example INP button activates for the five analysis type topics: modal, shock, SRS, random vibration, and harmonic response. This is the most distinctive feature of the Learning Center — the ability to produce a working, runnable Abaqus input file configured around the choices you make in a guided dialog.

The philosophy behind it is direct. Reading about modal analysis produces one level of understanding. Running a modal analysis on a known geometry and verifying that the results match the analytical solution produces a fundamentally different level of understanding. The example generator closes the gap between reading and doing.

The Options Dialog

Clicking Generate Example INP opens a configuration dialog specific to the selected analysis type. Each dialog has a title, a brief description of what will be generated, and a set of option groups — typically three to five choices, each with a dropdown selector and a description panel.

The description panel is key. It does not just name the option — it explains what it means, when you would choose it, and what to expect from it. When you select Steel as the material, the description tells you: Young's modulus 200 GPa, Poisson's ratio 0.3, density 7,800 kg/m³, stiff structure with well-separated modes, good baseline for learning. When you select Aluminum, the description tells you that the lower stiffness-to-mass ratio shifts frequencies lower and that this is common in consumer electronics and aerospace. When you select Titanium, it notes the high strength-to-weight ratio and aerospace and medical applications.

The description updates every time you change a selection. You are not just picking from a menu — you are reading engineering context for each choice as you make it. This is the teaching aspect of the generator: the act of configuring the example is itself an educational experience.

Modal Analysis Options

The modal analysis generator offers four configurable parameters. Material — Steel, Aluminum, or Titanium. Element type — C3D8R reduced-integration hex, C3D8 full-integration hex, or C3D10 quadratic tet. Boundary condition — cantilever with one end fixed, or free-free with no constraints. Number of modes — ten, twenty, or fifty.

The element type descriptions explain the engineering tradeoffs directly. C3D8R is labeled the industry workhorse: fast, accurate for well-shaped elements, requires hourglass control. C3D8 full integration is labeled susceptible to shear locking in bending — stiffer response than reduced integration, good for comparison studies. C3D10 tet is labeled for complex geometry where hex meshing is impractical.

The cantilever boundary condition description notes that this is the classic textbook case with well-known analytical solutions for validation — and that is exactly the point. The generated model is a 100-mm cantilever beam with a 10×10 mm cross section. The expected first bending frequency is approximately 35 Hz, the second approximately 220 Hz, the third approximately 620 Hz. These are the analytical solutions from Euler-Bernoulli beam theory. When you run the example in Abaqus and compare your FEA results to these expected values, you are performing model validation.

The free-free boundary condition description explains the rigid body mode phenomenon: no boundary conditions means the structure floats in space. The first six modes are rigid body modes at zero hertz — three translations and three rotations. The elastic modes begin at mode seven. This is not an error; it is the correct physical behavior of an unconstrained structure. Understanding why those six zero-frequency modes appear, and how to count past them to the first elastic mode, is foundational dynamic analysis knowledge.

Section 10 — Shock Analysis Generator: Pulses, Units, and Amplitude Cards

The shock analysis generator produces a transient dynamic model with base excitation. The choices are material, shock pulse shape, peak G level, and pulse duration. The description panels explain the physical and standard-compliance context for each option.

The peak G options — 50, 100, 500, and 1,000 G — each carry descriptions of the physical environments they represent. 50 G is described as moderate shock typical of bench-level handling drops onto compliant surfaces. 100 G is described as the standard qualification level for many consumer and military products, noting specifically that MIL-STD-810 Method 516 commonly specifies 100 G at 11 milliseconds half-sine. 500 G covers vehicle crash environments and high-drop-height qualification. 1,000 G covers extreme environments including near-field pyroshock.

These descriptions connect the abstract simulation parameter to its physical and regulatory context. An analyst who knows that their product must comply with MIL-STD-810 can select the appropriate pulse and peak G directly, understanding what they are simulating and why.

The Unit System in the Generated INP

All example INP files generated by the Learning Center use the millimeter-tonne-second unit system. This is deliberate and documented in the file header of every generated example: units = mm-tonne-s, frequency in Hz.

The acceleration of gravity in this system is 9,810 mm/s² — not 9.81 m/s². This is the same unit trap described in Part One of this series. The generated shock examples use the correct value: 1 G = 9,810 mm/s². 100 G = 981,000 mm/s². The code contains a lookup table for peak G values in this unit system so the generated amplitude curve uses the correct numbers.

Every generated file includes a comment block at the top documenting exactly which unit system was used and what that implies for result interpretation. This is the principle from the unit detection system applied to generated examples: make the unit system explicit, never leave it implicit.

The Amplitude Card

The shock pulse in the generated INP is defined using Abaqus's *Amplitude keyword. The amplitude card tabulates time-versus-value pairs that define the shape of the loading function. The G level is then applied as a body load or base acceleration referencing this amplitude curve.

For the half-sine pulse, the generator numerically samples the sine function at fine intervals across the pulse duration, producing a tabulated amplitude curve that closely approximates the continuous half-sine shape. For the terminal peak sawtooth, the function is sampled as a linear ramp. For the square wave, it is a step function.

The time discretization used for the amplitude card is deliberately finer than the analysis time step. A coarse amplitude curve would produce a pulse that the solver cannot integrate accurately, especially for the sharp terminations in the sawtooth and square wave. The generator uses at least twenty sample points across the pulse duration to ensure the pulse shape is faithfully represented to the solver.

Section 11 — The Cantilever Beam: A Concrete Teaching Model

The geometry used for all generated examples is a cantilever beam: 100 mm long, 10 mm wide, 10 mm deep. This specific geometry is not arbitrary — it was chosen because it has well-known analytical solutions for natural frequencies, stress under bending loads, and resonant deflection amplitudes.

The node layout is explicit in the code: forty-four nodes arranged in a 4×11 grid forming ten hexahedral elements along the beam length. The node coordinates are hardcoded as floating-point values at regular 10-mm intervals. The element connectivity table is hardcoded as ten elements, each referencing its eight corner nodes by ID.

This is deliberately simple. The mesh is coarse — ten elements along 100 mm is not a production mesh quality. But for a teaching model, coarseness is acceptable, and the analytical frequency solutions are the verification target regardless of mesh quality. The point is not to get the most accurate frequency — it is to run the analysis, see the result, and understand why it is close to the analytical prediction.

The C3D4 Substitution for Tet Selection

When the user selects C3D10 quadratic tet as the element type in the modal generator, the code performs a substitution and generates a C3D4 linear tet mesh instead, with a comment in the file explaining why.

C3D10 requires midside nodes — nodes placed at the midpoint of each edge of the tetrahedron. The node grid used for the cantilever example does not have midside nodes. Generating a proper C3D10 mesh would require a different node layout, one that was never built into the example generator.

Rather than silently generating an incorrect mesh or crashing, the generator substitutes C3D4 linear tets using a standard hex-to-tet decomposition algorithm: each hexahedral element is split into five tetrahedra using a fixed connectivity pattern. The file header documents this substitution. The comment in the file states clearly that C3D10 requires midside nodes and that C3D4 is used for this simple example, and instructs the analyst that in practice they should always use C3D10 for tetrahedral meshes.

This is transparent and honest. The generated file works, it runs, it teaches the boundary condition and step structure correctly — and it tells the analyst exactly what limitation was made and what to do in a real model.

Section 12 — Best Practices Topics from the Module

The best practices topics contributed by the best_practices module follow a different content format than the analysis type topics. They are structured reference entries rather than educational walkthroughs. Each topic covers a specific practice, why it matters, what the failure mode is when it is not followed, and what to do instead.

The topics include the unit system traps — with particular attention to the grams-millimeters-milliseconds versus tonnes-millimeters-seconds ambiguity described in Part One of this series. The thin brittle materials topic covers the specific challenges of glass and ceramic simulation: extremely low failure strain, sensitivity to stress concentrators, the inadequacy of reduced-integration elements in bending. The millisecond time unit topic — called The Time Trap in the Learning Center — is the detailed treatment of why millisecond-based unit systems are used for drop and impact simulation, what the density values look like in each system, and how to verify you are in the right system.

Hourglass control covers what hourglassing is — the zero-energy deformation modes that reduced-integration elements can exhibit — how to detect it in results, and what controls to apply. Bulk viscosity covers the shock wave damping parameters and the recommended values for different impact scenarios. Mass scaling covers the accuracy-versus-speed tradeoff and the tests you should run to verify that your mass scaling factor does not corrupt the dynamics.

Each best practices topic connects to the FEA Best Practices audiobook series published at McFaddenCAE.com. The cross-references at the end of each topic entry name the specific volume and chapter in the audiobook series that covers the topic in more depth. This is how the tool and the audiobook series function as companions: the tool surfaces the issue in the context of your specific model, and the audiobook series provides the extended treatment.

Section 13 — Filtering, Display, and the UI Architecture

The topic list filtering system uses two independent controls applied simultaneously. The category dropdown selects between All, Analysis Types, and Best Practices. The difficulty radio buttons select between All, Beginner, Intermediate, and Advanced.

Both filters apply to the same underlying topic list. When you change either control, the filter_lc_topics function re-iterates through the full topic list, applies both conditions in sequence, and repopulates the listbox with only the topics that pass both filters. The listbox is rebuilt from scratch on every filter change — no incremental update, no caching. For the topic counts involved — typically fifteen to thirty entries — this is fast enough that the rebuild is imperceptible.

The difficulty icons — green circle, yellow circle, red circle — are prepended to each topic title in the listbox. These are Unicode characters, not images. This is consistent with the program's general approach to icons throughout the interface: use Unicode characters where they provide visual clarity without requiring image assets.

When a topic is selected, the show_lc_topic function first determines which topics are currently visible after filtering, then maps the listbox selection index to the correct topic from that filtered list. The title label at the top of the right panel updates to show the selected topic's name. The Generate Example INP button is enabled or disabled based on whether the selected topic has an INP generator attached — the has_inp_generator flag in the topic dictionary.

The content area is a scrolled text widget. Topic content is inserted as a single text block. The widget is not read-only in the tkinter sense — it is displayed in normal state, which means the user can select and copy the text. This is intentional: if you want to copy the governing equation from the modal analysis topic, or copy the expected frequency values for manual verification, you should be able to do that without any export step.

Section 14 — The McFaddenCAE.com Connection

The Learning Center's welcome message identifies it explicitly as the companion resource to the FEA Best Practices audiobook series at McFaddenCAE.com. Understanding this relationship clarifies what the Learning Center is and is not trying to be.

The audiobook series — four volumes, covering topics from unit systems through modal analysis in depth — is the extended educational resource. It is narrated, searchable, and produced to a standard that allows someone to learn from it during a commute, at a gym, or any time they are not at a computer. The total running time is nearly one hundred minutes of core content, plus expanded discussions in companion reader documents.

The Learning Center inside the tool is the quick reference. You are looking at a model. You notice a keyword you do not recognize. You wonder what the correct unit system is for the density value you are seeing. You need to understand what hourglass control does before you act on the recommendation in the Recommendations tab. The Learning Center answers those questions in the context of your active session.

The cross-reference structure — topic content ending with a reference to the audiobook volume and chapter — is the bridge. The tool sends you to the audiobook for the deep treatment. The audiobook references the tool for practical application. Neither is complete without the other, and neither tries to be.

This is the multi-channel educational philosophy that runs through all of the work at McFaddenCAE.com. Different people learn through different media. Some need to hear something explained before they can read the technical detail. Some need the hands-on example before the explanation makes sense. The combination of audiobook, companion reader, and working tool with integrated reference material attempts to serve all of those learning styles from a single coherent body of content.

Section 15 — The Complete Learning Center Pipeline, End to End

Final numbered summary.

1. The Learning Center tab is built at program startup. The topic list is populated from two sources: built-in analysis type topic dictionaries defined in the main program, and the best practices module if it is importable.

2. Each topic is a dictionary with keys: ID, title, category, difficulty, has_inp_generator flag, and content string. Analysis type topics have the generator flag set to true. Best practices topics have it set to false.

3. The filter_lc_topics function applies category and difficulty filters simultaneously, rebuilding the listbox from the full topic list on every change.

4. Selecting a topic populates the content area with the topic's content string, updates the title label, and enables or disables the Generate Example INP button based on the has_inp_generator flag.

5. Clicking Generate Example INP opens a configuration dialog for the selected analysis type. Each dialog presents option groups with dropdown selections and live-updating description panels that explain the engineering context of each choice.

6. When the user confirms options and clicks Generate, the dialog calls the appropriate generator function — generate_modal_example, generate_shock_example, and so on — passing the options dictionary.

7. The generator function builds the INP content as an f-string, substituting the selected material properties, element type, boundary condition block, amplitude curve, and step parameters into a template structure that follows the correct Abaqus CAE block order.

8. The generated INP content is written to disk at the user-selected path with UTF-8 encoding. A success message confirms the save location.

9. The analyst opens the generated file in Abaqus, runs the job, and compares results to the expected analytical values documented in the topic content.

That is the complete Learning Center pipeline — from a topic selection to a runnable simulation with known expected results, designed to close the loop between understanding a concept and executing it.

Closing — The Purpose of Worked Examples

In engineering education, there is a well-known gap between conceptual understanding and practical execution. A student can understand Newton's second law and still struggle to set up the free body diagram for a non-trivial problem. An analyst can understand that natural frequency depends on stiffness over mass and still not know how to set the boundary conditions, choose the eigensolver, or interpret why they are seeing six modes at zero hertz.

Worked examples bridge that gap by making the abstract concrete. When you configure a modal analysis example, select your material, choose your boundary condition, generate the file, run it, and see that the first bending frequency is 35 Hz rather than an unexpected value — you have just done something that no amount of reading could fully replicate. You have closed the loop. The concept and the execution are now the same thing in your experience.

The critical thinking application goes further. Once you have a working baseline — a model you trust because it matches a known answer — you have a tool for systematic exploration. What happens to the frequency if I change the material to aluminum? The theory says it should decrease. Does it? What happens if I change the boundary condition from cantilever to free-free? The first six modes should go to zero. Do they? What happens if I cut the mesh from ten elements to two? How much does the frequency change? That is a mesh convergence study, run in minutes on a model you built yourself.

This is the Holistic Analyst approach. Not trusting a number because it came from a simulation. Trusting a number because you understand the model, you have validated it against a known case, you have tested its sensitivity to key parameters, and the result is consistent with your engineering judgment at every step.

This series will continue. There is more to cover — the penetration check system, the part relationship analysis, the nearest parts search, and the full Learning Center topic library.

Source code, audiobooks, and all companion readers are at McFaddenCAE.com.

End of Part 5 — The Learning Center, Topics, and the Example INP Generator

Next: Part 6 — Part Relationships, Penetration Checks, and the Nearest-Parts Search

Joseph McFadden https://www.mcfaddencae.com