Can you "stack" the "run analysis"?

[T3Bunny]

Well you can, but SHOULD you??? By "stack" it, I mean when your processing a datalog and hit "Run Analysis," then hit it again multiple times. In the past I have never done this, there is an unspoken rule that you shouldn't I guess. After some AFR target changes though I was getting 22 cell changes, dropping down to just 18. For giggles, I hit "Run Analysis" until it was zero cell change. Mind you this was with a single substantial length datalog....

It would seem to me that this would at the very least negate the "easy-very hard" cell change resistance.

What surprised me, was after doing this my next max cell change after a new run, was only 4! And the car had gone from driving just "okay" to running like a banshee! Past experience, has taught me that when things are this far out, I am looking to process at least 8-10 more logs to get it down to a reasonable amount (3-4 max cell changes).

Anyways I am sure something is lost doing this, but what and how much?

[piledriver]

veal works much more consistently.
if you have registered TS, use it instead of mlv for this.

the mlv based analysis uses a fixed lambda sample delay, and if on ms3 the allowable delay is inadequate at any rpm and load.
ts uses a lambda delay table that varies by map & rpm, makes a very significant difference if set properly.

[LT401Vette]

A trouble with running VE Analyze multiple times is that when you start it, it takes the current VE values and believes those to be what the car was running on. If you have already altered the table with VE Analyze or anything else, that is not true and so the corrections would be getting applied to a incorrect baseline.

Loading multiple logs is fine as long as there were no tune changes between them.

[T3Bunny]

veal works much more consistently.
if you have registered TS, use it instead of mlv for this.

Defiantly registered on both counts! And it is likely the ONLY softwares on any of my systems that I have paid for, and would do so again!

I should put some more effort into using TS. I just like to watch and see what areas were changed as I process it through MLV. Plus I DESTROYED a turbo one of the few times I used autotune... Things went sideways quickly when I was out on the highway, and the thought to cycle my key to stop it, never crossed my mind...

A trouble with running VE Analyze multiple times is that when you start it, it takes the current VE values and believes those to be what the car was running on.....

I figured this was the case but wasn't sure if it was still using the original .msq reference or the new changed one. Besides, I had to figure out a new way to "break" y tune so I have something to fiddle with!

Phil, don't know how you do it! You always seem to have a moment to answer even my silliest questions! Thanks!