Skip to content
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

Scalar Multiplicity Vector #1307

Open
jeremylt opened this issue Aug 24, 2023 · 0 comments
Open

Scalar Multiplicity Vector #1307

jeremylt opened this issue Aug 24, 2023 · 0 comments

Comments

@jeremylt
Copy link
Member

          Yeah, it is. But the important part is that is results in 1 scalar per node rather than 1 scalar per component per node (which is what `CeedElemRestrictionGetMultiplicity` gives out). So if there's an easy *Edit: and robust* way of getting out the components that correspond to a single component, then we could just do that and invert that vector.

Originally posted by @jrwrigh in #1223 (comment)

Local node multiplicity is the same across all components - we could save memory movement by letting a ElemRestriction provide a scalar multiplicity vector.

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

No branches or pull requests

1 participant