Thank you Jean! That was a very comprehensive summary for me to take initial steps and motivation for deal.ii. The main concern from me however remains now for the reading and dealing with boundary conditions I am interested in my solid mechanics case simulations. If there are some external, high end or specialized interfaces present for them too to control what has to happen inside of the the BC interpolation functions with named boundary ids that would make a lot more ease.
On Friday, March 15, 2019 at 4:40:43 PM UTC+1, Jean-Paul Pelteret wrote: > > Dear Muhammad, > > You can look at the documentation to the GridIn > <https://dealii.org/current/doxygen/deal.II/classGridIn.html> namespace > for some ideas as to which software supports the generation of mesh files > that deal.II can read, and the and GridOut > <https://dealii.org/current/doxygen/deal.II/classGridOut.html> namespace > for the types of output deal.II can make and some programs that can read > them in. > > I think that it depends greatly on what you’re trying to accomplish as to > what software you may consider using. For example, I often simulate > problems that require intricate geometry and, therefore, an intricate mesh. > So I use a commercial tool like Cubit to create the mesh and post-process > results using Paraview. I would say that GMSH and Salome are two other > preprocessors that would be commonly used (but neither of which I have much > familiarity with). Of course, deal.II has itself got some basic mesh > generation capabilities that may be perfectly suitable for you. Another > often-used post-processor is Visit. > > The application of boundary conditions is done differently to how one much > setup BCs in a mesh that is then read into, say, ABAQUS. With deal.II you > may only specify an identifying number (known as a boundary_id) to the > boundaries, which you then interpolate some boundary condition function > onto. I know thats some commercial software interprets physical boundary > conditions directly from the mesh itself but, since deal.II is a finite > element library and not a multi physics library, it would have no > understanding of what these types of boundary conditions mean. > > Does that help you? > > Best, > Jean-Paul > > On 15 Mar 2019, at 16:18, Muhammad Mashhood <[email protected] > <javascript:>> wrote: > > Dear all, > I am new to deal.ii and looking for a nice interfacing tool > for making mesh import, BC application, solution and post-processing for > simulation cases etc. easy for me. Can anyone give me suggestion regarding > this? Thank you! > > > > -- > 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 [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
