Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2014-07-04 13:54:18 →
Size: 2512
Editor: aerdemir
Comment:
← Revision 3 as of 2016-05-04 22:09:49 → ⇥
Size: 2512
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Recurring Meeting of Cleveland Clinic - University of Utah

Date: June 4, 2014

Time: 3:00 PM EST

Means: Conference call

Attendees:

  1. Ahmet Erdemir (Cleveland Clinic)
  2. Jason Halloran (Cleveland Clinic)
  3. Jeff Weiss (University of Utah)
  4. Ben Ellis (University of Utah)
  5. Steve Maas (University of Utah)

Agenda:

  1. Recap on in situ strain test problem.
  2. Update on local coordinate systems and connector elements.
  3. Update on set definitions in FEBio input and output.
  4. FEBio solution repeatability.
  5. Decide action items for next meeting.
  6. Other.

Immediate Action Items:

  • University of Utah (Steve)
    • Continue work on general purpose implementation of the in situ strain feature.

Notes:

  1. Recap on in situ strain test problem.
    • Steve continued working on the implementation of the in situ strain feature for coupled constitutive formulation. The team has discussed various possibilities to acquire data to appropriately model in situ strains in Open Knee(s) model. Joint level loading can provide information to represent ligament behavior at a structural level. However, Jeff noted that for a better material level representation of ligament behaviour, forces in individual ligaments may need to be measured, e.g. through superposition of multiple robotics testing. This will allow to back track approximate in situ strains in the ligaments, particularly when direct measurement is not possible.
  2. Update on local coordinate systems and connector elements.
    • Steve provided a summary of Gerard Ateshian's efforts on rigid body formulations. He will keep the Cleveland Clinic team informed about the developments.
  3. Update on set definitions in FEBio input and output.
    • Steve continued working on implementing set definitions for FEBio output file.
  4. FEBio solution repeatability.
    • Ben provided a solution suite to illustrate FEBio solution repeatability. This information is now available in the simulation software infrastructure wiki page as part of known issues. This issue is also noted in section 2.6 of the FEBio 2.0 User’s Manual.
  5. Decide action items for next meeting.
    • See Immediate Action Items above.
  6. Other.
    • None.

RecurringMeetings/2014-06-04 (last edited 2016-05-04 22:09:49 by localhost)