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 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • 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
  • #276

Closed
Open
Created Jan 08, 2021 by Andrew Wilson@andrew.wilson🐘Maintainer

Geometry Init/Current Refactor

Currently geometry composites post/pre (current/init) members. Such as in PointSet it has current and init positions. This has proven difficult. Instead an entirely separate geometry object should be used. This is especially helpful for post/pre velocities and other attributes. As well as every other member that has post/pre state, including those in primitive geometries.

Obvious failures of such thing are shown in PbdClothRemap. If one subdivides then resets, it will fail. Similarly for any attribute reset will fail.

Edited Jan 20, 2021 by Andrew Wilson
Assignee
Assign to
Time tracking