Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 423
    • Issues 423
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1755
Closed
Open
Issue created Jul 01, 2020 by Gabriel Barajas@barjasg🚴🏼

strange behaviour when comparing SixDoFRigidBodyMotion, RigidBodyDynamics and Overset libraries.

Hi,

While working in new developments I have come up with an expected results when comparing the three main libraries for rigid body motions (SixDoFRigidBodyMotion, RigidBodyDynamics and Overset) with the tutorial provided in the oficial release.

Please, note that I assume that the RigidBodyDynamics gives the correct results, as it has been widely validated.

If I compare (for a sligthly modified version of the tutorial), the results using the SixDoFRigidBodyMotion library (in green), and the RigidBodyDynamics library (in red), I get the same results (as expected).

image1 image2

Then, If I compare (using the same case), the RigidBodyDynamics library (in green) against the Overset library (in red), I get this weird result in the YAW rotation.

image3 image4

If I vary the constraint in the displacement (along axis Z or along axis X), I get the same weird results in the YAW rotation.

image5 image6

Please, can you clarify me if it is working correctly the Overset library?

Regards, Gabi

Assignee
Assign to
Time tracking