The Conventional Gait Model (CGM) is the most widely used biomechanical model for clinical gait analysis. It was first developed in the 1980s and although, it has many strengths, it has several well-known weaknesses. This project will develop and validate a new version of the CGM which maintains those strengths but corrects the weaknesses.
The new model will be as compatible as possible with the old but cannot be identical. It is therefore important that future users know exactly how the new version differs from the old. This will be ensured by developing the model in a series of iterations each addressing a specific weakness and each fully validated to understand the behaviour of the new model in comparison to the old one.
The new model to be as open and transparent as possible. All code will be developed in python and made available through GitHub. The project is part-funded by Vicon and we will focus first on implementations to support use of the new models with Vicon's suite of clinical gait analysis software. We are open to developing similar relationships with other manufacturers.
What's on the website
The web-site contains a full description of each of the models and instructions for both how to set up your system and to capture and process data. There is also a growing repository of .c3d files that can be used for reference purposes.
This is the background to the project.
- What is the CGM? The history of the CGM, how it is defined and an analysis of its strengths and weaknesses.
- Updating the CGM for the modern world. An analysis of futre requirements leading to formal desing criteria and a overview of the main issues to be addressed.
- The team. See who's involved in the project.
- Publications. Our plan is to publish all the validations we have performed but inevitable this will take some time.
Description of models
CGM1: The original Model
CGM1 is our version of the original model.
CGM1.0 - a clone of PiG. This is an exact clone of Vicon's PiG model. It is provided primarily to allow users to get used to implementing the new software with a model that gives exactly the same results as data processed with the original PiG model.
CGM1.1 - PiG as it should be? This is a modification correcting two small bugs we found with PiG and implementing two features that we feel should have been implemented a long time ago which do not affect the underlying model.
CGM2: Modifying the model step by step
CGM2.i is a series of models each adding one specific modification. This is done so that users can explore for themslelves what differences each specific modification make.
CGM2.1 - moving the hip joint centres. one of the main criticisms of the CGM over the years has been that it puts the hip joint centres in the wrong place. This version corrects that based on the latest published research.
CGM2.2 - inverse kinematics. It can be argued that the CGM was an algorithm rather than a true model. This version is a true model fitted to the measured marker positions using inverse kinematics.
CGM2.3 - removing the wands markers. People have used skin markers in palce of original wands for some time but this makes the CGM particularly sensitive to both marker misplacment and soft tissue artefact. This version replaces the wands with skin mounted markers in a more robust manner.
CGM2.4 - extending the foot model. The CGM had a single foot segment (and didn't model this fully). This version allows a modification to marker placment so that the original foot represents the hind foot. Extra markers can then be used to include a fore-foot segment.
CGM2.5 - calibrating the knee joint. There has been considerable research recently into the use of funcitonal calibration to improve biomechanical modelling. The broad conclusion is that hip calibration is less effective than knee calibration which is built into this version.
CGM2.6 - a model for larger people. Placing markers over excessive soft tissue in a manner that is consistent with the CGM has always been a challenge. This version exploits new research to improve this aspect of the modelling.
CGM2.7 - adding the upper body. Although the CGM was originally a lower body model PiG included upper body model as well which has been modified to use inverse kinematics and included in this version.
CGM3: The final product
This is identical to CGM2.7 and is the model we recommend for future clincial use. It will be provided with full documentation for those who just want to get on and use it (but this isn't quite finished yet).
How to use the system
The models have been written to run as Python scripts within Nexus. This requires you to take a little bit of time to install the latest version of Python and the CGM code and to set up various pipelines within Nexus. You will only have to do this once and when you have, capturing and processing data is very similar to using the current PiG Plugin. All the models run in essentially the same way, you just have to select the one you want.
These notes are written in a way which we hope will enable anyone who understands basic data capture in Nexus to set themsleves up to and start running the models.
Installation overview An brief introdcution to how the processes work.
Setting up Python. How to install Python and our new code.
Setting up the Nexus. How to set up Nexus in preparation for data processing.
Capturing and proceesing data. How to use the Nexus Python pipelines to run the different models.
We hope this is a model that other people will want to use and would like to invite you to work with us.
Help with validation There are very few repeatability studies validating models in centres other than those in which the model was developed. We'd love to work with you if you are interested in setting one up. We'd be particularly keen to set up multi-centre studies.
Share data If people are using the same models then the data should be comparable and we want to build a repository of representative data of people with different conditions which can be used for a variety of purposes. At present it includes anonymised data from children with cerebral palsy demonstrating a range of different gait patterns. It is formatted within an Vicon Eclipse database hierarchy to faciliatate easy access through Nexus or Polygon software.