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.

ok so i've been playing with more advanced forms of analysis algorithms and i'm getting really excited. this entire thing might be optimally represented in a way that opengl will do all the work for me.

- logs must be CSV (comma seperated) files. in tunerpro, you have to 'export log' to get a csv format log.
- they all have to have identical fields and ordering right now (so exported from the same program)
- for single o2 sensor (single bank) cars, just set BLM bank A.

this version uses an experimental type of analysis. instead of putting data into a 'cell' with 'borders', which would have no interpolation ability whatsoever, we use some geometry.

each data point kinda forms a circle of effect (actually an oval, we scale map and RPM different), and the center of each table cell is an observer. if the observer is located within the range of the data point, it counts towards its average. this should better reflect the reality of trims being an imprecisely located data point, and the usual logic that if one cell is affected, the surrounding cells also require modification or smoothing.

of course these are not literally circles, since checking distance between the two points is cheap mathematically, we can just check the range of radius between points, so the analysis happens very quickly.

i may add a bit of magnitude adjustment vs. distance later which might result in better data, early attempts failed because my math skills are a bit shitty.

Hi
Got annual MOT due shortly. Car has been running really well in OL SD but I've put it back to CL SD for the ticket.
Been out today for half an hour and ran the log through the analyzer.
VE tables came out 97 to 101. I presume this is %age.
Worst blm was 16 at 121/ 127

I was expecting a much richer result just swapping back to narrowband after tuning on the wideband as the wideband appears much more lean whilst cruising.

in default configuration it rejects tps < 1 so it isn't going to help you with idle (aka cell 16) (assuming it found that field, otherwise it wont add the filter for you)

stand by for next version with hugely improved analysis interpolation!

tricky part is, there's so much math now that we have to tune the tuner. there are all these scalars and multipliers to make the analysis behave correctly without adding data to the wrong cells. i think in the end it'll be awesome.