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
InterpInfo::interp can (initially?) be a std::vector<Real>. We will need to modify the send data to be std::pair<std::vector<Real>, Real> where first is the interpolation evaluations and second is the "distance". This would also require some work in libMesh to allow MeshFunction to evaluate vector variable (components)
Impact
More capability in our general field transfers
The text was updated successfully, but these errors were encountered:
Reason
Users may like to transfer vector variables
Design
InterpInfo::interp
can (initially?) be astd::vector<Real>
. We will need to modify the send data to bestd::pair<std::vector<Real>, Real>
wherefirst
is the interpolation evaluations andsecond
is the "distance". This would also require some work in libMesh to allowMeshFunction
to evaluate vector variable (components)Impact
More capability in our general field transfers
The text was updated successfully, but these errors were encountered: