Differences

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

--- commit:2018:07_13 [2018/07/13 10:17] – created boemer
+++ commit:2018:07_13 [2018/07/17 18:57] (current) – boemer
@@ Line 24: / Line 24: @@
   * Untabify in ''ContactElement.h/cpp''.
   * ''getSlaveNode()'', previously private method in ''ContactElement.h/cpp'', becomes public to use it in ''ContactTractionElement.inl''.
-  * The method ''isInContactPrev()'' was added in ''ContactElement.h/cpp'' to get the contact status at the end of the previous time iteration.  Using this contact status has the advantage that the contact traction activation/deactivation does not happen during the same time step, i.e. during the mechanical iteration.  It might be possible to use the current contact status but this could introduce some undesired oscillations.
+  * The method ''isInContactPrev()'' was added in ''ContactElement.h/cpp'' to get the contact status at the end of the previous time step.  Using this contact status has the advantage that the contact traction activation/deactivation does not happen during the same time step, i.e. during the mechanical iteration.  It might be possible to use the current contact status but this could introduce some undesired oscillations.
@@ Line 44: / Line 44: @@
 Two test cases were created in the folder ''mtContact/tests'' to test the ''ContactTractionElement'' in 2D and 3D.  Hence, they have the same names than the elements that are tested: ''contactTraction2DElement.py'' and ''contactTraction3DElement''.  The 3D test is the natural extension of the 2D case.  Hence, only some details about the 2D case are explained here.
-{{ :commit:2018:07_12:contacttraction2delement.png?600 |}}
+{{ :commit:2018:07_13:contacttraction2delement.png?600 |}}
 As shown in the previous figure, two squares are crushed by a compression pressure and a contact tool that moves downwards by $2 \; dy$.  In the case on the left, the traditional ''Traction2DElement'' is used, while the new ''ContactTraction2DElement'' is used on the right.  The ''ContactTraction2DElement'' works correctly, if the total force on node $P_{14}$ along $\mathbf{y}$ is equal to the contact force along $\mathbf{y}$ at the end of the computation, i.e. that the traction force has been set to zero for the node in contact.  To check this equality, the difference between both forces (total and contact) is computed in the extractor ''diffTotalAndContactForceInCase2''.  The results of the cases with the ''Traction2DElement'' and the ''ContactTraction2DElement'' are also compared by computing the differences of the total force along $\mathbf{y}$ at the nodes $P_{4}$ and $P_{14}$ in the extractor ''diffTotalForcesBetween2Cases''.  This difference should be different from 0, unlike the previous one.
+===== Added [a] / deleted [d] / modified [m] / renamed [r] test cases ======
+<code>
+[a] mtContact/tests/contactTraction2DElement.py
+[a] mtContact/tests/contactTraction3DElement.py
+</code>
+ --- // [[dominik.boemer@uliege.be|Dominik Boemer]] 2018/07/13 10:30 //