HAS-Motion Software Documentation

User Tools

Site Tools

You are here: Main Page » visual3d » documentation » pipeline » model_commands » Add Functional Joint Landmark
visual3d:documentation:pipeline:model_commands:add_functional_joint_landmark

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
visual3d:documentation:pipeline:model_commands:add_functional_joint_landmark [2024/06/19 12:51] – sgrangervisual3d:documentation:pipeline:model_commands:add_functional_joint_landmark [2024/07/17 15:46] (current) – created sgranger
Line 1: Line 1:
-{{**this is a legacy command in visual3d. visual3d version 4.0 has a new interface for functional joints, and new way of specifying a functional joint landmark as part of the model template. this command should continue to work as originally implemented but it is recommended that you adopt the current approach**+====== Add Functional Joint Landmark ======
  
-this command is based on:\\ +**This is a legacy command in Visual3D. Visual3D version 4.0 has a new interface for functional joints, and new way of specifying a functional joint landmark as part of the model template. This command should continue to work as originally implemented but it is recommended that you adopt the current approach**
-**schwartz mh, rozumalski a** (2005) a new method for estimating joint parameters from motion data. journal of biomechanics, 38, 107-116+
  
-add_functional_joint_landmark.png+This command is based on:\\ 
 +**Schwartz MH, Rozumalski A** (2005) A new method for estimating joint parameters from motion data. Journal of Biomechanics, 38, 107-116
  
-**add_functional_joint_landmark**+{{:Add_Functional_Joint_Landmark.png}}
  
-|**/landmark_name=**                          |the name of the landmark to be created.                                                                                                                                                                                                 | +**Add_Functional_Joint_Landmark**
-|**/calibration_file=**                       |the name of the hybrid model. use the full pathname.                                                                                                                                                                                    | +
-|**/tracking_segment_name=**                  |the joint landmark is created relative to an existing segment. for example, for the hip joint center, the pelvis is used.                                                                                                               | +
-|**/tracking_types=**                         |the types of reference markers used for defining the landmark.                                                                                                                                                                          | +
-|**/tracking_names=**                         |the names of reference markers used for defining the landmark                                                                                                                                                                           | +
-|**/tracking_folder=**                        |the folder containing the tracking markers                                                                                                                                                                                              | +
-|**/other_segment_name=**                     |the name of the other segment (e.g. the landmark does not refer to this segment                                                                                                                                                         | +
-|**/signal_types=**                           |the types of signals used for the tracking markers.                                                                                                                                                                                     | +
-|**/signal_names=**                           |the names of signals used for the tracking markers. any number of tracking markers may be used.                                                                                                                                         | +
-|**/signal_folder=**                          |the folders for signals used for the tracking markers.                                                                                                                                                                                  | +
-|**/motion_file=**                            |the full pathname of the motion file used. this command allows only one movement file to be used. the user should make sure that a full range of motion about all axes is contained in one file.                                        | +
-|**/event_start=**                            |the start frame for the range of data to be used.                                                                                                                                                                                       | +
-|**/event_stop=**                             |the stop frame for the range of frames of data to use.                                                                                                                                                                                  | +
-|**/compute_second_landmark_on_axis=**        |true= compute a second landmark that lies on an axis (used for computing a joint axis)                                                                                                                                                  | +
-|**/second_landmark_distance=0.1**            |the location of the second landmark relative to the joint center                                                                                                                                                                        | +
-|**/minimum_helical_rotation_accepted=**      |any combination of three frames for which the helical rotation angle is less than 5 degrees are rejected                                                                                                                                | +
-|**/create_100_representative_landmarks=**    |a random selection of the intermediate centers of rotation will be saved as landmarks.                                                                                                                                                  | +
-|**/approximate_number_of_combinations_used=**|if there are a large number of frames of data, the possible combinations of 3 frames becomes very big. the can specify an estimate of the number of combination used (these are selected randomly from the total number of combinations)| +
-|**/search_window=**                          |only centers of rotation within the search radius are used for the mean value.                                                                                                                                                          | +
-|**/rate_of_volume_reduction=**               |the rate at which the domain of possible solutions is reduced.                                                                                                                                                                          | +
-|**/number_of_iterations_reducing_radius=**   |the number of times the radius is reduced. at each iteration the cell containing the most crossings is used as the center for the next iteration.                                                                                       | +
-|**/minimum_number_of_values_in_radius=**     |when the number of landmarks within the current radius falls below this number, the mean value is determined from these markers.                                                                                                        |+
  
-this command was changed for visual3d version 3.83 to allow the specification of **reference markers** instead of **reference segment.**+|**/LANDMARK_NAME=**                          |The name of the landmark to be created.                                                                                                                                                                                                 | 
 +|**/CALIBRATION_FILE=**                       |The name of the hybrid model. Use the full pathname.                                                                                                                                                                                    | 
 +|**/TRACKING_SEGMENT_NAME=**                  |The joint landmark is created relative to an existing segment. For example, for the hip joint center, the pelvis is used.                                                                                                               | 
 +|**/TRACKING_TYPES=**                         |The types of reference markers used for defining the landmark.                                                                                                                                                                          | 
 +|**/TRACKING_NAMES=**                         |The names of reference markers used for defining the landmark                                                                                                                                                                           | 
 +|**/TRACKING_FOLDER=**                        |The folder containing the tracking markers                                                                                                                                                                                              | 
 +|**/OTHER_SEGMENT_NAME=**                     |The name of the other segment (e.g. the landmark does not refer to this segment                                                                                                                                                         | 
 +|**/SIGNAL_TYPES=**                           |The types of signals used for the tracking markers.                                                                                                                                                                                     | 
 +|**/SIGNAL_NAMES=**                           |The names of signals used for the tracking markers. Any number of tracking markers may be used.                                                                                                                                         | 
 +|**/SIGNAL_FOLDER=**                          |The folders for signals used for the tracking markers.                                                                                                                                                                                  | 
 +|**/MOTION_FILE=**                            |The full pathname of the motion file used. This command allows only one movement file to be used. The user should make sure that a full range of motion about all axes is contained in one file.                                        | 
 +|**/EVENT_START=**                            |The start frame for the range of data to be used.                                                                                                                                                                                       | 
 +|**/EVENT_STOP=**                             |The Stop frame for the range of frames of data to use.                                                                                                                                                                                  | 
 +|**/COMPUTE_SECOND_LANDMARK_ON_AXIS=**        |TRUE= compute a second landmark that lies on an axis (used for computing a joint axis)                                                                                                                                                  | 
 +|**/SECOND_LANDMARK_DISTANCE=0.1**            |The location of the second landmark relative to the joint center                                                                                                                                                                        | 
 +|**/MINIMUM_HELICAL_ROTATION_ACCEPTED=**      |Any combination of three frames for which the helical rotation angle is less than 5 degrees are rejected                                                                                                                                | 
 +|**/CREATE_100_REPRESENTATIVE_LANDMARKS=**    |a random selection of the intermediate Centers of Rotation will be saved as Landmarks.                                                                                                                                                  | 
 +|**/APPROXIMATE_NUMBER_OF_COMBINATIONS_USED=**|If there are a large number of frames of data, the possible combinations of 3 frames becomes very big. The can specify an estimate of the number of combination used (these are selected randomly from the total number of combinations)| 
 +|**/SEARCH_WINDOW=**                          |Only Centers of Rotation within the search radius are used for the mean value.                                                                                                                                                          | 
 +|**/RATE_OF_VOLUME_REDUCTION=**               |The rate at which the domain of possible solutions is reduced.                                                                                                                                                                          | 
 +|**/NUMBER_OF_ITERATIONS_REDUCING_RADIUS=**   |The number of times the radius is reduced. At each iteration the cell containing the most crossings is used as the center for the next iteration.                                                                                       | 
 +|**/MINIMUM_NUMBER_OF_VALUES_IN_RADIUS=**     |When the number of landmarks within the current radius falls below this number, the mean value is determined from these markers.                                                                                                        |
  
-  * if a reference segment is specified, the landmark will be created relative to that segment. +This command was changed for Visual3D Version 3.83 to allow the specification of **REFERENCE MARKERS** instead of **REFERENCE SEGMENT.**
-  * if no reference segment is specified, the landmark will be created relative to the first three reference markers (e.g. a technical coordinate system will be created from these markers). if more than 3 reference markers are specified, visual3d will use all reference markers to track the technical coordinate system.+
  
-==== notes ====+  * If a Reference Segment is specified, the landmark will be created relative to that segment. 
 +  * If no Reference Segment is specified, the landmark will be created relative to the first three REFERENCE MARKERS (e.g. a Technical Coordinate System will be created from these markers). If more than 3 REFERENCE MARKERS are specified, Visual3D will use all REFERENCE MARKERS to track the Technical Coordinate System.
  
-the motion trials being used to identify the functional joint landmark must be [[visual3d:documentation:pipeline:model_commands:assign_model_file|assigned]] to the static calibration trial.+=== NOTES ===
  
-if tracking_segment_name is specified, tracking_types, tracking_names, tracking_folder are ignored and can be left blank. the landmark will be created relative to the tracking segment.+The motion trials being used to identify the functional joint landmark must be [[Visual3D:Documentation:Pipeline:Model_Commands:Assign_Model_File|assigned]] to the static calibration trial.
  
-if tracking_segment_name is blank, tracking_types, tracking_names, tracking_folder must be specified. the landmark will be created relative to 3 of the tracking markers. the first two marker will be selected from the list of tracking markers so that these markers are the maximum distance apart. the third marker will be the maximum distance from a line between the other two.+If TRACKING_SEGMENT_NAME is specified, TRACKING_TYPES, TRACKING_NAMES, TRACKING_FOLDER are ignored and can be left blank. The landmark will be created relative to the Tracking Segment. 
 + 
 +If TRACKING_SEGMENT_NAME is blank, TRACKING_TYPES, TRACKING_NAMES, TRACKING_FOLDER must be specified. The landmark will be created relative to 3 of the Tracking markers. The first two marker will be selected from the list of tracking markers so that these markers are the maximum distance apart. The third marker will be the maximum distance from a line between the other two.
  
 \\ \\
  
  
-if other_segment_name is specified, signal_types, signal_names, signal_folder are ignored and can be left blank.+If OTHER_SEGMENT_NAME is specified, SIGNAL_TYPES, SIGNAL_NAMES, SIGNAL_FOLDER are ignored and can be left blank. 
 + 
 +If OTHER_SEGMENT_NAME is balcn, SIGNAL_TYPES, SIGNAL_NAMES, SIGNAL_FOLDER must be specified.
  
-if other_segment_name is balcn, signal_types, signal_names, signal_folder must be specified. 
  
  
-}} 
visual3d/documentation/pipeline/model_commands/add_functional_joint_landmark.1718801518.txt.gz · Last modified: 2024/06/19 12:51 by sgranger