Skip to content
Marc & Structures
Index

Save your progress

Enter your email and we will send a secure sign-in link. There is no password and the first link creates your account.

Debugging ~5 min · ~24 min remaining

Diagnose before correcting

Connect each symptom to a likely cause and a concrete check without changing options at random.

Common mistakes

SymptomLikely causeCheck
File not foundThe `.mac` is not in Working Directory.Check folder and name in `/INPUT`.
Division by zeroNo nodes found in x=1.0.Review geometry, mesh and selection.
No contoursThere is no valid result set.Look for SOLVE errors in m00_session.out.
Displacement toward +YThe load sign changed.Review FY and its sign.
Gigantic displacementInconsistent units.Check meters, newtons and pascals.
Only part of the model appearsResidual selection.Run ALLSEL,ALL.
What we have chosen to postpone

M00 does not use local coordinate systems, work plane, loads on element faces or SFCONTROL. They are valid tools, but introducing them here would hide the essential workflow.

We simplify the model, not the explanation. Each concept will appear when solving a problem that the student already recognizes.

Quick check

The model shows only part of the geometry. What would you check first?

Professional incident

Incident M00: diagnose before editing

The run finishes, but the results belong to the wrong job.

Execution cycle

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

Graduated hints

1 · Concept hint

Find the first broken contract.

2 · Command hint

Inspect state related to /FILNAME and /INPUT.

3 · Explained solution

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

Your reflection stays in this browser.