Wrists: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
 
(9 intermediate revisions by 2 users not shown)
Line 7: Line 7:




==Overall Pipeline==
==Description of Overall Pipeline==


#[[Data]]  
#[[Data]]  
Line 19: Line 19:
#[[Joint Simulation]]
#[[Joint Simulation]]


[[Wrist Pipeline Technical Details | More Technical Details on Wrist Pipeline]]
==Specific Tools and Technical Details==


==Tools==
#[[Registration of Bones Across Positions#Technical Notes|registration]]
 
#[[registration]]
#[[joint space area calculations]]
#[[joint space area calculations]]
#[[cartilage building]]
#[[cartilage building]]
#"wiggling" bones around
#"wiggling" bones around
#ligament length measures
#ligament length measures
#<fill in with more tools..>
 
[[Wrist Pipeline Technical Details | Technical Details on Wrist Pipeline and its relationship to the $G software framework]]

Latest revision as of 21:11, 9 April 2014

The wrist is a diarthrodial anatomical joint consisting of 8 small bones (scaphoid, capitate, hamate, lunate, trapezium, trapezoid, triquetrum, pisiform) and 7 long bones (radius, ulna, and 5 metacarpals). When subject to injury and disease the wrist undergoes changes in kinematics, inter-bone joint space areas, cartilage thickness, length of ligament paths, etc. Developing computational tools for the analysis of anatomical joint characteristics is important in understanding the cause of injury, tracing the progress of disease, and taking preventative measures.


Description of Overall Pipeline

  1. Data
  2. Bone Surface Extraction
  3. Registration of Bones Across Positions
  4. Retrieval of Kinematics
  5. Inter-bone Joint Space Area Calculations
  6. Ligament Path Calculations
  7. Cartilage Maps (location & thickness)
  8. Cartilage Surface Deformations
  9. Joint Simulation

Specific Tools and Technical Details

  1. registration
  2. joint space area calculations
  3. cartilage building
  4. "wiggling" bones around
  5. ligament length measures

Technical Details on Wrist Pipeline and its relationship to the $G software framework