Dear Matteo, The best solution here would be to serialize the mesh so you can re-read it anew. This would be identical to what you would do when you restart a simulation. We have a new tutorial that shows just how exactly this is done: https://www.dealii.org/current/doxygen/deal.II/step_83.html
If you have any questions, please feel free to reach out and we will be glad to help you with this. Best Bruno On Sunday, January 12, 2025 at 6:56:01 a.m. UTC-5 Matteo Malvestiti wrote: > Good morning. > I have a very fundamental question: in my project I do adaptive refinement > on a mesh. > The task is then to store it and provide the interface for the research > group to load it and proceed with their experiments. > > A small outline of the process: > 1) The initial conforming and coarse is initially created by gmsh > 2) The grid is read in by GridIn > 3) A Goal-oriented refinement algorithm (similar to step14) runs over > different cycles and refines it adaptively > 4) I store the mesh with GridOut (I'm using write_msh with all flags true) > Problem arise here, because when I import it again it's like the only > "recognised" cells are those with the highest refinement level. (see > picture) > > What's the right way to store and import meshes? > I've read some concerning discussion here on the group hinting at the fact > that it might not be achievable (?) > > Thanks for your support. > Kind regards, > Matteo Malvestiti > > > > > -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/dealii/3b58515e-9259-4a08-81cb-ad168d7d63c7n%40googlegroups.com.
