Resolve "Ceres assertion raised"

Closes #332 (closed)

added bug label

added 1 commit

• 2699e377 - added bool SolverManager::check const and fixed gtests

Compare with previous version

added 5 commits

• c8dae488 - trying to reproduce the error
• e102fd48 - changed order of remove for guaranteeing good notification order
• acf44d7f - more exhaustive check and handling notification interrupted
• f235c440 - handling truncated sets of notifications
• 972b44f7 - working on removal order

Compare with previous version

added 1 commit

• 65f28333 - consumeNotifiacations in one instance and checkDerived

Compare with previous version

added 1 commit

• a46d5745 - hotfix removing debugging asserts

Compare with previous version

ctest:

• core
• gnss
• imu
• vision
• bodydynamics KO (gtest_processor_force_torque_preint also happens in devel)
• apriltag KO (gtest_processor_tracker_landmark_apriltag error: C++ exception with description "yaml-cpp: error at line 0, column 0: bad conversion" thrown in SetUp(). also happens in devel)
• laser

unmarked as a Work In Progress

merged

mentioned in commit a98c3407