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
  • #276

Closed
Open
Opened 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
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#276