Merge branch 'splitting' of ssh://majorite/geophysics/walker/git-repos/msat into splitting
Added optional weight output to split_misfit. Still need to implement something
useful for this.
Added a basic demo for the splitting misfit calculation. This is still a work
in progress.
* Improvements to splitting misfit calculations.
- Added 'split intensity' misfit mode, and documented.
- Removed the option to return a weight (this wasn't used by any
  of the codes.)
Minor comment fixes
* Added a code to demonstrate the different misfit functions implemented
  in MS_split_misfit.m.
Make MS_measure_trace_splitting stricter

And add options to chance this and plot the
error surface. Using this version we get
reasonable results for the splitting_example
using the wavelet approach. Include
two pictures.
Trap unknown arguments

Or we loop forever.
* Improvements to splitting misfit demo.

- Added several source polarisations to demonstrate the effect of
  this on misfit functions.

- Tidied up the code.
* Added tests for the new options in MS_splitting_misfit.

- Two simple tests have been added for the 'intensity' and
  'simple' modes available to MS_splitting_misfit.
* Data overlays in MS_sphere.

- Added functionality to MS_sphere to allow P-wave velocity data to
  be overlayed on the sphere.
* Data overlay in MS_sphere.

- Added shear-wave splitting data overlay in MS_sphere.
Merge branch 'splitting' of ssh://majorite/geophysics/walker/git-repos/msat into splitting
* Splitting misfit example.

- Added decent comments to the misfit example.
* Splitting misfit example

- Added a new example script to demonstrate using MS_splitting_misfit
  to invert splitting data for the orientation of a TTI medium.
Remove duplication in MS_plot

This is in preperation to dealing with
issue #6.
Add plotmap argument to MS_pole

%     MS_plot(..., 'plotmap', pmap)
%          Change the order, or content, of the subplots. This allows a
%          single pole figure (e.g. the P-wave velocity) to be drawn, or
%          the pole figures to be drawn in a different order. The argument
%          pmap must be a cell array of strings. Each string represents a
%          different pole figure and its location in the cell array
%          represents the location of the pole figure. Thus the default
%          {'VP', 'AVS', 'AVSPOL'} draws three pole figures in a row. If
%          the argument were {'VP'; 'AVS'} two pole figures would be drawn,
%          one above the other. Valid strings are 'VP", 'AVS' and 'AVSPOL'.
%          These are not case sensitive.
Allow V_S1 and V_S2 pole figures to be drawn

Plugs into plotmap.
Working, but ugly, data plot in MS_pole

This only works for S-wave data at the
moment and needs significant cleanup. For
example use:

[C r] = MS_elasticDB('ol')
MS_plot(C, r, 'sdata', ...
    [0 90 180 270 10 100 190 280 350 80 170 260 0 90 180 270 180], ...
    [45 45 45 45 60 60 60 60 60 60 60 60 0 0 0 0 90], ...
    [90 90 90 90 0 0 0 0 0 0 0 0 90 90 90 90 90], ...
    [2 4 8 10 2 4 8 10 2 4 8 10 2 4 8 10 16], 'plotmap', {'avspol'})

arguments after 'sdata' are arrays of azi, inc, pol and magnitude,
respectivly.
Plot pdata on MS_pole

e.g. can do:
MS_plot(C, r, 'pdata', ...
    [0 90 180 270 10 100 190 280 350 80 170 260 0 90 180 270 180],...
    [45 45 45 45 60 60 60 60 60 60 60 60 0 0 0 0 90], ...
    [8 8.5 9.0 9.5 8 8.5 9.0 9.5 8 8.5 9.0 9.5 8 8.5 9.0 9.5 8], ...
    'sdata', ...
    [0 90 180 270 10 100 190 280 350 80 170 260 0 90 180 270 180], ...
    [45 45 45 45 60 60 60 60 60 60 60 60 0 0 0 0 90], ...
    [90 90 90 90 0 0 0 0 0 0 0 0 90 90 90 90 90], ...
    [2 4 8 10 2 4 8 10 2 4 8 10 2 4 8 10 16], ...
    'plotmap', {'vp' 'avspol'})