Skip to content

Mapped element - #109

Open
jacobmerson wants to merge 12 commits into
SCOREC:mainfrom
jacobmerson:mapped-element
Open

jacobmerson wants to merge 12 commits into
SCOREC:mainfrom
jacobmerson:mapped-element

Conversation

@jacobmerson

Copy link
Copy Markdown
Contributor

This PR is an alternative strategy to handle non isoparametric geometry. The mapping policies should be extensible to handle the Bell elements from M3DC1 and when we get to it, vector elements.

See discussion in #100. This is an alternative strategy to what @Sichao25 implemented in #99.

Note: this PR is based on changes in #108. If you merge that PR rather than rebase it, it'll make merging this PR much simpler.

jacobmerson and others added 12 commits October 6, 2026 02:48
This performs interpolation to target elements. We use ownership to
avoid having multiple element write to the same dofs on shared entities.
This interpolation capability will be used to support generic coordinate
field initialization for higher order elements.
cannot have lambdas in function with auto return type with cuda
To support non-isoparametic elements, we split the evaluation of the
nodal coefficients and the multiplication with the shape functions
MappedElement composes a field element with a geometry element over the
coordinate field (see SCOREC#100)
In the case of affine (straight sided) and isoparametric elements
we will want to take compile-time optimized code paths so the
performance of a MappedElement is similar to a base FieldElement

This branch was successfully deployed

1 active deployment
asics — e6d56185 Deployed Oct 11, 2026 by jacobmerson via build_and_test #18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant