Contents - Index

Handicap Task Calculator FAQs

Q. How can I check that the tasks don't conflict with airspace?

A. Open the Bestpoints.igc file, that the program saves in the tasks folder when it calculates the task, in SeeYou or another igc viewer. This will show the task with variable barrels set to the size calculated for the lowest handicap and the shortest path around the task that can be flown. In map view it is then easy to see whether the task tracks conflict with airspace etc.

Q. What do I do if the calculator needs to set barrel sizes larger that the Maximum Barrel Radius for low handicap gliders?

A. The length of your task is incompatible with the range of handicaps and maximum barrel radius that you have selected.
You can either:
1) Reduce the task length, or
2) Increase the Maximum Barrel Radius setting, or
3) Add one or more variable barrel turn points to the task.

Tip: If you allow the calculator to 'continue' when it alerts you to this problem then the report will show you how large the maximum barrel radius needs to be to accommodate the lowest handicap glider.

Q. How much difference in task lengths is there between the different calculation schemes?

A. Bisectors will be longer than Bestpoints. Only use Bisectors if your competition rules demand it or your computer is really slow. The difference between Bestpoints and Windicapped Bestpoints depends upon the wind speed and direction entered. If the windspeed is very low, there is not much difference. If there is any wind, using Bestpoints will give an advantage to the higher handicap gliders. You can see the differences on the status bar at the bottom of the task entry form after calculation, and you can load the various tasks into SeeYou to compare the tracks.

Q. Do low handicap gliders get an unfair advantage by being able to turn anywhere in a large barrel?

A. On the face of it, yes. However, they will only fly the shortest possible task by flying to the optimum point on the edge of the barrel. If they fly to a sub optimal point anywhere on the edge or within the barrel they will fly further than they need, and will take extra time to complete the task. The higher handicap gliders have less opportunity to get this wrong!

It can be argued that low handicap gliders have an advantage in that they can avoid bad air by turning at a sub-optimal point. On the other hand, high handicap gliders are much more able to fly through bad air without landing out. Handicap competition will never be completely fair but this format is pretty close. 
Q. How can I add additional data to the Task Report?

A. You can add notes to the Task Report by clicking the 'Add Notes' button when creating the task. Alternatively you can save the Task Report as a Microsoft Word file using the 'Save' icon on the report and add the data in your word processing program.

Q. Why do I need to register the program and enter a licence key?

A. The quality and accuracy of the Handicap Task Suite of programs is important to us so we are keen that you are always using the latest version. This way we can be sure that you are notified of changes and updates to the software.

Q. Why aren't the task notes saved with task?

A. Sorry, just didn't get that far. Will be dealt with in future versions. In the meantime, please cut and paste your notes into a text file to save them.

Q. I am using numeric turn point identifiers. Why don't they appear in the expected order in the turnpoint drop down list?

A. The drop down list is ordered alphabetically by default. This means that 31 will appear before 4. If you wish the turnpoints to be listed exactly in the order that they appear in your turn point file then add the line "TPSort:False" to the handicaptask.ini file using a text editor.

Q. How can I contact the author to give feedback on features and bugs?

A. Contact Jim White by email at jim at If you detect a bug please first try to replicate it then give me enough detail in your email for me to replicate it also. I will then try to fix the problem in the next release. If you have ideas that would improve future versions, I would be pleased to hear them too.