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
  • #28
Closed
Open
Issue created Jul 13, 2015 by Ricardo Ortiz@ricardo-ortizContributor

Separate Assembler and Solvers form Scene Objects

At present the scene object class handles (a) internal force computation (b) assembly (c) solver. According to the design, assembly and solver part of the code should be separate modules in the framework.

The assembler should be able to:

  • determine the type of assembly that is required based on the type of objects
  • Number of sub-systems that has to be formed based on the collision context
Assignee
Assign to
Time tracking