HyperWorks Release Notes

General Updates

General Updates

Previous topic Next topic Expand/collapse all hidden text  

General Updates

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

Highlights


hmtoggle_arrow1Contact TYPE24
Improved automatic treatment of initial penetrations with Inacti = 5 flag. It allows to adjust the initial position of the contact segment to the penetration value; when the penetrating node has rebounded the contact segment goes back to its original position (defined by the nodes of the master surface).
Compatibility with /INTER/SUB (force transducer): extracts time history forces on a subset of the contact surface
Single precision version: robustness improvements

 

hmtoggle_arrow1Global Time Step
Element based time-step in some cases might be underestimated; GTS method tries to estimate a higher stable time-step on the full model. The estimation has a computational overhead, but in most of the cases the overcost is low compared to the cpu saving. Beta implementation in this version as its usage is currently limited to certain elements types and contact interfaces.
hmtoggle_arrow1Nodal Time Step Compatibility with Advanced Mass Scaling
When AMS is applied to a group of parts, now /DT/NODA/CST is correctly applied to the remaining parts; in former versions, element time-step was applied at borders of non-AMS parts, which was either reducing AMS benefits or making it ineffective in some cases.

 

hmtoggle_arrow1Multi-Domain
In previous versions Starter was allowing SPH in one of the two domains only; now SPH can be present in both time domains. This might be useful for applications like airplane ditching where SPH are used to model both the on-board fuel and the external water.
/ALE/LINK/VEL now compatible, allowing an ALE mesh to follow the Lagrange structure motion without needing a huge ALE volume to embed the structure in its displacement.
/PLOAD now compatible to speed-up a Lagrange surface deployment in an ALE volume or simulate wind based motions of a structure over a liquid.

 

hmtoggle_arrow1SPH
New formulation to prevent tensile instability.
TH output of mass-flow through a section.
Robustness improvement: memory is dynamically allocated for SPH. (It is no longer necessary to define the MAXSPH parameter in /SPHGLO.)
Solid elements deletion and conversion into SPH (Sol2SPH).
-Compatibility extended to HEPH
-LAW81
Starter checks and error messages improvements for /SPH/RESERVE: Starter checks and errors out if PART_ID does not exists and/or if it does not refer to a SPH part.

 

hmtoggle_arrow1Optimization
Support of solid topology in RAD-OPT and ESLM with Direct Density Control: new input / output keywords for solids filling percentage /INIBRI/FILL and /ANIM/BRICK/FILL
Multi Model Optimization (MMO): possibility to define a coordinate system (/SKEW) to map the design domains
Composite sizing optimization in RAD-OPT; support of:
-/PROP/TYPE11 (Sandwich shell)
-/PROP/TYPE17 (STACK)
-/PROP/TYPE19 (PLY)
-Manufacturing constraints (/DCOMP related entry)
Support Bulk format data in RAD-OPT with /BULK, /BULKFMT, /BULKMAT and /BULKPROP

 

hmtoggle_arrow1Output
/PROP/TYPE20: Element strain output for thick shells (Istrain=1).
/STATE/NO_DEL: option to exclude deleted elements from the state file (.sta).
/INIBRI/AUX: possibility to reduce file size of state file for brick elements initialization. For some material models only few variables are needed; the ones which are not specified are set to zero.

 

hmtoggle_arrow1User Subroutines

Several enhancements to improve usability; accessibility is extended to:

Charactheristic element length and area for USER/FAIL.
Deformation gradient tensor, both for solids and shells.
Stretch tensor U.
Thermal information.

 

hmtoggle_arrow1Implicit Non-Linear
Improved usability with visual convergence indicator and table with time step, iteration history, residual
/MAT/LAW12 support in implicit analysis

 

hmtoggle_arrow1Starter and Engine Checks
Possible segmentation violation may occur in previous releases, if an include file is missing. RADIOSS Starter provides now a proper error message whenever nodes are not read.
Starter checks all include files (instead of stopping at the first missing one) and prints a clean summary.
Starter checks if sections content is empty and prints a warning message.
Starter checks in /MAT/LAW1 if more than 1 Integration Points is prescribed; N is reset to zero and a warning is output; it prevents possible .sta file reading issues.
Starter checks if PART is defined in the input deck and outputs a proper error message, if no part is detected.
Engine errors out with a proper error message, if Ncycle in /RFILE is too large ( >10 digits); segmentation violation error was occurring in previous releases.
More specific Engine error pointing to the actual input line with the unrecognized keyword(s) is replacing the existing generic engine “INPUT ERROR IN OPTION ANIM”.

 

hmtoggle_arrow1Messages
Repetitive Starter warnings and errors messages have been reformatted and compacted. For example, for incompatible kinematic conditions for tie contact, a list of nodes for a given tie interface is printed (as opposite to print a warning for each node).
An additional summary of warnings and errors is printed at the end of the Starter *0.out file.
Engine outputs a specific message when /SENSOR/TIME is activated.

 

hmtoggle_arrow1Resolved Issues

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:

/INTER/TYPE2
-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
/TSHELL16
/MAT/LAW83 and /MAT/LAW58
/FAIL/TAB and /FAIL/TAB1
/REFSTA with Offsets

 

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
-For /GRBRIC
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.