visual3d:tutorials:overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| visual3d:tutorials:overview [2024/06/10 15:43] – wikisysop | visual3d:tutorials:overview [2024/06/14 16:14] (current) – removed sgranger | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Welcome to HAS-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' | ||
| - | |||
| - | If you are a new user of Visual3D, here is a guide to suggest in which order the tutorials should be done for learning Visual3D. [image Learning Visual3D] | ||
| - | |||
| - | Visual3Ds native CMZ file format contains the entire Visual3D workspace, so the files can get quite big. If you need to send a file to support@has-motion.com please reduce the size of the [[Visual3D: | ||
| - | |||
| - | |||
| - | =====Tutorial Overview===== | ||
| - | |||
| - | To begin, an overview of the Visual3D workspace and the interface in the [[Visual3D: Workspace|Visual3D Workspace]] page and the [[Visual3D: Getting Started|Getting Started]] page is recommended. Additionally, | ||
| - | |||
| - | All files for the tutorials can be found [[Visual3D: Tutorial Files|here]]. | ||
| - | |||
| - | This page begins with a list of tutorials intended for a beginner user, once those are completed the other tutorials can be followed as needed. The rest of the tutorials follow a typical order in which Visual3D is used, with more tutorials targeting specific and advanced commands. | ||
| - | |||
| - | =====Beginner Tutorials===== | ||
| - | |||
| - | ====Laboratory Checklist==== | ||
| - | There are many crucial steps in collecting " | ||
| - | |||
| - | The following partial list, **[[Visual3D: | ||
| - | |||
| - | We encourage users to contribute to this list by sending additional tasks to support@has-motion.com | ||
| - | |||
| - | ====Typical Processing Session==== | ||
| - | These tutorials are meant to be followed for a first time user or a beginner. It will provide guidance for building a model, opening movement trials, assigning a model to motion trials, basic signal processing, model based items and reporting. The [[Typical Processing Session|typical processing session]] tutorial provides an overview of the tutorials, but it is recommended to follow these tutorials listed in chronological order. Once these tutorials are finished you will be able to save a complete CMZ file. | ||
| - | |||
| - | * **[[Model Building|Tutorial: | ||
| - | |||
| - | * **[[Visualizing Data|Tutorial: | ||
| - | |||
| - | * **[[Command Pipeline|Tutorial: | ||
| - | |||
| - | * **[[Signal Processing|Tutorial: | ||
| - | |||
| - | * **[[Force Platforms|Tutorial: | ||
| - | |||
| - | * **[[Event Processing|Tutorial: | ||
| - | |||
| - | * **[[Model Based Computations|Tutorial: | ||
| - | |||
| - | * **[[Creating a Report|Tutorial: | ||
| - | |||
| - | * **[[IOR Gait Full-Body Model|Tutorial: | ||
| - | |||
| - | * **free CMO reader??** | ||
| - | |||
| - | ===Pipeline for Creating Basic CMZ File=== | ||
| - | Once you feel like you understand the basics of how Visual3D works and processes your .c3d files, it is possible to complete all steps using pipeline commands. The **[[Generic Pipeline to Create CMZ|Generic Pipeline to Create CMZ]]** tutorial walks through the pipeline commands typically used to create a CMZ file. | ||
| - | A full pipeline script for a typical processing session following these steps can be found **[[Basic Pipeline For Processing A Session|here]]**. | ||
| - | |||
| - | ===Support Email Format=== | ||
| - | We encourage you to reach out to support@has-motion.com for any questions or suggestions. | ||
| - | |||
| - | The following **[[Support Format]]** provides guidance on how to send scripts and data. | ||
| - | |||
| - | =====Building Models===== | ||
| - | It is important to fully understand how to build a model as it is typically one of the first things that is completed and needed for a proper analysis. The following tutorials go in depth on how to build a model, and common models. | ||
| - | |||
| - | ====Modeling Concepts ==== | ||
| - | * **[[Building a 6 DOF Model|Tutorial: | ||
| - | |||
| - | * **[[Creating Landmarks|Tutorial: | ||
| - | |||
| - | * **[[Building an IK Model|Tutorial: | ||
| - | |||
| - | * **[[Modeling the Thorax|Tutorial: | ||
| - | |||
| - | ====Gait Models==== | ||
| - | |||
| - | * **[[Building a Conventional Gait Model|Tutorial: | ||
| - | |||
| - | * **[[IOR Gait Full-Body Model|Tutorial: | ||
| - | |||
| - | * **[[Plug-In Gait Lower-Limb| Tutorial: Plug-In Gait Lower-Limb]]**: | ||
| - | |||
| - | ====Upper-Body Models==== | ||
| - | |||
| - | * **[[Plug-In Gait Full-Body|Tutorial: | ||
| - | |||
| - | * **[[Rab Upper Extremity Model|Tutorial: | ||
| - | |||
| - | ====Foot Models==== | ||
| - | |||
| - | Visual3D is a general tool capable of modeling all of the different foot models. The following tutorials list variations of foot models for your choosing. | ||
| - | |||
| - | * **[[Oxford Foot Model|Tutorial: | ||
| - | |||
| - | * **[[IOR Foot Model 2014|Tutorial: | ||
| - | |||
| - | * **[[IOR Foot Model 2007|Tutorial: | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | ====Other Models==== | ||
| - | * **[[Tutorial: | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | A Virtual Laboratory is not a physical segment in Visual3D but is equivalent to a physical segment to the effect that it has a Segment Coordinate System that can be used to represent the laboratory (or other objects) and has an associated surface model that can be animated as part of the scene. | ||
| - | |||
| - | A Virtual Laboratory is often used as the reference for segment angles (e.g. a segment relative to the laboratory) because it can accommodate the subject walking in a direction different from the laboratory coordinate system. | ||
| - | |||
| - | * **[[Digitizing Pointer Post Processing|Tutorial: | ||
| - | |||
| - | =====Movement Data===== | ||
| - | |||
| - | * **[[Visualizing Data|Tutorial: | ||
| - | |||
| - | * **[[Correcting Mislabeled Markers|Tutorial: | ||
| - | |||
| - | * **[[Force Platforms|Tutorial: | ||
| - | |||
| - | * **[[Instrumented Treadmills|Tutorial: | ||
| - | |||
| - | |||
| - | =====Command Pipeline===== | ||
| - | The Command Processing Pipeline provides access to the core of Visual3D’s functionality by providing a command line interface into all of Visual3D' | ||
| - | |||
| - | * **[[Command Pipeline|Tutorial: | ||
| - | |||
| - | * **[[Create a CMZ via the Command Pipeline|Tutorial: | ||
| - | |||
| - | * **[[Tutorial Basic Pipeline For Processing A Session|Tutorial: | ||
| - | |||
| - | * **[[Advanced Command Pipeline|Tutorial: | ||
| - | |||
| - | * **[[Gait Profile Score and Movement Analysis Profile Pipeline|Tutorial: | ||
| - | |||
| - | * **[[Pipeline Favorites|Tutorial: | ||
| - | |||
| - | * **[[Meta-Command Creation|Tutorial: | ||
| - | |||
| - | =====Signal Processing===== | ||
| - | |||
| - | * **[[Signal Processing|Tutorial: | ||
| - | |||
| - | =====Events===== | ||
| - | Movement data is often collected for more time that is required for the analysis. This is often done to minimize the effects of filtering at the endpoints. Sometimes it is because more than one cycle can be collected at a time or to ensure that the entire cycle is collected. Sometimes it is because there are long periods of meaningless activity between epochs. Regardless of the reasons for collecting extra data, it should not be necessary to analyze all of the data. The interval of interest must be extracted from the trial. The user must be able to define a time frame of interest. Most often the region of interest is defined by specific events, such as heel strike or toe off. This can be accomplished by editing the data file or by entering the start and end frame. This process is extremely tedious and in many circumstances can be automated. | ||
| - | |||
| - | An Event is simply an occurrence of interest that correlates to a motion capture frame, i.e. to a particular time point within a movement. The key events for gait studies (e.g., heel strike, toe-off) are now so well standardized that Visual3D can detect and mark them automatically . For other applications, | ||
| - | |||
| - | * **[[Event Processing|Tutorial: | ||
| - | |||
| - | * **[[Bad Force Assignments causing Bad Gait Events| Tutorial: Bad Force Assignments causing Bad Gait Events]]**: This tutorial examines how bad gait events happen due to bad force assignments, | ||
| - | |||
| - | * **[[Gait Events|Tutorial: | ||
| - | |||
| - | * **[[Manually Creating Events|Tutorial: | ||
| - | |||
| - | =====Metrics===== | ||
| - | Metrics are discrete quantitative values of signals such as maximum value, median value, value at a specified frame. In other words, metrics do not have a time-base like the other signals. | ||
| - | |||
| - | Metrics also refer to combinations of other metric values. For example, the metric describing the range of motion of a joint angle during a movement would be the difference between the metric defining the maximum value of the joint angle and the minimum value of the joint angle. The metric describing the time for a step cycle would be the time from Right Heel Strike to Right Heel Strike. | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | =====Model Based Signals===== | ||
| - | All Kinematic and Kinetic calculations in Visual3D are described as either [KINETIC_KINEMATIC] Items or [Model_Based_Items|Link_Model_Based Items]. [Kinematics_Overview|Kinematic calculations] are based on segment coordinate systems with no reference to inertial properties. [Kinetics_Overview|Kinetic (Inverse Dynamic) calculations] are performed using the assumption of linked rigid segments, " | ||
| - | |||
| - | * **[[Model Based Computations|Tutorial: | ||
| - | |||
| - | =====EMG===== | ||
| - | Electromyography ([EMG]) signals are electrical signals generated by the activity of skeletal muscles when they respond to inputs from the central nervous system. Processing EMG signals typically follows some variation of the following steps: | ||
| - | |||
| - | #High Pass Filter | ||
| - | #Low Pass Filter | ||
| - | #Rectify Data | ||
| - | #Filter Noise | ||
| - | #Normalize and Scale Data | ||
| - | |||
| - | * **[[Tutorial EMG|Tutorial: | ||
| - | |||
| - | =====Stability===== | ||
| - | In this tutorial, we will review the current literature definition of Margin of Stability (MoS) and provide an example of calculating this measure in Visual3D. | ||
| - | |||
| - | We will also explore a new way to present the MoS that we think is more intuitive and overcomes some of the limitations of MoS during walking. We will provide an example of measuring a new MoS in Visual3D, and visualizing this measure using Inspect3D. | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | |||
| - | ==Reporting== | ||
| - | Visual3D creates a Workspace into which all data is stored, models are integrated, and reports are produced. The entire workspace can be saved and shared as a digital report in which all the underlying analysis, data, and models can be accessed. | ||
| - | |||
| - | Every Visual3D workspace includes exactly one report, which is initially blank, and to which you may add any number of distinct pages. In a sense, the entire workspace is itself a kind of extended electronic report, which contains not only the contents of the Reporting page but also all of the original data and records of all data-processing steps. | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | * **[[Tutorial: | ||
| - | |||
| - | * **[[More Report Tutorials|More Report Tutorials]]**: | ||
| - | |||
| - | =====CalTester===== | ||
| - | [CalTester_Mode|CalTester] provides proper calibration and is an essential tool for laboratories that: | ||
| - | |||
| - | *Have instrumented Treadmills | ||
| - | *Have instrumented Stairs | ||
| - | *Move cameras and/or Move force platforms regularly | ||
| - | *Have amplifier switches that can be easily bumped, or are regularly changed | ||
| - | *Have settings that are regularly changed | ||
| - | *Have students or unsupervised visitors in the laboratory | ||
| - | *Are required to have regulatory oversight of their laboratory | ||
| - | |||
| - | * **[[CalTester Report|Tutorial: | ||
| - | |||
| - | * **[[CalTester Force Platform Locator|Tutorial: | ||
| - | |||
| - | * **[[CalTester Force Platform Jig|Tutorial: | ||
visual3d/tutorials/overview.1718034232.txt.gz · Last modified: by wikisysop
