commit:futur:db

# Differences

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

Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||

commit:futur:db [2018/07/12 11:11] – [Implementation] boemer | commit:futur:db [2018/07/17 11:45] – [Test case] boemer | ||
---|---|---|---|

Line 1: | Line 1: | ||

- | ====== Commit 2018-07-12 ====== | + | ====== Commit 2018-07-17 ====== |

- | In this commit, a new contact traction element was created to set the traction force to zero at the nodes that are in contact within a specified contact interaction. | + | ===== Description ===== |

+ | In this commit, the out-of-plane thickness evolution in the generalized plane strain state is coherently accounted for in the computation. | ||

- | ===== How to use the new feature ===== | ||

- | A '' | ||

- | prp = ElementProperties(ContactTraction2DElement) | + | In the previous figure, the square was represented in 3D although the computation is performed in the generalized plane strain state. The lateral movement of the left and right sides of the square is blocked. A pressure $p$, identical in both cases, pushes the square against to contact tool (frictionless). When the out-of-plane thickness of the square increases, as shown on the right, the resultat force created by the pressure increases due to the increase of the surface on which this pressure is applied. Moreover, if the increase of the out-of-plane thickness is not taken into account in the contact interaction,in the computation of the area in contact, the increase of the resultat pressure force will increase the gap. Hence, $\text{gap}_{1} < \text{gap}_{2}$ previously. . |

- | prp.put(PRESSURE,p[') | + | |

- | prp.put(NBR_CONTACT_INTERACTION, 3) | + | |

- | | + | |

- | Hence, if nodes in this ''in contact (in the previous mechanical iteration) in the contact interaction 3, the traction force applied to these nodes is set to zero. | + | |

- | ===== File structure ===== | + | ===== Test case ===== |

- | | + | |

- | Instead of implementing the new feature directly in the '' | + | |

- | | + | |

- | Some minor modifications: | + | |

- | * The new property '' | + | |

- | * It was necessary to add '' | + | |

- | * Untabify in '' | + | |

- | * '' | + | |

- | * The method '' | + | |

- | | + | |

- | | + | |

- | | + | |

- | | + | |

- | ===== Implementation ===== | + | |

- | | + | |

- | Concerning the implementation, | + | |

- | * '' | + | |

- | | + | |

- | * '' | + | |

- | | + | |

- | * '' | + | |

- | | + | |

- | * '' | + | |

- | | + | |

- | ===== Test cases ===== | + | |

+ | The test case in the following figure is identical to what was decribed previously. | ||

+ | The gap can be computed in various ways, numerically, | ||

+ | * First, the numerical computation simply consists in extracting the gaps in the Metafor computation and choosing the one at $P_{4}$. | ||

+ | * Second, the analytical computation provides the value of the gap via the following formula: $\text{gap} = p/k_{n}$, where $k_{n}$ is the normal penalty coefficient. | ||

+ | * Thirdly, the semi-analytical/ |

commit/futur/db.txt · Last modified: 2018/07/17 12:03 by boemer