-
Notifications
You must be signed in to change notification settings - Fork 1
Upgrade to ZED SDK 5.x #57
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
Conversation
ZEDSVOLogger zedSVOLogger = new ZEDSVOLogger(); | ||
|
||
zedSVOLogger.start(svoFile, datFile, | ||
zedSVOLogger.connect(svoFile, datFile, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
indent remaining parameters
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Good cleanup too
// on the robot at the moment both the sensor & controller are running | ||
long sensorTimestamp = sl_get_current_timestamp(cameraID); | ||
long controllerTimestamp = sensorTimestamp - controllerZeroInSensorFrame; | ||
timestampWriter.write("%d %d %s%n".formatted(controllerTimestamp, sensorTimestamp, svoPrefix)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just pointing out that the timestampWriter
could be null if an exception was thrown in the connect
method, and that's not handled here. Unlikely to happen, but worth noting
try | ||
{ | ||
// We assume both the sensor on board & controller real time thread clocks | ||
// run at the same speed to try an resolve delay and time stretching issues. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// run at the same speed to try an resolve delay and time stretching issues. | |
// run at the same speed to try and resolve delay and time stretching issues. |
// Wait some time before trying to grab again | ||
ThreadTools.park(5.0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know how this affects the resulting SVO file? I'd imagine it'd be stuck on the previous frame for some time, but maybe it doesn't handle it well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah might come back to this, I think for now its fine
No description provided.