Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
iMSTK
iMSTK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 12
    • Merge Requests 12
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • iMSTK
  • iMSTKiMSTK
  • Issues
  • #269

Closed
Open
Opened Dec 06, 2020 by Andrew Wilson@andrew.wilson🐘Maintainer

CollisionData And Contact VisualObjects

Make specific VisualObjects in iMSTK for debugging simulations that have simple interference like so:

imstkNew<PbdConstraintVisualObject> object;
object->setPbdSolver(myPbdSolver); // or setPbdModel(myPbdModel);
// May also be useful to have control over adding/removing them individually yourself so you can filter them, or add your own
scene->addSceneObject(object);

imstkNew<RbdConstraintVisualObject> object;
object->setRbdModel(myRbdSolver);
scene->addSceneObject(object);

imstkNew<CollisionDataVisualObject> object;
// Can handle and filter types of collision datas
object->addCollisionData(myCollisionData);
scene->addSceneObject(object);

Other visualization controls can be added such as line widths, arrows, scales, etc.

Edited Dec 06, 2020 by Andrew Wilson
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: iMSTK/iMSTK#269