HPC CalculiX
Treat CalculiX as an input-deck-driven FEM workflow centered on .inp keywords.
Start
- Read
references/input-deck-manual.mdbefore creating or editing a.inpfile. - Read
references/keyword-and-step-matrix.mdwhen mapping materials, sections, loads, and analysis steps. - Read
references/mesh-boundary-and-output.mdwhen working with nodes, elements, sets, boundary conditions, and result output. - Read
references/cluster-execution-playbook.mdwhen staging a CalculiX deck for scheduler-backed cluster execution. - Read
references/error-recovery.mdwhen parsing, solving, or post-processing fails.
Additional References
Load these on demand:
references/time-control-and-amplitudes.mdfor step time, amplitude logic, and incremental loading behaviorreferences/result-files-and-postprocessing.mdfor.dat,.frd, and eigenmode artifactsreferences/thermal-and-coupled-procedures.mdfor heat transfer and coupled analysis patternsreferences/step-load-output-matrix.mdfor procedure-to-load-to-output compatibility tablesreferences/element-section-material-matrix.mdfor element, section, and material assignment lookup tablesreferences/error-pattern-dictionary.mdfor structured parse, singularity, and procedure-mismatch failure signaturesreferences/cluster-execution-playbook.mdfor launch style, result-artifact planning, and cluster-side deck execution
Reusable Templates
Use assets/templates/ when a concrete .inp scaffold is needed, especially:
static_minimal.inpfrequency_minimal.inpthermal_minimal.inpbeam_static.inpcalculix-ccx-slurm.sh
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