visual3d:tutorials:tutorial_overview
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:tutorials:tutorial_overview [2024/07/16 19:33] – created sgranger | visual3d:tutorials:tutorial_overview [2024/07/31 13:33] (current) – Deleted page. wikisysop | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Tutorial_Overview_ ====== | ||
- | |||
- | Welcome to C-Motion’s Visual3D motion analysis software. The Visual3D software provides kinematics and kinetics (inverse dynamics) calculations for biomechanical analysis of 3D motion capture data. Prior to beginning the tutorials, if you haven' | ||
- | |||
- | Our tutorials are designed to walk you through the process for creating skeletal models representing your MoCap data and performing a biomechanical analysis. Each tutorial picks up where the last one left off, but the results of each tutorial are saved as a .cmo file so that you may skip a part that you already are familiar with, or try out different features and capabilities during a tutorial - using it only as a guideline. You do not need a data capture file, the various sample input data will be supplied as needed through out the tutorials. We hope you find the tutorials beneficial. We are constantly seeking to improve. If you have any suggestions for enhancements or new features, we would love to hear them. Just drop us a note at info@c-motion.com any time. | ||
- | |||
- | This is only part of the documentation for Visua3D. There is a large [[https:// | ||
- | |||
- | ==== Contents ==== | ||
- | |||
- | |||
- | |||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | * [[# | ||
- | |||
- | |||
- | === Preparing for the Tutorials === | ||
- | |||
- | It is assumed that version 3.0 of Visual3D (or later) has been downloaded from C-Motion’s web site and installed. License keys are required to run the software. Please see the Visual3D [[https:// | ||
- | |||
- | === Visual3D Workspace === | ||
- | |||
- | The following graphic illustrates the Workspace, its components, and external files.\\ | ||
- | {{WorkspaceFiles.jpg}}\\ | ||
- | It is very important to understand how these files relate to each other. Understanding how the Visual3D Workspace is created and used will make using Visual3D easy to use. | ||
- | |||
- | === Workspace Modes === | ||
- | |||
- | Visual3D’s graphical user interface is designed to reflect this work-flow. It features a tabbed work area with the following tabs: | ||
- | |||
- | * **Workspace Status Tab** - The place where you work with your C3D files for standing and motion trials, as well as various other files. | ||
- | * **Signals and Events Tab** - The place you can view animations, examine the contents of your original C3D data files in detail, set up and execute a variety of calculations of derived data, and define event labels representing events of significance in your application (e.g. heel strike and toe-off in gait analysis). | ||
- | * **Models Tab** - On this tab you will construct your biomechanical models. You can also specify its characteristics such as The number and kind of segments Segment geometry and inertial properties Joint properties (e.g. number of degrees of freedom) biomechanical model-based calculations, | ||
- | * **Reports Tab** - Here you will define and construct your printed reports (tabular and graphical representations of data). | ||
- | * **CalTester Tab** - This is for the CalTester results | ||
- | * **Real-Time Tab** - This is for viewing and processing streaming data | ||
- | * **Simulation Tab** - | ||
- | |||
- | === Workspace Concepts === | ||
- | |||
- | If you are adventurous you can begin the tutorials now otherwise the information below will give you some further background that you may find helpful. Visual3D is typically used as an analysis tool – not a data collection tool. An analysis requires 2 input components. | ||
- | |||
- | * The first is a standing calibration file of the subject, which is used to define a model. | ||
- | * The second is the actual movement data to analyze. You will begin to work with movement data in tutorial 2. | ||
- | |||
- | These files should be in .c3d format. Most motion capture systems can output their data in this format. | ||
- | |||
- | === C3D Format === | ||
- | |||
- | * The C3D format is an open format and the specifications are available at [[https:// | ||
- | * Visual3D creates a unique Workspace into which file data is added, models are integrated, and reports are produced. The whole workspace can then be saved and shared as a digital report in which all the underlying analysis, data, and models can be referenced. | ||
- | * Visual3D follows a philosophy that your original data is sacrosanct – and must never be changed or modified. This protects the researcher and allows analysis results to be reproduced at any time. Thus data is copied into the Visual3D workspace, and Plug-ins that do data conversions only read the original data, and send c3d formatted output directly into the Visual3D | ||
- | * The entire Visual3D Workspace is contained in a special file, with the extension ”*.cmo” (for C-Motion Output). | ||
- | |||
- | == Visual3D works with the following types of files: == | ||
- | |||
- | * **C3D file:** C3D formatted movement files that contain movement point data, force plate information, | ||
- | * **CMO file:** Is a special C-Motion output file that holds the entire Visual3D Workspace. It holds c3d movement data; c3d static calibration data; a model definition (which can be saved out as a template); processed signal, kinematic, and kinetic data; and a report (the format and definition of which can be saved as a template). A .cmo file (i.e. Workspace) may contain several models and/or movement trails at one time for more complex analyses. | ||
- | * **Model Template:** A template is NOT a complete model, but is just an ASCII file that contains segment definitions and specific subject data (mass, height, segment radius values, and model expressions/ | ||
- | * **Report Template:** Contains the page layouts of selected graphs and tables – but NO DATA. Each graph is configured to look in a specific Visual3D Workspace for the named signals, event ranges, etc. Reusing a report template requires you to use consistent names for targets, labels, metrics, tags, events, and calculations between the various subjects and movement trials. | ||
- | * **Script/ | ||
- | |||
- | For example, a ”model” can only exist conceptually within the Workspace, and is actually the combination of: | ||
- | |||
- | * A static calibration file | ||
- | * Landmark definitions | ||
- | * Segment definitions | ||
- | * Segment anthropometry | ||
- | * Subject specific data | ||
- | |||
- | The kinds of **models** you will usually work with in Visual3D are called **Six-degree-of-freedom (6DOF) Link Models**, comprised of **6 degree of freedom segments** (e.g., thigh, shank and foot in the leg), each of which corresponds to a major bone structure of the body, or a rigid section of hardware such as a cane. | ||
- | |||
- | Each segment is treated as a **rigid body** as that term is used in mechanics—it has mass and fixed dimensions, and it does not undergo deformation (shape change) in response to external forces. In 3-dimensional space, a rigid body is said to have **six degrees of freedom**, meaning that mathematically, | ||
- | |||
- | === Coordinate Systems === | ||
- | |||
- | Model-related computations are facilitated by associating a distinct coordinate system with each model segment. These segment-relative coordinate systems (called simply **segment coordinate systems** or SCS) move with respect to the LCS as the segment itself moves, i.e., the SCS-to-LCS transformations are not fixed, but change from moment to moment throughout the motion. Different laboratories have their own conventions about how SCS’s are defined; one possibility is that the SCS Z axis is oriented along the length of the segment, the X axis is aligned medio-laterally, | ||
- | |||
- | In Visual3D, each model **segment** is defined by two points in space, called its proximal end and distal end, roughly corresponding to the endpoints of the major bone which the segment represents, and a third point, which defines the orientation of the vector between the two endpoints. Of course, the segments of the human body do not move independently of one another—they are linked by joints. This is why Visual3D models are called link models. A joint is a linkage (mechanical connection) between the **distal end** of one segment and the **proximal end** of another. | ||
- | |||
- | == Force Platform Coordinate System == | ||
- | |||
- | Each force platform measures force parameters (such as the center of pressure or COP) relative to the edges of the platform itself, i.e., in terms of a **”platform coordinate system”** which is aligned with the platform. Force parameters such as COP must often be transformed from this device-relative coordinate system to the LCS. Motion-capture systems must be correctly set up and calibrated so as to output coordinates in the LCS. | ||
- | |||
- | == Coordinate System Transformation == | ||
- | |||
- | Given any two coordinate systems S1 and S2, the coordinates of any point can be given as (x1,y1,z1) in system S1, or as (x2,y2,2) in system S2. An important principle of analytic geometry is the notion of **coordinate transformation**, | ||
- | |||
- | == Tracking the Segment Coordinate System == | ||
- | |||
- | Motion capture systems use video cameras or similar devices to track the instantaneous locations of target markers (often called simply ”r; | ||
- | |||
- | |||
visual3d/tutorials/tutorial_overview.1721158401.txt.gz · Last modified: 2024/07/16 19:33 by sgranger