Am 05.01.2011 um 13:57 schrieb Hannu Niemi: > Sorry, can't help, but 100% bugged glider looks (by definition) a (big) > bug ;)
Yepp, but XCSoar only allows you to set a 50% to 100%, so, in real life it appears 100% means clean and 50% is what? - 50% of LE surface covered with bugs or - 50% performance reduction due to bugs? I know it's the latter, as per the manual. Still, that's hard to estimate. I wonder how you guys do that? Do you check your sink rate at a given speed? I usually don't deal with it at all, I just add an estimate to the arrival safety height ... Just thinking loud here: Could an overall performance degradation be automatically estimated from the average flight data over a given time interval? Could this be used as a proposal for bug setting? Or could we maybe set an estimated bugging rate for the day for XCS to include in the calculations and only hit a "Bugwiper" button when we have wiped them off? Flying low would increase the bug build up rate, while flying high would add less, of course. Viele Grüße, Martin ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Xcsoar-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcsoar-user
