Quote:
Originally Posted by ToBeFrank
See below for what I define as spikey.
This is NOT what I'm doing. I am not smoothing the VEs after they are generated. I have completely replaced the Twin Scan VE generator software with my own algorithm. That algorithm includes a smoothing algorithm. There are no assumptions being made. The data logged from the bike tells it what to do.
So do you think this surface plot looks acceptable? This plot is what you get when street tuning with the Twin Scan software. BTW, Steve Cole agrees with me that the answer here should be "no" (supporting link posted earlier in this thread).
This is NOT what I'm doing.
When did I say "having a smooth color transition is the only thing that matters"? My point is if the algorithm to generate the new VEs is correct, you automatically end up with a smooth graph. And for the nit pickers, yes, you'll have some spikes, but in general the map will be pretty smooth.
BTW, interpolating cells is mandatory if you want a correct algorithm. An example: suppose your VE table has a TPS axis with 10 and 15 and a RPM axis with 2000 and 2250. Now suppose you log a data item at 12.5 TPS and 2125 RPM. Which cell does this data item contribute it's data to? The next data item is logged at 12.0 TPS and 2150 RPM. Which cell does it go into? |
Ok, another question, when you say you are using the data from the bike, are you talking about the data from the factory 02's? Just want to be clear on this, if so, I would assume you are taking the VE vs VE new in the data mode of the SERT/SEST/tts type tuners and using that info to generate a new ve table, maybe converting that data to "comma delimited" and viewing in an excel spreadsheet.
