|
I'm thinking that the program would mostly acquire data from the car computer and a GPS, and perhaps an accelerometer. I guess that the data on the throttle opening used might make a better baseline than my suggestion of using just three throttle modes for a first iteration. If the early runs along the route encountered a lot of traffic, that would have to be recognized as transient impediments, while the system gathered information on the route. I don't think the program would have trouble over varying terrain or unevenly distributed stop signs - there is always acceleration, some period of constant speed, and then deceleration. The various algorithms would nudge the profile of throttle use during each cycle in different ways, and the program would then predict the results. I'd let it just run through all the accelerate/decelerate cycles in a route, letting it accumulate results, just as a car would with drivers of different styles, rather than trying to compare A to B at each section, and then see how that affects the next section like a chess match.
With each real run through a route, the program would get more hard data, and in between times, could run simulations against each other to come up with the best suggestions for improvements. You might want a button to tell the program if there are places on the route where its suggestion is inappropriate for "given" reasons.
|