visual3d:documentation:pipeline:expressions:signal_functions
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
visual3d:documentation:pipeline:expressions:signal_functions [2024/11/15 19:24] – [Point Relative to 3 Points] wikisysop | visual3d:documentation:pipeline:expressions:signal_functions [2024/11/15 19:27] (current) – [Point_Tracked_By_3Points] wikisysop | ||
---|---|---|---|
Line 246: | Line 246: | ||
The difference is that a model isn't required. | The difference is that a model isn't required. | ||
- | Why would this be useful? | + | Why would this be useful?\\ |
- | The c3d format specifies that the lowest sampling rate is the POINT rate (i.e. the marker rate) | + | The c3d format specifies that the lowest sampling rate is the POINT rate (i.e. the marker rate)\\ |
- | Marker based tracking, however, often has possible sampling rates that are much higher than video rates used by markerless tracking. | + | Marker based tracking, however, often has possible sampling rates that are much higher than video rates used by markerless tracking.\\ |
- | In a situation like baseball batting or golf many users record marker and markerless synchronously and merge the files. | + | In a situation like baseball batting or golf many users record marker and markerless synchronously and merge the files.\\ |
- | The markers are used to track the club or bat at a higher sampling rate than the video | + | The markers are used to track the club or bat at a higher sampling rate than the video\\ |
- | Then the c3d format, and Visual3D' | + | Then the c3d format, and Visual3D' |
- | When merging the two files, Visual3D automatically downsamples the POINT rate to the ROTATION rate. | + | When merging the two files, Visual3D automatically downsamples the POINT rate to the ROTATION rate.\\ |
- | To compensate (at least somewhat), Visual3D stores a copy of the POINT data as a DERIVED signal at the original POINT rate | + | To compensate (at least somewhat), Visual3D stores a copy of the POINT data as a DERIVED signal at the original POINT rate\\ |
- | The data is preserved, but the model and model based items cannot refer to the DERIVED signals | + | The data is preserved, but the model and model based items cannot refer to the DERIVED signals\\ |
- | The workaround is to perform some calculations only on the DERIVED signals independent of any model. | + | The workaround is to perform some calculations only on the DERIVED signals independent of any model.\\ |
- | **As as aside, for some applications, | + | **As as aside, for some applications, |
+ | Example: | ||
+ | locate a point in the model relative to 3 markers\\ | ||
+ | then track this point in the movement trial | ||
+ | < | ||
+ | Evaluate_Expression | ||
+ | / | ||
+ | | ||
+ | / | ||
+ | / | ||
+ | / | ||
+ | ; | ||
+ | </ | ||
==== Snip ==== | ==== Snip ==== |
visual3d/documentation/pipeline/expressions/signal_functions.1731698662.txt.gz · Last modified: 2024/11/15 19:24 by wikisysop