-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow VectorElement to take a variant argument. #17
Allow VectorElement to take a variant argument. #17
Conversation
Can you do this for |
@@ -263,6 +263,8 @@ def __init__(self, family, cell=None, degree=None, dim=None, | |||
viewed as k-form), ignored if family is a FiniteElement | |||
quad_scheme | |||
The quadrature scheme (optional), ignored if family is a FiniteElement | |||
variant |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs a bit more explanation. I don't understand the docstring.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This variant thing was first introduced to distinguish between GL, GLL, and equispaced Langrange elements without a profusion of names: Q, dQ, RTCE, RTCF, NCE, NCF type elements could be built from equispaced Lagrange as well as from spectral ingredients.
Later uses of this include RT and N1curl elements being available with different nodal basis, etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
c.f. FEniCS/fiat#52
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For further reference, see this UFL issue and this UFL pull request.
* add variant for MixedElement (#129) * Allow VectorElement to take a variant argument. (#17) Co-authored-by: Patrick Farrell <[email protected]> Co-authored-by: Pablo Brubeck <[email protected]> Co-authored-by: Patrick E. Farrell <[email protected]> Co-authored-by: Patrick Farrell <[email protected]>
No description provided.