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 » Technical Discussion » When is my command executed?

Posted by
kroppyer


Users avatar

Posts
347
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


Users avatar

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


Users avatar

Posts
235
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.
Posted by
ForbanduCollet44


Users avatar

Posts
1
Registered at
2024-10-18 23:02:24
2025-03-12 22:33:41 - Re: When is my command executed?
Hi kroppyer

Thanks a lot for your explanation.

This post is quite ancient so, is it still true or had the situation changed ?

At the end, you speak about another post on solfans, I didn't find it.

Thanks
Posted by
kroppyer


Users avatar

Posts
347
Registered at
2010-02-05 15:25:55
2025-03-13 14:32:40 - Re: When is my command executed?
The server-side hasn't changed much in this regard as far as I know. But there's a whole new client by now, so that part of the story may have changed.

I have never written that post on solfans. I think partially because I didn't find easy and reliable ways to get a significant advantage from the knowledge.

By now, I think there is software that tries to sync up with the server jumps. I believe Kipper's AGL does this, and possibly even the HTML5 client. Which makes it easier, and more intuitive to work with the server jumps.

From what I recall, I had some thoughts that could help you navigate around a mark with the server jumps. If you are in sync with the server jumps, you basically have 10 seconds to decide when and how much you want to steer, and it should be fairly obvious when to turn and by how much. What matters a lot here is that you need to get luck with where you end up after each jump. For example: If you jump just short of the mark, you'll have to continue sailing in the same direction for another 11 second, even though you needed only 2 more seconds to reach the mark. Depending on the situation, you can reduce the effect of this by aiming a bit wider, so that when you're less than 10 second from the mark, you can already start part of your turn. Of course, beware of wind direction and performance loss. And finally, I recall that maybe I wanted to figure out and describe a somewhat reliable way to determine where you'd end up multiple jumps ahead so that you know whether you need to steer wider or not.

Please login to post a reply.

Races

Next Race: 00d 00h 00m

Current Races:

Bahamas and Back TIMED Race 2025

Welcome to sunny South Florida for this race that has us crossing the Gulf Stream twice. We depart from Palm Beach for a short run over to Freeport, Bahamas then it’s on to Miami before heading to the finish line back in Palm Beach. This is a TIMED race, so you may RE-REGISTER HERE to try again, after finishing a run. You will have 13 days and 11 hours to test your skill and decision making after the race opens.
Race #1911
INFO by brainaid.de
Santa Cruz 70 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
TRQ2 - TRCH - SUPSOL - SYC
RACE CLOSE: Saturday,
26 April at 23:00 UTC
Race starts: Apr 13th 12:00 Registration will open soon
▶ Flash
GO TO RACE

Sinbad by Balloon 2025 - Toamasina to Baia de l'Oiseau


You may recall that when last we visited Madagascar in the company of Sinbad, the Sultan commanded our intrepid inspirator to seek out fabled islands where in Summer the sun barely set. We did and we returned but the Sultan wasn’t happy with Sinbad’s report, so here we go again, now by SOL Balloon instead of sailing vessel. Expect to be in the air for at least 2100nm and depending on how the wind brings us, anything between two weeks and two months before we shall descend at the Sultan’s given coordinates!
Race #1884
INFOby brainaid.de
SOL Balloon PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC - SBB
Race starts: Apr 09th 11:00 Registration Open!
▶ Flash
GO TO RACE

Valparaiso to San Francisco 2025

Get ready for an exhilarating new challenge as we set sail on the fourth leg of the 2025 Ocean Championship Series! Following in the 19th century footsteps of Isabel Allende's heroine, Eliza Sommers, 'Daughter of Fortune', this all-new route takes us across the vast eastern Pacific, from Valparaíso, Chile, to San Francisco, California - a 3500nm journey of endurance, strategy, and pure sailing adrenaline. This leg will be raced aboard the powerful Rapido 60, pushing sailors to their limits as they navigate the open ocean. Do you have what it takes to conquer the Pacific? Join us and put your skills to the ultimate test!
PRIZE: SMPF
Race #1900
INFO by brainaid.de
Rapido 60 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ2 - OCCH - SUPSOL - SYC
Race starts: Apr 07th 11:00 Registration Open!
▶ Flash
GO TO RACE

Red Eye - Round White Island 2025

We remain in New Zealand for our second “Red Eye Special” and another IRL Kiwi classic - the Round White Island! IRL still “currently on hiatus” following the island’s eruption of 2019, this race was last raced on SOL in 2020. It’s about 300nm there - out the Hauraki Gulf and south down to the island in the Bay of Plenty - and back to Auckland. This year we’ll be racing in our ever-popular take on the TP-52. Hau tika!
Race #1844
INFOby brainaid.de
TP-52 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC - RED
RACE CLOSE: Sunday,
April 13 at 2300 UTC.
Race starts: Apr 06th 12:00 Registration Closed
▶ Flash
GO TO RACE

Melbourne Osaka Cup Double-Handed Yacht Race 2025

Welcome once again to what these days is Sailonline’s almost annual virtual Melbourne to Osaka Yacht Race. In real life, this double-handed 5500 nm race between these two sister cities, one deep in the southern hemisphere, the other high in the northern hemisphere, is run every four to five years, and this year is such a year. So, this year’s online version is in sync with the Melbourne Osaka Cup 2025 organised by the Ocean Racing Club of Victoria (ORCV), and the Sandringham (SYC) and Osaka Hokko (OHYC) yacht clubs. We’ll be racing the well-known First 40, a popular size of boat which should be a good match for many of the boats entered in the real race. With the doldrums unavoidably lying across our course, you can expect to be at virtual sea for at least a month!
Race #1669
INFO by brainaid.de
First 40 Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: SYC
Race starts: Mar 16th 06:00 Registration Closed

▶ Flash
GO TO RACE

Go to race archive

SYC Ranking

  1. Sailonline Yacht Club Member WRmirekd
  2. Sailonline Yacht Club Member Patrick70119
  3. Sailonline Yacht Club Member CriticalHippo
  4. Sailonline Yacht Club Member KaSToR
  5. Sailonline Yacht Club Member vida
  6. Sailonline Yacht Club Member FreyjaUSA
  7. Sailonline Yacht Club Member rafa
  8. Sailonline Yacht Club Member Kipper1258
  9. Sailonline Yacht Club Member bonknhoot
  10. Sailonline Yacht Club Member rumskib

View full list

Series

Mobile Client

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

The mobile client