Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- projects [2024/04/24 05:15]
47.128.119.21 alte Version wiederhergestellt (2024/03/19 23:18)
+++ projects [2024/05/06 02:00]
178.151.245.174 alte Version wiederhergestellt (2024/05/05 04:44)
@@ Zeile 1: / Zeile 1: @@
 ======Projects======
-A folder with subfolders which includes a set of xml-files to describe what to do with a dataset (session, a set of trials, typcially with c3d-files) is called a "Project". There are some projects specific for the Heidelberg Motionlab.
+A folder with subfolders which includes a set of xml-files to describe what to do with a dataset (session, a set of trials, typcially with c3d-files) is called a "Project". There are some projects specific for the Heidelber Motionlab.
 =====PiGMo10 Vicon PiG based=====
@@ Zeile 50: / Zeile 50: @@
 =====PiG with functional knee joint axes only =====
-This project adds functional knee joint axes determination (SARA) only to the default Vicon PlugInGait model. It works together with the old Vicon Workstation system and allows to control the usage of the motion phases, which are used for the estimation by setting of events.
+This project adds functional knee joint axes determination (SARA) to the default Vicon PlugInGait model. It works together with the old Vicon Workstation system.
-In the gait trials the lateral knee markers are projected onto the functional knee joint axes and the knee joint center is determined based on the clinical measurement of the knee width. Than the femur coordinate system is constructed equivalent to the original PiG. Keep in mind that this coordinate system does not have the functional axis as one of its axes. The axes are defined by cross products and have the longitudinal femur axes included.
+Additional to the SCoRE/SARA functional method implementation of Vicon Nexus, motion phases, which are used as input for the estimation, can be controlled by setting of events in the dynamic calibration trials.
-The proximal tibia (anatomical) coordinate systems are defined by PiG virtual markers.
+It is assumed, that the Vicon PiG is processed before processing with this model.
-==== Preconditions ====
+====Eclipse entries====
-  * It is assumed, that the Vicon PiG is processed for the static calibration trial and all gait trials, before processing with this model. Vicon PiG processing is not needed for the dynamic calibration trials.
+To process the data, specific dynamic calibration trials must be done and its specific eclipse entries must be set:
-  * Additional markers on the shank are needed. Have a look at the follwing markerset picture
-  * Specific dynamic calibration movements with knee flexion; events to define the phases used by the estimation.
-  * Specific eclipse entries. Have a look at the following table and screenshot.
-==== Markerset ====
+^ Name ^ Value ^ Description ^
+^ CLASS | Static_Cal | Static standing trial with knee alignment device. |
+^ CLASS | HipFlex/Ext | Flexion/Extention of the hip, which should cause also flexion/extention of the knee; last is used for knee-axis estimation; so it is important, that in this trial also the knee is flexed at minimum of 30 degrees RoM. |
+^ SIDE | Side R, Side L, bds | |
-{{ :markerset.png?400 |}}
-====Eclipse entries====
-To process the data, specific dynamic calibration trials must be available and its specific eclipse entries must be set:
-^ Trial ^ Name ^ Value ^ Description ^
-^ 1 |  CLASS | Static_Cal | Static standing trial with knee alignment device. |
-^ 2 |  CLASS | HipFlex/Ext | Flexion/Extention of the hip, which should cause also flexion/extention of the knee; last is used for knee-axis estimation; so it is important, that in this trial also the knee is flexed at minimum of 30 degrees RoM. |
-^ all trials | SIDE | Side R, Side L, bds | Hip/Flex/Ext trials are typically unilateral, gait trials are typically bilateral |
-^ 3-n | CLASS | Dynamic or Dynamic+Kinetics | Trial with gait, Strides defined by events. |
 {{ :eclipse_functionalpig_54662.png?800 |}}
-====Modelparameter files====
-Modelparameter-files are needed to read parameters from clinical measurements, which are used to define offset angles in the kinematics model.
-There is an important limitation in the mechanism to work with these files: You can have an mp-file only for each session and not for each group. That is why the mp-files are found only, if they are saved in the session and not in the group. Details of working with .mp-files and its limitations you can find [[http://nimue-platform.motion-science.org/doku.php?id=glue:vicon&#mp-files|here]].
-Used parameters are:
-<code>
-$LKneeWidth = 103
-$RKneeWidth = 104
-</code>
-==== Output ====
-In the default configuration the output is written into ".glx"-files in the hd-asc file format besides the corresponding input c3d-files. These files are written only for the gait-trials.
-Hip- and knee-angles are saved to its corresponding PiG angles with the same names but based on the functional knee joint axes.
-^ Name ^ Description ^
-^ R/LKneeAngles | Cardan angles describing the knee motion based on functional knee joint axes corresponding to the equal named original PiG angles.  |
-^ R/LHipAngles | Cardan angles describing the hip motion based on functional knee joint axes corresponding to the equal named original PiG angles  |
-==== Process Log ====

Gait- and Motionlab Heidelberg Tools

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Unterschiede

Seiten-Werkzeuge