visual3d:documentation:pipeline:metric_commands:metric_compute_temporal_distance
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:metric_commands:metric_compute_temporal_distance [2024/11/15 18:34] – wikisysop | visual3d:documentation:pipeline:metric_commands:metric_compute_temporal_distance [2024/11/15 18:52] (current) – [Subject computation using subject name/prefix parameters] wikisysop | ||
---|---|---|---|
Line 11: | Line 11: | ||
* Second, make the other TAG active and set a unique output folder. | * Second, make the other TAG active and set a unique output folder. | ||
- | ==== Pipeline Command ==== | + | ===== Pipeline Command |
Command including default values. | Command including default values. | ||
Line 58: | Line 58: | ||
Note that the treadmill direction is new, and is specified as a unit vector. | Note that the treadmill direction is new, and is specified as a unit vector. | ||
- | === Legacy Treadmill Parameters === | + | ==== Legacy Treadmill Parameters |
If the subject is walking in the y-direction of the laboratory the unit vector would be: | If the subject is walking in the y-direction of the laboratory the unit vector would be: | ||
Line 73: | Line 73: | ||
/ | / | ||
- | ==== Temporal Distance Dialog ==== | + | ===== Temporal Distance Dialog |
- | |**Version 4 & Earlier: | + | |**Version 4 & Earlier: |
- | === Files for computing temporal distances === | + | ==== Files for computing temporal distances |
- | |{{: | + | |{{: |
|{{: | |{{: | ||
- | |{{: | + | |{{: |
|{{: | |{{: | ||
Line 91: | Line 91: | ||
|{{: | |{{: | ||
- | ==== Subject computation using subject name/prefix parameters ==== | + | ===== Subject computation using subject name/prefix parameters |
- | Visual3D | + | Visual3D |
When using a version of Visual3D prior to implementing multisubject support, Visual3D treats each CMO/Z file as a single subject. In this way, the temporal and distance metrics are computed in the CMO/Z GLOBAL for the subject processed within that CMO. In the same manner, when computing the temporal and distance metrics across a library of subjects, each CMO/Z is treated as a single subject and then the subject averages are computed across CMO/Z files and placed into the workspace GLOBAL for the overall mean values across subjects. | When using a version of Visual3D prior to implementing multisubject support, Visual3D treats each CMO/Z file as a single subject. In this way, the temporal and distance metrics are computed in the CMO/Z GLOBAL for the subject processed within that CMO. In the same manner, when computing the temporal and distance metrics across a library of subjects, each CMO/Z is treated as a single subject and then the subject averages are computed across CMO/Z files and placed into the workspace GLOBAL for the overall mean values across subjects. | ||
Line 101: | Line 101: | ||
When working across CMO/Z files in the CMO/Z library, multisubject support for this command will treat each subject mean in each CMO/Z file as separate subject averages to be included for calculating the temporal and distance metric averages across all the subjects in the CMO/Z library. | When working across CMO/Z files in the CMO/Z library, multisubject support for this command will treat each subject mean in each CMO/Z file as separate subject averages to be included for calculating the temporal and distance metric averages across all the subjects in the CMO/Z library. | ||
- | ==== Temporal Distance Control Data ==== | + | ===== Temporal Distance Control Data ===== |
The following are useful resources for temporal data metrics for Control Data Sets. | The following are useful resources for temporal data metrics for Control Data Sets. |
visual3d/documentation/pipeline/metric_commands/metric_compute_temporal_distance.1731695684.txt.gz · Last modified: 2024/11/15 18:34 by wikisysop