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
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.
Local node multiplicity is the same across all components - we could save memory movement by letting a ElemRestriction provide a scalar multiplicity vector.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: