Debugging ~6 min · ~24 min remaining

Diagnose attributes

Identify misleading active pointers, mixed materials, and incomplete partitions.

Bug hunt

Run 03_bug_hunt.mac. It does not target fatal errors: it contains five plausible decisions that produce a model different from the stated intent. For each one, write: symptom, cause, test and correction.

Check the steel elastic modulus units.
Identify which material was active during VMESH.
Explain your answer. SECNUM,1 does not create a section and is left over in this solid.
Locate where the scope of mid_elems is lost.
Demonstrate why MAT,1 does not repair existing elements.

Quick check

n_mat2>0 in the homogeneous base case. What does that indicate?

An element received MAT,2 when it should have received MAT,1. The mesh is too fine. The solver did not converge.

Professional incident

Incident M03: diagnose before editing

The active pointer says MAT,1 while elements store MAT,2.

Execution cycle

1 Run the broken script in a clean folder.
2 Preserve the original .out.
3 Write one causal hypothesis and make one change.
4 Compare evidence before and after.

Evidence to retain

Initial hypothesis Changed line or block Output proving the cause Reusable prevention rule

What evidence separates the root cause from a lucky edit?

Graduated hints

1 · Concept hint

Find the first broken contract.

2 · Command hint

Inspect state related to *GET and EMODIF.

3 · Explained solution

Compare with the module deliverable and explain why the corrected state restores the contract.

Your reflection stays in this browser.

View complete module Download m03-kit.zip