Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performances (speed + accuracy) #41

Open
Vilo176 opened this issue Sep 8, 2021 · 0 comments
Open

Performances (speed + accuracy) #41

Vilo176 opened this issue Sep 8, 2021 · 0 comments

Comments

@Vilo176
Copy link

Vilo176 commented Sep 8, 2021

Hi dear friends,

I'm heavily testing fTetWild on a model that is well representing what kind of geometry I want to deal with.
It's a CAD produced building element, composed of many sub-elements.
The model is composed of 21k nodes and 18k triangles.
Window

I've compiled fTetWild under Windows, with VS2022, into Release.
To compute the result, I'm using the CSG approach with all sub-elements linked into a huge union chain (JSON).
On my mid range laptop (core i5 8265U + 16Go), overall process with default settings takes 200s.
The result is good at first sight, but if you zoom in :
Detail tetras 1
Detail tetras 2
Detail tetras 3

The result tretrahedralization is largely not respecting model boundaries.

Here are the computations parameters taken from early stage of process :
Default

So here are my questions ;-)

  1. Is the 200s processing time a "normal" score according to your experience ?

  2. Are there any optimizations I can do to severally reduce that processing time ?
    I've tested by increasing target edge size (x10) but processing time get worse (230s).
    I've tested increasing Min Energy threshold, but this only saved a few seconds.

  3. Is there maybe a parallelized version that could run on multiple cores / thread locally ?

  4. As far as geometric precision is concerned, you can see that with a 2E-3 effective Epsilon, many of the model sub-objects have been "swallowed" during the process, even if these objects are thicker/larger than this limit.
    Addtionnaly, you can see that there are many tetras that are protrusing/penetrating the initial model.
    To reduce this phenomenon I have to reduce envelop, but computation time seams to be quadratic from this parameter, leading to very very long process time.
    I've tested TetWild too, with better results, but with processing time that are not acceptable for my purposes (15 minutes on that model).
    Is there other thing to do to reduce that phenomenon ?

Thanks a lot !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant