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

Problem in using fix_tet_windup #99

Open
A-ep93 opened this issue Nov 9, 2020 · 2 comments
Open

Problem in using fix_tet_windup #99

A-ep93 opened this issue Nov 9, 2020 · 2 comments

Comments

@A-ep93
Copy link

A-ep93 commented Nov 9, 2020

Hello all,
I want to use the "fix_tet_windup" option for avoiding inside-out tetrahedra in the output mesh. However, I get the following error when I activate this option:
"option '--fix_tet_windup' cannot be specified more than once"
Can you please help me to find the problem?
Thanks

@A-ep93
Copy link
Author

A-ep93 commented Nov 9, 2020

From the error I mentioned above, it seems that the fix_tet_windup option is enabled by default. But the result is not what I want. You can see that in the attached figure, some sections of the green part are drawn upward and some sections are purple part are drawn down in the outward of the real sphere. How can I fix this?
image

@jessdtate
Copy link
Contributor

The tet-windup refers to the order of the vertices in each tet of the mesh, and the fix_tet_windup will change the order, but not change the positions of values of any of the vertices. This is help when some software follows a different convention of tet ordering than others.

What I understand is that you are concerned with mislabeling of elements. This could be a problem with the mesh cleaving the wrong place or the incorrect mapping of the label. I think starting with a higher resolution image would fix both, but you could also try increasing the sampling_rate option a little.

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

2 participants