Skip to content
GitLab
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 83
    • Issues 83
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • iMSTKiMSTK
  • iMSTKiMSTK
  • Issues
  • #146
Closed
Open
Issue created Jun 13, 2017 by Sreekanth Arikatla@sreekanth-arikatlaContributor

Efficient rigid offset transformation for deformable meshes

From @unihui, When we set each position for deformable object, this function will be called, m_transformApplied would be set to false, then updatePostTransformData will be called for one time for each getVertexPosion, which leads to much unnecessary calculation and reduces the performance. I think it is very powerful with this transformation matrix, but there might be no need for deformable object, just for rigid body. I can solve it in my branch, but it would make no sense to iMSTK platform, so could you help me to check and fix this issue? void

Mesh::setVertexPosition(const size_t& vertNum, const Vec3d& pos)
{
    m_vertexPositions.at(vertNum) = pos;
    m_dataModified = true;
    m_transformApplied = false;
}
Edited Jun 01, 2021 by Sreekanth Arikatla
Assignee
Assign to
Time tracking