Upperlimb

User Tools

Site Tools

Trace:
kinematic_model

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
kinematic_model [2018/12/13 09:26] – [Project files] oliverkinematic_model [2023/08/07 00:05] (current) – [Classical SHR ratio] oliver
Line 11: Line 11:
 **The details of the original model are described here:** **The details of the original model are described here:**
  
-{{pubmed>long:19651514}}+{{pmid>long:19651514}}
          
 **The angles to describe shoulder girdle movement are described here:** **The angles to describe shoulder girdle movement are described here:**
  
-{{pubmed>long:26646907}}+{{pmid>long:26646907}}
  
 {{:fig2.jpg?650|}} {{:fig2.jpg?650|}}
Line 21: Line 21:
 **Shoulder internal/external rotation is described by a specific angle definition, called conjunct rotation as described here:** **Shoulder internal/external rotation is described by a specific angle definition, called conjunct rotation as described here:**
  
-{{pubmed>long:19396487}}+{{pmid>long:19396487}}
  
 ====Marker placement==== ====Marker placement====
Line 104: Line 104:
 A detailed description of the angles (also several variants are available) is published here: A detailed description of the angles (also several variants are available) is published here:
  
-{{pubmed>long:15844264}}+{{pmid>long:15844264}}
  
 ==== Tip positions ==== ==== Tip positions ====
Line 143: Line 143:
 For this RoM the maximum error should be less than 8 degrees in all cases. That is higher than for the other upper extremity joint angles but it sounds worse than it is because typical daily life arm movements have variabilities in the same order. There are several publication about accuracy, e.g.: For this RoM the maximum error should be less than 8 degrees in all cases. That is higher than for the other upper extremity joint angles but it sounds worse than it is because typical daily life arm movements have variabilities in the same order. There are several publication about accuracy, e.g.:
  
-{{pubmed>long:26099159}} +{{pmid>long:26099159}} 
-{{pubmed>long:24856913}} +{{pmid>long:24856913}} 
-{{pubmed>long:21875756}} +{{pmid>long:21875756}} 
-{{pubmed>long:18815043}}+{{pmid>long:18815043}}
  
 ==== Angles ==== ==== Angles ====
Line 350: Line 350:
 ^ Name ^ Used values ^ Deprecated values ^ Description ^ ^ Name ^ Used values ^ Deprecated values ^ Description ^
 ^ TYPE | Static_Cal, Static, EllbowFlex/Ext, ShoulderAnte/Retro, ShoulderAbd/Add, Dynamic, Proprio, proprio | ^ TYPE | Static_Cal, Static, EllbowFlex/Ext, ShoulderAnte/Retro, ShoulderAbd/Add, Dynamic, Proprio, proprio |
-| CLASS | | | This property was originally used in the Heidelberg Motionlab. Please use TYPE instead. |+^ CLASS | | | This property was originally used in the Heidelberg Motionlab. Please use TYPE instead. |
 ^ ACTIVITY | Scapula TS, Scapula AI, Scapula AA, Scapula PC, Humerus EL, Humerus EM, Forearm RS, Forearm US | | All of the values can haven an suffix "Pos1" or "Pos2" ... (old deprecated: "Position 1" or "Position 2" ...), if positions are tipped for humerus elevation angles > 90 degrees. | ^ ACTIVITY | Scapula TS, Scapula AI, Scapula AA, Scapula PC, Humerus EL, Humerus EM, Forearm RS, Forearm US | | All of the values can haven an suffix "Pos1" or "Pos2" ... (old deprecated: "Position 1" or "Position 2" ...), if positions are tipped for humerus elevation angles > 90 degrees. |
-| POSITION | | | This property was originally used in the Heidelberg Motionlab. Please use ACTIVITY instead. |+^ POSITION | | | This property was originally used in the Heidelberg Motionlab. Please use ACTIVITY instead. |
 ^ SIDE | Side R, Side L, Both, bds | rechts, links | If a motion or position is side depenended in the meaning it can be done with the right side and the left or with both sides you can define the side. | ^ SIDE | Side R, Side L, Both, bds | rechts, links | If a motion or position is side depenended in the meaning it can be done with the right side and the left or with both sides you can define the side. |
 ^ DESCRIPTION | Abduk, Ante-/Retro, Elevation/Depression, Protraktion/Retraktion ARO/IRO-0, ARO/IRO-90Abduk, ARO/IRO-90Ante | Schuerzengriff, Kaemmen, Armkreisen, Buch, WaschenAchsel, | ^ DESCRIPTION | Abduk, Ante-/Retro, Elevation/Depression, Protraktion/Retraktion ARO/IRO-0, ARO/IRO-90Abduk, ARO/IRO-90Ante | Schuerzengriff, Kaemmen, Armkreisen, Buch, WaschenAchsel, |
-| NOTES | | | This property was originally used in the Heidelberg Motionlab. Please use DESCRIPTION instead. |+^ NOTES | | | This property was originally used in the Heidelberg Motionlab. Please use DESCRIPTION instead. |
 For Vicon Nexus users these properties are available per default. No Vicon Nexus Eclipse-properties configuration is needed any more, for its usage. You only have to set the values for each trial as configured in the projects "job configuration". For Vicon Nexus users these properties are available per default. No Vicon Nexus Eclipse-properties configuration is needed any more, for its usage. You only have to set the values for each trial as configured in the projects "job configuration".
  
Line 386: Line 386:
 </code> </code>
  
-The deprecated values are formaly used in the [[http://www.heidel-motionlab.de/|Heidelberg Motionlab]] and should not be used any more. They are only listed to remember if you find these values in older sessions collected in the Heidelberg Motionlab.+The deprecated values are formaly used in the [[http://www.heidel-motionlab.de/|Heidelberg Motionlab]] and should not be used any more. They are only listed to be remembered, if you find these values in older sessions collected in the Heidelberg Motionlab.
  
 You can change the usage of the properties as you want. All is defined in the "job configuration". Have a look at the Nimue platform [[http://nimue-platform.motion-science.org/doku.php?id=glue:processconfiguration|Process documentation]] to understand how to define groups of trials and how to process them. You can change the usage of the properties as you want. All is defined in the "job configuration". Have a look at the Nimue platform [[http://nimue-platform.motion-science.org/doku.php?id=glue:processconfiguration|Process documentation]] to understand how to define groups of trials and how to process them.
Line 437: Line 437:
 Typically the SHR is given as the ratio of the glenohumeral abduction angle and the scapula medio-lateral rotation angle during humeral abduction movements (movement mainly in frontal or scapula plane). In many publications, due to technical reasons, the glenohumeral abduction angle is determined from the thoracohumeral abduction angle by subtracting the scapula medio-lateral rotation angle. All of these angles can be defined by cardan sequences or by projection angles. Typically the SHR is given as the ratio of the glenohumeral abduction angle and the scapula medio-lateral rotation angle during humeral abduction movements (movement mainly in frontal or scapula plane). In many publications, due to technical reasons, the glenohumeral abduction angle is determined from the thoracohumeral abduction angle by subtracting the scapula medio-lateral rotation angle. All of these angles can be defined by cardan sequences or by projection angles.
  
-{{pubmed>long:27583116}}+{{pmid>long:27583116}}
  
 Typically the SHR ratio is presented as a function of the humeral elevation.   Typically the SHR ratio is presented as a function of the humeral elevation.  
Line 472: Line 472:
 elevation.  elevation. 
  
-{{pubmed>long:25591459}}+{{pmid>long:25591459}}
  
 This is a different measure, which results in different numerical values, for the so called SHR ratio but it is robust against angle-offsets. A numerical feature of this definition is, that it can be implemented a way that the measure does not depend on the rotation order of the cardan angles. This is a different measure, which results in different numerical values, for the so called SHR ratio but it is robust against angle-offsets. A numerical feature of this definition is, that it can be implemented a way that the measure does not depend on the rotation order of the cardan angles.
Line 501: Line 501:
 ==== Project files ==== ==== Project files ====
  
-[[https://github.com/gaitlabhd/Diadochokinesis|Here]] are the Nimue platform based project files. How to clone a github repository is explained [[https://help.github.com/articles/cloning-a-repository/|here]]. +[[https://github.com/gaitlabhd/Diadochokinesis|Here]] are Nimue platform based project files as a starting point to learn how to model with the "Upperlimb" software. How to clone a github repository is explained [[https://help.github.com/articles/cloning-a-repository/|here]]. The model was developed in the [[http://www.heidel-motionlab.de/|Heidelberg Motionlab]] to analyse inter-limb coupling during diadochokinesis in children with bilateral spastic cerebral palsy. Have a look into the [[https://www.thieme-connect.com/products/ejournals/abstract/10.1055/s-0035-1550645|Conference abstract]].
- +
-This simple project/model can be used as a starting point to learn how to model with the "Upperlimb" software. +
- +
-The model was developed in the [[http://www.heidel-motionlab.de/|Heidelberg Motionlab]] to analyse inter-limb coupling during diadochokinesis in children with bilateral spastic cerebral palsy. +
- +
-[[https://www.thieme-connect.com/products/ejournals/abstract/10.1055/s-0035-1550645|Conference abstract]]+
kinematic_model.1544689598.txt.gz · Last modified: 2018/12/13 09:26 by oliver

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki