ArduPilot / ArduPilot/MissionPlanner

FFT display fails on some logs and is inaccurate on others with pre/post concurrent FFTs

Open
#2,986 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2.4k
Forks
2.9k
Avg merge
19h 16m
Merged PRs (30d)
4

Description

This log fails to display at all: https://www.dropbox.com/s/862n77ezp9tial2/FFT%20filter%20log.bin?dl=0
but does so in mavfft_isb.py

This log displays incorrect Gyro FFT levels: https://www.dropbox.com/s/zqqvgqili046u5a/FFT%20filter%20log2.bin?dl=0

correct display
![Screenshot from 2022-10-24 08-03-22](https://user-images.githubusercontent.com/6076534/197534192-32a41394-0f98-470d-b998-b9eaa80c92ce.png)
MP display
![MP log2](https://user-images.githubusercontent.com/6076534/197534318-e7a659ab-bfe1-418e-b6e2-68b6102a0345.jpg)

Contributor guide

No contributing guide indexed for this repository

Research direction

Download and inspect the two linked FFT log files, then compare Mission Planner's display with mavfft_isb.py. Trace the log parsing and FFT display entry points to identify how pre/post concurrent FFTs are handled; done means both logs display and the gyro FFT levels match the reference output.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, python
Domain
data-visualization, desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.