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
Currently, MeshData only accept an AbstractVector (by opposition with AbstractMatrix). When we want to represent a vector field, should we:
modify the implementation of MeshData to accept matrices, then the "get_value" will look like get_value(data,i) = view(data,i,:)
build a MeshData with a "vector of vectors" : MeshData([[u1_x, u1_y], [u2_x, u2_y], ...])
?
For sure method 2. does the job for now, but I am just asking the question. Note however that, with solution 2, our write_vtk methods will fail for MeshCellData (because we don't materialize them, we just get the values).
The text was updated successfully, but these errors were encountered:
Currently,
MeshData
only accept anAbstractVector
(by opposition withAbstractMatrix
). When we want to represent a vector field, should we:MeshData
to accept matrices, then the "get_value" will look likeget_value(data,i) = view(data,i,:)
MeshData
with a "vector of vectors" :MeshData([[u1_x, u1_y], [u2_x, u2_y], ...])
?
For sure method 2. does the job for now, but I am just asking the question. Note however that, with solution 2, our
write_vtk
methods will fail forMeshCellData
(because we don't materialize them, we just get the values).The text was updated successfully, but these errors were encountered: