Oded Yaakobi
Dear all,
I am trying to solve a 3D problem with moving boundaries that exhibit very large deformations. During my runs, the grid, that is represented by a MappingQEulerian object, becomes highly distorted. For instance, some of the cells are pinched.
I have wondered whether I could use CUBIT in order to overcome this issue, by implementing the following strategy during runs of my code:
(1) Export the mesh at a chosen predefined time (or maybe when it is determined that the mesh quality does not satisfy some criteria).
(2) Call CUBIT in a batch mode and import into it the mesh.
(3) Improve the mesh quality in CUBIT by applying some predefined algorithms.
(4) Export the new mesh from CUBIT.
(5) Import the new mesh to my code.
(6) Resume the run of my code using the new mesh.
Does anyone have any experience in implementing such a strategy?
In particular, is there a way to export the mesh from dealii in a file format that CUBIT can import directly? I weren't able to find a such a format, so it seems to me that between (1) and (2) above I would have to add a mesh file format conversion between dealii exported file and CUBIT imported file.
I would also be happy to know if there are suggestions for another strategy that may be used to overcome the issue of mesh distortion.
Thanks,
Oded
Wolfgang Bangerth
Oded,
> I am trying to solve a 3D problem with moving boundaries that exhibit very
> large deformations. During my runs, the grid, that is represented by a
> MappingQEulerian object, becomes highly distorted. For instance, some of the
> cells are pinched.
>
>
> I have wondered whether I could use CUBIT in order to overcome this issue, by
> implementing the following strategy during runs of my code:
>
> (1) Export the mesh at a chosen predefined time (or maybe when it is
> determined that the mesh quality does not satisfy some criteria).
>
> (2) Call CUBIT in a batch mode and import into it the mesh.
>
> (3) Improve the mesh quality in CUBIT by applying some predefined algorithms.
>
> (4) Export the new mesh from CUBIT.
>
> (5) Import the new mesh to my code.
>
> (6) Resume the run of my code using the new mesh.
>
>
> Does anyone have any experience in implementing such a strategy?
everything from within deal.II, rather than going through all of these other
file formats and programs. For example, you could investigate how one would
call the functions in the Trilinos package "Mesquite", see
https://trilinos.org/packages/mesquite/
This would allow you to do things from within your application.
Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: bang...@math.tamu.edu
www: http://www.math.tamu.edu/~bangerth/