-
Notifications
You must be signed in to change notification settings - Fork 143
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
DEPTH_AHAT frame rate #38
Comments
In general, the framerate might depend on how many streams you open, if you're in Debug or Release etc.. If you try the StreamRecorder app, when you extract the recorded data via |
Hi @fbogo , Thanks for the suggestion. I ran the Thanks. |
Hmm looks like I cannot repro (I'm getting almost 45fps). When you run |
I ran the StreamRecorder app again just to be sure. I don't know if there was some issue with the build the last week (I am pretty sure I was running in Release mode), but I couldn't get more than 2fps.
In Release mode, printing out Debug logs causes the framerate to slow down to 1 to 2 fps. The AHAT visualization is sometimes visibly low (especially in Debug config). Thank you so much for your help! :) |
Hi,
The API doc states that the DEPTH_AHAT sensor runs at 45 fps. We are trying to figure out the actual frame rate that we receive.
We found that the time difference between each frame is 0.2 to 0.1 seconds.
I just took the difference between the SensorTicks and divided them by SensorTicksPerSocond to get that.
The difference between System Time for the frames is consistent with the SensorTicks.
I tested this in CameraUpdateThread in the SensorVisualization Sample.
Did I miss something or is that the best framerate for DEPTH_AHAT?
Thanks.
The text was updated successfully, but these errors were encountered: