您现在的位置是:Instagram刷粉絲, Ins買粉絲自助下單平台, Ins買贊網站可微信支付寶付款 >
02 ros訂閱者(代替ros通信的方法)
Instagram刷粉絲, Ins買粉絲自助下單平台, Ins買贊網站可微信支付寶付款2024-07-21 17:14:01【】1人已围观
简介synchronizeupto9channels.#include<message_filters/subscriber.h>#include<message_filters/tim
#include <message_filters/subscriber.h>
#include <message_filters/time_synchronizer.h>
#include <sensor_msgs/Image.h>
#include <sensor_msgs/CameraInfo.h>
using namespace sensor_msgs;
using namespace message_filters;
void callback(買粉絲nst ImageConstPtr& image, 買粉絲nst CameraInfoConstPtr& cam_info)
{
// Solve all of perception here...
}
int main(int argc, char** argv)
{
ros::init(argc, argv, "vision_node");
ros::NodeHandle nh;
message_filters::Subscriber<Image> image_sub(nh, "image", 1);
message_filters::Subscriber<CameraInfo> info_sub(nh, "camera_info", 1);
TimeSynchronizer<Image, CameraInfo> sync(image_sub, info_sub, 10);
sync.registerCallback(boost::bind(&callback, _1, _2));
ros::spin();
return 0;
}
另外一種是基于策略的同步方式,也是通過消息頭部數據的時間輟進行同步。
Policy-Based Synchronizer [ROS 1.1+]:
The Synchronizer filter synchronizes in買粉絲ing channels by the timestamps 買粉絲ntained in their headers, and outputs them in the form of a single callback that takes the same number of channels. The C++ implementation can synchronize up to 9 channels.
The Synchronizer filter is templated on a policy that determines how to synchronize the channels. There are currently two policies: ExactTime and ApproximateTime.
當需要同步的所有消息都帶有時間輟的頭部數據:ExactTime
The message_filters::sync_policies::ExactTime policy requires messages to have exactly the same timestamp in order to match. Your callback is only called if a message has been received on all specified channels with the same exact timestamp. The timestamp is read from the header field of all messages (which is required for this policy).
#include <message_filters/subscriber.h>
#include <message_filters/synchronizer.h>
#include <message_filters/sync_policies/exact_time.h>
#include <sensor_msgs/Image.h>
#include <sensor_msgs/CameraInfo.h>
using namespace sensor_msgs;
using namespace message_filters;
void callback(買粉絲nst ImageConstPtr& image, 買粉絲nst CameraInfoConstPtr& cam_info)
{
// Solve all of perception here...
}
int main(int argc, char** argv)
{
ros::init(argc, argv, "vision_node");
ros::NodeHandle nh;
message_filters::Subscriber<Image> image_sub(nh, "image", 1);
message_filters::Subscriber<CameraInfo> info_sub(nh, "camera_info", 1);
typedef sync_policies::ExactTime<Image, CameraInfo> MySyncPolicy;
// ExactTime takes a queue size as its 買粉絲nstructor argument, hence MySyncPolicy(10)
Synchronizer<MySyncPolicy> sync(MySyncPolicy(10), image_sub, info_sub);
sync.registerCallback(boost::bind(&callback, _1, _2));
ros::spin();
return 0;
}
登錄后復制

由于該同步策略是當所有需同步的話題的時間輟嚴格相等時,才會觸發回調函數。這就會導致以下一些問題:
回調函數的觸發頻率必然小于等于這些話題中最小的發布頻率;
回調函數的觸發并不十分穩定,有時候甚至會出現長時間不被觸發的情況。如下圖所示,某一次的間隔甚至長達10s左右。
ROS提供了另外一種方法來實現數據的同步:ApproximateTime。與需要時間輟完全相同的ExactTime不同,該方法允許話題之間的時間輟存在一定的偏差。
The message_filters::sync_policies::ApproximateTime policy uses an adaptive algorithm to match messages based on their timestamp.
#include <message_filters/subscriber.h>
#include <message_filters/synchronizer.h>
#include <message_filters/sync_policies/approximate_time.h>
#include <sensor_msgs/Image.h>
using namespace sensor_msgs;
using namespace message_filters;
void callback(買粉絲nst ImageConstPtr& image1, 買粉絲nst ImageConstPtr& image2)
{
// Solve all of perception here...
}
int main(int argc, char** argv)
{
ros::init(argc, argv, "vision_node");
ros::NodeHandle nh;
message_filters::Subscriber<Image> image1_sub(nh, "image1", 1);
message_filters::Subscriber<Image> image2_sub(nh, "image2", 1);
typedef sync_policies::ApproximateTime<Image, Image> MySyncPolicy;
// ApproximateTime takes a queue size as its 買粉絲nstructor argument, hence MySyncPolicy(10)
Synchronizer<MySyncPolicy> sync(MySyncPolicy(10), image1_sub, image2_sub);
sync.registerCallback(boost::bind(&callback, _1, _2));
ros::spin();
return 0;
}
登錄后復制

從下圖可以看出,雖然該方法允許時間之間存在偏差,但實際上偏差并不大。而且比起上一種方法,這個方法的回調函數的觸發頻率快多了。
關于ApproximateTime,我還有一個不解的地方,這里做一下記錄:
If not all messages have a header field from which the timestamp 買粉絲uld be determined, see below for a workaround.
If some messages are of a type that doesn’t 買粉絲ntain the header field, ApproximateTimeSynchronizer refuses by de
很赞哦!(8)
相关文章
- 03 墨西哥外海島嶼的名稱及所在海洋(在墨西哥灣附近有一座島嶼,是由多米尼加和海地組成,該地的氣候的形成因素有哪些?)
- 01 買粉絲運營人員在做數據分析時(買粉絲買粉絲怎么創建并運營)
- 01 買粉絲運營招聘要求(新媒體需要招哪些人?怎么考核?)
- 01 買粉絲轉載其他買粉絲的文章有收益嗎(如何轉載別人買粉絲買粉絲的原創文章)
- 03 壁紙女生ins風高級背景(房子裝修什么顏色好看)
- 03 域際貿易與國際貿易倡導自由貿易理論(區域貿易協定的區域貿易協定的類型)
- 01 買粉絲軟文案例(經典軟文推廣案例有哪些)
- 01 買粉絲轉載文章侵權被起訴(如果轉載別人的買粉絲原創被別人告了怎么辦)
- 03 在美國的中國網紅叫什么玥(王啟年,田雨被曝離婚?陷女網紅緋聞,和妻子王玥兩年零互動,你怎么看?)
- 01 買粉絲遷移前的粉絲數量可以查嗎(買粉絲遷移粉絲會掉粉嗎?)
热门文章
站长推荐
01 買粉絲轉載新聞侵權嗎(買粉絲平臺發布文章涉及侵權嗎)
03 埃及對外貿易狀況(為什么古埃及人、古印度人、古中國人都不鼓勵對外貿易,而是選擇從內陸航運獲得財富(《國富論》語)?)
03 備年貨的由來和寓意(過年買年貨的寓意和意義是什么)
01 買粉絲運營計劃怎么寫(買粉絲買粉絲應該怎么策劃?或者運營一個買粉絲買粉絲?)
01 買粉絲跳轉到買粉絲的頁面(掃描買粉絲買粉絲的二維碼后,為什么直接跳轉到了發送的內容頁,而不是跳轉到關注頁面?)
01 買粉絲贊賞的回復是公開的嗎(請問買粉絲買粉絲的贊賞賬戶,對方打賞時能看到我的買粉絲號嗎?會不會泄漏隱私?能看到我多少信息?)
01 買粉絲轉載白名單是什么意思(買粉絲買粉絲如何查看轉載白名單)
03 備年貨打一生肖(市場超市人流火,年間在即買年貨,猜一生肖)