Sailonline.org - Online Sailing

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!

Tweets by @sailonline

Board » Technical Discussion » When is my command executed?

Posted by kroppyer Posts 346 Registered at 2010-02-05 15:25:55	2016-10-26 16:30:33 - When is my command executed?
	warning: I'll explain how serverjumps, commands and the client refresh rate work, but it's complicated and I cannot tell you yet how to take advantage of this knowledge (when rounding a mark for example) Most of you know about server jumps. For rounding a mark, it's important to turn as early as possible, but absolutely not too early. This is made difficult by the server jumps, and client refresh rate, you rarely see your boat where it actually is. What you see is running a couple of seconds behind, in rare cases it could reach up to about 45 seconds. So what is exactly happening. It's more than just the server jumps and the client update rate, but let's start with them anyway: The server continuously checks all boats. For every boat that has not been moved by the server for at least 10 seconds, the server updates its position. This means, your boat will move every 10-12 seconds (when it's busy, it may take 2 seconds before the server notices it hasn't moved your boat yet). When you haven't issued a command in the last 15 minutes or so, the server may skip you once or twice, and then do one big jump to catch up. This unloads the server a bit from boats that aren't actively steered. useful tip: send a command 5-10 minutes before rounding a mark (setting a delayed command for 5-10 minutes before the mark also works). It'll make sure the server jumps for your boat are short when you reach the mark. For the rest of this post, let's assume server jumps of 11 seconds: your boat is moved by the server every 11 seconds. I'm also assuming you have a fast internet connection. The client polls the server every 15 seconds (roughly). Let's see what can happen with an example: 12:00:00 (jump) server moves your boat 12:00:00 (poll) client polls boat position, you see your boat at its current position (barely any delay!) 12:00:11 (jump) 12:00:15 (poll) your boat moves from its 12:00:00 position to its 12:00:11 position (running 4 second behind) 12:00:22 (jump) 12:00:30 (poll) your boat moves from its 12:00:11 position (19 seconds behind) to its 12:00:22 position (8 seconds behind). 12:00:33 (jump) 12:00:44 (jump) 12:00:45 (poll) your boat moves from its 12:00:22 position (23 seconds behind) to its 12:00:44 position (1 second behind). Note: the 12:00:33 position is not shown, it looks like you made one large jump. A better understanding of how this works may not easily transfer into being able to steer your boat better. One useful tip is: when you see your boat make a large jump, you know two server jumps happened in the last 15 seconds, meaning the last jump happened less then 4 seconds ago. If you see a short jump, you know only 1 server jump happened in the last 15 seconds, meaning the last jump happened between 4 and 11 seconds ago. Commands are executed independently from serverjumps. What does this mean? You might have seen your command execute at the start of a new server jump, or at the end. Both can happen. A command will never execute in the middle of a serverjump. All commands due to be executed (of every boat, in every race) are executed in one go, with 4 or 5 seconds between each go. So your command will generally be executed within 5 seconds after the time you set the command for. BUT your boat may still be at a position from 11 seconds ago. This means, your command will have an effect 11 seconds earlier than it was set to execute. So now there are three things with an interval: the client polls ever 15 seconds, the server moves boats every 11 seconds and turns boats every 4 or 5 seconds. This is complicated, I can't tell you yet how to take advantage of this knowledge. Up to now I've done one of two things for markroundings: - wait until the client shows me clear to round, then send the command. - when I expect a double jump to happen until the next client refresh, and I only need one more jump, I count, to 10. But 11 is probably safer. Now I've researched how commands work, I might come up with a method that results in better roundings, without the risk of missing the mark. That will be something I'll post on solfans
Posted by JimKnopf Posts 24 Registered at 2010-06-10 23:14:48	2016-10-26 21:18:39 - Re: When is my command executed?
	One advantage I take of your very informative explanation is: Don’t tack (gybe) too short for rounding a waypoint/buoy. To set a tack command in advance may have the effect to round too early. Seems to be better to wait for the visible pass by of the waypoint – then tack or gybe or set new course. (Apologies for bad english).
Posted by Kipper1258 Posts 185 Registered at 2015-06-18 22:08:49	2016-10-26 22:36:58 - Re: When is my command executed?
	This is why roundings are missed even though DC Checker shows the mark as clear. DC Checker assumes that the DC is going to fire exactly at that time with no uncertainty. That is not the case in reality.

Please login to post a reply.

Races

Next Race: 00d 00h 00m

Current Races:

Southampton to Punta del Este 2024

Sailonline is delighted to offer our sailors a 'reversed' Atlantic ocean race. As the RTW championship Atlantic part takes a detour to the Bahamas, we will offer you a reversed course as we will not do the 'usual' leg this year either. It is the July edition of this year's Ocean Championship. Our boat is the OD_65v3.
PRIZE: SMPF
Race# 1820
INFO from brainaid.de
OD65 PARTICULARS
WX updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ3 - OCCH - SUPSOL - SYC
Race starts: Jul 01st 11:00 Registration Open!

▶ Flash

GO TO RACE

Tall Ships Races 2024 - Klaipeda to Helsinki

Welcome to the first of three virtual Tall Ships Races on the Baltic Sea which are being organized in-real-life by Sail Training InternationalThis first race is from Klaipeda, Lithuania to Helsinki, Finland; circa 240nm in Sailonline’s stately fanciful Full Rigger.
NOTE: Starts and Finishes in tall ships racing are always offshore to avoid conflict with shipping and shipping lanes.
Race #1811
INFO by brainaid.de
Full Rigger PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: TS - SYC
RACE CLOSE: Saturday,
July 6 at 2300 UTC.
Race starts: Jun 27th 14:00 Registration Open!

▶ Flash

GO TO RACE

Haida Gwaii 2024

We will end the second quarter of the ARCH competition with a 390nm race around the Haida Gwaii islands (literally "Islands of the Haida people"), also known as the Queen Charlotte Islands. This is an archipelago located on the northern Pacific coast of Canada. In SOL, we last raced on this route in 2012 and few people remember what happened there. Prepare your Riptide 50 well, it's going to be a lot of fun.
Race #1819
INFO from brainaid.de
Riptide 50 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
ARQ2 - ARCH - SUPSOL - SYC
RACE CLOSE: Wednesday,
July 3 at 2300 UTC.
Race starts: Jun 24th 17:00 Registration Closed

▶ Flash

GO TO RACE

Newport Bermuda Race 2024

The 636-mile biennial Newport Bermuda Race is one of the oldest regularly scheduled ocean races, and with the Fastnet Race and the Sydney to Hobart Race, it is one of the three great classic races of the yachting world. Founded in 1906, this 53rd running of the Bermuda Race can again also be participated in online.
Entries are invited for one of the four divisions:
Double-Handed Division:
Jeanneau Sun Fast 3600
St. David's Lighthouse Division:
Santa Cruz 52
Gibbs Hill Lighthouse Division:
Judel Vrolijk 62
Finisterre Division:
Riptide 50
Details for each yacht are available in the ‘Particulars’ links below. As in real life, you can only sail one boat in one division, so choose your virtual yacht carefully, and because of the unusual (for SOL) 4-division nature of the event, please note results will not count towards any Sailonline rankings.
Race #1808
INFOby brainaid.de
Sun Fast 3600 PARTICULARS
Santa Cruz 52 PARTICULARS
Judel Vrolijk 62 PARTICULARS
Riptide 50 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: None
RACE CLOSE: Friday,
July 5 at 2300 UTC.
Race starts: Jun 21st 17:05 Registration Closed

▶ Flash

GO TO RACE

Auckland to San Francisco 2024

Welcome back to Auckland as we continue our Round The World voyage. This 5600 nautical miles race from Auckland to San Francisco, first sailed in 2023, is the third leg of the RTW, proposed by SOLer ita10267. It is also the June edition of this year's Ocean Championship. Our boat is the Swan 65, as in all RTW races this year.
PRIZE: SMPF
Race# 1790
INFO from brainaid.de
Swan 65 PARTICULARS
WX updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ2 - OCCH - RTW - SUPSOL - SYC
RACE CLOSE: Tuesday,
July 9 at 2300 UTC.
Race starts: Jun 03rd 11:00 Registration Closed

▶ Flash

GO TO RACE

Go to race archive

SYC Ranking

View full list

Series

Mobile Client

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

The mobile client