Set recursion depth for top level split to 1

[AntonPiccardoSelg]

Original ticket here

For testing:
You can find the necessary python script here

You need the data set SXD23767.nxs which can be found in the trainging pack.
Run the script. This should produce the workspaces Split and No_Split.

Test for workspace with top level splitting

1. Open the data set Split into the VSI.
   • Confirm that the recursion depth entry of the source shows 1
   • Confirm that the recursion depth is actually 1. Change it to 5 - you should see a difference (finer granularity)

Test for workspace without top level splitting

1. Open the data set No_Split into the VSI.
   • Confirm that the recursion depth entry of the source shows 5
   • Confirm that the recursion depth is actually 5. Change it to 1 - you should see a difference (coarser granularity).

[OwenArnold]

Could you please add something to the release notes about these changes. Probably to bug fixes http://www.mantidproject.org/ReleaseNotes_3_5_UI_Changes

[AntonPiccardoSelg]

Added information regarding these changes to the release notes

[OwenArnold]

Functionally correct. Some refactoring changes proposed.

[AntonPiccardoSelg]

Refactored the check for top level splitting. The refactored function is directly called from within MDEWSource and ViewBase. In the former case we are not going through the presenter, as this is a generic interface for both MDEvent- and MDHisto-based sources, whereas the recursion depth is only applicable for MDEvent-based sources.

[AntonPiccardoSelg]

• Changed the include guards
• Changed the unit test for MDEvent data with top level splitting

[AntonPiccardoSelg]

RHEL6 build issue seems to be a gcc4 issue