docs

trixi-framework · Dec 20, 2024 · fc2d1f1 · fc2d1f1
1 parent 41e5c31
commit fc2d1f1
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 2 deletions.
diff --git a/docs/literate/src/files/p4est_from_gmsh.jl b/docs/literate/src/files/p4est_from_gmsh.jl
@@ -315,7 +315,7 @@ end #hide #md
 # ```
 # which forces `gmsh` to generate quadrilateral elements instead of the default triangles.
 # This is strictly required to be able to use the mesh later with `p4est`, which supports only straight-sided quads,
-# i.e., `C2D4, CPS4, S4` in 2D and `C3D` in 3D.
+# i.e., `CPS4, S4, ...` in 2D and `C3D8` in 3D.
 # See for more details the (short) [documentation](https://p4est.github.io/p4est-howto.pdf) on the interaction of `p4est` with `.inp` files.
 # In principle, it should also be possible to use the `recombine` function of `gmsh` to convert the triangles to quads, 
 # but this is observed to be less robust than enforcing quads from the beginning.

diff --git a/docs/src/meshes/p4est_mesh.md b/docs/src/meshes/p4est_mesh.md
@@ -386,6 +386,7 @@ transfinite map of the straight sided hexahedral element to find
 
 Also for a mesh in standard Abaqus format there are no qualitative changes when going from 2D to 3D.
 The most notable difference is that boundaries are formed in 3D by faces defined by four nodes while in 2D boundaries are edges consisting of two elements.
+Note that standard Abaqus also defines quadratic element types. In Trixi.jl, these higher-order elements are currently only supported in 2D, i.e., 8-node quadrilaterals.
 A simple mesh file, which is used also in `examples/p4est_3d_dgsem/elixir_euler_free_stream_boundaries.jl`, is given below:
 ```
 *Heading

diff --git a/src/meshes/p4est_mesh.jl b/src/meshes/p4est_mesh.jl
@@ -659,7 +659,7 @@ function preprocess_standard_abaqus_for_p4est(meshfile_pre_proc,
                                 new_line = join(parts[1:5], ',')
                             elseif occursin(quadratic_hexes, current_element_type)
                                 # Print the first (element), second to ninth (vertices 1-8) indices to file.
-                                # The node order is fortunately the same for hexes/bricks of type "C3D20", "C3D27", see
+                                # The node order is fortunately the same for hexes/bricks of type "C3D27", see
                                 # http://130.149.89.49:2080/v2016/books/usb/default.htm?startat=pt06ch28s01ael03.html
                                 new_line = join(parts[1:9], ',')
                             end