Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • deepOF deepOF
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Lucas Miranda
  • deepOFdeepOF
  • Issues
  • #7
Closed
Open
Issue created Feb 09, 2021 by Joeri Bordes@joeribordes

Speed parameters

Hi Lucas,

I do have another question though! I remember we talked about this before, but I would like to investigate the speed parameters a little more in the data. And previously you said this about that:

The current speed parameter is measuring (by default) the 10-frame average speed of the centre of the animal (in pixels over frames). The result is converted to millimeters per frame (a not-so-friendly measuring unit that can be easily changed to something more meaningful). The averaging is a way of handling small noise in the predicted position.

Does this still hold true for the measurements? So if I for instance have camera with 30fps, would this mean that if I would sum the values per 30 rows that I would get the total millimeters difference per second of the animal?

Best, Joeri

Assignee
Assign to
Time tracking