-
Notifications
You must be signed in to change notification settings - Fork 190
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
Is there way to change dynamic parameter with timestamp? #1444
Comments
The first option may break current system and the nodes' behavior will change, so I think it's not good idea. |
It depends on your purpose. Whey you need timestamp on dynamic_reconfigure? |
Yes, so I don't want to break current system.
To change the parameter from now (the time I changed the parameter), not the time the |
hmm, it sounds difficult. |
Maybe no, the problem is a node cannot know that what data with what timestamp other node processing. What I want to do is to specify the timestamp and parameter for a processing, this can be significant in dynamic environment. |
I'd like to use dynamic_reconfigure for recognition with timestamp.
Currently, the config callback does not see the timestamp https://github.com/jsk-ros-pkg/jsk_recognition/blob/master/jsk_pcl_ros/src/organized_multi_plane_segmentation_nodelet.cpp#L172
and dynamic_reconfigure seems to be not designed to do so.
Any idea to fix this issue?
I think there are two solutions:
configCallback
to make the node to see the timestamp.dynamic_reconfigure
to serve another topic with timstamp (likedynamic_reconfigure/ReconfigureStamped
). (currently, dynamic_reconfigure servesset_parameters
service not topic)The text was updated successfully, but these errors were encountered: