Using both p4est and p8est in an application

[arthurbawin]

Hello !

I use p4est in gmsh, to compute and store a mesh size field that is used during unstructured mesh generation. The goal is to deal with 2D and 3D models with the same code, so I'd like to be able to generate both octrees and quadtrees, with the decision being made at runtime when a model is loaded. For 3D models, I use p8est to create an octree around it and store the size field in the octree. For 2D planar models, I currently create an octree and only work on the slice of octants that have an intersection with the z = 0 plane. The 3D works as intended, but the 2D looks like a huge waste of time and resources to me, having to deal with the whole octree, but I haven't found another solution yet, since as I understand it the choice between p4est and p8est has to be made at compile time.

Am I understanding it wrong ? Or is there a workaround I could use to choose between p4est and p8est at runtime ?

Thanks,
Arthur

[Carsten Burstedde]

You may include both p4 and p8 .h files from the same file. Name spaces are separate. Compiling with both is fine! Sent by Webmail -- please excuse a certain lack of formality.

…

----- Ursprüngliche Mail ----- Von: "arthurbawin" ***@***.***> An: "cburstedde/p4est" ***@***.***> CC: "Subscribed" ***@***.***> Gesendet: Donnerstag, 12. August 2021 21:16:05 Betreff: [cburstedde/p4est] Using both p4est and p8est in an application (#121) Hello ! I use p4est in gmsh, to compute and store a mesh size field that is used during unstructured mesh generation. The goal is to deal with 2D and 3D models with the same code, so I'd like to be able to generate both octrees and quadtrees, with the decision being made at runtime when a model is loaded. For 3D models, I use p8est to create an octree around it and store the size field in the octree. For 2D planar models, I currently create an octree and only work on the slice of octants that have an intersection with the z = 0 plane. The 3D works as intended, but the 2D looks like a huge waste of time and resources to me, having to deal with the whole octree, but I haven't found another solution yet, since as I understand it the choice between p4est and p8est has to be made at compile time. Am I understanding it wrong ? Or is there a workaround I could use to choose between p4est and p8est at runtime ? Thanks, Arthur

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #121