See You : "Task Not Finished"

When I look at my flights in See You, it always tells me I haven't
completed the task. I don't know if it's because See You wants me to
fly cylinders, or of the ZERO entries in my Takeoff and Landing
Coordinates are the issue. Here's what shows in the declaration:

C0000000N00000000WTAKEOFF
C3803480N11705370W*TONOPAH
C3918500N11450510WEly AP
C3924400N11656600WAustin6
C3803480N11705370W*TONOPAH
C0000000N00000000WLANDING

In case anyone is bored and feeling like digging into it, this is the
flight:

http://www.onlinecontest.org/olc-2.0...Id=-1674917029

If the issue is the TAKEOFF and LANDING coordinates, I don't know how
to get them in the 302A declaration. Need help dispelling my
ignorance.

TIA

You are not required to declared your takeoff and landing points. The zeros
in the declaration code will not affect your flight claim nor will they
affect SeeYou.
The problem here is that SeeYou has awarded you an oputlanding before the
first turn point, and I cannot see why. There is a glitch in the SeeYou
analysis somewhere.
Clearly you completed the task.
When I analyse flight claims, I do not rely on what SeeYou tells me. It is
an aid, but not the final word. I use it to enable me to make a step by
step analysis of the flight.
If someone can say why SeeYou awarded an outlanding, and stopped recording
task time, while still recording all other parameters, I'd love to hear
it.
Pam Kurstjens
Data Analyst
Australia

At 22:44 10 November 2008, Uncle Fuzzy wrote:
When I look at my flights in See You, it always tells me I haven't
completed the task. I don't know if it's because See You wants me to
fly cylinders, or of the ZERO entries in my Takeoff and Landing
Coordinates are the issue. Here's what shows in the declaration:

C0000000N00000000WTAKEOFF
C3803480N11705370W*TONOPAH
C3918500N11450510WEly AP
C3924400N11656600WAustin6
C3803480N11705370W*TONOPAH
C0000000N00000000WLANDING

In case anyone is bored and feeling like digging into it, this is the
flight:

http://www.onlinecontest.org/olc-2.0...Id=-1674917029

If the issue is the TAKEOFF and LANDING coordinates, I don't know how
to get them in the 302A declaration. Need help dispelling my
ignorance.

TIA

On Nov 10, 3:30*pm, Pam Kurstjens wrote:
You are not required to declared your takeoff and landing points. The zeros
in the declaration code will not affect your flight claim nor will they
affect SeeYou.
The problem here is that SeeYou has awarded you an oputlanding before the
first turn point, and I cannot see why. There is a glitch in the SeeYou
analysis somewhere.
Clearly you completed the task.
When I analyse flight claims, I do not rely on what SeeYou tells me. It is
an aid, but not the final word. I use it to enable me to make a step by
step analysis of the flight.
If someone can say why SeeYou awarded an outlanding, and stopped recording
task time, while still recording all other parameters, I'd love to hear
it.
Pam Kurstjens
Data Analyst
Australia

At 22:44 10 November 2008, Uncle Fuzzy wrote:



When I look at my flights in See You, it always tells me I haven't
completed the task. *I don't know if it's because See You wants me to
fly cylinders, or of the ZERO entries in my Takeoff *and Landing
Coordinates are the issue. *Here's what shows in the declaration:

C0000000N00000000WTAKEOFF
C3803480N11705370W*TONOPAH
C3918500N11450510WEly AP
C3924400N11656600WAustin6
C3803480N11705370W*TONOPAH
C0000000N00000000WLANDING

In case anyone is bored and feeling like digging into it, this is the
flight:

http://www.onlinecontest.org/olc-2.0....html?flightId...

If the issue is the TAKEOFF and LANDING coordinates, I don't know how
to get them in the 302A declaration. *Need help dispelling my
ignorance.

TIA- Hide quoted text -

- Show quoted text -

Me too!

Go to / Edit / Optimize while viewing the flight.

This will open the window on the RHS showing the various distances
optimized.

Select OLC.

At the bottom of this window, click the 'Copy' button.

This will copy the selected optimized task to the flight, and the
stats etc. will now be corrected.

Regards, Bernie.
(See you at Narromine Pam!)

PS:

If you search on "photo landing" at http://www.naviter.si/forum/index.php
you will find more info on the actual reason, but I am not really any
the wiser after reading the answers from Andrej.

From http://www.naviter.si/forum/index.php?topic=1004.0

2. If you have a task in your IGC file, then you will get the
statistics according to that task as if you flew it in competition.
This includes the fact that the closest point to the next Waypoint
that was not reached will be the "landout", formerly known as Photo-
landing.

If you wish to have the statistics for the flown task (and get rid of
the Photolanding mark) do this:
.. Optimiize the flight (CTRL+L)
.. Choose one type of task, then press Copy button
.. Go to Statistics and enjoy the full stats over this newly assigned
task

Point 2 suggests that you turned short of the next waypoint on that
part of the flight, and got scored to that point.
As I don't have US waypoints in See You (I'm Australian) I can't check
but you probably can!
The optimize/copy process I described ignores your actual DECLARED
TP's and just uses arbitrary points along your flight path that fit
the selected criteria (ie, OLC, FAI, whatever)

See You thinks your task is a 571.0 Km triangle for some reason. (See
the light blue/mauve line on the map) and had FAI sector TP's. You
actually didn't go though the sector near the photo landing,
and then your course described a semi circle to the left, but I dont
think you ever got closer to the sector than the photo landing point.

So that agrees with the above: " the closest point to the next
Waypoint that was not reached". Perhaps your latest task didnt upload
properly, and a prior task with a very similar route to what you flew
was still declared? Tricky stuff.

Regards, Bernie.

I don't think the problem is with Seeyou, I think the problem is with your
302. I often get a similar result from Seeyou using a 302. The problem is
with the engine noise detector; despite having a pure sailplane the 302 is
too sensitive and picks up noise that is assumed to be engine noise by
Seeyou. Next time you open one of your flights in seeyou, right click,
select flight properties and check pure glider.
There is a modification that Dickie Feakes (UK) does to the 302 to solve
this problem; maybe you have someone in the US that can do the same.


At 22:44 10 November 2008, Uncle Fuzzy wrote:
When I look at my flights in See You, it always tells me I haven't
completed the task. I don't know if it's because See You wants me to
fly cylinders, or of the ZERO entries in my Takeoff and Landing
Coordinates are the issue. Here's what shows in the declaration:

C0000000N00000000WTAKEOFF
C3803480N11705370W*TONOPAH
C3918500N11450510WEly AP
C3924400N11656600WAustin6
C3803480N11705370W*TONOPAH
C0000000N00000000WLANDING

In case anyone is bored and feeling like digging into it, this is the
flight:

http://www.onlinecontest.org/olc-2.0...Id=-1674917029

If the issue is the TAKEOFF and LANDING coordinates, I don't know how
to get them in the 302A declaration. Need help dispelling my
ignorance.

TIA

Hi,

Cambridge Aero Instruments can do the 302 Engine Noise Level upgrade here in
the USA. All new 302 ENL units built starting around Jan. 2008 have the
hardware change that fixes the previous problem with the ENL recording. If
you own an ENL version built before that I highly recommend sending it to
Cambridge for upgrade. www.cambridge-aero.com.

Good Soaring,

Paul Remde
Cumulus Soaring, Inc.
http://www.cumulus-soaring.com

"Mark Dickson" wrote in message
...
I don't think the problem is with Seeyou, I think the problem is with your
302. I often get a similar result from Seeyou using a 302. The problem
is
with the engine noise detector; despite having a pure sailplane the 302 is
too sensitive and picks up noise that is assumed to be engine noise by
Seeyou. Next time you open one of your flights in seeyou, right click,
select flight properties and check pure glider.
There is a modification that Dickie Feakes (UK) does to the 302 to solve
this problem; maybe you have someone in the US that can do the same.


At 22:44 10 November 2008, Uncle Fuzzy wrote:
When I look at my flights in See You, it always tells me I haven't
completed the task. I don't know if it's because See You wants me to
fly cylinders, or of the ZERO entries in my Takeoff and Landing
Coordinates are the issue. Here's what shows in the declaration:

C0000000N00000000WTAKEOFF
C3803480N11705370W*TONOPAH
C3918500N11450510WEly AP
C3924400N11656600WAustin6
C3803480N11705370W*TONOPAH
C0000000N00000000WLANDING

In case anyone is bored and feeling like digging into it, this is the
flight:

http://www.onlinecontest.org/olc-2.0...Id=-1674917029

If the issue is the TAKEOFF and LANDING coordinates, I don't know how
to get them in the 302A declaration. Need help dispelling my
ignorance.

TIA

No Mark, if you look at the noise trace it is reasonable, and at the
'photo landing' time noise is relatively low. The problem is clearly
the setting of the TP zone radius, and the 'photo landing' is at the
closest approach to the waypoint, since the flight path never enters the
zone within the radius set.

In SeeYou, go into Edit/Flight Properties/Observation Zone. Change the
two waypoint radii from 3km to 30km. The flight is now analysed as
completed at a speed of 82.58 kph.

Interestingly, the analysis also shows that every thermal was turning
right.

I have seen traces where SeeYou interprets a noise peak (due to opening
the DV panel for extra ventilation) as an engine run, but this isn't one
of them.

At 11:00 11 November 2008, Mark Dickson wrote:
I don't think the problem is with Seeyou, I think the problem is with
your
302. I often get a similar result from Seeyou using a 302. The problem
is
with the engine noise detector; despite having a pure sailplane the 302
is
too sensitive and picks up noise that is assumed to be engine noise by
Seeyou. Next time you open one of your flights in seeyou, right click,
select flight properties and check pure glider.
There is a modification that Dickie Feakes (UK) does to the 302 to solve
this problem; maybe you have someone in the US that can do the same.

I'm wondering if SeeYou is confused by the fact that the flight wraps
around midnight (UTC) and apparently starts after it has ended.

When I run animation against the relevant IGC file its starts at the
launch time but when it reached midnight UTC (part way along the second
leg) it thinks the flight has ended and jumps back to the launch.

Looks like this could be a SeeYou bug - even if it's not the root cause
of the original landout problem.