NEWFEATURE: get_cut_coords(...) function to heuristically compute good cross-sectional cut_coords (see demo in localize_glm_ar.py)
ENH: in plot_map, optional cut_coords=None and cut_coords='auto' merged
TEST: test for get_cut_coords(...) feature
FIX: fixed misleading docstring (see bertrand's comments on PR #280)
FIX: fixed misleading docstring (see bertrand's comments on PR #280)
FIX: local merge conflict
Merge pull request #280 from dohmatob/master

NF: get_cut_coords(...) function to heuristically compute good cross-sectional cut_coords

In the plot_map(...) API, if cut_coords='auto' is specified and sliceris one of 'x', 'y', 'z', then a series of 'cross-sectional' cut_coords is generated and used (similar to FSL activation maps).

localizer_glm_ar.py demo script now uses this feature