Skip to content

Conversation

@dhruvtya
Copy link
Contributor

No description provided.

@dhruvtya dhruvtya self-assigned this Oct 31, 2025
@@ -0,0 +1,9 @@
## Request
Copy link
Contributor

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?

Copy link
Contributor Author

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

Comment on lines +3 to +7
# Start time for retention
polymath_msgs/DateTime start_time

# End time for retention
polymath_msgs/DateTime end_time
Copy link
Contributor

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

Copy link
Contributor Author

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

Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants