bunny | 易学教程

基于正交投影的点云局部特征描述详解

阅读更多关于基于正交投影的点云局部特征描述详解

点击上方“ 3D视觉工坊 ”，选择“星标” 干货第一时间送达本次介绍一个发表于Pattern Recognition的经典三维点云描述子TOLDI，首先进行算法阐述，然后再给出数据集的介绍、局部参考坐标系与描述子的评估方法。论文地址：Jiaqi Yang, QianZhang, Yang Xiao, Zhiguo Cao, “TOLDI: An effective and robust approach for 3Dlocal shape description”, Pattern Recognition, vol. 65, pp. 175–187, 2017. 源码地址：https://github.com/TaylorAmy1995/3D-feature-description.git 1.引言影响点云局部特征描述能力和稳定性的因素主要包括几何属性的利用以及空间信息的解码。因为点云具有无序、不规则、无拓扑结构等特性，可以凭借三维到二维投影的方式来用多张二维图像表征三维点云的几何特征，图像的表征能提供稳定的信息解码，而多视角机制可以弥补投影导致的信息损失；对于空间信息的解码，意识到充分利用三维空间信息依赖于三维物理坐标系的构建，然而敏感器的坐标系没有抗旋转的能力，因此尝试在点云局部曲面构造了一个本征、抗旋转的局部坐标系。基于上述分析

RabbitMQ change queue parameters on a production system

阅读更多关于 RabbitMQ change queue parameters on a production system

问题 I'm using RabbitMQ as a message queue in a service-oriented architecture, where many separate web services publish messages bound for RabbitMQ queues. Those queues are in turn subscribed to by various consumers, which perform background work; a pretty vanilla use-case for RabbitMQ. Now I'd like to change some of the queue parameters (specifically, I'd like to bind queues to a new dead-letter exchange with a certain routing key). My problem is that making this change in place on a production

RabbitMQ keeps stacking unacked messages although they are rejected or acknowledged

阅读更多关于 RabbitMQ keeps stacking unacked messages although they are rejected or acknowledged

问题 My Ruby code below processes RabbitMQ events. I'm using Bunny for Ruby and the sneakers gem. Although I think I'm acting on all possible events, the local channels are getting stacked with unacked messages. This happens every time the log says something like: sneakers_1 | I, [2017-02-08T19:03:31.088857 #14] INFO -- : Rejecting 172.21.0.21. Name invalid tld This is my Ruby code: require 'sneakers' class EventProcessor include Sneakers::Worker from_queue :edge_requests def work(msg) msg = JSON

Routing messages in RabbitMQ topic exchange that do NOT match a pattern

阅读更多关于 Routing messages in RabbitMQ topic exchange that do NOT match a pattern

问题 Two queues are bound to a topic exchange with the following routing keys: Queue A, bound with routing key pattern match *.foo Queue B, bound with routing key pattern match *.bar I'd like to add a third queue to this exchange that receives messages that are neither foo messages nor bar messages. If I bind this queue with a # routing key, I naturally get all messages I need, but including foo 's and bar 's which I don't want. Any way to route messages patching a pattern NOT *.foo AND NOT *.bar

How do I get old messages from RabbitMQ?

阅读更多关于 How do I get old messages from RabbitMQ?

问题 I'm publishing RabbitMQ messages using Bunny (Ruby) like this: x.publish("Message !"+n.to_s, :routing_key => 'mychannel') and subscribing like this: ch = conn.create_channel x = ch.topic('fling',durable: true) q = ch.queue("") q.bind(x, :routing_key => 'mychannel') puts "Waiting for messages." q.subscribe( :block => true) do |delivery_info, properties, body| puts " [x] Received #{body}, message properties are #{properties.inspect}" Once I start the subscriber, it immediately receives any

RabbitMQ change queue parameters on a production system

阅读更多关于 RabbitMQ change queue parameters on a production system

I'm using RabbitMQ as a message queue in a service-oriented architecture, where many separate web services publish messages bound for RabbitMQ queues. Those queues are in turn subscribed to by various consumers, which perform background work; a pretty vanilla use-case for RabbitMQ. Now I'd like to change some of the queue parameters (specifically, I'd like to bind queues to a new dead-letter exchange with a certain routing key). My problem is that making this change in place on a production system is problematic for a couple reasons. Whats the best way for me to transition to these new queues