Parameters for type 14 (solid) property? [SOLVED]

Altair Forum User
Altair Forum User
Altair Employee
edited October 2020 in Community Q&A

After reading the reference guide, I don't understand the parameters for the property 14:

1. Isolid - What is this for??

2. Ismstr - What is the purpose? We already define linear or non-linear in material, so why this option? What does value 4 'full geometric nonlinearities' do?

3. Istrain - What does 'strain post-processing' mean? Does this affect result values or is this just for animation purposes?

Tagged:

Answers

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited June 2016

    Refer below video from Radioss ebook.Isolid is for fromulation

    Refer  after 2mint for I solid & 6mint for Ismstr.

    https://altair-2.wistia.com/medias/9ahjo4tqz8

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    I could not understand much from the video, so I will ask questions specifically for my case:

     

    1. What is the difference between value 1, 4 and 10 for Ismstr :

    = 1: small strain from time=0

    = 4: full geometric nonlinearities (/DT/BRICK/CST
    has no effect)
    =10: Lagrange type total strain (see Comment 20)

    What is the purpose of this parameter? We already define linear or non-linear in material, so why this option? What does value 4 'full geometric nonlinearities' do?

     

    2. Istrain - What does 'strain post-processing' mean? Does this affect result values or is this just for animation purposes?

     

    Please try to answer specifically instead of directing to some generalised video, it would save a lot of time for both of us.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    Isolid is to define different solid element and hourglass formulations. The various element formulations are explained in detail In the video link provided by Rahul.

     

    Ismstr (Strain formulation flag) has a major influence in the simulation. Usually for problems involving large deformations, a large strain formulation would be used. In RADIOSS this is the default setting, but it is also possible to use a small strain formulation. This formulation is not very accurate for large deformations, but it is more robust and enables the time step to not decrease too much. Indeed, large deformation/rotation problems may lead to mesh distortion which causes the time step to drop drastically; computation may even stop due to a negative volume. The small strain formulation overcomes all this by assuming a constant volume, consequently the time step becomes constant, and even if the mesh is completely distorted, computation will not be stopped due to the negative volume. It is also possible to switch from a large strain formulation to a small strain formulation in order to prevent a negative volume and to maintain a good time step using the /DT/BRICK/CST option in the engine file having a critical time step.The option /DT/BRICK/CST is only active if the brick elements have the flag Ismstr=2. When Ismstr is 4, ie full geometric non linearity , time step imposed using /DT/BRICK/CST will not have any effect on the simulation. Small strain formulation is activated from time t=0, if Ismstr =1. It may be used for a faster analysis, but the accuracy of results is not ensured. The flag Ismstr =10 is only compatible with some material laws using total strain
    formulation (example, Laws 38, 42, 69 and 82). The Left Cauchy-Green strain is used forLaws 38, 42, 69 and 82.

    For detailed Ismstr - element formulation compatibility you can refer the material library available in help menu.

     

    Istrain does not affect any result values. The strain tensor is not computed by default. By setting flag Istrain (flag to compute strains for post-processing) to 1 the user will get strain tensor output.

     

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    Thanks for the detailed reply George! I guess I will stick to large deformation option for my drop test. I am not getting any negative volume and the computation time is also fine with me.

    the user will get strain tensor output.

    Is it possible to view this strain tensor with HyperView? I am viewing the plastic strain already, and from what you said, I don't think that that result is getting modified by this parameter.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited June 2016

    We can view the strain tensor in HyperView. Please find the attached image.

    <?xml version="1.0" encoding="UTF-8"?>TENSOR.JPG

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi all,

     

    I have ran an RADIOSS impact analysis. Where i am facing issue that elements are deforming severely where ever it contacts. I not sure this is due to contact issue or  section properties of the solids. Please help with this. 

     

    Contact type = 7

    section properties : P14 solid

     

    All are brick mesh and the dm/m is less only

    image.png.83e9f9e411f63fbd2574a8d4f550b28f.png

     

     

     

     

     

     

     

     

     

     

    image.png.407b003f977ef3d174f5e87a1cd7ba69.pngimage.png.aca08f1925a55f263823a685fac7c202.png

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi,

    The property card seems fine.

    In the interface card try with Istf=4, Igap=2 options. Also check the material parameters and ensure they are correct.

    From the time history file (T01) please plot the internal energy, kinetic energy, contact energy and hourglass energy curves in HyperGraph, take a snapshot and upload the same.

     

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi George,

     

    Please find the attached image of energy curves.I think material properties are perfect since i haev converted it from the Ls dyna model which was successful run. I have used  MATLAW 36. 

     

     

    image.png.6292c7c0e2b8f70f7c9553ca2ec074c4.png

     

    image.png.8ef9d24bc42faafada9a2a461d3f6968.png

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi,

    Contact energy seems to be high in this model.

    You can check for any penetrations/intersections in the model. The material parameters is another chance which can cause high contact energy.

     

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi ,

     

    There is no intersection in the model. And a slight penetration is there about 0.09mm and for that i have used the Inaction = 6. 

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi,

    Can you please share the model file through the secure dropbox?.

     

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi George,

     

    Sorry. Unfortunately i can't share the model due to privacy. 

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi,

    How did you create the Type 7 interface?. Did you create contact surfaces and recalled in the interface or selected as components?.

    Can you share the material parameters?.

     

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi,

     

    I have selected the contact  by components not by the contact surfaces. Please see the attached image for the same.

    image.png.4f7225aac1cd7f43d0cd2efabb4cf5bf.png

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited April 2018

    Hi,

    Use Igap=2, and provide a Stmin of 1000 N/mm so that it will avoid too soft contact.

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi,

     

    I feel that there is issue in Section properties definition. Is there anyone has faced the same issue before ? element deforming severely(no Hourglass) without any error notification.   

  • jsk459
    jsk459 Altair Community Member
    edited April 2018

    Hi @George P Johnson

     

    What may be the reason for below shown behavior ? It is due to contact or brick elements section parameters issue? 

    image.png.98eccaf770b0aa6677780dd80fb36d04.pngimage.png.8c53dc5bc66b65b7e12d1865ee120092.png