From 8f34707cf520bab3d66de1a26328015af65581a8 Mon Sep 17 00:00:00 2001 From: Jukka Aho Date: Sat, 9 May 2026 17:37:08 +0300 Subject: [PATCH] docs(mesh): clarify mixed topology and kernel ownership Document that multi-topology meshes are still unsupported and replace the old `Physics` wording with kernel-centric language about shared meshes. - Swap the future `MixedMesh` bullet for an explicit limitation note. - Describe mesh ownership vs kernel references for multiphysics reuse. --- src/mesh/api.jl | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/src/mesh/api.jl b/src/mesh/api.jl index bbcd6da..b82616a 100644 --- a/src/mesh/api.jl +++ b/src/mesh/api.jl @@ -30,13 +30,17 @@ Concrete mesh types must implement: # Concrete Types - `Mesh{T<:AbstractTopology}` - Parametric mesh with single topology type -- `MixedMesh` - Mesh with multiple topology types (future) + +Mixed-topology meshes (multiple element families in one mesh) are not +implemented yet; the assembly pipeline currently assumes a single +concrete topology type. # Design Philosophy -Meshes own topology (node coordinates, connectivity). -Physics references meshes (does not own them). -Multiple Physics can share one Mesh (multiphysics coupling). +Meshes own topology (node coordinates, connectivity). Kernels and +constraint objects reference meshes; they do not own them. Multiple +kernels (e.g. `ContinuumKernel` + `HeatKernel`) can share one mesh for +multiphysics coupling. # Element Sets and Node Sets