Mike Lezhnin

@bombela I am a bit late to the party, but you seem to be very well-knowledged inthese matters; so I decided to ask you: there is also such a thing...

Also related to this issue: if I have an option that takes an integer, it can no longer be negative, since Clara can't parse things that start this a minus.

As of right now you can just use something like this: ```node #!/usr/bin/env node const { sparse } = require('mathjs'); function kron(m1, m2) { let re = sparse([[0]]); let height...

@josdejong if I manage my free time properly, then yes, but so far I am not good at this...

Well, that is unusual, it is supposed to work better outdoors than indoors :) You can try: 1) Moving slower. 2) Playing around with exposure (lowering it / trying autoexposure)....

I'd assume something is wrong with image width/height, which would cause image wrapping and produce strips just like what you see. I can't tell exactly where the problem occurs though...

Do you have a sonar attached to px4flow? If not then the behavior you observe is to be expected.

Hm, afaik PX4FLOW itself does not do anything with GPS, so any kind of combination with GPS happens on the PixHawk side, so you better ask there.

+1, it is a good idea to have at least some release version.

I am a bit confused why you submitted `CMakeLists.txt.user` and also why you changed focal length values. Overall it is a good idea to replace the code for sonar into...