You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, for mixed-topology meshes we have to create a FunctionSpace and Form for each cell type. This isn't very natural and leads to objects with almost the same data; for example, the main difference between the forms is just the kernel.
I think we should restructure this so we create a single FunctionSpace (with possibly multiple element types) and a single Form (with possibly multiple kernels).
This should hopefully simplify both the user interface and the assembler implementation, since we can just loop over all kernels in the assembler rather than having to reverse engineer the cell type from the form.
The text was updated successfully, but these errors were encountered:
Currently, for mixed-topology meshes we have to create a
FunctionSpace
andForm
for each cell type. This isn't very natural and leads to objects with almost the same data; for example, the main difference between the forms is just the kernel.I think we should restructure this so we create a single
FunctionSpace
(with possibly multiple element types) and a singleForm
(with possibly multiple kernels).This should hopefully simplify both the user interface and the assembler implementation, since we can just loop over all kernels in the assembler rather than having to reverse engineer the cell type from the form.
The text was updated successfully, but these errors were encountered: