User Tools

Site Tools


interface

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
interface [2022/05/11 13:29]
calogero [.geo file]
interface [2024/02/07 14:25] (current)
calogero [Programation tips]
Line 1: Line 1:
 +Implemented by Calogero Gallo 2021
 +
 +[[interface:​first_start|First start]]
 +
 ====== Gmsh ====== ====== Gmsh ======
  
Line 24: Line 28:
  
 - 3.Nodes => Add nodes to the list of nodes (they have no condition or mesh), these are usefull for specific case that can't be created in Gmsh. - 3.Nodes => Add nodes to the list of nodes (they have no condition or mesh), these are usefull for specific case that can't be created in Gmsh.
 +
 +- 4.Fixed => possible to fix node created in gtl file
  
 - 5.Degrees of freedom (DOF) renumbering - 5.Degrees of freedom (DOF) renumbering
Line 95: Line 101:
  
  
-Not yet developped. 
  
 === 10. Setting of the initial speeds in dynamics === === 10. Setting of the initial speeds in dynamics ===
Line 150: Line 155:
  
 List of elements developped :  List of elements developped : 
-BLZ3D (3D case) +  * BLZ3D (3D case) 
-CFI3D (interface element in 3D => surface) +  ​* ​CFI3D (interface element in 3D => surface) 
-BINDS (element with non specifical dimension) +  ​* ​BINDS (element with non specifical dimension) 
-BLZ2T (2D case) +  ​* ​BLZ2T (2D case) 
-CONRA (interface element in 2D => line/curve)+  ​* ​CONRA (interface element in 2D => line/curve) 
 +  * SUCHA (see [[interface:​sucha|SUCHA for G2L]]) 
 +
  
 To developped other elements, it can be done by nearly doing a copy and paste of these examples. To developped other elements, it can be done by nearly doing a copy and paste of these examples.
Line 199: Line 206:
 ==== Transition macro ==== ==== Transition macro ====
  
-These macro are developped ​in Gmsh, the idea is to get a well structured transition to reduce as much as possible the number of elements.+These macro are developed ​in Gmsh, the idea is to get a well-structured transition to reduce as much as possible the number of elements. ​To determine exactly the transition, some parameters are needed :  
 + 
 +- the position of two points (see Figure below) 
 +- the length of the upside 
 +- the length of the downside 
 +- the number of element on the raffine side (upside) (must be a multiple of 3) 
 +- the number of transition between the down and up 
 + 
 +{{ :​interface:​image_transition.jpg?​nolink&​400 |}} 
 + 
 +It is possible to keep nodes duplicated, or avoid them by using "​Coherence;"​ or "​Coherence Mesh;"​ 
 + 
 +{{ :​interface:​test1.rar |}} 
 + 
 +{{ :​test2_rotation.rar |}} 
 + 
 +{{ ::​test4_cylinder.rar |}} 
 +==== Listing for .dep/.loa files ==== 
 + 
 +Using "​LISTE"​ as name of physical group, the interface will create a .txt file with a list of all the nodes which belongs to the physical group. 
 ====== Exemple ====== ====== Exemple ======
  
Line 214: Line 241:
  
 {{ :​interface:​binds_rolling_support.rar |}} {{ :​interface:​binds_rolling_support.rar |}}
 +
 +
 +====== Programation tips ======
 +
 +GMSH is a powerful tool, but due to its completness it is not always easy to find some informations. There exists a where people can directly ask question to developpers [[https://​gitlab.onelab.info/​gmsh/​gmsh/​-/​issues]]. There exists also a place where archives are stored [[https://​onelab.info/​pipermail/​gmsh/​]],​ this place is not very friendly to find a subject (it is better to use google with a research that looks like "GMSH XXX" where XXX represents the subject, better to try all the possibilities). ​
 +
 +
 +Below you can find a list of all questions that were looking very interesting :
 +
 +  - **Modify .geo trough python** : [[https://​onelab.info/​pipermail/​gmsh/​2011/​006588.html]]
 +  - **Avoid duplicate geometry/​mesh** : [[https://​gitlab.onelab.info/​gmsh/​gmsh/​-/​issues/​983]]
 +
interface.1652268561.txt.gz · Last modified: 2022/05/11 13:29 by calogero