Planning overview for Demo 1

[Lathreas]

Our first milestone will be a demo-version capable of editing a minimal set of anatomical features in functional detail. This will be focused on the elbow region, for which the backend and frontend must work together.

Proof of concept demo 1:

For proof of concept demo 1, we will need to finish the following implementation tasks:

Blender-specific backend work

• Implement barebones GeoScript implementation
  • See Node tree abstraction in order to improve maintainability #4
• Implement ARF data model in Blender
  • This makes use of Blender's custom properties system, explanation will be written down shortly

Bones and Joints

• Implement placeholder (unconstrained) long bone geometry
  • This is the geometry representation of a bone before constraints are applied
• Raytracing smoothing equations for bones-to-joints
  • Raytracing is required for the bone-joint model, as the bone and joint have to link together. This is done through raytracing the bone onto the joint.
  • Implement smoothing function
  • Implement raytracing smoothing logic for Hinge Joints
  • Implement raytracing smoothing logic for Ball-and-Socket Joints
  • Translate joint smoothing logic to GeoScript for improved maintenance #11
  • Other joint types will be completed in the next demo
• Implementation of long-bone geometry generation model
  • Implement logic for joint-based deformation
  • Implement logic for tubercle-based deformation
  • Translate bone deformation logic to GeoScript for improved maintenance #12
• Implement user interface for editing properties
  • (See UI design drafts, will be published soon too)
  • Identify and expose all editable properties of HingeJoint, Ball-and-Socket Joint
  • Create easy interface within the ARF sidepanel for editing joint properties #10
  • Create easy interface within the ARF panel inside Blender's 3D View showing all joints & tubercles affecting a bone.
• Implement ARF armature-bone-muscle-skin pipeline constraints.
  • An important aspect for the ARF is to ensure that there are no redundant degrees of freedom. This means that the positions of joints must be tightly linked to the positions of bones and armature, such that there is only one datapoint describing the joint's position rather than two or three. The same holds for any other property.
  • Link joints to armature intersections.
  • Ensure that joints can be easily moved by the user when wanted, and that the armature will follow.
• Implement 3D editing gauges for editing joint and bone properties #9
• Implement custom edit contexts #8
  • These "edit contexts" do not correspond to the edit modes in Blender, but rather are custom views where certain features are hidden so other features can more easily be edited.
  • ARF Armature Edit Context
    • Displays armatures, and allows for selecting and editing joints. Hides bones, muscles, skin, and other such tissue.
  • ARF Skeleton Edit Context
    • Displays bones, allowing for easy selecting and editing of the skeleton. Only shows joints relevant to the selected bone. Muscle insertion sites are displayed, but muscles themselves are hidden.
  • ARF Bone Edit Context
    • Displays a single bone, and all connected elements in a transparent way, to make editing a single bone easier.
  • ARF Muscle Routing Context
    • Displays skeleton and muscles, allows muscles to be selected and rerouted smoothly.
  • ARF Skin Edit Context
    • Displays skin, allowing for editing skin and fat tissue underneath.

Muscles

• Implement insertion sites
  • Implement logic and geometry
  • Translate muscle insertion sites to GeoScript for improved maintenance
• Implement muscle fiber model
  • Implement logic and geometry
  • Translate muscle fiber model to GeoScript for improved maintenance
• Implement muscle-to-bone anti-intersection algorithm
• Implement muscle-to-muscle anti-intersection algorithm