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 Jan 2, 2024. It is now read-only.
Right now, the magnitude of wind speed is completely ignored. We may or may not want to use it.
For instance, we could have it change the wind cost function. Perhaps upwind/downwind sailing isn't super bad with only 1km/h wind, but absolutely unacceptable every in 20km/h.
Perhaps the MOCK_controller could have the boat speed change based on wind speed and/or wind direction.
Perhaps the MOCK_controller should tell us if we "got stuck in irons" (went upwind to too long).
The text was updated successfully, but these errors were encountered:
If the wind speed is super low, tacking is not a good idea as you may get stuck "in irons" (upwind).
If the wind changes direction and the wind angle is still 'sailable', the sail angle should change but not the rudder.
A lot of this can be left to the control team, since any angle except upwind is still able to be sailed.
From current discussion, ignoring wind speed makes sense, but care about boat speed. Essentially try to avoid using rudder turning in general, especially if we are going slowly.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now, the magnitude of wind speed is completely ignored. We may or may not want to use it.
For instance, we could have it change the wind cost function. Perhaps upwind/downwind sailing isn't super bad with only 1km/h wind, but absolutely unacceptable every in 20km/h.
Perhaps the MOCK_controller could have the boat speed change based on wind speed and/or wind direction.
Perhaps the MOCK_controller should tell us if we "got stuck in irons" (went upwind to too long).
The text was updated successfully, but these errors were encountered: