View Single Post
Old 04-25-2009, 02:24 PM   #4 (permalink)
bwilson4web
Engineering first
 
bwilson4web's Avatar
 
Join Date: Mar 2009
Location: Huntsville, AL
Posts: 843

17 i3-REx - '14 BMW i3-REx
Last 3: 45.67 mpg (US)

Blue Bob's - '19 Tesla Std Rng Plus
Thanks: 94
Thanked 248 Times in 157 Posts
I appreciate the heads up on excel. With my older excel, I get just three rows and a fraction of the data.

The problem with most spreadsheets is a limit on the number of rows, typically 64k rows. The browser Camino performs the xml parsing perfectly and I could probably cut-and-paste into excel but that doesn't solve the scaling problem.

The Perl program reduces the number of rows (aka, records) from 7,122 to 1,158 and this was just one day's worth of data, four trips. A full tank or more of data could easily exceed the analysis capacity of any spreadsheet. But I think you've suggested an excellent, parallel approach.

It sounds as if the more recent spreadsheets with xml parsing could import Garmin xml data directly. With a well crafted set of macros, the spreadsheet could identify the 'coast down' data and solve the data recording problem of 'coast down' testing. Sad to say, my old excel won't be able to help.

Bob Wilson
__________________
2019 Tesla Model 3 Std. Range Plus - 215 mi EV
2017 BMW i3-REx - 106 mi EV, 88 mi mid-grade
Retired engineer, Huntsville, AL
  Reply With Quote