-
Notifications
You must be signed in to change notification settings - Fork 1
Interfaces for managing Continuous Recording #12
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
base: main
Are you sure you want to change the base?
Conversation
| @@ -0,0 +1,9 @@ | |||
| ## Request | |||
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.
Given how generic this .srv is, why not just make it something like BasicRequest.srv?
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 we can make a basic trigger request, since even StopBagRecording.srv is the same
| # Start time for retention | ||
| polymath_msgs/DateTime start_time | ||
|
|
||
| # End time for retention | ||
| polymath_msgs/DateTime end_time |
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.
why define a new datetime? Why not rostime? Let other tools define the human readable interface
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.
Since all bags are stored with UTC timestamp, I assume it'll be more intuitive for someone to provide that when requesting to retain bags instead of builtin_interfaces/Time (sec + nanosec). Would be intuitive to use from raw service panels and cli as well if required
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.
We will be writing tooling in Foxglove/Polyglot to set retentions right? They can manage the human readable datetime -> ros time conversion.
No description provided.