Frequently Asked Questions - General
Q: What types of training are offered?
A: Motek provides different services, for example additional or advanced training, research services or on-site support during the clinical usage of a system with patients (companionship).
For a complete overview of our services, please contact us using the contact us form at the bottom of this webpage.
Download latest software
Please use this link to request the latest D-Flow and or GOAT software.
D-Flow Scripting Tutorials
These tutorials can be used to learn the basics of scripting in D-Flow using the lua programming language. Please download both the .pdf file and the zip file before starting.Scripting tutorials Scene files needed for the tutorials
Gait Offline Analysis Tool (GOAT) explained
Watch this video to find out more about how to use the GOAT for analyzing your data.
Changing the Camera Order in Vicon
Here you can read how to change the camera order in Vicon.Changing the Camera Order in Vicon
Retrieving the log files from the MOOG
Frequently Asked Questions GOAT
Q: I’m not able to visualize the stick figure, how is that possible?
A: In order to visualize the stick figure the kinematic and kinetic data should be reprocessed at least once in GOAT. During the reprocessing of data, the joint centers are calculated (again) in GOAT. These joint centers are needed for the stick figure. After reprocessing, save the file so reprocessing is not needed anymore.
Q: The 3D model visualization doesn’t match the marker data, is my data incorrect?
A: The Human Body Model has two separate pipelines, one for the inverse dynamics and one for the muscle visualization. Therefore, it is possible that the muscle visualization does not perfectly fit the marker data. If so, please check if the stick figure is correct. The stick figure is based on the inverse dynamics pipeline and therefore the visualization of the stick figure can give an indication whether the data is correct. If the stick figure is correct, then the kinematic, kinetic and muscle estimation data are correct and only the muscle visualization is off. If the stick figure shows a strange behavior, then the kinematic and kinetic data has the same strange behavior and then there might be something wrong with the data.
Q: The stick figure visualization doesn’t match the marker and force plate data, why?
A: The stick figure is based on the joint center locations that are calculated with inverse kinematics calculation of the HBM. For these inverse kinematics calculations, filtered marker data is used. The visualization of the marker and force plate data can be filtered or unfiltered. If the stick figure visualization does not match the visualization of the marker and force plate data, the latter is probably unfiltered. This means that the checkbox: ‘Show filtered markers and forces’ is not checked. This checkbox can be found on the Menu bar: View > Settings > View and is checked by default.
Q: I don’t see any data, what could be wrong?
A: After loading a mox file, make sure that cycles are selected. When there are no cycles selected, there is no data to visualize.
Q: I see outliers in the results, what could be a reason for outliers?
A: Stepping with one foot on both belts might cause an outlier in the results of the kinetics. Outliers in the kinematics can occur if a marker is covered for a short amount of time. In the last case the calculation of the kinematics will use the last known marker position, until the marker reappears again.
Q: How can I create an overlay of previous recording in my report?
A: It is possible to create an overlay in the report which contains data of another recording of the same subject. With this overlay it is possible to compare two (or more) sessions with each other. In order to add a comparison file to the report: File | Compare | Import and select the file you wish to compare to.
Note: A file can only be added as a comparison after it is loaded and saved in GOAT at least once before the file is imported as comparison file.
Q: What do the pink, black and blue lines in the report graphs represent?
A: When a cycle is selected three lines are visible in the report graphs:
- Blue line: This is the current selected gait cycle.
- Pink vertical line: The selected frame in the cycle. This is the moment in the graph that corresponds with the current frames in the 3D window and the video window.
- Black vertical line: Toe-off of the selected cycle.
Q: Can I create and add custom norm data to a GOAT report?
A: Yes. More information can be found in the GOAT Help manual, under GOAT functionalities | Norm data.
Q: How is the stick figure created?
A: The stick figure is based on the joint center locations that are calculated by HBM. Small spheres represent the joint center locations and lines are drawn between the spheres to create the stick figure. More information about the calculations of the joint centers can be found in the HBM reference manual, which can be downloaded from the HBM tab in Post-training.
Frequently Asked Questions D-Flow
Q: What PC specs do I need for a D-Flow development computer?
A: Please contact our Support department at email@example.com for the latest specifications.
Q: How do I install a new D-Flow version?
A: An installer for a new D-Flow version, with download instructions, can be requested via firstname.lastname@example.org
Q: Where can I see the expiration date of my license?
A: Open D-Flow and go to Help | System Information…
Q: How do I update my D-Flow license?
A: Please follow the steps described in Pre-training/D-Flow Installer/Request a License. This is also described in the D-Flow Help software, under Getting started.
Q: What is the difference between Frontend and D-Flow?
A: Both software programs can be used to run the applications. However, D-Flow comes with the D-Flow editor, allowing to edit and create new applications. Frontend allows to operate the system, to store data and results in a subject database and to create reports all without the risk of accidentally changing something in the application.
Q: Can the self-paced settings be changed?
A: Some settings for self-paced are system-specific, depending on e.g. treadmill length or motor drive settings. It is, however, also possible to change other self-paced settings. These settings are either accessible via the Treadmill module in D-Flow or via the configuration file. More details about self-paced and its settings can be found in the D-Flow Help menu (F1).
Q: How can I create Frontend files?
A: Frontend applications require a different file format to D-Flow applications. If you want to use a D-Flow application in Frontend, it is possible to convert the D-Flow file into a Frontend file with the Smash tool. You can read how to use the Smash tool in the GRAIL or CAREN system manual.
Q: Which EMG systems can I use with D-Flow? How do I use EMG in D-Flow?
A: By default we support Delsys Trigno. Information about the configuration and use in D-Flow can be found in the D-Flow Help. If you want to integrate other EMG systems, please contact us via email@example.com.
Q: What additional hardware can I connect to D-Flow?
A: The D-Flow configuration tool contains a Peripherals tab on which additional hardware options can be checked and configured. Please also consult the D-Flow Help menu. If you can’t find the information you need, please contact support at firstname.lastname@example.org.
Q: How are the two CoP values from two force plates combined into one CoP value?
A: The Mocap module contains an option called ‘Simulate single force plate” on the Analog tab. This combines the output of the left and right force plate into one force plate. Because the force plates of a CAREN or GRAIL use the same coordinate system, the moments and forces can be added up and be used to calculate the CoP:
- CoPX = MomZ / Fy
- CoPZ = -MomX / Fy
Q: What is the main difference between Frontend and D-Flow?
A: Both software programs can be used to run the applications. However, D-Flow comes with the D-Flow editor, allowing to edit and create new applications. Frontend is allows to operate the system, to store patient data and the outcomes of the applications and to create reports of those outcomes, without the risk of accidentally changing something in the application.
Frequently Asked Questions HBM
Q: What does HBM mean?
A: HBM stands for Human Body Model and is an inverse dynamic model to calculate joint kinematics (angles), joint kinetics (moments) and estimate muscle activity. Marker positions, measured with motion capture, and force plate data are used to calculate kinematics and kinetics. The estimation of the muscle activity is done with the joint kinematic and kinetic data in combination with assumptions of optimal voluntary muscle contractions and generalized mass properties.
Q: When do I need to calibrate HBM and when can I use reset HBM?
A: Calibration of the HBM model needs to be done in D-Flow before the first session. It is the part of the subject preparation as described in the system manual. With the HBM calibration subject-specific calibration information is saved to a T-pose file. Sometimes, during a session, the HBM calibration is lost, mostly due to occluded markers. In that case a reset of the HBM model suffices, to retrieve the HBM calibration information from the T-pose file. In short, Calibrate HBM should be done before the first session, reset HBM can be applied during a session. When a new subject arrives, a new calibration needs to be executed to write new subject-specific information to the T-pose file.
Q: How is the stick figure created?
A: The stick figure is based on the joint center locations that are calculated by HBM. Small spheres represent the joint center locations and lines are drawn between the spheres to create the stick figure. More information about the calculations of the joint centers can be found in the HBM reference manual.
Q: Can the HBM model be used for children?
A: The HBM is already being used in research for children with cerebral palsy and Duchenne’s Muscular Dystrophy in clinical gait analysis. It is also used to provide real-time feedback on kinematic and kinetic variables. When pathologies such as paralysis or spasms are involved, the outcomes of the muscle force optimization require careful attention. These precautions do not apply to the kinematic and kinetic analysis.
Q: Is there a possibility of incorporating ligament tension models (e.g., ACL, MCL) in the real-time output?
A: The existing ligament tension models are fairly simple. These could be programmed in a D-Flow expression or script module, and so provide real-time output, but this is not incorporated in HBM.
Q: What would be the difficulty in including a feature of user-defined cost functions such as muscle stress raised to a definable power exponent?
A: Professor van den Bogert has tried this, but the recurrent neural network method would not solve such a cost function quickly enough for real-time use. A different solution method would be required, which may be possible, but would definitely require more research.
Q: Is there any chance of incorporating actual EMG signals into the HBM realtime analysis?
A: In the long term, professor van den Bogert thinks this is a good idea. The CEINMS toolbox developed by David Lloyd’s group is very interesting to look at. However, currently, there are very few labs that do this, as setup requires extensive calibration. There is still a lot of research needed before this makes it into clinical practice.
Q: How does the model handle cross over between a split belt treadmill with 2 force plates?
A: The model itself assumes that correct ground reaction force data is available from both force plates. However, in our Gait Offline Analysis Tool we’ve built the ability to automatically and manually filter out gait cycles based on unexpected forces (e.g. half of the body-weight in single-stance). This is particularly useful for cross-steps on a split-belt treadmill.
Q: Can you switch off static optimisation in order to increase the rate of joint torque calculation?
A: Yes, in the MoCap module under the HBM tab there is a checkbox available called ‘Calculate muscle forces’, which switches the static optimization on and off.
Q: How are the ankle and subtalar joint axes defined?
A: Please refer to the HBM Reference Manual found in Post-Training/Software/HBM for these definitions.
Q: How accurate is the hip joint center predicted by the HBM2 model?
A: The hip joint center prediction of HBM2 is based on the regression equations of Harrington (2007). Kainz (2015) also recommends this method in his systematic review as the most accurate predictive method.
Q: I see offsets in internal/external hip rotation. How can these be influenced?
A: When using medial epicondyle markers, one of the axes used to define the femur segment is a vector through the lateral and the medial epicondyle. This means that correct marker placement of the lateral and medial epicondyle markers is vital to determine hip internal/external rotation without an offset. For example, if the medial epicondyle marker is placed anteriorly compared to the lateral epicondyle marker, this will result in a hip rotation angle which has an offset towards external rotation. When seeing an offset in internal/external hip rotation, always check the placement of the lateral and medial epicondyle markers.
Q: Double bump pattern in ankle flexion/extension moments
A: In some gait analyses, we’ve seen a clear double bump pattern in the ankle flexion/extension moments. For typically developing children, this is not what was observed in (van der Krogt, Sloot, Buizer, & Harlaar, 2015). However, typical joint kinematics associated with a pathological double dump ankle moment pattern such as excessive plantarflexion at initial contact and rapid dorsiflexion during loading response (Gage, Schwartz, Koop, & Novacheck, 2009) were not present. Examining video showed the subjects performing an early heel rise, which may explain the double bump pattern. This is also in line with (Rozumalski, Novacheck, Griffith, & Schwartz, 2014). When seeing a double bump pattern, check whether the subjects are doing an early heel rise, and whether other factors associated with a pathological double bump pattern are present.
Q: One DOF for the knee, or why we have less than three markers on the shank and thigh.
A: We often get asked why HBM does not calculate the knee internal/external rotation and abduction/adduction DOFs. Under normal conditions, the knee has very little abduction/adduction ROM. Modelling the abduction/adduction DOF would most likely reflect inherent crosstalk error in 3D kinematics calculations, rather than a true anatomical movement (Ramakrishnan & Kadaba, 1991). As for internal/external rotation, the knee does have 45 degrees of internal/external rotation ROM when flexed 90 degrees. However, HBM is mostly aimed at clinical gait analysis. During gait, the knee is largely extended, and there is little internal/external rotation ROM. So again, crosstalk would affect how well the measured angles reflect true anatomical movement. Bone pin studies showed that the soft tissue artifact for internal rotation at the knee is larger than the actual internal rotation that takes place during walking (Reinschmidt et al 1991). In summary, HBM only calculates knee flexion/extension, because the other DOFs have ROMs that are too small relative to the crosstalk error inherent in 3D kinematics. Furthermore, if three hinges were used, muscle forces would be overestimated, this problem was described nicely by Glitsch and Baumann (1997). They have shown that this is best for the analysis of muscle function and estimation of muscle forces. Users with an education in 3D kinematics are also often surprised that HBM has less than three markers on the shank and thigh. HBM can do this precisely because there is only one DOF in the knee. In most biomechanical models, each segment is modelled separately. To determine the position and orientation of a 3D segment, at least 3 markers are required. The joints between the segments then all have 6 DOF, as the segments can move independently from each other. In HBM, the position and orientation of the entire biomechanical model is determined at the same time, using global optimization. This means that HBM can also restrict joint movement to only the DOFs that make anatomical sense. HBM uses this to disallow all translational DOFs between joints, and to restrict the knee to only flexion/extension. In a sense, HBM only looks at the knee in the sagittal plane. And to calculate one angle in a 2D plane, only three markers are required: one on the top segment (thigh), one at the joint, and one at the bottom segment (shank). This allows HBM to use fewer markers on the thigh and shank than other biomechanical models.
Q: How precise models HBM2 the trunk internal/external rotation?
A: Normative literature on trunk kinematics is not readily available, due to there not being a standard model for trunk kinematics. However, Leardini et al. compared eight different trunk models, of which one is the ISB trunk model (Leardini, Biagi, Belvedere, & Benedetti, 2009). The trunk model in HBM2 uses almost the same marker set as the ISB trunk model, the only difference is using T10 vs. using T8. The trunk tilt and lateroflexion found in HBM2 shows a similar pattern to the pattern seen in Leardini et al. Trunk internal/external rotation however is slightly different: in HBM2, peak rotation is at 10% of the gait cycle, whereas Leardini et al. see the peak rotation exactly at initial contact. Otherwise the pattern is similar. It’s hard to say which one best models the true trunk rotation, but both will be a simplification of the true movement of the trunk, since both consider the trunk as a single segment.
Q: Please explain the toe joint center
A: HBM has a toe joint, which is used in the kinematic analysis, but this toe joint should probably be removed in future versions. The existence of the toe joint is for historical reasons: when HBM was first developed, the kinematic analysis was also used for the visualization. It would have looked bad to have a completely rigid foot. However, the visualization currently uses its own skeleton, so this no longer applies. Also, although the toe joint is used in the kinematic analysis, it is not used in the muscle modeling or the inverse dynamics. This is because a force plate cannot distinguish between force applied at the foot and force applied at the toe. So the only function the toe joint served (the visualization) no longer applies, and it can be safely removed. A reason to do the work to remove the toe joint is that when HBM joints are used as input for an OpenSim model (as in MD-PAEDIGREE), the place of the HBM toe joint results in an anatomically incorrect foot. This is because the HBM toe joint is placed 6 centimeters behind the CM2 marker, which is anatomically incorrect, but necessary to prevent problems in the inverse kinematic solver. Removing the toe joint would prevent propagating this anatomically incorrect toe joint to a derived OpenSim model.
HBM2 Reference Manual
In this manual you can find all you need to know about the HBM2 model that is used in D-Flow. HBM stands for Human Body Model and is the model used to calculate the kinematics, kinetics, spatio-temporal parameters and muscle forces during gait. Two versions exist; the lower limb (22 or 26 markers with trunk markers), and the full body model (46 markers).HBM2 Reference Manual - Lower Body HBM2 Reference Manual - Full Body
Tips and Tricks for D-Flow Scene Development
Editing a GOAT layout file
In this section you can learn how to edit the layout of a GOAT report. This is useful for example, when you need want to add additional graphs or change the position of existing graphs.How to edit a GOAT layout file