Average of all wheels will be in the next version (and 2 other averages: of the front wheels, and of the rear wheels). For the average over a certain period of time, see my response to FL!Ps first remark, below.
The legend would not be the right place to show this amount of data, because then it would be too wide for a "sidebar" pane.
But I can envision a "stats" window containing a table of numerical data, one row for each loaded lap. The columns in the table would be user-selectable, chosen from the same list as the graphs. You would also have an option to display either the value at the crosshair position, or the average, minimum or maximum value over the selected part of the track.
Whoa, this is getting complicated!
How would this help you in analysing your laps? For myself, the time difference graph tells me all I need to know: where in the lap I lost time, and where I gained some. What would a detailed list of sector times add to this?
OK, noted. It'll get a high priority.
F1PerfView can do this. It's called overlays. You can add other data to the graph (provided that it's expressed in the same units).
I can't say I like it, though. I find it difficult to distinguish which line is for which type of data. The display gets messy very quickly.
It's not supported by the library I use (wxWidgets). Anti-aliasing is rare for Windows desktop apps. Do you have any readability problems with LRA, perhaps?
And of course, when you have watched lap 45 you could then type "/goto 2", and the replay would automatically be restarted and then fast-forwarded to lap 2. Thus, you'd have rewindable replays, although a bit clunky: whole laps only and with delays.
I'm biased on this, so I'd better not answer the question.
Why don't you try both programs, and see which one suits your needs best?
LRA should be useful for both. If you want to analyse the driving style, you can look at speed, time (difference), and at the driver's inputs. If you want to analyse the setup, you can take a look at camber, slip ratio, tyre load, etc.
When you see someone who is trying to cut down a tree with a hammer, do you blame the hammer?
The video may be funny, but the idea is silly. Only an idiot would try to enter programming code though a speech recognition tool, and expect a good result. The tool is meant for processing spoken natural languages. Perl isn't in that domain, last time I checked.
Um, what do you use histogram plots for? I've seen them in MoTec, but couldn't see how they can be useful.
XY plots are already on my list. Or in any case, a traction circle graph is on it. That seems to me the most useful example of an XY plot. (BTW, F1PerfView can do them, but maybe they're too limited for your taste.)
Yes, generating RAF files in LFS is stil a bit clunky. An auto-save feature like I mentioned in post #11 would make things much easier, and would make the learning cycle (drive -> analyse -> adapt -> drive etc.) much faster.
Yes, there is a reason: it takes time to make it, so other features will be postponed or even cancelled. I'd much rather that Scawen 'opens up' LFS so it interacts nicely with add-on apps, and concentrates on core features.
Not because it isn't a good idea, but IMHO this stuff should be left to external add-ons. Browse For Speed does a nice job, and Mates@Track does something similar, IIRC. In this way, the various wishes can be realized faster than if it would be somewhere on Scawen's list.
However, the integration isn't perfect: when you want to connect to a certain host, BFS needs to start LFS anew. There is no way to make LFS connect to a host when it's already running.
The good thing about the Global Warming frenzy is that it detracts our attention from the Islamic Terrorists frenzy.
Prediction: In 2 years, a court will find Al Gore guilty of causing the climate change, on grounds of (a) being an American, (b) having loads of frequent flyer miles, (c) making a film that made people realize that climate change really exists.
In a way, that vid reminds me of the old phrase "This day is the first day of the rest of your life". At first sight it looks impressive and thought-inspiring, but when you think about it some more, you find that it's utter BS. You can prove anything with statistics, especially if you use loads of it.
For many species, interbreeding of close relatives is risky. That's why evolution created an inhibition: individuals won't mate with the ones they grew up with. In humans, this inhibition grew into a taboo. So, if you're digusted when reading about this couple, you know why.
Note that the inhibition only works if you come from the same family. You don't need to share any genes, you need to share history. The couple in the news item did not grow up together, so they felt free to fall in love.