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 » Performance loss

Page: First Previous 3 4 5 6 7 8 9 Next Last

I've run some more tests, and sometimes the models predict a value that is so close to the actual one that it's scary, I've seen a difference of 0.000000004 (I might have missed a zero).

Looking at my results, I think we have (almost) unravelled the performance recovery model:
new_perf = min(100, old_perf + delta_time*3/(20*abs(boatspeed)))
> new_perf and old_perf in %
> boatspeed is actual boatspeed (not boatspeed when perf would be 100%) from previous "server jump" in knots
> delta_time: time since previous "server jump", in seconds
> abs(x) makes x positive
> min(x, y) returns the smallest value of x and y.
This formula basically translates to
"Your performance will increase with 9/boatspeed% per minute, until you reach 100%"

The performance loss model that matches the actual values the best, is really close, but no perfect match:
if(tack or gybe and old_perf >= 93)
new_perf = old_perf * (1 - abs(boatspeed)/200)
else if(normal course change and old_perf >= 93)
new_perf = old_perf * (1 - dTWA/25)
end if
> new_perf and old_perf in %
> boatspeed in knots
> dTWA is the positive difference between TWA before and after the course change, in radians (1 radian = 180/pi degrees)

I think the last thing to unravel is what boatspeed to use in the calculation for performance loss while taking/gybing.
> new boatspeed if perf would be 100%
> old boatspeed if perf would be 100%
> new boatspeed if perf would be the the same as before the tack
> old actual boatspeed (with performance the same as before the tack)

And there's another thing to do with performance loss that I we haven't tried yet: bbq'ing, I'm not sure why we would want to know the exact performance loss after a bbq, but why not?

Attached:

> Image with actual values, and values as predicted by 4 different models:
- model 1: use current boatspeed for tack/gybe-perf.loss-calculation
- model 2: use max boatspeed (when perf would be 100%) for tack/gybe-perf.loss-calculation
- model 3: like model 1, but performance loss is directly subtracted from performance (instead of multiplying with the (1 - loss) thing.
- model 4: like model 2, but same substraction method as in model 3

model 1 fits best.

> Raw data, csv file, can be opened with excel
Attachments
Kroppyer wrote:

>>>>>
The performance loss model that matches the actual values the best, is really close, but no perfect match:
if(tack or gybe and old_perf >= 93)
new_perf = old_perf * (1 - abs(boatspeed)/200)
else if(normal course change and old_perf >= 93)
new_perf = old_perf * (1 - dTWA/25)
end if

>>>>>

So, just to complete the logic [and make sure that I am following you] ...
If the code falls through the IFs above, we are left with:

new_perf = min(100, old_perf + delta_time*3/(20*abs(boatspeed)))

And that implements the 93% rule?

Can you determine from the data whether the "recovery" code executes before, after, or instead of the "course change" code?

Thank you for your work on this.

Looks like it is about time for the SOL developers to change the performance loss parameters! hehehe
Why? It wasn't supposed to be a secret, was it? However, it does seem somewhat complicated, unless it was derived from actual data gathered from IRL boats. I would question, however the perf loss from a gybe,, which seems too great, UNLESS it involves dropping and re-hoisting a spinnacker. And a mere change of course should not involve a perf loss of any great amount. The rudder is still a good brake, however!
I am going to attempt to reduce the math to two ready-reference graphs, one showing perf loss at any angle and wind-speed, the other showing expected recovery and time to add to any DC to compensate for the loss in distance travelled.
If it breaks, it's not strong enough--if it doesn't, it's too heavy.
Why Rod ? Why Indeed !

The Rationale for this hindrance has been expounded on in the previously linked thread.

Wrong Speed VMG

Posted by
Jakob Kuttenkeuler
2009-02-12

"We introduced this performance loss not to punish normal sailing maneouvers but to prevent boats to tack e.g. once every minute during hours just to ride on a tws that optimizes vmg. The performance loss implementation succeeded in preventing that behavior and is as stated above not a problem for normal maneouvers."

But please don't let me stop anyone from actually going to the source material and reading it for themselves as there are even more useful tidbits to be gleaned should one choose to do so.

There is merit in spending an equal amount of time reading these Forums as is devoted to contributing in them.

None so blind
A2R: Thanks for the link to that thread.

To think that the PERF formulas have been sitting on the forum since 2009!
Ya think we need a search function for this puppy?

Or, as you suggested, ya think we need to RTFF?

(Note: Those who know me as an avid fan of MAD Magazine will recognize that the first 'F' in the acronym above stands for 'Furshlugginer'.)
NSA recommends using Google for this purpose

site:http://www.sailonline.org/board/ "performance loss"

yeilded only only 9 hits when I went looking for it. Today there are 11. Took about all of 20 minutes to find the good stuff. Time well spent considering.
None so blind
Performance Recovery
new_perf = min(100, old_perf + delta_time*3/(20*abs(boatspeed)))
> new_perf and old_perf in %
> boatspeed is actual boatspeed (not boatspeed when performance would be 100%) from previous performance calculation. Speed in knots
> delta_time: time since previous performance calculation, in seconds
> abs(x) makes x positive
> min(x, y) returns the smallest value of x and y.
This formula basically translates to
"Your performance will increase with 9/boatspeed% per minute, until you reach 100%"

Performance loss
if(tack or gybe and old_perf >= 93)
new_perf = old_perf * (1 - abs(boatspeed)/200)
else if(normal course change and old_perf >= 93)
new_perf = old_perf * (1 - dTWA/25)
end if
> new_perf and old_perf in %
> boatspeed is the boat speed after the tack, calculated using the old performance. Speed in knots
> dTWA is the positive difference between TWA before and after the course change, in radians (1 radian = 180/pi degrees)

I believe performance loss only kick in when a command is executed, or when the boat tacks or gybes (when you are sailing cc trough a windshift, your performance drops when you gybe/tack)

I think performance recovery is also active in the "server jump" that performance loss is calculated. But the command to change course can be at the start of the server jump, or at the end, or somewhere in between. I'm not sure what boatspeeds are used how in the recovery formula in the same jump performance loss is calculated.

I think we have reach the limit now, the server jumps limit us from being more accurate, and I think it's not really of any use to be able to predict performance more accurate.

I will, when I caught up with other things I should've done, implement this performance model in my program spinnacer, so that calculations with performance will be easier to do.

---

It might be interesting to think of tricks with this model. hmm did his trick with the gybe, but I'm sure there's more:
- a 100.3 degree course change will cause 7% performance loss. So when you need to do a sharper turn (without gybing/tacking) you can turn 105 degrees first (perf<93%), and directly after that the rest of the turn (perf does not drop anymore than those 93%)
- Performance loss is smaller when your performance is not yet at 100%, but you're faster when you wait for your performance to reach 100% (sailing two times 5 minutes with average performance 98.5% is faster than sailing 10 minutes with an average performance of 97.2%). But what if your perf is lower than 93%, it's of course better to do it at that moment, as it won't do anything with your performance. And then there's an area in between, where part of the perf. loss could be "absorbed" by the 93% rule.
- Tacking, and then turning to the right course is extra performance loss, if you tack to the right course in one go, it faster, unless boat speeds differ much.. It's getting complicated..
- It in light winds, it might be better to do two tacks/gybes instead of one course change. Since tacking/gybing doesn't result in a big drop in performance when sailing slow, while a course change always has the same performance drop.
- etc.. etc..

I think we have unravelled the model and calculations, now comes the hard part: how to use it in our advantage :) Anyway, with this we can at least do better calculations for DCs/routing
NSA recommends using Google for this purpose

site:http://www.sailonline.org/board/ "performance loss"

yeilded only only 9 hits when I went looking for it. Today there are 11. Took about all of 20 minutes to find the good stuff. Time well spent considering.
Tried that as a search engine in Google and got '404'. What am I doing wrong?

--- Last Edited by Go4iT at 2013-10-15 23:16:35 ---
Go to Google;

In the Search bar

site:

followed without any space
by the url of this board

then your search terms after that

You can also go to the link at the bottom of the Google search page and click the link that says "Advanced Search"

There are boxes there to do the same thing, so when you hit search look at how Google has arranged the same business in the Search bar for you.



--- Last Edited by A2R at 2013-10-16 00:12:13 ---
None so blind
Attachments

Page: First Previous 3 4 5 6 7 8 9 Next Last

Please login to post a reply.

Races

Next Race: 00d 00h 00m


Current Races:

Cross the Convergence 2026 - Guam to Ouvéa


The third race of our series of ocean voyages across the World’s convergence zones takes us southeastward now down the Pacific, from Guam’s Apra Harbour at 13.5 degrees North, back across the Equator to the glorious New Caledonian resort island of Ouvéa, on the edge of the Tropic of Capricorn at 20.5 degrees North. It’s 2400nm, and there’s more than a few other islands in the way, so mind where you go in your Ocean 50s. Race #1981
INFOby brainaid.de
Ocean 50PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: CCZ - SYC
Race starts: Mar 20th 18:00 Registration will open soon
▶ Flash
GO TO RACE

Lake Victoria TIMED Race 2026

This month’s TIMED race takes us inland to Lake Victoria in the heart of Africa. Starting at Rosebery Channel in Uganda sail the AC72v2 on a 196nm course around Bugala Island on the way to the finish line in Tanzania’s Speke Gulf. This is a TIMEDrace so you may RE-REGISTER HEREto 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 #2018
INFOby brainaid.de
AC72v2 Particulars
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
TRQ1 - TRCH - SYC
RACE CLOSE: Saturday,
28 March at 23:00 UTC
Race starts: Mar 15th 12:00 Registration Open!
▶ Flash
GO TO RACE

SSANZ Round North Island Race 2026 - Leg 4

The final challenge awaits in Leg Four of the Round North Island Series! From Napier, the fleet sets off on a 354 nautical mile run back to Auckland, completing the full circumnavigation where the journey began. Fatigue may be setting in, but this last leg could decide the overall standings. Sailing the fast and responsive Sun Fast 3600, our skippers will need sharp tactics and steady focus to finish the series strong and claim victory!

The start time for this race may change at short notice to align with the real race. The confirmed start date and time will be announced via an in-race “L” flag message — Please monitor race communications closely.
Race #2014
INFO by brainaid.de
Sun Fast 3600 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: RNI - SUPBUD - SYC
RACE CLOSE: Friday,
March 20 at 2300 UTC.
Race starts: Mar 12th 22:00 Registration Closed
▶ Flash
GO TO RACE

SSANZ Round North Island Race 2026 - Leg 3

Leg Three of our Round North Island Series, in partnership with SSANZ, keeps the pressure on! From Cook Strait, the fleet turns north for a 187 nautical mile passage up the east coast to Napier. It may look like a quick overnighter, but shifting coastal winds and the ever-lively Cook Strait demand sharp focus. In our responsive Sun Fast 3600s, a proven short-handed racer and powerful downwind performer, tactical decisions and precise timing will make all the difference!

The start time for this race may change at short notice to align with the real race. The confirmed start date and time will be announced via an in-race “L” flag message — Please monitor race communications closely.
Race #2013
INFO by brainaid.de
Sun Fast 3600 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: RNI - SUPBUD - SYC
RACE CLOSE: Wednesday,
March 18 at 2300 UTC.
Race starts: Mar 08th 22:00 Registration Closed
▶ Flash
GO TO RACE

Iceland to the Falklands 2026

Welcome to an all-new route, the first of three Round the 'Old World' of Europe, Africa, Australia and Asia. To give each leg of the ROW a bit of length we'll try to hug the coasts as little as possible, so starting in Iceland our first leg of the series, which will also be the final leg of our Quarter 1 Ocean Championships takes us 7200nm to the Falklands, the full length of the Atlantic end to end. To make sure we'll get it done within the month we'll be sailing our Maxi Trimaran.
Race #2010
INFO by brainaid.de
Maxi Trimaran PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ1 - ROW - OCCH - SYC
RACE CLOSE: Tuesday,
March 24 at 2300 UTC.
Race starts: Mar 02nd 11:00 Registration Closed
▶ Flash
GO TO RACE

Go to race archive

SYC Ranking

  1. Sailonline Yacht Club Member KaSToR
  2. Sailonline Yacht Club Member WRmirekd
  3. Sailonline Yacht Club Member rafa
  4. Sailonline Yacht Club Member rumskib
  5. Sailonline Yacht Club Member Sax747
  6. Sailonline Yacht Club Member CriticalHippo
  7. Sailonline Yacht Club Member vida
  8. Sailonline Yacht Club Member CollegeFund
  9. Sailonline Yacht Club Member Panpyc
  10. Sailonline Yacht Club Member sassy63

View full list

Series

Mobile Client

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

The mobile client