- name
- hpc-elmerfem
- description
- Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer
.sifsolver input files, mesh directories, equation and material blocks, multiphysics coupling, boundary conditions, transient controls, or ElmerSolver execution and output issues.
HPC ElmerFEM
Treat ElmerFEM as a solver-input workflow centered on the .sif file plus a mesh directory.
Start
- Read
references/sif-workflow-manual.mdbefore creating or editing a.sif. - Read
references/block-and-equation-matrix.mdwhen mapping simulation, body, material, equation, solver, and boundary blocks. - Read
references/mesh-boundary-and-output.mdwhen working with mesh directories, body IDs, boundary IDs, and result files. - Read
references/cluster-execution-playbook.mdwhen staging an ElmerFEM workflow for scheduler-backed cluster execution. - Read
references/error-recovery.mdwhen ElmerSolver parsing, coupling, or solve behavior fails.
Additional References
Load these on demand:
references/solver-controls-and-linear-systems.mdfor direct versus iterative settings and nonlinear or steady tolerancesreferences/transient-and-timestep-control.mdfor transient simulation blocks and timestep policiesreferences/elmergrid-and-mesh-conversion.mdfor mesh conversion and ElmerGrid workflowsreferences/simulation-body-solver-matrix.mdfor block-responsibility and ID-mapping lookup tablesreferences/physics-output-matrix.mdfor physics-to-solver-to-output selection tablesreferences/error-pattern-dictionary.mdfor structured parse, ID-mapping, and solver-family failure signaturesreferences/cluster-execution-playbook.mdfor mesh-directory staging, launch style, and cluster-side continuation planning
Reusable Templates
Use assets/templates/ when a concrete .sif scaffold is needed, especially:
heat_steady.sifelasticity_static.sifheat_transient.sifstokes_minimal.sifelmerfem-solver-slurm.sh
Guardrails
- Do not invent SIF keys outside documented Elmer syntax.
- Do not mismatch Body, Material, Equation, and Boundary Condition IDs.
- Do not reuse a solver block blindly across unrelated physics.
- Do not treat mesh boundary IDs as self-explanatory; map them explicitly.
Outputs
Summarize:
- physics family
- mesh directory assumptions
- core solver and equation blocks
- body and boundary mapping
- expected result files