undesirable grid.get_grid_point() behaviour

[stephenmwilkins]

grid.get_grid_point returns the closest grid point as a tuple for a specified set of values given as keyword arguments, e.g.
grid.get_grid_point(metallicity=0.01, log10age=6.)

However, the ordering of the returned tuple matches the ordering of the arguments not the actual grid axes. IMO it would be better to always return in the order of grid axes, not the ordering of the keywords.

[WillJRoper]

Good point, simple fix too.