Fps ouput parameter for tracking data#401
Conversation
move transform frames logic to transform_dataset
d5eb926 to
a0b1493
Compare
|
I believe linearly interpolating the positions may not provide sufficient accuracy, as it doesn't account for accelerations, which can significantly impact movement patterns. A higher-order interpolation method would likely be more suitable in this case. Although, I would have to think a bit more about this. Another challenge arises when players are not tracked in specific frames. For optical tracking data, this is relatively rare, but with broadcast tracking data, it's common for a player to be tracked in only one or two successive frames. How do you handle these situations? That said, implementing this should be more straightforward once we’ve completed #377. My recommendation would be to defer this PR until then. Lastly, I only did a quick scan of the code, so apologies if I’ve overlooked anything. Let me know if there’s anything I missed or misunderstood! And thanks for your contribution! |
My attempt for issue 200, to support arbitrary frame per second resampling for tracking dataloaders.
Based on a 'fps_output' parameter we transform a tracking dataset with an interpolation algorithm.
One question before we can merge this, can i just used an incrementing number for the frame id's?
Or do they have some deeper meaning?
Closes #200