Home arrow SeeYou arrow User Interface arrow Landout distance calculation for Racing Tasks
Landout distance calculation for Racing Tasks

Author Topic: Landout distance calculation for Racing Tasks  (Read 3986 times)

Offline johnw

  • Newbie
  • *
  • Posts: 4
    • View Profile
Landout distance calculation for Racing Tasks
« on: February 09, 2009, 10:52:40 pm »
When Seeyou calculates the achieved distance for landouts on Racing Tasks the length of the uncompleted leg is reduced by the distance from the Turn Point.

Is there any way of getting Seeyou to reduce the length of the uncompleted leg by the distance from the boundary of the Observation Zone ?
« Last Edit: February 10, 2009, 07:56:39 am by johnw »

Offline Andrej Kolar

  • Administrator
  • Hero Member
  • *****
  • Posts: 1907
    • View Profile
    • Naviter
Re: Landout distance calculation for Racing Tasks
« Reply #1 on: February 12, 2009, 12:07:49 am »
Please explain why. Thanks.

Offline johnw

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Landout distance calculation for Racing Tasks
« Reply #2 on: February 12, 2009, 10:22:54 pm »
With a 20k radius, 90 degree sector OZ it is currently possible to land out 20k from the TP but 10m outside the OZ and be radiussed back by 20k.  Flying the extra 11m and landing just inside the OZ means that you are controlled at the TP so the extra 11m flown is worth at least 20k of distance.  The geometry of the OZ and the task ensures that this is not generally an issue but it may be on difficult days with large diversions.

I have been asked to explore the pros and cons of using a 20k radius, 180 degree sector for showery day Racing Tasks and one of the problems that I foresee is that this is likely to highlight this anomaly.

Changing the distance calculation to that described would remove this problem ... but may well introduce others !

You may well say use an AAT instead but the intention of the revised OZ is to encourage the use of Racing Tasks on days when an AAT may be inappropriate.


Offline Andrej Kolar

  • Administrator
  • Hero Member
  • *****
  • Posts: 1907
    • View Profile
    • Naviter
Re: Landout distance calculation for Racing Tasks
« Reply #3 on: February 16, 2009, 10:59:12 am »
If you make this sector Assigned Area sector that is almost exactly how it will be scored. Please see Sporting Code, section 3, Annex A for exact rules. Where else would you use a 20km radius sector?

Offline johnw

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Landout distance calculation for Racing Tasks
« Reply #4 on: September 29, 2009, 07:28:48 pm »
Apologies for the delay...

This season all British competitions have had the option of specifying a 20k radius, 180 degree Observation Zone for Racing Tasks on showery days.  This has generally been received very well by the pilots with the exception that the treatment of landouts is seen as unfair.  The problem, as described above, is that their achieved distance is reduced by their distance from the TP - not from the OZ.

I understand that the achieved distance of a landout on an Assigned Area task is reduced by the distance from the next OZ.  Making that option available in SeeYou for Racing Tasks would resolve this problem.  Just setting an Assigned Area Task instead of a Racing Task is not the correct solution as this would mean setting Assigned Area Tasks in inappropriate, showery, conditions.

Offline oconor

  • Newbie
  • *
  • Posts: 17
    • View Profile
Re: Landout distance calculation for Racing Tasks
« Reply #5 on: October 02, 2009, 12:42:25 am »
Declaring the task to SeeYou as AAT may sort the distance to next OZ issue.
If this Racing task, declared as AAT is given a nominally long time eg 12 hours,
when it is fed through the scoring program, will it give correct racing task scores?
Or will it incorrectly use the AAT scoring algorithm.

Rory

Offline johnw

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Landout distance calculation for Racing Tasks
« Reply #6 on: October 02, 2009, 07:18:23 am »
I think that you probably mean give a nominally short time so that the default time isn't used when you finish early but...

...the problem with your suggestion is that an AAT calculates the distance of the completed legs differently so the achieved distance would be incorrect.