Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • iMSTK iMSTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 63
    • Issues 63
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTK
  • iMSTKiMSTK
  • Issues
  • #309

Closed
Open
Created May 02, 2021 by Andrew Wilson@andrew.wilson🐘Maintainer0 of 16 tasks completed0/16 tasks

Boundary Value Testing for CD

Many intersection methods may be inclusive or exclusive. To keep them consistent we should add boundary value tests for them.

A list of all CDs with boundary value testing:

  • BidirectionalPlaneToSphereCD
  • ImplicitGeometryToPointSetCCD
  • ImplicitGeometryToPointSetCD
  • MeshToMeshBruteForceCD
  • PointSetToCapsuleCD
  • PointSetToOrientedBoxCD
  • PointSetToPlaneCD
  • PointSetToSphereCD
  • SphereToCylinderCD
  • SphereToSphereCD
  • SurfaceMeshToCapsuleCD
  • SurfaecMeshToSphereCD
  • SurfaceMeshToSurfaceMeshCD
  • TetraToLineMeshCD
  • TetraToPointSetCD
  • UnidirectionalPlaneToSphereCD
Edited Feb 09, 2022 by Andrew Wilson
Assignee
Assign to
Time tracking