Contact TYPE24:
• | Possible overcosts due to abnormal number of impact candidates identified. |
• | Elastic part of contact energy not computed in TH |
• | Wrong force output for shells in case of node sliding in corners of a T or X connection |
• | Single precision + AMS + HMPP: possible segmentation violation in Starter |
• | Possible segmentation violation in SPMD with Inacti=0 and 5 |
Connectors and kinematic constraints:
- | Penalty formulation (spotflag=25, 26): |
▪ | Wrong behavior with the option Idel. |
▪ | Incorrect contact energy |
- | Possible negative mass error |
- | Incorrect contact forces in Anim file when using solid (hexa) elements |
- | Possible non repeatability issue (/PARITH/ON) with Ignore=2, Spotflag=1, Idel2=1.
It appears when a node is projected at the border of 2 segments |
• | //SUBMODEL compatibility with /RBE3 |
• | /PROP/KJOINT2 + /DT/NODA/CST: in case F(0)<>0, the joint is locked |
• | Possible Starter segmentation error when using KJOINT2 |
• | Possible Engine segmentation violation when using /RBE2 |
Sensors:
• | /SENSOR based on force does not work as described in manual |
• | /SENSOR/INTER compatibility with /INTER/SUB ID: possible Starter Error ID 339 (undefined Interface ID) |
Multi-domain:
• | Possible Starter error with /SPH + /SECT + /FRAME/MOVE |
• | Possible errors with /FRAME orientation computation related to /SPHBCS when applied to SPH particles belonging to the subdomain |
SPH:
• | In /SPH/INOUT if Fscaler is not defined, no SPH elements were created. Fscaler default value is now set to 1.0 |
• | Checkpoint restart (CHKPT) not working correctly with SPH |
• | Possible corrupted anim files when /ANIM/BRICK/DAMA output was requested for SPH |
Output
• | /STATE/NO_DEL: Writes in .sta file connectivities and all variables only for non-deleted elements. This is useful when several load-cases are run sequentially on the same model: we want to use the deformed geometry and the plastic strains coming from the previous run, but the deleted elements. |
• | /STATE/BRICK/STRESS/FULL for tshell16 is not working. |
• | Extrapolated values of /ANIM/GPS/TENS are incorrect when SPMD is used; similarly stress values for bricks (for example SXijk value) in TH output are incorrect. |
• | Possible Engine failure when /STATE/BRICK/FAIL + /PROP/TYPE20 (thick shells) are used. |
• | /LOAD/PFLUID and /ANIM/VECT/FEXT: external forces output in ANIM file is incorrect. |
• | Possible Engine segmentation violation error if scalar values output on 1D elements are requested (for example: /ANIM/TRUSS). |
• | Stress tensor output for coating shells (skin of brick elements) in ANIM file is null. |
• | /ANIM/SHELL/EPSP/ALL: wrong plastic strain value in animation output. |
Submodels compatibility extended to:
• | /MONVOL/COMMU1 and /MONVOL/FVMBAG1 with porosity option |
• | /INTER/TYPE2 with Spotflag=20, 21 |
• | /MAT/LAW83 and /MAT/LAW58 |
• | /FAIL/TAB and /FAIL/TAB1 |
User Subroutines:
• | Advanced user laws are not working in multithread. |
• | Wrong user values in animation output, if user law has high number of uvar (like number 99). |
• | Results repeatability (/PARITH/ON) is not ensured for solid with user-defined property (igtyp > 29). |
• | Possible segmentation error in Engine, if interface TYPE2 with failure + using user dynamic library. |
• | Material User Law in dynamic Library for Shell - Wrong Integration point number |
Poor Scalability in SPMD Parallel Mode:
• | Possible load unbalance with consequent poor scalability when parabolic tetra4 (Irot=1) are used (domain decomposition issue in the Starter). |
• | Poor scalability with high number of SPMD domains in case of SPH + TYPE7 contact. |
Implicit
• | /ANIM/VECT/DISP output is incorrect (by a factor 2x) with displacement computed from nodes coordinates. |
• | /IMPL/NONLIN: Possible Engine segmentation violation error if models contains RBE2 or RBE3. |
• | Results cannot be output for decreasing load in post buckling analysis. |
• | Starter may take too much time to run and hang. |
• | Possible Engine segmentation violation when using /IMPL/SOLVER/2 (MUMPS). |
Miscellaneous:
• | /SENSOR/INTER and /SENSOR/SECT compatibility with SPMD: when changing the number of SPMD domains, the sensor is not activated at the same time (impulse instead of force was used) |
• | Possible time step under-estimation for parabolic tetra4 (Itet=1): time step smaller than tetra10 |
• | Result repeatability not respected when /ADMAS/PART is used |
• | Possible starter segmentation violation if the model contains unused functions (affects 14.0 and 13.0.214 only) |
• | Possible engine segmentation violation on win64 with /IMPVEL/LAGMUL |
• | Starter may output non-ASCII characters |
- | If the number of warnings is too high |
• | Orthotropy initialization in version 14.0 (/INISHE/ORTHO and /PROP/TYPE9): Starter stops with ERROR ID: 26. |
• | Encrypted material /MAT/LAW50 not correctly handled in submodel |
• | Possible starter failure, if /PROP/SPH cards are encrypted |
• | Possible engine failure, if /MONVOL/GAS with venting is used |
• | /TH/FRAME output is null, if SPMD is used (correct in SMP) |
• | Starter errors out when /TH/FRAME + SUBMODEL + SPH are used |
• | Transformations and rotations of submodels: sequences are not respected (rotations are applied first) |
• | Possible Engine failure (segmentation violation) when |
- | /OUTP + SPMD + IMPI are used |
- | /OUTP/VECT/ROT is requested for solid elements; /OUTP/VECT/ROT is not available for solids |
- | /MAT/LAW32 + /PROP/TYPE1 are used |
• | Warning 542 (rigid body inertia): inertia components mixed in the warning message |
• | /INTER/TYPE18: Possible false memory allocation error in Starter (increase MULTIMP) |
• | Starter outputs an unexpected warning (temperature is not computed) when DEF is requested in /TH/NODE |
• | If no title in /TH/NODE, the run goes through, but there is no output in TH; error message has been added in the Starter. |
|