![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]() "Frank" wrote in message ... On Jun 9, 5:40 am, "Peter Wyld" wrote: "Frank" wrote in message ... I flew a TAT today at the Cordele, Ga USA contest, and as I always do I opened my flight in SeeYou 3.95 for analysis. Except this time it showed a 'photo landing' between the 2nd and 3rd turn areas, and there seems to be no way to get rid of it. I have been using SeeYou for at least 8 years, and am pretty familiar with the common sorts of task declaration errors that can lead to this situation. However, this time I can't get rid of it for the life of me. I attempted to post this on the Naviter support forum, but that seems to be screwed up too. I can't get an activation email, and since I can't get an activation email, I can't complete the forum registration and therefore can't post. I also looked at their forum postings about 'photo landings' and it seems that the SeeYou folks aren't really interested in addressing this issue (assuming it *is* an issue and not just something I'm doing wrong). Anyone else had this problem with SeeYou 3.95? Frank (TA) Without a copy of the igc file I can't be sure, but if it was an AAT (which it looks like from the task description), I would guess that the photo landing is when the time ran out (i.e. 2h30 from the start). Posting to OLC was the right thing to do. As soon as I saw the trace, I noticed that the ENL levels were spiking way up, even though I have a pure glider. There happened to be a big spike at 2:06 that coincided with a low point, and I guess the algorithm in SeeYou decided that I had started the engine there. It would be nice if 'Photo Landing' were replaced with 'Engine Start' in this case - would have avoid a lot of electron abuse ;-). TA Now that your trace has been posted where I can get at it, I've looked at it. I can't see any noise in SeeYou. If you set the task time to 2:30, you get a photo outlanding after 2 hours 30 (no surprise there!), If you set the task time to 3:30 you get a completed flight. If you leave the tasktime at 00:00:00 it gives you a completed flight. I ran it against a UK scoring script with a 2:30 task time and it scores you just fine (3h25m38s, 154miles, 44.9 mph) although it still shows a photo outlanding at the task timeout time (as it should). I don't think SeeYou can create good results from an AAT without the help of a scoring script, it's OK with Racing tasks without a script (simple computation of distance vs time). good luck with the comp! |
#2
|
|||
|
|||
![]()
On Jun 9, 3:39*pm, "Peter Wyld" wrote:
If you set the task time to 2:30, you get a photo outlanding after 2 hours 30 (no surprise there!), Under what set of rules is a maximum task time ever set? Andy |
#3
|
|||
|
|||
![]() "Andy" wrote in message ... On Jun 9, 3:39 pm, "Peter Wyld" wrote: If you set the task time to 2:30, you get a photo outlanding after 2 hours 30 (no surprise there!), Under what set of rules is a maximum task time ever set? Andy FAI Annex 3a. |
#4
|
|||
|
|||
![]()
On Jun 9, 11:05*pm, "Peter Wyld" wrote:
FAI Annex 3a. Sorry can't find it there. Can you please give a paragraph reference. 6.2.2 Assigned Area Task, mentions a Minimum task time which is the same as US rules. A search for maximum task time returned no results. Andy |
#5
|
|||
|
|||
![]() "Andy" wrote in message ... On Jun 9, 11:05 pm, "Peter Wyld" wrote: FAI Annex 3a. Sorry can't find it there. Can you please give a paragraph reference. 6.2.2 Assigned Area Task, mentions a Minimum task time which is the same as US rules. A search for maximum task time returned no results. Andy I obviously fell into the trap of not answering your question correctly... As I said before, it's not a maximum but a minimum. SeeYou has a setting for Task Time, what your scoring script does with it is up to you. Perhaps you should ask Naviter to change the flag to "Task Time Out" instead of "Photo Landing" when the task time expires. It has occasionally caused me to wonder what was happening after a long day scoring contest traces until I realised it was just the clock going 'ping'. However, I was trying to answer the OP and not just give SeeYou a hard time. The answer is, If you don't want to run a scoring script (i.e. most of the time) and you have an AAT flight, don't set a task time and SeeYou will give you all the information you need. If you do set a tasktime, SeeYou will treat the timeout as a photolanding. Tasktime is (I believe) only of consequence when trying to sort out the scores for a competition. |
#6
|
|||
|
|||
![]()
On Jun 10, 11:05*am, Andy wrote:
On Jun 9, 3:39*pm, "Peter Wyld" wrote: If you set the task time to 2:30, you get a photo outlanding after 2 hours 30 (no surprise there!), Under what set of rules is a maximum task time ever set? On any day that has a CIvil Twilight, for a start. I don't know what they do if there are gliding contests north of a line from Oslo to St Petersberg. |
#7
|
|||
|
|||
![]()
On Jun 10, 2:16*am, Bruce Hoult wrote:
On any day that has a CIvil Twilight, for a start. No, that may be used to define the time at which a task will end even if the glider has not landed, but it does not define a maximum task time in the context being discussed. Maximum task time would imply a maximum allowed duration between the time of starting and the end of the scoring flight. Andy |
#8
|
|||
|
|||
![]()
On Jun 10, 7:55*am, Andy wrote:
On Jun 10, 2:16*am, Bruce Hoult wrote: On any day that has a CIvil Twilight, for a start. No, that may be used to define the time at which a task will end even if the glider has not landed, but it does not define a maximum task time in the context being discussed. Maximum task time would imply a maximum allowed duration between the time of starting and the end of the scoring flight. Andy Rule 10.1.10 Finish closes - At contest sunset time therefore task end = Finish close Contest sunset time defined as Rule 10.1.8 Contest sunset - the CD shall designate a contest sunset time, which shall be approximately 10 minutes prior to the earliest time of sunset at the contest site during the period of the contest. |
#9
|
|||
|
|||
![]()
On Jun 10, 9:16*am, Ron Gleason wrote:
Rule 10.1.10 * *Finish closes - At contest sunset time therefore task end = Finish close Contest sunset time defined as Rule 10.1.8 * *Contest sunset - the CD shall designate a contest sunset time, which shall be approximately 10 minutes prior to the earliest time of sunset at the contest site during the period of the contest. Sure, but what point are you making. What is under discussion is that SeeYou ended a flight after 2.5 hours because a max task time of 2.5 hours had been defined. It had nothing to do with sunset. What I was trying to find out was why SeeYou even has a definition for maximum task time. To that end I asked what set of rules defined a maximum task time. So far there is no indication that any does. Andy |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Photo of a Newspaper Photo - 1919 Mail | Terry M[_3_] | Aviation Photos | 0 | May 15th 08 04:03 AM |
A Jet Blue Aircraft Landing with Sideway Landing-Gear | Lufthansi | Piloting | 18 | July 19th 06 05:13 AM |
Seeyou NMEA to Winpilot/Seeyou | Jean | Soaring | 4 | June 3rd 06 11:38 AM |
Photo: An S-3B Viking, comes in for a sunset, arrested landing | T. & D. Gregor, Sr. | Simulators | 0 | August 31st 04 10:28 PM |
What does 'Photo Landing' mean on SeeYou analysis? | Stewart Kissel | Soaring | 2 | June 15th 04 06:36 PM |