Accelerometer Thread
9/11/14, 04:23 PM
#12
Legacy TMS Member
Not on a Skid pad no, but running behind a KTM Motard Running through the Tail of the Dragon.This is also not jerking the wheel like someone else made the comment, steady in with Braking and steady out of the corners with acceleration. It is 318 corners in 11 miles so there are times when you are going into an opposite corner pretty quickly but I do know the corner that those numbers came from.
Last edited by Siber Express; 9/11/14 at 04:38 PM.
9/12/14, 06:41 AM
#14
Cobra Member
UMMM.... well.... I have a V6 and i have the EXACT same as you... does that mean I win because i have a smaller engine?
I didn't bring my car to work today but I will definitely take a shot if you want proof.
9/12/14, 02:01 PM
#16
9/12/14, 03:19 PM
#17
Cobra Member
Is that how you achieved .87? lol no. I just took a picture. I was wrong. not .87.... it was .84. still not bad.
Last edited by JoeMidnight; 9/12/14 at 03:27 PM.
9/12/14, 08:51 PM
#20
Banned
Join Date: August 2, 2013
Location: Little north of Stuttgart, Germany
Posts: 3,090
Received 254 Likes
on
230 Posts
And he did it with a V6, so what's your excuse?
Although if I look at the numbers.... and this seems like "the bridge to nowhere".. thanks Sara Palin, you effin idiot.
0.84g = 8.24 m/s/s hmmmm...
So 100km/h = 62mph =27.7 m/s so theoretically 0-62 would be achieved in 27.7/8.24 = 3.36s. Therefore the results are implausible unless we consider the theory that the Track Apps use MAX of the absolute value of acceleration collected over time. Which makes them pretty useless.
The end.
oh, and this isn't meant to say that the Track Apps are doomed, but to make them useful it would take a bit more software engineering effort to design them to average the data points along with some peak filtering to eliminate outliers in the data.
Although if I look at the numbers.... and this seems like "the bridge to nowhere".. thanks Sara Palin, you effin idiot.
0.84g = 8.24 m/s/s hmmmm...
So 100km/h = 62mph =27.7 m/s so theoretically 0-62 would be achieved in 27.7/8.24 = 3.36s. Therefore the results are implausible unless we consider the theory that the Track Apps use MAX of the absolute value of acceleration collected over time. Which makes them pretty useless.
The end.
oh, and this isn't meant to say that the Track Apps are doomed, but to make them useful it would take a bit more software engineering effort to design them to average the data points along with some peak filtering to eliminate outliers in the data.
Last edited by 5.M0NSTER; 9/12/14 at 09:17 PM.