Operands ========= Operand MATER -------------- .. code-block:: text ♦ MATER =/mat, [subdue] /l_mat, [l_mater] This keyword allows you to enter the name of the material (subdue) defined by DEFI_MATERIAU [:external:ref:`U4.43.01 `], where the parameters necessary for the chosen behavior are provided. In the case of polycrystals, it may be necessary to donate several materials (cf. ssnv194c). Keyword COMPORTEMENT ------------------- The syntax for this keyword is described in document [:ref:`U4.51.11 `]. Some laws of behavior use "intrinsic" state variables, that is, state (control) variables that are not defined by AFFE_VARC. There are two cases: * The state variables corresponding to the size of an element. These are behaviors BETON_DOUBLE_DP, ENDO_PORO_BETON, FLUA_ENDO_PORO, and RGI_BETON. These behaviors are not usable in SIMU_POINT_MAT * The state variable corresponding to the velocity gradient used in MONOCRISTAL. By default, we set this variable to zero **Note:** in the SUPPORT =' POINT 'mode, it is assumed that the coordinates of the Gauss point are :math:`(\mathrm{0,0,0})`. Keywords INCREMENT/ARCHIVAGE/NEWTON ------------------------------------- The syntax for these keywords is described in document [:ref:`U4.51.03 `]. The INCREMENT keyword defines the time intervals taken in the incremental method. The ARCHIVAGE keyword defines when the results are stored in the tabres table. In the case SUPPORT =' POINT ', these moments can only be defined by the keyword LIST_INST with the relative precision PRECISION. The keyword NEWTON, optional, allows you to modify the default values of the convergence parameters of the Newton method. Keyword CONVERGENCE ------------------- .. code-block:: text ◊ CONVERGENCE =_F () If neither of the following two operands is present, then everything is as follows: RESI_GLOB_RELA = 1.E-6. Operand RESI_GLOB_RELA/RESI_GLOB_MAXI ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .. code-block:: text ◊ |RESI_GLOB_REAL = resrel, [R] The algorithm continues global iterations as long as: :math:`\underset{i=\mathrm{1,}\dots ,\mathrm{nbddl}}{\mathrm{max}}\mid {F}_{i}^{n}\mid >\text{resrel}\mathrm{.}\mathrm{max}\mid L\mid` where :math:`{F}^{n}` is the residue of iteration :math:`n` and :math:`L` is the vector of the imposed load and the support reactions (Cf. [:ref:`R5.03.01 `] for more details). When the load and the support reactions become zero, i.e. when :math:`L` is zero (for example in the case of a total discharge), we try to pass from the relative convergence criterion RESI_GLOB_RELA to the absolute convergence criterion RESI_GLOB_MAXI. This operation is transparent for the user (alarm message sent in the.mess file). When the vector :math:`L` becomes different from zero again, we automatically go back to the relative convergence criterion RESI_GLOB_RELA. However, this failover mechanism cannot work at the first step of time. Indeed, to find a reasonable value of RESI_GLOB_MAXI automatically (since the user did not enter it), we need to have had at least one step converged on a RESI_GLOB_RELA mode. Therefore, if the load is zero from the first moment, the calculation stops. The user must then already check that the zero load is normal from the point of view of the modeling he is doing, and if this is the case, find another convergence criterion (RESI_GLOB_MAXI for example). If this operand is not present, the test is performed with the value by default, unless RESI_GLOB_MAXI is present. .. code-block:: text ◊ |RESI_GLOB_MAXI = resmax, [R] The algorithm continues global iterations as long as: :math:`\underset{i=\mathrm{1,}\dots ,\mathrm{nbddl}}{\mathrm{max}}\mid {F}_{i}^{n}\mid >\text{resmax}` where :math:`{F}^{n}` is the residue of iteration :math:`n` (Cf. [:ref:`R5.03.01 `] for more details). If this operand is absent, the test is not performed. If both RESI_GLOB_RELA and RESI_GLOB_MAXI are present, both tests are performed. Operand ITER_GLOB_MAXI ~~~~~~~~~~~~~~~~~~~~~~~~~ .. code-block:: text ◊ ITER_GLOB_MAXI = /10 [DEFAUT] /maglob Maximum number of iterations performed to solve the global problem at each point in time (10 by default). Keyword RECH_LINEAIRE -------------------- The syntax for these keywords is described in document [:ref:`U4.51.03 `]. The RECH_LINEAIRE keyword allows, in the case SUPPORT =' ELEMENT ', to activate the linear search to help the convergence of Newton's algorithm. This feature is not available for SUPPORT =' POINT ', as it does not seem necessary. Keyword MODELISATION ------------------ The keyword MODELISATION allows, in the case SUPPORT =' ELEMENT ', to perform the calculation on a 3D element or on a 2D element, in plane constraints or in plane deformations. It is not available in the case SUPPORT =' POINT ', because it suffices to impose a zero value on the components corresponding to the plane stresses or to the plane deformations to obtain the same result. This keyword allows you to define the dimension of the problem being treated: 3D (by default) or 2D: plane deformation or plane stress. In the 2D case, the components of the tensors provided under the keywords SIGM_IMPOSE, EPSI_IMPOSE,, SIGM_INIT, EPSI_INIT are 4 in number: XX, YY, ZZ, ZZ, XY. Operand ANGLE -------------- This keyword allows you to specify an angle (in degrees) to perform an overall rotation around :math:`Z` applied to both loading, meshing, and stripping. Above all, this makes it possible to verify the reliability of the integration of behavior, as in tests COMP001, COMP002. By default, the rotation is identically zero. In the case of materials with an intrinsic orientation (orthotropy, crystalline behaviors), the keyword MASSIF should also be used, with a first angle value identical to that provided under ANGLE. Keyword MASSIF -------------- Operands ANGL_EULER/ANGL_REP ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ These keywords make it possible to define an orientation intrinsic to the material (orthotropy, crystalline behaviors), and make it possible to use the keyword MASSIF from AFFE_CARA_ELEM [U4.42.01] in the macro-command. By default, the orientation is zero, and AFFE_CARA_ELEM is not used as a step. Tags SIGM_INIT/EPSI_INIT/VARI_INIT -------------------------------------- These keywords make it possible to define an initial state using the data: 1. components of the initial constraints (all the components are not necessary, by default the value 0 is taken), 2. components of the initial deformations (if the keyword EPSI_INIT is present, all the components of the initial deformations must be provided: 4 in 2D, and 6 in 3D) 3. the set of initial internal variables for the behavior used. This feature is shown in test SSNV160E. Tags SIGM_IMPOSE/EPSI_IMPOSE -------------------------------- Operands SIXX, SIYY, SIZZ, SIXY,, SIXZ, SIYZ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ These keywords make it possible to define components of the stress tensor imposed at the material point, using time functions. These functions can be defined using DEFI_FONCTION [:ref:`U4.31.02 `] or using FORMULE [:ref:`U4.31.05 `]. By default, unassigned components are identically zero. Operands EPXX, EPYY, EPZZ, EPXY,, EPXZ, EPYZ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ These keywords make it possible to define components of the deformation tensor imposed at the material point, using time functions. These functions can be defined using DEFI_FONCTION [U4.31.02] or using FORMULE [:ref:`U4.31.05 `]. By default, unassigned components are left without value (no imposed deformation). It should be noted that, in the case of deformation model PETIT_REAC, it is not possible to impose the deformation exactly using EPSI_IMPOSE. In fact, because of the *incremental* nature of this model, the deformations obtained by this model at the end of calculation SIMU_POINT_MAT will be different from what will have been imposed, except in small deformations. For large deformations it is therefore preferable to use model GDEF_LOG, which does not suffer from this disadvantage. Tags GRAD_IMPOSE -------------------- Operands F11, F12, F13, F13, F21, F21, F22, F22, F23, F31, F32, F33 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ These keywords make it possible to define all the components of the imposed transformation gradient tensor, in large deformations (DEFORMATION =' SIMO_MIEHE ') cf. ssnd113 test). Tags MATR_C1/MATR_C2/VECT_IMPO -------------------------------------- These keywords make it possible, in the case SUPPORT =' POINT ', to directly define the coefficients of the matrices :math:`\mathit{C1}` **,** :math:`\mathit{C2}` and of the vector :math:`g` described in § :ref:`4.2 `: this thus makes it possible to define linear conditions on the unknowns (constraints and deformations of the material point) that are more general than the components imposed by the keywords SIGM_IMPOSE/EPSI_IMPOSE. All terms in matrices :math:`\mathit{C1}` and :math:`\mathit{C2}` that are not specified are zero. For an example of use, see test WTNV134B [:external:ref:`V7.31.134 `]. Operand AFFE_VARC ------------------ This keyword allows you to specify a command variable (cf. [:external:ref:`U4.43.03 `]) whose name is defined under the keyword NOM_VARC; the function defining the time evolution of this command variable is provided via the keyword VALE_FONC. The possible reference value vref is given by VALE_REF. In the case SUPPORT =' ELEMENT ', all command variables are allowed. In addition, for M_ ZIRC (resp. M_ ACIER), it is necessary to provide the evolutions of the 4 (resp. 7) metallurgical phases as a function of time. In the case SUPPORT =' POINT ', only command variables' TEMP ',' SECH ', and' IRRA 'are allowed. Keyword NB_VARI_TABLE ------------------- In the case SUPPORT =' POINT ', the NB_VARI_TABLE keyword allows you to limit the number of internal variables written in the table. In fact, for polycrystalline media, this one can reach several thousand. The number of columns in the table is then limited to nvar. On the other hand, the calculations are of course carried out with all the internal variables: these are only truncated in the result table. Keyword FORMAT_TABLE ------------------ ◊ FORMAT_TABLE = /' CMP_COLONNE '[DEFAUT] .. code-block:: text /' CMP_LIGNE ' In the case SUPPORT =' POINT ', the keyword FORMAT_TABLE makes it possible to define how quantities are stored in the result table (test SSNV194C illustrates these two formats). If the number of internal variables exceeds the maximum number of columns allowed for a table (9999, cf. D4,02,05), the format automatically switches to: FORMAT_TABLE = /' CMP_LIGNE '. FORMAT_TABLE = /' CMP_LIGNE ': ... V845 V846 V847 V848 NB_ITER ... 1.16186E-17 1.32359E-17 1.11751E-17 1.00000E+00 1.00000E+00 1.00000E+00 ... 1.29473E-16 1.47341E-16 1.24474E-16 1.00000E+00 1.00000E+00 1.00000E+00 ... 8.90739E-16 1.00875E-15 8.55093E-16 1.00000E+00 1.00000E+00 1.00000E+00 ... 4.40109E-15 4.92817E-15 4.21938E-15 1.00000E+00 1.00000E+00 1.00000E+00 ... 1.70332E-14 1.87022E-14 1.63484E-14 1.00000E+00 1.00000E+00 1.00000E+00 ... 5.44940E-14 5.80870E-14 5.25904E-14 1.00000E+00 1.00000E+00 1.00000E+00 FORMAT_TABLE = /' CMP_COLONNE ': ... INST GRANDEUR CMP VALEUR ... 4.97867E-03 VARI V845 -1.43828E+01 4.97867E-03 VARI V846 -2.63548E+01 4.97867E-03 VARI V847 2.80907E+01 4.97867E-03 VARI V848 1.00000E+00 5.00000E-03 EPSI EPXX -2.20535E-03 5.00000E-03 EPSI EPYY -1.96506E-03 5.00000E-03 EPSI EPZZ 5.00000E-03 5.00000E-03 EPSI EPXY -1.98892E-04 5.00000E-03 EPSI EPXZ -2.11427E-04 5.00000E-03 EPSI EPYZ -3.00870E-04 5.00000E-03 V7.32.119 SIGM SIXX 1.67146E-04 5.00000E-03 SIGM SIYY 2.78713E-05 5.00000E-03 SIGM SIZZ 3.01140E+02 5.00000E-03 SIGM SIXY 9.15194E-05 5.00000E-03 SIGM SIXZ 1.62000E-04 5.00000E-03 SIGM SIYZ 6.86376E-05 5.00000E-03 SIEQ VMIS 3.01140E+02 5.00000E-03 SIEQ TRACE 3.01140E+02 5.00000E-03 VARI V1 -1.58316E-03 5.00000E-03 VARI V2 -1.34287E-03 5.00000E-03 VARI V3 2.92604E-03 5.00000E-03 VARI V4 -2.81276E-04 ... Keyword OPER_TANGENT ------------------ ◊ OPER_TANGENT = /' NON '[DEFAUT] /' OUI ' The OPER_TANGENT keyword allows, in the case SUPPORT =' POINT ', to add to the result table the 36 values of the tangent operator resulting from the behavior. Operand INFO ------------ .. code-block:: text ◊ INFO = under Allows various intermediate printings to be made in the message file.