Case01 Mesh size defined on geometry entities
Contents
In the present case the method for defining mesh element sizes on geometry entities is shown. The following files are provided in Mesh_002\Case01\Data :
•Mesh_002_Case01a.dat : mesh generation with a default element size of 120 m and a smaller mesh size to two surfaces
•Mesh_002_Case01b.dat : mesh generation with a default element size of 120 m and a smaller mesh size to two surfaces and the lines that define those two surfaces
Below a description of the data files is provided. It should be noted that only the data relative to mesh generation will be described in detail while for the remaining data a brief description is provided.
Datafile Description
The basic data includes:
1.Geometry definition data (Nodal_data , Geometry_line , Geometry_surface and Geometry_volume ) at the end of the file after the END DATA command to define the cube geometry. 2.Group_data and Group_control_data for a single group with TET4V elements (note that the Element_type defined must be valid for the type of mesh being generated) 3.Material_data and Fluid_properties defining an elastic material 4.Support_data defining displacement fixities in the 3 directions for the whole cube volume (by assigning the corresponding Displacement_codes set to the internal Geometry_set "All_volumes" ) 5.Mesh generation data (Mesh_control_data and Unstructured_mesh_data ) with the appropiate data for each case 6.Control_data defining the Duration of the simulation stage, the Target_number_time_steps for the stage as well as several output options.
Case01a Mesh Generation Data
Case01b Mesh Generation Data
|
| Results |
The results are provided in: Mesh_002\Case01\Results. As can be seen in the figure below in Case01a the elements in the edges do not have the same size as the adjacent surface. This is because the mesh is generated in an hierarchical manner where lines are discretized first, then surfaces and last volumes. In Case01b can be seen that the specified element sizes on the lines enforced the mesh size in those entities. Where two lines share a node the smaller size takes priority.
Results for the two cases
|
