sfmig
commented
5 months ago Agreed terminology
- default (cartesian) coordinate system:
- origin top left of the image,
- x-axis is positive across columns (pointing right),
- y-axis resulting from the right hand rule; i.e., positive across rows (pointing down). This convention matches DLC, napari and most image processing tools.
- position vector for keypoint i at time t: vector from the origin of the coordinate system to keypoint i $$\vec{r_i}(t) = (x_i(t), y_i(t))$$
- velocity vector for keypoint i at time t: instant velocity of keypoint i at time t $$\vec{v_i}(t) = (\dot{x}_i(t), \dot{y}_i(t))$$
- acceleration vector for keypoint i at time t: instant acceleration of keypoint i at time t $$\vec{a_i}(t) = (\ddot{x}_i(t), \ddot{y}_i(t))$$
- displacement vector for keypoint i at time t: vector representing the displacement of a keypoint i with respect to its position at the previous frame t-1 $$\vec{d_i}(t) = (x_i(t) - x_i(t-1), y_i(t) - y_i(t-1))$$
talmo
niksirbi
The problem
Throughout the code and the docs we refer to specialist terms such as "poses", "pose tracks", "pose estimation", "tracking". We either resort to explaining these terms at multiple places, or we assume the the user/reader know what they mean.
Solution
As proposed by @lochhh, we could have a glossary of terms in the docs, defining these terms unambiguously. We could then reference the glossary when we need to.
We could even add a schematic to each term, which will greatly aid their understanding. We can reuse the schematics in talks etc.
Resources
This paper defines some of these terms well.