You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
Can we work on minimizing console output for the estimator? It gets a little absurd when running multiple instances of ecl/EKF (PX4/PX4-Autopilot#14650).
INFO [ecl/EKF] reset position to last known positionINFO [ecl/EKF] reset velocity to zeroINFO [ecl/EKF] reset position to last known positionINFO [ecl/EKF] reset velocity to zeroINFO [ecl/EKF] reset position to last known positionINFO [ecl/EKF] reset velocity to zeroINFO [ecl/EKF] reset position to last known positionINFO [ecl/EKF] reset velocity to zeroINFO [ecl/EKF] reset position to last known positionINFO [ecl/EKF] reset velocity to zeroINFO [ecl/EKF] reset position to last known positionINFO [ecl/EKF] reset velocity to zeroINFO [ecl/EKF] 11544067: EKF aligned, (baro hgt, IMU buf: 18, OBS buf: 14)INFO [ecl/EKF] 11644085: EKF aligned, (baro hgt, IMU buf: 18, OBS buf: 14)INFO [ecl/EKF] 11751436: EKF aligned, (baro hgt, IMU buf: 18, OBS buf: 14)INFO [ecl/EKF] 11813268: EKF aligned, (baro hgt, IMU buf: 18, OBS buf: 14)INFO [ecl/EKF] 11951770: EKF aligned, (baro hgt, IMU buf: 18, OBS buf: 14)INFO [ecl/EKF] 11973531: EKF aligned, (baro hgt, IMU buf: 18, OBS buf: 14)
I would propose we (incrementally) eliminate all console output by default, ensuring the equivalent information is trivial to find in the logging. Critical in flight errors and resets could still make sense if used sparingly, but even there we'll want to make sure it's again captured by logging and perhaps even handled higher level (ekf2_main) to produce a mavlink critical message rather than console noise.
Can we work on minimizing console output for the estimator? It gets a little absurd when running multiple instances of ecl/EKF (PX4/PX4-Autopilot#14650).
I would propose we (incrementally) eliminate all console output by default, ensuring the equivalent information is trivial to find in the logging. Critical in flight errors and resets could still make sense if used sparingly, but even there we'll want to make sure it's again captured by logging and perhaps even handled higher level (ekf2_main) to produce a mavlink critical message rather than console noise.
FYI @priseborough @bresch
The text was updated successfully, but these errors were encountered: