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

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

Posted by kroppyer Posts 346 Registered at 2010-02-05 15:25:55	2013-10-15 12:48:46 - Re: Performance loss
	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_time3/(20abs(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 perflog_1.csv (36.7 KB) perf-model-4_1.png (82.1 KB)
Posted by javakeda Posts 73 Registered at 2013-03-01 03:18:22	2013-10-15 14:08:25 - Re: Performance loss
	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_time3/(20abs(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.
Posted by Go4iT Posts 124 Registered at 2011-03-14 23:58:15	2013-10-15 15:03:51 - Re: Performance loss
	Looks like it is about time for the SOL developers to change the performance loss parameters! hehehe
Posted by Rod Posts 392 Registered at 2010-06-24 22:30:48	2013-10-15 16:44:33 - Re: Performance loss
	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.
Posted by A2 Posts 347 Registered at 2009-10-26 00:39:42	2013-10-15 17:16:24 - Re: Performance loss
	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
Posted by javakeda Posts 73 Registered at 2013-03-01 03:18:22	2013-10-15 19:52:44 - Re: Performance loss
	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'.)
Posted by A2 Posts 347 Registered at 2009-10-26 00:39:42	2013-10-15 20:18:38 - Re: Performance loss
	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
Posted by kroppyer Posts 346 Registered at 2010-02-05 15:25:55	2013-10-15 20:28:49 - Re: Performance loss
	Performance Recovery new_perf = min(100, old_perf + delta_time3/(20abs(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
Posted by Go4iT Posts 124 Registered at 2011-03-14 23:58:15	2013-10-15 23:15:49 - Re: Performance loss
	A2R said @ 2013-10-15 20:18:38: 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 ---
Posted by A2 Posts 347 Registered at 2009-10-26 00:39:42	2013-10-15 23:29:08 - Re: Performance loss
	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 Site_Search.jpg (694.1 KB)

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:

Kapiti Chetwodes Race 2024

For only the second time in SOL history, we have the pleasure of inviting you to the Kapiti Chetwodes Race, held in the Cook Strait region. Organised IRL by the Royal Port Nicholson Yacht Club from Wellington in New Zealand. The approximately 160nm long route, full of turning points, will take us from the bay at RPNYC around the islands of Somes, Kapiti and Chetwodes and back to the finish line at RPNYC. We have only a 26 ft Albin 79 yacht at our disposal. All this means that we will have a lot of fun, so fair winds!
Race #1864
INFO by brainaid.de
Albin 79 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
ARQ4 - ARCH - SUPSOL - SYC
Race starts: Nov 25th 17:00 Registration Open!

▶ Flash

GO TO RACE

Raja Muda Selangor 2024 - Penang to Langkawi

Welcome to the third and last online race of the Raja Muda Selangor International offshore series – a 70nm final trip further north again up the Malacca Strait from Penang to the exotic island of Langkawi, and again in Ker 40s.
Race #1871
INFO by brainaid.de
Ker 40 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: RMS - SYC
RACE CLOSE: Monday,
November 25 at 2300 UTC.
Race starts: Nov 21st 04:00 Registration Open!

▶ Flash

GO TO RACE

Raja Muda Selangor 2024 - Pangkor to Penang

Welcome to our second online offshore race in cooperation with Raja Muda Selangor International – an 80nm trip from Pangkor north to Penang up the Malacca Strait, again in Ker 40s.
Race #1870
INFO by brainaid.de
Ker 40 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking: RMS - SYC
RACE CLOSE: Saturday,
November 23 at 2300 UTC.
Race starts: Nov 18th 04:00 Registration Open!

▶ Flash

GO TO RACE

Two Oceans Doublecross TIMED Race 2024

Our November Timed race takes us to Cape Town near where the Atlantic and Indian oceans meet. Our ride is a beautiful ketch, the Archer 78. Starting at Cape Town, we’ll round Robben Island, then head south to round Cape Point, up around Seal Island before heading north to round Dassen Island before returning to Cape Town. 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 #1872
INFO by brainaid.de
Archer 78 PARTICULARS
WX Updates:
0430 / 1030 / 1630 / 2230
Ranking:
TRQ4 - TRCH - SUPSOL - SYC
RACE CLOSE: Saturday,
30 November at 23:00 UTC
Race starts: Nov 17th 12:00 Registration Open!

▶ Flash

GO TO RACE

Nassau to Bodo 2024

Prepare for the grand finale - the 6th and concluding leg of the RTW challenge, an odyssey from Nassau in the Caribbean to Bodø in Norway. Embracing a journey of 4000 nautical miles, this leg promises an exhilarating 18-day voyage. It also heralds the November installment of our prestigious Ocean Race Championship. Embark on a voyage of a lifetime, where prowess, tactics, and camaraderie unite in the pursuit of triumph. We eagerly await your presence at the starting line! May the winds be ever in your favor.
PRIZE: SMPF
Race# 1866
INFO from brainaid.de
Swan 65 PARTICULARS
WX updates:
0430 / 1030 / 1630 / 2230
Ranking: OCQ4 - OCCH - RTW - SUPSOL - SYC
Race starts: Nov 11th 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