UAVCAN: Optical Flow: Bug fix missing integration_timespan field

[JacobCrabill]

…optical_flow topic).

This is pretty straightforward. The uORB topic optical_flow includes a field integration_timespan, which is used within EKF2 (after being copied to the dt field of a flowSample object) for a number of calculations, including for the variable flow_innov. The UAVCAN sensor driver for optical flow devices (HereFlow) did not copy this field to the topic before publishing (but it does exist in the CAN message frame). This resulted in flow_innov always being 0. The fix: copy the field (ensuring consistent units).

[TSC21]

@JacobCrabill please run make format to fix the style and amend the commit.

[bresch]

Looks good for the rest

[JacobCrabill]

Fixed the formatting issues
Should be all set

[MaEtUgR]

@JacobCrabill Just a hint: if you set the git identity on your machine to the mail address you use on GitHub it will assign it to your profile and show the profile picture next to the commit and you'll appear in the GitHub statistics.
e.g. $ git config --global user.email [email protected]

[JacobCrabill]

@MaEtUgR thanks for the tip. We changed domain names at Volans-i a while back and I forgot to update my email address in my account.

[JacobCrabill]

@dagar , @bresch should this be rebased on / merged with the current "beta" branch (v1.10-beta4) instead of master in order to include in the 1.10 release? Or, is the current head of master going to end up in v1.10?

[julianoes]

@JacobCrabill I think we can cherry-pick it into the release branch.