B modeling
==============


But
---

The purpose of this test is to validate the use of imposed moves (other than blocks) in CALC_EUROPLEXUS.


Description
-----------

The plexu03a test is repeated by keeping only the cable in the model.

The degrees of freedom DY and DZ of the 5 nodes present are blocked. The movements are imposed in DX on the 5 nodes also so that there is no dynamic effect (which makes it possible to have a reference solution with STAT_NON_LINE).


.. csv-table::

    "**Knot**", "**DX**"
    "NC001001 ", "0"
    "NC001002 ", "0.025"
    "NC001003 ", "0.05"
    "NC001004 ", "0.075"
    "NC001005 ", "0,1"



Principle of validation
----------------------

We test the movements in DXsur with several knots at the end of loading.


Tested values
---------------


.. csv-table::

    "**Node**", "**Component**", "**Reference Type**", "**Reference Value**", "**Tolerance**"
    "NC001005 "," :math:`\mathit{DX}` ", "'AUTRE_ASTER'", "''", "0.1"," 0.1%"
    "NC001003 "," :math:`\mathit{DX}` ", "'AUTRE_ASTER'", "''", "0.05"," 0.1%"



.. csv-table::

    "**Mesh**", "**Component**", "**Reference Type**", "**Reference Value**", "**Tolerance**"
    "SG001003 "," :math:`N` ", "'AUTRE_ASTER'", "''", "1428571.42857"," 2.5%"


The expected trips are obtained, which means that the load has been correctly taken into account. The difference in constraints is due to the difference in kinematics between Code_Aster and EPX. Indeed Code_Aster does not have GROT_GDEP kinematics for BARRE modeling, so we use PETIT_REAC.