Recent changes to bugs

#3 Request to add support for variable-barrel task handicapping

2016-03-10T10:37:45.946000Z

A 'zoom-to-task' (Key T) is implemented in todays development version:
http://pc12-c714.uibk.ac.at/GPLIGC/download/develop/

Also, a user configurable border zoom_border in .gpligcrc

#3 Request to add support for variable-barrel task handicapping

2016-03-08T22:25:09.093000Z

In 1.10 there is support for a 'radius factor' which can individually set for each waypoint in the task editor. Using the 1km cylinders (or cylinders+FAI sectors) option, you can enter your variable barrel in km for each wp.

in your example the shortest logged distance to littleport is 4.37 km, at 12:36:47. Is that correct?

'zoom to task' is on the todo list (as well as save and load task)
In the mean time you may use the 'right mouse button zoom' and drag the zoom box out of the window. that way you may be able to zoom over the edge.

#2 Problem displaying turnpoint barrels

2016-03-08T19:35:30.319000Z

status: open --> closed

#2 Problem displaying turnpoint barrels

2016-03-08T19:34:50.688000Z

The GPLIGCfunction.pm file is read from a path which is set during the installation.
The default is /usr/local/lib/gpligc. The prefix (/usr/local) may be changed with the --prefix option to ./configure.

However, the user configuration file (~/.gpligcrc) provides a way to override the 'hard-coded' path. As this file is written with gpligc's option 'save configuration' it is quite possible that an old path (e.g. as likely in your case the old default path, which was /usr/local/share/gpligc) is still in .gpligcrc and overrides the new default path.

Solution:
rm ~/.gpligcrc
or edit ~/.gpligcrc and delete the lines with 'libdir' and 'datadir'

However, as this feature isn't quite useful for end users, I'll try to find a better solution for the next release.

#2 Problem displaying turnpoint barrels

2016-03-08T17:11:21.571000Z

I haven't changed the installation path, but it did install over the top of 1.07.
Since then I've cleaned up the installation by deleting anything gpligc-related
outside the untarred directory structure, run 'make clean' and then done a from-scratch configure, build and install from README. All worked without complaining, but there was still one problem:

$ gpligc
Can't locate GPLIGCfunctions.pm in @INC (you may need to install the GPLIGCfunctions module) (@INC contains: . /usr/local/bin/ /usr/local/share/gpligc/ /usr/local/lib/perl5 /usr/local/share/perl5 /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5 /usr/share/perl5 .) at /usr/local/bin/gpligc line 305

It turned out the this time GPLIGCfunctions.pm wasn't found because it was installed as
/usr/local/lib/gpligc/GPLIGCfunctions.pm which is not included in @INC so, as a quick kludge I copied it to /usr/local/share/gpligc/ and everything is now working as expected.

Many thanks for your help.

Request to add support for variable-barrel task handicapping

2016-03-08T15:47:49.973000Z

Here in the UK we've started using 'variable barrel' tasks as a popular way to allow a wide range of glider types to fly the same task. The idea is to declare a single 3 or 4 turn racing task using barrel turnpoints but to apply handicapping by setting the turnpoint barrel size to suit the glider's handicap. Each pilot is given his barrel size at briefing, sets it into his navigation computer and flies the task. This simplifies scoring because the fastest time wins, with the scoring systrem only having to check that each glider that completes the task has a fix in every barrel: the standard scoring programs can be scripted to do this.

All the common navigation programs, e.g. LK8000, XCSoar and SeeYou Mobile can already handle the required barrel sizes, which range from 500m radius for the highest performance glider out to several km for the lower performance gliders. The last variable barrel task I flew assigned me a 4.2km radius: I fly an H.201 Standard Libelle while other pilots were flying Discus 2s and Duos.

So, here's my request. Please change the Options menu so that the required barrel radius can be typed in as metres or km, that would do the trick. The ideal would be if Options was to allow start/finish line length and turnpoint default radius to be set separately and the Task Editor could be used to override the turnpoint radius for individual turnpoints. I think the task setting rules allow some turnpoints to have different radii, e.g. the 'steering' TPs that are sometimes used to control the finish direction would typically be 500m radius for everybody.

As an actual example I've attached my trace from the last variable barrel task I've flown. In case you're wondering, I didn't finish the task because thick top cover arriving from the west caused me to abandon about 10km short of Towcester. Look at the first turnpoint (Littleport, out to the east), where it looks as though I turned very early. However, recalling that my handicapped barrel radius was 4.2km, if you create a KML file and look at it on GoogleEarth you'll find Littleport is around 4km NE of where I turned, so was in the barrel.

This trace nicely shows another problem: that where the task is bigger than the flight path, the default scaling prevents the whole task from being seen. So far I haven't been able to find how to zoom further out. So, please consider doing one of the following:
1) leave the default size as is, i.e. fitted to the flight log, and provide a way to zoom further out so everything can be seen.
2) rescaling the display so it includes all of the flight path and all of the task plus the FAI sectors/barrels.

Note: unfortunately its not possible to extract the barrel size from the IGC log because the C record doesn't include that information. Hence my request for changes to Options and the Task Editor.

#2 Problem displaying turnpoint barrels

2016-03-08T15:21:05.074000Z

Please check whether you're using the correct GPLIGCfunctions.pm file.
The 1.10 version shouldn't have $gpx's in the stated lines...

A possible explanation is, that you've changed the installation path, and .gpligcrc still includes an old path directing to an old GPLIGCfunction.pm.

Problem displaying turnpoint barrels

2016-03-08T14:53:37.632000Z

I've just installed version 1.10, which looks good, but I'm having problems with displaying barrel-turnpoints. This is probably due to a bug in GPLIGCfunctions.pm because hitting 'c' to draw turnpoints causes a whole series of the following line pairs to be written to the console when gpligc has been started from the command line:

Use of uninitialized value $gpx in multiplication () at
/usr/local/share/gpligc/GPLIGCfunctions.pm line 476.
Use of uninitialized value $gpx in multiplication () at
/usr/local/share/gpligc/GPLIGCfunctions.pm line 477.

The line numbers are always 476 and 477. They are always output when turnpoints should be drawn. They are not output when 'c' is hit again to hide turnpoints and they are not output when the task is being drawn or erased. Barrel-type turnpoints are never displayed and FAI sectors only appear as a set of straight lines: there are no arcs shown to delimit the sector.

Problem displaying turnpoint barrels

2016-03-08T14:53:37.632000Z

Ticket 2 has been modified: Problem displaying turnpoint barrels
Edited By: Hannes Krueger (kruegerh)
Status updated: u'open' => u'closed'

Test Bug

2008-07-30T18:39:17Z

This is a test Bug