Description of the task
When the ball is not on the field, thunderscope fails to recognize the robots and keeps printing the message:
"There are robots on the field, but no ball. It is highly likely that sensor fusion has filtered the ball out!"
Edit:
I took a quick look at sensor fusion.cpp. Turns out, the get_world function has a gate where it will only return the new world if BOTH the field and ball is present. If we initialize sensorfusion without the ball, the ball will always be a nullopt, meaning that thunderscope will never get the update world and thus the robots. Changing this gating should fix this issue.
Acceptance criteria
Blocked By
Description of the task
When the ball is not on the field, thunderscope fails to recognize the robots and keeps printing the message:
"There are robots on the field, but no ball. It is highly likely that sensor fusion has filtered the ball out!"Edit:
I took a quick look at sensor fusion.cpp. Turns out, the get_world function has a gate where it will only return the new world if BOTH the field and ball is present. If we initialize sensorfusion without the ball, the ball will always be a nullopt, meaning that thunderscope will never get the update world and thus the robots. Changing this gating should fix this issue.
Acceptance criteria
Blocked By