HPC CalculiX

Treat CalculiX as an input-deck-driven FEM workflow centered on .inp keywords.

Start

1. 1. Read references/input-deck-manual.md before creating or editing a .inp file.
2. Read references/keyword-and-step-matrix.md when mapping materials, sections, loads, and analysis steps.
3. Read references/mesh-boundary-and-output.md when working with nodes, elements, sets, boundary conditions, and result output.
4. Read references/cluster-execution-playbook.md when staging a CalculiX deck for scheduler-backed cluster execution.
5. Read references/error-recovery.md when parsing, solving, or post-processing fails.

Additional References

Load these on demand:

• - references/time-control-and-amplitudes.md for step time, amplitude logic, and incremental loading behavior
• INLINECODE8 for .dat, .frd, and eigenmode artifacts
• INLINECODE11 for heat transfer and coupled analysis patterns
• INLINECODE12 for procedure-to-load-to-output compatibility tables
• INLINECODE13 for element, section, and material assignment lookup tables
• INLINECODE14 for structured parse, singularity, and procedure-mismatch failure signatures
• INLINECODE15 for launch style, result-artifact planning, and cluster-side deck execution

Reusable Templates

Use assets/templates/ when a concrete .inp scaffold is needed, especially:

• - INLINECODE18
• INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22

Guardrails

• - Do not invent Abaqus-style keywords that CalculiX does not support.
• Do not mix node or element set names inconsistently across sections and steps.
• Do not define loads and boundary conditions without checking the active step type.
• Do not skip material and section coherence when the deck fails later in the solve.

Outputs

Summarize:

• - analysis type
• materials and sections
• sets and boundary assumptions
• step sequence
• expected result files