Closed sedghi closed 7 months ago
:tada: This issue has been resolved in version 29.4.3 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
@finetjul I tried it with a fix and this is what I see for my vtkCutter outputs (the code sandbox example), is this expected results?
I guess it is not what is expected...
What if you re-order the input points (and cells) so that they each follow each other ?
I don't know how to order these points that are the output from the vtkCutter. Do you have any ideas?
I meant to do it with your codesandbox example to see if the vtkContourTriangulator
is performing better. There might still be a bug in the JS code...
Bug description
Initially, I experimented with the
ContourTriangulator
example. I increased the number of points,nbPoints
, to 16000, and it performed efficiently. It did slow down a bit when I reached around 100,000 points, but that's not a concern at the moment.However, when I obtain the points from the vtkCutter, which involves cutting through a surface, even if the resulting cut points are very small (~100), the vtkContourTriangulator remains inactive and fails silently, seems like.
Steps to reproduce
You can reproduce it two ways.
First: Here in the codesandbox Turn the flag on for the
EnableContourTriangulator
in line 18Second: Run the vtkCutter example (the dragon) and add the following snippet at the end so that it runs after one second. This snippet will grab the output of the vtkCutter, create a polyData, and then feed it to the triangulator.
Detailed Behavior
Running vtkContourTriangulator does nothing (freezes the app) on the output of the vtkCutter
Expected Behavior
Should work similar to syntetic data
Environment