Facebook

Login

Support Sailonline

If you haven't already - join the SAILONLINE YACHT CLUB!

Please also consider making a donation - all amounts are greatly appreciated!

Board » Sailonline Race Committee » Rules and Decisions » “Clause 4” and ISAF rule #69.

Page: 1 2 3 4 Next

Richard and all,

Good morning.

Finally, some light?
Well, I would like to have some extra knowledge on this “Clause 4” amendment to the SOL Rules.
Can you please disclose it?

Even don’t knowing if ex-SYC members are eligible and/or can contribute with suggestions to the SOL Rules, I have the following proposal:

Inclusion of the ISAF rule #69 in SOL rules with the necessary alterations/adaptations.

ISAF link: sailing.org/...

Thank you and a
Big Hug.

João / psail


--- Last Edited by kroppyer-admin at 2016-12-22 11:19:52 ---
Sail Fair.
For information, Rule 69 deals with "bad behaviour". More: yachtingnz.org.nz/...

--- Last Edited by kroppyer-admin at 2016-12-22 11:22:20 ---
=== Navegare Necesse ===
Good morning all.

Meanwhile ISAF changed the above mentioned link to:

sailing.org/...

João / psail


________
kroppyer: cleaned up the links


--- Last Edited by kroppyer-admin at 2016-12-22 11:21:33 ---
Sail Fair.
Hi ;)

1) Rule 69 of ISAF rules has been specifically mentioned in each Championship NOR since 2014, and it is so in the 2017 ones just published as well.

2) As the SRR revision will become valid from January the 1st , and present edition is still valid , it has been decided to publish the new one only a few days before the end of 2016. ( likely tomorrow ).

Stay tuned !! ;)

SOL Coordinator
The new SRR rules (2017).

It was introduced recently a new paragraph to the SRR aka as the “Clause 4”, here transcribed:

“4. 3rd Party Software

With effect from 1st January 2017, the use of 3rd Party software to send, edit or delete commands to a boat while racing is only permitted when both of the following conditions are satisfied:

a) The commands are issued by the skipper, a team member or a boat-sitter.
b) The commands are sent to the server as soon as possible after being initiated.

Where, following a protest from a competitor in that race or from SRC, a skipper is suspected of breaching this rule the matter shall be investigated by SRC. If a breach is considered to be possible then the race results will be declared “PENDING” and the “PROTEST PROCEDURE” described below will be carried out.

Access to the SOL server may be offered to investigate the allegation; this will be conducted by authorized technicians who will provide an expert written report to both parties and the protest committee prior to any hearing on their findings.”, (end of transcription).

Immediately I had some doubts about the interpretation and full extent of ” b)” item.

“b) The commands are sent to the server as soon as possible after being initiated.”.

Something is escaping me, because boat commands (or, boat steering actions) “after being initiated” and “as soon as possible”, are somehow redundant actions.

You can only initiate a boat command - by means of an immediate action (ok, there’s the ping delay) or by delayed actions (aka “DC’s”) - if you send it (individual or a series of commands) to the SOL server.
The moment you sent the command(s) the ASAP is already happening.

Second.Two questions to SRC.
If I have a 3rd party software that automatically tracks the others boats and, also automatically reacts to their changes, is this forbidden, or not, by this new SRR “Clause 4”?

If not, does SRC intend to ban it, or not?

Thank you.

João / psail
Sail Fair.
gone

--- Last Edited by sol at 2017-12-22 16:05:50 ---
As one of people responsible for clause 4, let me give some explanation:

João: item (b): when the user gives 3rd party software a command to send to the server, the 3rd party software must do so immediately. The software may not decide itself when it sends the command to the server, nor may the user tell the software when it must send the command to the server. (Note: there is a difference between "sent to the server" and "executed": a delayed command can be send to the server immediately after the user enters the command, but only be executed at the time the user intended to.)

What software is allowed, what software is not?
- routers are allowed: they are not software that send commands (should you have a router that does send commands to sol, then it may only send those commands directly after a human (authorised to steer the boat) gives the router instruction to do so.)
- brainaid's DC editor is allowed: there may be some delay between the user giving the software the instruction to send the commands, but this delay is as short as possible. The software does not make a decision when to send the commands, it sends the commands the first possible moment after the user tells it to.
- WxInspector: doesn't send commands, this rule does not apply
- hmm's sollog: doesn't send commands, this rules does not apply
- SPINNACER is partially allowed: all except the autopilot is allowed. You may use SPINNACER, as long as you never activate the autopilot. This is because the autopilot chooses itself (without human intervention) when to send commands to the server
- Some "follow boat X" software: not allowed: the software sends commands without a human telling it to.
- Kipper's bbq rescue tool: partially allowed: boatsitting applies, during one race, only one person may rescue you.
gone

--- Last Edited by sol at 2017-12-22 16:06:39 ---
Clause 4 simply limits the sending of commands by 3rd party programs: in simple words: a human allowed to steer the boat needs to instruct the software to send the command. The software may not decide on its own when to send a command and certainly not what command to send.

This should ban all bots, autopilots, and other software that takes over human decisions, without affecting any other software.

Certainly there may be software that is unwanted be some/most people that is still allowed within the rules, but I am fully convinced that this rules bans all unwanted ways of sending commands (i.e. the ones not directly coming form a human).

There may be other ways 3rd party software can be unwanted (spamming chat or whatever), but these
(1) have been permitted last year(s) as well, so at least things don't get worse
(2) do not affect the courses of boats while racing

I hope you see that this rule is a very good and essential step in regulating 3rd party software.
Viva Huib and all.

Thank you so much for bringing light on this subject.

Your SPINNACER and Andrew’s tools were never a problem, at least in my opinion.
IRL we use autopilots, radar, AIS, depth devices, namely, all with alarm settings.
That’s pacific and above all, for the safety of boats and people.

As previously discussed the real issue is the “robot sailboat” that automatically collects the (should be private) boats live data - or directly from the Server and/or using the hmm’s data center - and, automatically reacts accordingly to the others sailing boats paths.

The first step to stop/avoid this unfair “robot” sailing is simply ruling it out, i.e., ban any type of software that runs with this purpose.
The second measure is to avoid private and precise boat data being public disclosed, as it is obvious that without data input the “robot” software is meaningful.

There’s no other way to say it.
The boat data public availability, noble in principle but, bad in results, brings situations like the one you can easily verify in the two attached PDF files. They speak for themselves.

The data contained in those files were collected for two pairs of opponent boats during the RTW Leg 2, during the Cape Horn approach.

The immediate response and behavior for two of the four boats, at least, can only be explained by two ways:

1 - The use of above mentioned “robot” software, or;
2 - The use of the hmm’s live data center.

That is the reason why I left psail in the dock and also for some skippers opting for “different” paths during races - they know well what is happening.

Happy New Year all.

João / psail
Sail Fair.
Attachments

Page: 1 2 3 4 Next

Please login to post a reply.

Races

Next Race: 00d 00h 00m


Current Races:

Maryland to Alaska 2020
Inspired by Matt Rutherford's single-handed Red Dot Expedition around the Americas in 2012, SOLer Renegade proposed a half around from Maryland over the North into the Pacific and back through the Panama Canal, in 5 legs, 5 years later. Leg 2 across the North West Passage proved to be particularly challenging and so to create a proper Ocean Race, SRC has combined Leg 2 with Leg 1 to give you a race of at least 4000nm from Maryland to Alaska in our magnificent 90ft Monohull.
PRIZE: SMPF
Race #1366
INFOby brainaid.de
90ft Monohull Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
OCCH - OCQ3 - SUPSOL - SYC
ALT. CLIENT: Classic
Race starts: Aug 04th 20:00 Registration Open!
New HTML5 Client GO TO RACE

SSANZ Triple Series 2020 - Lewmar 100 Baltic

Welcome back to Auckland for the second of three races in this year's SSANZ two-handed series, raced around the waters of the Hauraki Gulf off the E coast of New Zealand’s North Island. Our direct competitors in this 2020 Lewmar 100 Baltic course are, again, the real racers of the Young 88 Association.
Race #1377
INFO from brainaid.de
Young 88 Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
SSANZ 2020 - SYC
ALT. CLIENT Classic
Race starts: Jul 31st 21:15 Registration Closed
New HTML5 Client GO TO RACE

Brisbane to Keppel Tropical Yacht Race 2020


When the winter weather turns cool in southern Australia sailors head up to the warmer tropics. Every year in August sailors from all over the world make their way to The Great Barrier Reef for the big winter regattas at Hamilton Island, Airlie Beach and Magnetic Island. What better way to get there than to race to the reef. This year Sailonline is joining with the racers from RQYS to race the 343 nautical miles from Brisbane to Keppel Island in our TP52s. It might be winter downunder but all you will need is shorts and t-shirts.
Race #1367
INFOby brainaid.de
TP-52 Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
ALT. CLIENT:Classic
RACE CLOSE: Friday,
August 7 at 2300 UTC.
Race starts: Jul 31st 01:00 Registration Open!
New HTML5 Client GO TO RACE

The Tall Ships Races 2020 - Race 3

Welcome to the third and last of our races in this year's European Tall Ships Races - a race of 642nm from A Coruna, Spain to Dunkirk France
NOTE:Starts and Finishes in tall ships racing are always offshore to avoid conflict with shipping and shipping lanes.
Race #1361
INFO by brainaid.de
Clipper 240 Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
RANKING: TSE - SYC
ALT. CLIENT: Classic
RACE CLOSE: Thursday, 6 August at 2300utc
Race starts: Jul 27th 12:00 Registration Closed
New HTML5 Client GO TO RACE

Go to race archive

SYC Ranking

  1. Sailonline Yacht Club Member Kipper1258
  2. Sailonline Yacht Club Member bonknhoot
  3. Sailonline Yacht Club Member WRmirekd
  4. Sailonline Yacht Club Member Dingo
  5. Sailonline Yacht Club Member knockando60
  6. Sailonline Yacht Club Member calmxy
  7. Sailonline Yacht Club Member rafa
  8. Sailonline Yacht Club Member batatabh
  9. Sailonline Yacht Club Member sassy63
  10. Sailonline Yacht Club Member GREATSKUA

View full list

Series

Mobile Client

SYC members have the benefit of access to our mobile/lightweight web client!

The mobile client