Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disambiguate frame id in latencylogger #24164

Merged
merged 9 commits into from
Apr 19, 2022

Conversation

lukaspetersson
Copy link
Contributor

If the same service for different frames overlap, there is ambiguity in when assigning frame id to a timestamp. In latencylogger, warn the user about this. The user can provide the frame id from the timestamp in these situations.

@lukaspetersson lukaspetersson marked this pull request as ready for review April 7, 2022 18:47
@lukaspetersson lukaspetersson merged commit 397bd25 into master Apr 19, 2022
@lukaspetersson lukaspetersson deleted the latencylogger_disambiguate branch April 19, 2022 21:29
cydia2020 pushed a commit to cydia2020/dodgypilot that referenced this pull request Apr 20, 2022
* add tools to disambiguate frame id

* Update selfdrive/camerad/cameras/camera_qcom2.cc

Co-authored-by: Gijs Koning <gijs-koning@live.nl>

* bug fix

* remove duplicate code

* PR comments

* bug fix

Co-authored-by: Gijs Koning <gijs-koning@live.nl>
Co-authored-by: Comma Device <device@comma.ai>
spektor56 pushed a commit to spektor56/ghostpilot that referenced this pull request May 7, 2022
* add tools to disambiguate frame id

* Update selfdrive/camerad/cameras/camera_qcom2.cc

Co-authored-by: Gijs Koning <gijs-koning@live.nl>

* bug fix

* remove duplicate code

* PR comments

* bug fix

Co-authored-by: Gijs Koning <gijs-koning@live.nl>
Co-authored-by: Comma Device <device@comma.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants