COMP: Remove "MeshContourSegmentation" CLI until tests are fixed.

* As discussed, considering the output of the module isn't reliably tested
on the different platforms, while working on the coming 4.1 release,
it has been decided to disable the module.

* Not willing to keep code that's note compiled and tested in the
repository, this one has been *removed*. Before doing so, note that
the corresponding code has been extracted and pushed into
a repository on Slicer github organization accessible using the
following URL:

  http://github.com/Slicer/MeshContourSegmentation

* When the issue will be fixed. There are two options:
  - Create an extension
  - Revert that commit and apply the bug fixes.

* It's important to consider that at some point in time the code
of the module has been moved from:

      Applications/CLI/SparseFieldLevelSetContour  (a)

   into

      Modules/CLI/SparseFieldLevelSetContour       (b)

   and then renamed into

      Modules/CLI/MeshContourSegmentation          (c)


  The current extraction will only consider the history following (c).

* Here are the step executed to be able to extract the code from the
main repository:

 1) Install git subtree module.
      - Clone https://github.com/apenwarr/git-subtree
      - Run install.sh
      - See also http://ruleant.blogspot.com/2011/04/git-subtree-module.html

 2) Create locally a bare repo that will host the extracted code
    cd ~/Projects
    mkdir MeshContourSegmentation && cd MeshContourSegmentation && git init --bare && cd..


 3) Proceed to the extraction

     git checkout master
     git subtree split --prefix=Modules/CLI/MeshContourSegmentation/ -b MeshContourSegmentation


  5) Push topic into bare repo previously created

    git remote add local-MeshContourSegmentation file:///home/jchris/Projects/MeshContourSegmentation
    git push local-MeshContourSegmentation MeshContourSegmentation:refs/heads/master

  5) After you created a project on github, push.

    cd ~/Projects/MeshContourSegmentation
    git remote add origin git@github.com:Slicer/MeshContourSegmentation.git
    git push origin master

git-svn-id: http://svn.slicer.org/Slicer4/trunk@19788 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: Remove empty directory. Using git-svn option --rmdir would avoid this commit.

git-svn-id: http://svn.slicer.org/Slicer4/trunk@19789 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: Disable "MRIBiasFieldCorrection" CLI until tests are fixed.

It resumes the windows 64-bit test associated with MRIBiasFieldCorrection are
failing for now quite some time.

The incriminated test are the following:

  MRIBiasFieldCorrection_N3_Brain2D_1 http://slicer.cdash.org/testDetails.php?test=1284620&build=13977

and

   MRIBiasFieldCorrection_N4_Brain2D: http://slicer.cdash.org/testDetails.php?test=1284621&build=13977

From mailing list archive [1]:

  MRIBiasFieldCorrection -- Probably just remove this one N4ITKBiasFieldCorrection does a much better job.

[1] http://massmail.spl.harvard.edu/public-archives/slicer-devel/2011/006988.html

git-svn-id: http://svn.slicer.org/Slicer4/trunk@19790 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: Focus on Slicer warnings by reducing ITKv3 warning level from 3 to 2

git-svn-id: http://svn.slicer.org/Slicer4/trunk@19791 3bd1e089-480b-0410-8dfb-8563597acbee
STYLE: Changed number of default EM iterations to speed up EMSegmenter without Atlas - request of Ron; BUG: Removed atlas test from windows platform and added 2 input channel test; BUG: Removed compiler warning messages; BUG: N4 did not work correctly with multiple input channels; TYLE: Changed Error to Warning so that test pass

git-svn-id: http://svn.slicer.org/Slicer4/trunk@19792 3bd1e089-480b-0410-8dfb-8563597acbee
BUG: Changed code to remove warning messages; BUG: Changed test to adopt to new default settings

git-svn-id: http://svn.slicer.org/Slicer4/trunk@19793 3bd1e089-480b-0410-8dfb-8563597acbee
COMP: consistently pass chosen compilers to sub-builds
Merge branch 'master' of github.com:Chaircrusher/Slicer