Remove Tack voting when the boat round a buoy

[Nanoseb]

Right now the tack voting system is enabled when the boat is close to a waypoint, however to round a buoy we need to have several waypoints (2 or 3) close to the buoy, thus close to each other. Between them we don't want the tack voting system because we need to be able to tack without having to wait 7.5 seconds.

[Nanoseb]

I think we will need to have 2 'type' of waypoints,

• the first one can be considered like usual waypoints (with the tack vote system when we get closer to it) and can be used for the first wp around the buoy.
• the second the rest of wp around the buoy, when heading to these one the boat need to be able to tack/jibe without waiting

I think the easiest way of implementing it without breaking compatibility with previous parameter file is to add a list of wp of 'type 2' in the waypoint parameter file, something like wp/list_no_vote: ['2', '5', '8']

[Nanoseb]

according to the rules we don't need to round buoy...

If a boat succeeds completing the whole course, it will be scored by its arrival order. If not, boats will be scored according to the number of marks reached in the correct order and the order of arrival to that mark. [...] A mark/buoy is considered reached if at least one track point is recorded within a radius of 5m around the position of the (virtual) buoy.

So in the end this is not needed.

[takluyver]

Nice, that makes the course sailing quite a bit simpler; especially as 5m is a more generous tolerance than we've been aiming for.

On 24 August 2016 at 15:32, Nanoseb notifications@github.com wrote:

according to the rules we don't need to round buoy...

If a boat succeeds completing the whole course, it will be scored by its arrival order. If not, boats will be scored according to the number of marks reached in the correct order and the order of arrival to that mark. [...] A mark/buoy is considered reached if at least one track point is recorded within a radius of 5m around the position of the (virtual) buoy.

So in the end this is not needed.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Maritime-Robotics-Student-Society/sailing-robot/issues/135#issuecomment-242064363, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUA9YKA0SCp0txQMk1hCWKGFjbjX5Lxks5qjEfRgaJpZM4Jrfd_ .

[Nanoseb]

Moreover the 5m tolerance is based on our gps data (the log file we provide to them), so no worries on that point either.

[takluyver]

Hmmm, not sure about that. I think they might refer to their gps data as well.

[Nanoseb]

As the scoring process will be based on the course done by each boat, it will be preferable to use the actual position data processed by the boat’s navigation system to prevent possible deviations resulting from the different location data produced by the trackers and the boat’s navigation system.

[takluyver]

OK, great. I might still set a 4m target zone just to be on the safe side.

On 24 August 2016 at 16:00, Nanoseb notifications@github.com wrote:

As the scoring process will be based on the course done by each boat, it will be preferable to use the actual position data processed by the boat’s navigation system to prevent possible deviations resulting from the different location data produced by the trackers and the boat’s navigation system.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Maritime-Robotics-Student-Society/sailing-robot/issues/135#issuecomment-242074492, or mute the thread https://github.com/notifications/unsubscribe-auth/AAUA9UHnA1EHezI--7RMo67Ajx9mWFLbks5qjE5sgaJpZM4Jrfd_ .