Differences between revisions 1 and 2
Revision 1 as of 2018-04-16 13:03:44
Size: 2309
Editor: aerdemir
Comment:
Revision 2 as of 2018-04-16 17:56:17
Size: 2767
Editor: aerdemir
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:

<<TableOfContents>>

== Goal ==

== Earmarked Data ==

== Deliverables ==

=== Modeling & Simulation Outcomes ===

=== Documentation ===

== Guidance ==

=== Where to get the data? ===

=== How to document and submit Specifications? ===

=== How to document and submit Protocol Deviations? ===

=== How to curate, document and submit Modeling and Simulation Outcomes? ===

=== Preparing a package for Comparative Analysis ===

--

Goal

Earmarked Data

Deliverables

=== Modeling & Simulation Outcomes ===

Documentation

Guidance

Where to get the data?

How to document and submit Specifications?

How to document and submit Protocol Deviations?

How to curate, document and submit Modeling and Simulation Outcomes?

Preparing a package for Comparative Analysis

--

  • Earmarked data (provided in the downloads section of project site)
    • Specimen? - Open Knee(s) - MRI (general purpose, cartilage, three orthogonal connective tissue) in NIfTI format
    • Specimen? - DU - CT, MRI in DICOM format, anatomical landmarks + ligament insertion origin sites in text format
  • Workflow documentation (to be uploaded to the documents section of project site)
    • Specifications. A document describing individual steps to obtain outcomes from earmarked data. The detail should be provided in a manner that other teams can reproduce the decision making process of the modeler. Any subjective and arbitrary decisions should be noted and as much insight as possible should be provided for justification and reproduction this decision.
    • Protocol deviations. If specifications need to be updated during activities to go from earmarked data to outcomes, these should be documented as protocol deviations. As much insight as possible should be provided for justification of deviation.
    • Ideally, when a third-party modeler has the earmarked data, specifications, and protocol deviations, they can follow the steps of the modeling team to reproduce the outcomes.
    • The documentation should list all the resources used and note estimated and actual effort level of personnel (and the expertise level of personnel) to estimate cost burden.
  • Outcomes (to be uploaded to the downloads section of project site)
    • Model 1 from Specimen? - Open Knee(s)
      • Working capacity, i.e., simulating passive flexion OR other type of activity?
      • Representation of anatomy (in formats preferred by modeling team)
        • Segmentations of modeled tissues, e.g., binary image label
        • Geometry of modeled tissues, e.g., triangulated surface representation
        • Mesh, e.g. tetrahedral/hexahedral volume mesh
      • Representation of tissue behaviour
        • Constitutive models, e.g. coefficients and equation of strain energy potential
        • Tissue stress-strain response, e.g. raw data or calculated from constitutive model
        • Tissue bulk response?, e.g. total ligament force under simplified loading
    • Model 2 from Specimen? - DU
      • Same as above.

ModelDevelopment (last edited 2018-07-02 18:47:06 by aerdemir)