Merge pull request #99 from wzinke/no_interpolation

ENH: disabling interpolation for plot_distance_matrix
NF: added surface and volgeom properties to volsurf
Merge branch 'master' of https://github.com/PyMVPA/PyMVPA into _tent/surface_searchlight
NF: volgeom ijk2triples and triples2ijk
BF: to prevent bugs with ucasing+unicode -- flag in capital sfor ctypes

Thanks to Ceyhun Çakar for troubleshooting
DOC: Update contributor list
ENH: moved afni and i/o specific stuff from misc.surfing to support.{nibabel,afni}
Merge branch 'master' of https://github.com/PyMVPA/PyMVPA into _tent/surface_searchlight
ENH: provide export functionality for mvpa2.support.{afni,nibabel} for standalone operation. ENH: testing funcitonality in mvpa.support.afni.afni_anat_preproc.py. BF: minor bug fixes in afni_anat_preproc.py
DOC: better documentation of stats.get_triangle_vector_form. ENH: made caching dictionary private
ENH: fmri_dataset detects 5-D NIFTI files with empty 4th axis (typically generated by AFNI), squeezes to 4-D
ENH: query-engine returns a mask of selected voxels
ENH: faster implementation of surf.map_to_high_resolution_surf_slow
BF: s/gnb/knn/ in sphere_m1nnsearchlight
BF(workaround): adhocsearchlights -- do not allow partitioners changing targets

The reason is that ATM due to current implementation with "groupping" of targets and partitions
presumably for efficiency, it would be tricky, and thus not implemented.
For now at least state that in docstring and raise Exception so people do
not fall into the trap
Merge remote-tracking branch 'origin/master'

* origin/master:
  DOC: Update contributor list
BF: rng= option for Permutator so default is to use a new RandomState()

Otherwise it leads to generation of the same permutations while generating
MC distribution of searchlight performances, in fancy two-stage way
(unittests accompanies).  So from now on we should not rely on the single
np.random all around to guarantee correct operation in the child processes
BF: forgotten import for mvpa2.tests.test_usecases.test_gnbsearchlight_permutations
NF: get_random_seed -- little helper to return a random int for seeding RNG
RF: follow Tiziano's wisdom -- provide seeds to child pprocesses

This way no control over rng for every use of np.random should be needed
and RNGs would provide different sequences in different child processes.

Sideeffect:  searchlight results with nproc=1 and nproc>1 might still differ.
the only solution for that would be to provide seed values per each roi_fid
which might be a bit overkill