Sven Bone

Yes, the normalization I do. The whole pipeline is running perfectly with the bin files. I added the division by 255 for the intensity as well. No the point cloud...

@orta I haven't installed Node at all. I just installed danger globally as I did it on my old MacBook a year ago. I followed these instructions. https://danger.systems/swift/guides/getting_started#homebrew I also...

Hi, please find the test files here: https://drive.google.com/drive/folders/11PkiTw2ZXh1KaXzBlsjYgT4chPIcsOgJ?usp=sharing In the meanwhile I could fix the binary format. I used another version (fork) of pypcd to write the files. If I...

Any update? Could you download the files?

I checked your changes. It seems not to work correctly. On Python 2.x it behaves as expected. But in case of writing binary PCD files from a PointCloud2 message on...

I found a solution for that. By combining the following two pull request, the issue is solved. - https://github.com/dimatura/pypcd/pull/35 (Migration to Python 3) - https://github.com/dimatura/pypcd/pull/22 (fixing the numpy >1.15, [The...

The issue has been solved by https://github.com/danger/danger-js/issues/1448

I had the same issue with danger-swift installed via brew. Seems danger-swift uses danger-js under the hood. https://github.com/danger/swift/issues/608

If that helps, on my machine I installed no node js at all. I just installed danger by `brew install danger/tap/danger-swift` this installs danger-js and danger-swift ``` % brew info...

I can confirm the fix. After reinstalling `danger-js` and `danger-swift` via brew everything works as expected.