Run any Skill in Manus with one click

hpc-elmerfem

Stars67

Forks8

UpdatedMarch 16, 2026 at 15:31

Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer `.sif` solver input files, mesh directories, equation and material blocks, multiphysics coupling, boundary conditions, transient controls, or ElmerSolver execution and output issues.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

SciMate-AI

SciMate-AI/HPC-Skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Mechanical EngineersArchitecture and Engineering Occupations·SOC 17-2141

File Explorer

18 files

SKILL.md

readonly

name	hpc-elmerfem
description	Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer `.sif` solver 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.md before creating or editing a .sif.
Read references/block-and-equation-matrix.md when mapping simulation, body, material, equation, solver, and boundary blocks.
Read references/mesh-boundary-and-output.md when working with mesh directories, body IDs, boundary IDs, and result files.
Read references/cluster-execution-playbook.md when staging an ElmerFEM workflow for scheduler-backed cluster execution.
Read references/error-recovery.md when ElmerSolver parsing, coupling, or solve behavior fails.

Additional References

Load these on demand:

references/solver-controls-and-linear-systems.md for direct versus iterative settings and nonlinear or steady tolerances
references/transient-and-timestep-control.md for transient simulation blocks and timestep policies
references/elmergrid-and-mesh-conversion.md for mesh conversion and ElmerGrid workflows
references/simulation-body-solver-matrix.md for block-responsibility and ID-mapping lookup tables
references/physics-output-matrix.md for physics-to-solver-to-output selection tables
references/error-pattern-dictionary.md for structured parse, ID-mapping, and solver-family failure signatures
references/cluster-execution-playbook.md for 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.sif
elasticity_static.sif
heat_transient.sif
stokes_minimal.sif
elmerfem-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

More from this repository

same repository

hpc-ls-dyna

SciMate-AI/HPC-Skills

Create, review, debug, and recover LS-DYNA keyword decks and simulation workflows. Use when working with LS-DYNA `*.k` or `*.key` input files, include trees, explicit crash or impact models, implicit static or quasi-static solves, contact definitions, section and material selection, timestep or mass-scaling control, hourglass stabilization, thermal or coupled workflows, ALE/SPH/ICFD/EM/DEM/CESE/IGA cases, or LS-DYNA runtime instability and model-quality issues.

2026-04-0667

hpc-gmsh

SciMate-AI/HPC-Skills

Build, review, debug, and automate Gmsh geometry and meshing workflows. Use when working with `.geo` scripts, the Gmsh Python API, GEO versus OpenCASCADE modeling, physical groups, mesh-size fields, transfinite or recombine options, boundary layers, structured/unstructured algorithm selection, mesh partitioning, periodic meshes, high-order elements, mesh export and solver handoff (FEniCS, OpenFOAM, Elmer, SU2, etc.), CAD/STL import, or Gmsh CLI and meshing failures.

2026-04-0467

hpc-openfoam

SciMate-AI/HPC-Skills

Generate, review, debug, and recover OpenFOAM case files for CFD workflows. Use when working with OpenFOAM dictionaries, case structure, turbulence fields, boundary conditions, decomposition, numerics, or OpenFOAM runtime errors. Also covers RANS/LES turbulence setup, wall functions, y+ targeting, conjugate heat transfer, compressible flows, VOF multiphase, mesh quality, and scheme tuning.

2026-04-0467

hpc-vasp

SciMate-AI/HPC-Skills

Build, review, debug, and automate VASP first-principles workflows. Use when working with VASP input sets such as INCAR, POSCAR, KPOINTS, and POTCAR; when choosing SCF, relaxation, static, DOS, or band-structure stages; or when fixing convergence, symmetry, cutoff, and k-point issues. Also covers magnetic calculations, spin-orbit coupling, hybrid functionals, surface slabs, DFT+U, van der Waals, phonons, molecular dynamics, NEB, and defect calculations.

2026-04-0467

hpc-foundations

SciMate-AI/HPC-Skills

Navigate foundational HPC knowledge across concepts, architectures, schedulers, Linux usage, storage and RDMA, containers, cloud basics, and cluster administration patterns distilled from hpclib.com. Use when the task is about understanding or explaining HPC basics, Slurm or PBS or LSF concepts, Linux-on-cluster workflows, software environment setup, storage or network fundamentals, or when turning general HPC knowledge into future skills.

2026-04-0167

hpc-gpu-stack

SciMate-AI/HPC-Skills

Build, review, debug, and launch CUDA- and GPU-accelerated HPC workflows. Use when working with `nvcc`, host-compiler compatibility, CUDA-aware MPI, rank-to-GPU mapping, `CUDA_VISIBLE_DEVICES`, Slurm GPU scheduling, GPU memory or stream behavior, or CUDA build and runtime failures.

2026-04-0167

name	hpc-elmerfem
description	Build, review, debug, and automate ElmerFEM workflows. Use when working with Elmer `.sif` solver 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.md before creating or editing a .sif.
Read references/block-and-equation-matrix.md when mapping simulation, body, material, equation, solver, and boundary blocks.
Read references/mesh-boundary-and-output.md when working with mesh directories, body IDs, boundary IDs, and result files.
Read references/cluster-execution-playbook.md when staging an ElmerFEM workflow for scheduler-backed cluster execution.
Read references/error-recovery.md when ElmerSolver parsing, coupling, or solve behavior fails.

Additional References

Load these on demand:

references/solver-controls-and-linear-systems.md for direct versus iterative settings and nonlinear or steady tolerances
references/transient-and-timestep-control.md for transient simulation blocks and timestep policies
references/elmergrid-and-mesh-conversion.md for mesh conversion and ElmerGrid workflows
references/simulation-body-solver-matrix.md for block-responsibility and ID-mapping lookup tables
references/physics-output-matrix.md for physics-to-solver-to-output selection tables
references/error-pattern-dictionary.md for structured parse, ID-mapping, and solver-family failure signatures
references/cluster-execution-playbook.md for 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.sif
elasticity_static.sif
heat_transient.sif
stokes_minimal.sif
elmerfem-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