Unwanted beam appearing in Hyperview

rea2
rea2 Altair Community Member
edited October 2020 in Community Q&A

When visualizing my simulation (femur/tigh bone and pelvis/hip) in Hyperview, some kind of beam is appearing which seems to be a part of the cartilage of the tigh bone (femur). Does anyone know where this could come from?

Tried different versions with/without contacts and including or not including the lower layer of nodes of the cartilage (close to the femur) in the rigid body but nothing changed anything about the beam.

 

2n2ibq.png

 

Unable to find an attachment - read this blog

Tagged:

Answers

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited October 2018

    at first

    -which units did you use?

    -is it necessary to make model for radioss solver?

     

  • rea2
    rea2 Altair Community Member
    edited October 2018

    at first

    -which units did you use?

    -is it necessary to make model for radioss solver?

     

     

    Units are mm/ms/g.

     

    Not sure whether I understand what you mean, but yes, we want to solve the model in Radioss to quantify the loads on the cartilage parts during a gait cycle.

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited October 2018

    I think that's not a beam. It is deformation, 

  • rea2
    rea2 Altair Community Member
    edited October 2018

    I think that's not a beam. It is deformation, 

     

    Thank you - that's what I assumed, just used the term beam to descirbe its shape. But do you know how it might be caused and how I could get rid of it?

  • Altair Forum User
    Altair Forum User
    Altair Employee
    edited October 2018

    Hi,

     

    I need to check the file, 

     

    It could be a modeling error or something to do with the contacts. I will get back to you soon.

  • rea2
    rea2 Altair Community Member
    edited October 2018

    Hi,

     

    I need to check the file, 

     

    It could be a modeling error or something to do with the contacts. I will get back to you soon.

     

    Thank you. We've solved the problem, it was caused by too much acceleration (I speeded the movement up by factor 100 to decrease computation time).