Tools: LogAnalyzer: don't continue if we fail to set vehicle type from MSG
Tools: LogAnalyzer: cope with renamed CTUN.BarAlt attribute
Tools: LogAnalyzer: cope with renamed CTUN.BarAlt attribute
Tools: LogAnalyzer: cope with missing THR_MIN parameter
Tools: TestAutotune.py: Fix undefined name VehicleType
__VehicleType__ is used on line 58 but is never defined or imported.
Tools: TestPerformance.py: Fix undefined name VehicleType
__VehicleType__ is used on line 19 but is never defined or imported.
Tools: TestParams.py: Fix undefine name VehicleType
__VehicleType__ is used on line 21 but is never defined or imported.
Tools: TestThrust.py: Fix undefine name VehicleType
__VehicleType__ is used on line 19 but is never defined or imported.
Tools: TestVibration.py: Fix undefined name VehicleType
__VehicleType__ is used on line 21 but is never defined or imported.
__lit.next()__ is not Python 3 compatible but __next(lit)__ is compatible with both Python 2 and 3.
In Python 2.6 and later, it is safe to merely switch from lit.next() to next(lit). See: http://python3porting.com/improving.html#the-next-next Both the automated tools 2to3 and futurize consider this "fixer" to be a "safe" change as we saw in #6954
Tools: LogAnalyzer: avoid fatal error if mag data is all zeros
Tools: LogAnalyzer: correct comparisons against logdata.vehicleType
Tools: LogAnalyzer: handle logs with TimeUS in place of TimeMS
Tools: LogAnalyzer: handle logs with CTUN.ThO in place of CTUN.ThrOut
Tools: LogAnalyzer: correct motor average value
`reduce()` is called on line 55. Python 3 dropped reduce() as a builtin. https://docs.python.org/3/whatsnew/3.0.html#builtins encourages the rewriting of reduce() calls as explicit for loops or list comprehensions but I am not confident to try that in this context.
Calculate and display recommended values of FLOW_FXSCALE and FLOW_FYSCALE from an optical flow sensor calibration test
Save plots to flow_calibration.pdf file
Save calibration parameters to flow_calibration.param file
Signed-off-by: priseborough <p_riseborough@live.com.au>
Tools: Address optical flow calibration script review comments
Tools: LogAnalyzer: stop executing TestOptFlow on insufficient data
We changed from ArduCopter to APM:Copter, breaking parts of the LogAnalyzer
This change has LogAnalyzer canonicalise its output to Ardu{Plane,Rover,Copter}
Also account for change in MODE message - ThrCrs has gone away