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 Sep 26, 2024. It is now read-only.
The issue regarding movement states requires an edge_case callback. For each specific mission, we should be able to define a unique edge_case to abort the movement.
This functionality needs to be implemented in tasks/src/edge_cases.py.
Our current priority is to develop the movement_edge_case_callback function.
This function should address all the obvious edge cases encountered during movement, such as avoiding collisions with walls or imminent objects. It should utilize data from all sensors, incorporating as much information as possible.
To fully resolve this issue, a test method in test_camera.py must also be included. This test will ensure the edge cases are handled as expected.
The text was updated successfully, but these errors were encountered:
The issue regarding movement states requires an edge_case callback. For each specific mission, we should be able to define a unique edge_case to abort the movement.
This functionality needs to be implemented in tasks/src/edge_cases.py.
Our current priority is to develop the movement_edge_case_callback function.
This function should address all the obvious edge cases encountered during movement, such as avoiding collisions with walls or imminent objects. It should utilize data from all sensors, incorporating as much information as possible.
To fully resolve this issue, a test method in test_camera.py must also be included. This test will ensure the edge cases are handled as expected.
The text was updated successfully, but these errors were encountered: