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.

Sign up for GitHub

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

Jump to bottom

Expose qos setting for /rosout #253

Closed
wants to merge 1 commit into from
Closed

Expose qos setting for /rosout #253

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions rmw/include/rmw/qos_profiles.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,20 @@ static const rmw_qos_profile_t rmw_qos_profile_default =
false
};

static const rmw_qos_profile_t rmw_rosout_qos_profile_default =
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
static const rmw_qos_profile_t rmw_rosout_qos_profile_default =
static const rmw_qos_profile_t rmw_qos_profile_rosout_default =

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this expected to be used for ros2cli profile such as ros2 topic echo --qos-profile rosout_default /rosout?

Copy link
Author

@Ada-King Ada-King Jul 22, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't familiar with the roscli code, but i think it can be used after expanding the code about parsing user input.
I will check it later.

{
RMW_QOS_POLICY_HISTORY_KEEP_LAST,
1000,
RMW_QOS_POLICY_RELIABILITY_RELIABLE,
RMW_QOS_POLICY_DURABILITY_TRANSIENT_LOCAL,
RMW_QOS_DEADLINE_DEFAULT,
RMW_ROSOUT_QOS_LIFESPAN_DEFAULT,
RMW_QOS_POLICY_LIVELINESS_SYSTEM_DEFAULT,
RMW_QOS_LIVELINESS_LEASE_DURATION_DEFAULT,
false
};


static const rmw_qos_profile_t rmw_qos_profile_services_default =
{
RMW_QOS_POLICY_HISTORY_KEEP_LAST,
Expand Down
3 changes: 3 additions & 0 deletions rmw/include/rmw/types.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -430,6 +430,9 @@ enum RMW_PUBLIC_TYPE rmw_qos_liveliness_policy_t
/// QoS Lifespan default, 0s indicate lifespan policies are not tracked or enforced
#define RMW_QOS_LIFESPAN_DEFAULT {0, 0}

/// Rosout QoS Lifespan default, 10s indicate lifespan policies are tracked
#define RMW_ROSOUT_QOS_LIFESPAN_DEFAULT {10, 0}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not so convinced that we introduce specific default value only for rosout. instead of this, could we just specify {10, 0}?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, i think it make more sense, i will modity it.


/// QoS Liveliness lease duration default, 0s indicate lease durations are not tracked or enforced
#define RMW_QOS_LIVELINESS_LEASE_DURATION_DEFAULT {0, 0}

Expand Down