815 816 817 819 in step 515 in fig6 the glide solver 410 may use the data it received in step 514 from the request manager 812 to calculate the coefficient matrices of the constraints in step 516 in fig6 the glide solver 410 may use the coefficient matrices constructed in step 515 to minimize the acceleration vector the glide solver 410 may be an inequality constrained norm 2 solver that uses the coefficients calculated in step 515 to minimize the norm 2 of the acceleration for each point along the route for the next x miles along the current route the norm 2 solver referenced above is depicted in fig4 with reference to fig4 the glide solver 410 may include multiple algorithm blocks 420 430 one of these blocks may be an route optimizer 420 this route optimizer 420 may be the norm 2 solver referenced above the acceleration vector that is being minimized is proportional to the energy vector minimizing the acceleration vector corresponds to minimizing the energy vector included as part of step 516 in fig6 may be the glide solver 410 producing a set of acceleration points that constitute the solution to the minimized acceleration vector in step 517 in fig6 the glide solver 410 may use the set of acceleration points created in step 516 to create a set of speed points along the route for the next x miles along the current route this set of speeds along the route may serve as targets for the glide controller.