Ticket #256 (closed defect: fixed)

Opened 4 years ago

Last modified 4 years ago

race to anywhere 1:3:4

Reported by: philchett Owned by: joerg
Priority: major Milestone: 2013 R2
Component: FsComp Version: 1.3.4
Keywords: Cc:

Description

Files are attached to demonstrate bug.

In summary: We set a race to anywhere

1 0.0km SLM014 (400 lat:52.52103 lon:-2.88113 open:2013-06-24T13:00:00+01:00 close:2013-06-24T20:00:00+01:00) 2 4.6km SS SLM014 (5000 lat:52.52103 lon:-2.88113 open:2013-06-24T13:00:00+01:00 close:2013-06-24T20:00:00+01:00) 3 89.3km ES SLM014 (90000 lat:52.52103 lon:-2.88113 open:2013-06-24T13:00:00+01:00 close:2013-06-24T20:00:00+01:00)

this gave some very strange results. We reverted to 1:2.14 to resolve the problem (with a bit of a fudge)

Attachments

bos2013all_glidersr2.fsdb (93.0 KB) - added by philchett 4 years ago.
fsdb
Richard Hunt.20130624-160943.712.22.kml (87.3 KB) - added by philchett 4 years ago.
test track to go with fsdb
Gordon Rigg.20130624-175226.9113.21.kml (62.9 KB) - added by philchett 4 years ago.
another track for testing
Andrew Hollidge.20130624-165452.1076.51.igc (47.0 KB) - added by philchett 4 years ago.
another one for testing
Rob_Gregg.20130624-154244.7342.13.kml (170.1 KB) - added by philchett 4 years ago.
last one

Change History

Changed 4 years ago by philchett

fsdb

Changed 4 years ago by philchett

test track to go with fsdb

Changed 4 years ago by philchett

another track for testing

Changed 4 years ago by philchett

another one for testing

Changed 4 years ago by philchett

last one

comment:1 Changed 4 years ago by joerg

  • Version set to 2013
  • Milestone set to 2013 R2

comment:2 Changed 4 years ago by joerg

  • Version changed from 2013 to 1.3.4

comment:3 Changed 4 years ago by joerg

  • Owner changed from ste to joerg

comment:4 Changed 4 years ago by joerg

Hi Phil

I'm investigating your "Race to Anywhere" bug. You say you got "strange results" with FS 2013 - could you please be a bit more specific? What am I looking for?

thanks Joerg

comment:5 Changed 4 years ago by joerg

  • Status changed from new to closed
  • Resolution set to fixed

Found the bug: We wrongfully assumed so far that any SSS where the next turnpoint is around the same set of coordinates is an enter start. That's of course wrong for "race to anywhere" or "dutch cylinder" (as they're also called sometimes) tasks. We need to also look at the two turnpoint radius to figure out which way the start goes.

Note: See TracTickets for help on using tickets.