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
It may happen that the tracker cannot update the current critical point due to delays in communication. The current architecture is not robust to such types of faults. How to deal with them?
The text was updated successfully, but these errors were encountered:
setCriticalPoint() returning a boolean is an option, but not a very robust one since it assumes that you know that the message has not been received. A more robust way is to check in the next RobotReport (after invoking setCriticalPoint(), that is) to see if the currently known CP is the one that you wanted to set.
It may happen that the tracker cannot update the current critical point due to delays in communication. The current architecture is not robust to such types of faults. How to deal with them?
The text was updated successfully, but these errors were encountered: