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

c3t3 -> binary -> c3t3 -> vtu writes invalid vtu files #8773

Open
sloriot opened this issue Mar 6, 2025 · 4 comments · May be fixed by #8778
Open

c3t3 -> binary -> c3t3 -> vtu writes invalid vtu files #8773

sloriot opened this issue Mar 6, 2025 · 4 comments · May be fixed by #8778
Assignees
Milestone

Comments

@sloriot
Copy link
Member

sloriot commented Mar 6, 2025

Dumping a c3t3 to a cgal binary, reading it back and writing the result to vtu generates an invalid vtu files.
If you we directly write the c3t3 to vtu it is correct.

A first step should be to compare the two vtu files generated to get a guess on what could be wrong.

@lrineau
Copy link
Member

lrineau commented Mar 7, 2025

Dumping a c3t3 to a cgal binary, reading it back and writing the result to vtu generates an invalid vtu files.
If you we directly write the c3t3 to vtu it is correct.

On Linux, too?

@sloriot
Copy link
Member Author

sloriot commented Mar 7, 2025

Actually on Linux yes, on Windows I don't know.

@afabri
Copy link
Member

afabri commented Mar 7, 2025

Code on gist.github.com.
Does not yet repoduce the problem, but maybe it needs an example with more domains, or sharp features, or....

@afabri
Copy link
Member

afabri commented Mar 7, 2025

Sebastien just told me that he had observed this with a polyhedral mesh complex.

lrineau added a commit to lrineau/cgal that referenced this issue Mar 10, 2025
… files"

When a c3t3 is loaded, its far vertices were not loaded correctly.
@lrineau lrineau added this to the 6.1-beta milestone Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants