Thanks everybody for feedback.

Tobias, but when XCSoar or your device crashes then you're blind about the
arrival time, right? Or maybe you have some backup..I would like to avoid
buying expensive instrument just to have backup for the AAT calculations.

I've used quite unstable HW/SW configurations with mSeeYou but I never had
to remember the start time and calculate the arrival time in my head. Only
this season I actually realized how difficult it is for me.

Simon, as for reporting crashes as soon as possible I agree. The best are
automated tests in these regard. Also a wide and enthusiastic user base
helps a lot. If considered with my feature request I would say this. The
better is crash recovery, the more people will use the beta versions and the
sooner there will be crash reports.

As for the extensive proposal some of you wrote. Am I wrong to assume that
the only input information into the AA dT/automatic optimization is the
start time and the rest of the task to be flown?

If there is only one last turnpoint and finish to be reached the algorithm
doesn't need to care if you reached the previous turnpoints at all. (or how
far did you go.)

So it needs to know:
- start time
- the task (actually only the remaining turnpoints of the task)
- next turnpoint (go to), the software assumes you know what you're doing
and that you did round the previous turnpoints of the task.

(and of course other stuff like wind, bugs, MC all of which can already be
changed by user)

The task is already remembered between invocations of XCSoar. I'm capable of
specifying the "next turnpoing" and other user values after a restart. The
only thing missing is "start time", which I need XCSoar to remember from the
previous run. I can live with incorrect task speed calculation or other
fancy stats.

I trust Tobias it's not that easy :/. Instead of full solution, would a user
specified start time be difficult to implement?

Tibor


On Tue, Jul 19, 2011 at 08:28, Tobias Bieniek <tobias.bien...@gmx.de> wrote:

> **
> Hi Tibor,
>
> I'm flying competitions regularly here in Germany and I love the AAT
> auto-optimization of XCSoar. With my PDA (Asus A636 with WM5) I rarely ever
> have crashes. Since I usually fly with an unstable testing version there are
> some, but most are fixed a few days later. I agree though that remembering
> the task state would be a useful thing. Unfortunatly it's not as easy as it
> sounds ;)
>
> Turbo
>
>
>
> Am 18.07.2011 23:53, schrieb Tibor Arpas:
>
> Hi guys,
>
>  I would like to ask those of you that fly competitions if you are happy
> flying AAT tasks with XCSoar? During the two competitions I used XCSoar I
> came too soon too many times. Once I made a user error and a couple of time
> XCSoar crashed during the flight. I don't think that the crash itself is
> anything that bad and I can live with that. What makes XCSoar unusable for
> me for my AAT tasks is that the start time is lost when the program or the
> device crashes.
>
>  After experiencing the problem I was trying hard to notice/remember my
> start time and do my calculations manually. But my conclusion is that it's
> too difficult and distracting. How many people here fly AAT tasks on
> competitions? I find it surprising that hardly anybody asks for the
> functionality mentioned in subject.
>
>  The feature request in the bugtracker is here
> http://www.xcsoar.org/trac/ticket/1303 and here
> http://www.xcsoar.org/trac/ticket/1222 .
> Please let the developers know if you need this functionality. Thanks a
> lot.
>
>  Tibor
>
>
> ------------------------------------------------------------------------------
> Storage Efficiency Calculator
> This modeling tool is based on patent-pending intellectual property that
> has been used successfully in hundreds of IBM storage optimization engage-
> ments, worldwide.  Store less, Store more with what you own, Move data to
> the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/
>
>
> _______________________________________________
> Xcsoar-user mailing 
> listXcsoar-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/xcsoar-user
>
>
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Xcsoar-user mailing list
Xcsoar-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcsoar-user

Reply via email to