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
When we render the voxel VTK we are going to give to the EVPFFT backend, the positions of the voxels are stored in coordinate space. This can be confusing for users, as the mesh they see can change scale upon voxelization. If they enter a voxel ratio of 1x2x1, for example, it will appear that their mesh was stretched by a factor of 2 along the y dimension. Additionally, the mesh is not centered, which makes it annoying to manipulate in the viewer.
Potential fixes
Lots of potential solutions
Let the EVPFFT backend handle real space coordinates and not index space coordinates. Then just ask the voxelizer to give the real coordinates.
Voxelize it twice, once for EVPFFT backend and once for the rendering. Little stupid, but trivial to do. Performance is probably still "fine".
Scale the resulting voxel grid in paraview.
The text was updated successfully, but these errors were encountered:
Issue
When we render the voxel VTK we are going to give to the EVPFFT backend, the positions of the voxels are stored in coordinate space. This can be confusing for users, as the mesh they see can change scale upon voxelization. If they enter a voxel ratio of 1x2x1, for example, it will appear that their mesh was stretched by a factor of 2 along the y dimension. Additionally, the mesh is not centered, which makes it annoying to manipulate in the viewer.
Potential fixes
Lots of potential solutions
The text was updated successfully, but these errors were encountered: