E-glide FES mini competition

[Vertigo]

And actually; if anyone cares to fly with a regular DuoDiscus, that might be interesting to see.

[Bre901]

Ok, lets give it a try. Ill set max WL to 42Kg and will apply the DAeC index to the speeds.
There are a few side effects, like I wont be able to restrict planes in the NOTAM, but Ill just kick anyone from the server who picks an EB29

No need to kick the EB29s, there won't be any (min W/L = 48kg/m2)

[Vertigo]

Actually, Ill not kick anyone, anyone wants to fly, why the heck not, sky is big enough, just dont expect me to score you when you pick a Stemme.

[Vertigo]

First task:



In the two smaller airspace zones you need to stay below 1676m. In the bigger one to the north, below 2896m.
We will use GP scoring for this, any penalty point you get will be converted in to 5s.

I havent tried yet how LX handles the use of the FES; but if you use the condor PDA, it will no longer navigate/calculate correctly to the next TP after using it. I suggest using xcsoar (or maybe the LX) to help you with final glide calculations.

Does anyone know what the optimal strategy even is for using FES? I would assume its best to use it while flying minimum sink speed, Im much less sure if full power vs partial power makes a difference in efficiency?

[timbaeyens]

First task:



Does anyone know what the optimal strategy even is for using FES? I would assume its best to use it while flying minimum sink speed, Im much less sure if full power vs partial power makes a difference in efficiency?

http://glidingnews.com/e-glide-concept-contest-pavullo

[JLN]

Hello,

After trying the minilak I can't find the flaps indications on the speed indicator.
So would it be possible to have the max mini speeds for each setting of the flaps

Thanks in advance

[Vertigo]

From cotasa (https://condorutill.fr/) :
MiniLAKFES=230,80,325,350,40,L,85,+2,95,+1,120,0,150,-1

So
above 150KmH, flaps -1
above 120 KmH, flaps 0
Thermaling +1 or +2

Not 100% if those numbers are for empty or max ballast, but thats not a big difference in the lak.

If you install cotasa, you will get a visual indication of the current/correct flap setting.

[JLN]

Thanks a lot !

[wickid]

The MiniLAK is Uros' personal plane. So we have the cockpit the same as his personal glider. He has the flap indications on the LX9070, so we didn't add a flapring.

The exact speeds are:

L: 82 - 87 kph
+2: 87 - 96 kph
+1: 96 - 116 kph
0: 116 - 145 kph
-1: 145 - 230 kph

[JLN]

The MiniLAK is Uros' personal plane. So we have the cockpit the same as his personal glider. He has the flap indications on the LX9070, so we didn't add a flapring.

Happy man !!

But could you please add the flapring for the Condor pda flyers !

[Vertigo]

First race is behind us. I probably cant score until tomorrow, as I cant access the FTRs until the upload window closes. Results will be available here:
(spoiler alert: WRW won)

First a question to LX users; were you able to use the LX for final glide computation ?

Then some other things I noticed/learned:

I set airspace violation penalty to "outlanding". While that is my preferred setting, if you already used the FES, you already "outlanded" so you dont get extra penalties. The server/chat log still recorded this I think, so its probably possible to figure out who should be penalized/scored zero (GP scoring gives you zero points for outlanding), but if we ever do a real competition, its probably better to set the penalty to the maximum 200 points. Cloud flying penalties are still applied even after "outlanding" so I presume airspace infractions are too. Ill double check this later.

Condor PDA navigates to the next TP, but because after using the FES, condor doesnt record turning a TP (because you "landed out") so it will work until after the first TP after using the FES, as the PDA never registers you turned that TP, so it will keep trying to navigate/calculate to the TP that you will never turn. That makes straight line tasks a possible workaround, at least until condor better supports this format.

Im considering letting people just enter their own results in a google spreadsheet/google form. That would reduce my workload to near zero, meaning I dont really care how many ppl participate. Instead of manually entering everything I would just spot check some results, everyone else can check or report suspect /incorrect results and I can sling a ban hammer if anyone abuses the system.

Lastly; some things never change. Do something completely different and WRW will still beat everyone by a wide margin lol.

[Vertigo]

188 and ZAQ entered airspace. Because of my NOTAM which penalized this with outlanding, this goes undetected by condor (we all landed out when using our FES, well all except KH who did not use his FES ). Interestingly, DShelper did not log those events either, but I remembered seeing it, and my videocapture did not miss it:



I just manually gave those pilots 200 penalty points, as will be the penalty going forward.

I did the rest of the scoring, but it is approximate; when using CC flight analysis, its really easy to score this, but I only noticed later the time I was using is relative to crossing the start line, not opening of the line:

I should have used the absolute time for regatta start, then it would have been correct relative to opening of the line, but since it wont really change anything here, and this is just training, Im leaving it as is.

Anyway, here are the not entirely correct results, congrats again to WRW and AM in particular:


spreadsheet:
https://docs.google.com/spreadsheets/d/ ... ingle=true

Next time I will provide everyone with a Google Form to fill out their own time, and we will see how that goes.

[sillewap121]

Hello Vertigo,
yes LX works normally it does not stop navigation.

As for scoring maybe a good solution is for pilots to enter the time they crossed the finish line (it say all) not the time of the task because as you noticed the time CC show is relative to crossing the start line, not opening of the line. Of course, we can add the start time manually and an additional column with the task time, which will be recalculated automatically.
Thanks to Vertigo for organizing, see you on the next flight with charged batteries

[Vertigo]

Training Day 2 may push the limits somewhat, make sure your batteries are fully charged! Im posting this early to give everyone time to familiarize themselves with the airspace situation, you will need to wait for the actual briefing for the correct meteo, but there is likely a sea breeze near the coast and some better conditions further inland.



Lucca-Tassignano (LIQL) airport is closed, we have permission to fly over it as long as you stay between 610m and 914m; be sure to have enough juice left in your battery! Alternatively if you feel lucky or you are low on battery power, you can also opt to stay below 305m and hope for the best.

We failed to receive permission to enter the Bologna CTR Z5, so on the second leg you will also need to stay low for a bit, below 1372m which is barely above some of the higher ridges. The weather forecast there does look a bit better than the rest of the task.

Make note of your finish time And also your penalty points. Or just hit S to make a screenshot with the realtime scoring open. I will provide you with a google form tomorrow that you can use to enter your own result. Assuming you do finish, you can immediately fill out the form with your manually recorded/guestimated finish time so we can have almost instant preliminary results. The next day you can check on condor club, analyse your flight and get the correct finish time, and then update your result using the same form. I know it doesnt matter, its a training day on an unranked test competition, but if you can, please try it, lets see if/how it works.

[timbaeyens]

First task was erroneously loaded, some problem which Vertigo is trying to fix asap.