Animation for non 4D workspaces

[Owen Arnold]

Original message from Michael, which I've verified causes the specified issue:

"The issue revolves around viewing an MDHistoWorkspace. I've got a script that takes a MDEventWorkspace and rebins it into a MDHistoWorkspace. Upon viewing that MDHistoWorkspace, I look at the input geometry from the dataset. What I see look like default values for the dimension information instead of the expected dimension information that is already contained within the MDHistoWorkspace. My main issue is that if I take a 4D MDEW and integrate one dimension via BinMD, I should get a 3D MDHW with no time steps. However, that is not what I see. I'd like to be able to trap this condition so that the animation controls can be disabled. You can look at this by using the script in ticket #4552 and viewing the MDHW. The animation controls are still enabled in spite of the 3D nature of the MDHW since the input geometry says there are 10 time steps. "

[Owen Arnold]

Three problems identified:

• Xml creation for integrated mapped dimension. Solution is to switch to the NoPolicyChecking.
• Checking for the presence of a time dimension, but not checking to see if it is integrated or not before adding the time properties in the filter/source.
• Use of TimeStepToTimeStep mapping policy rather than TimeToTimeStep in the MDHWSource. This is just wrong and causes crash during animation for 4D workspaces.

[Owen Arnold]

refs #4564. Will fix animation + timestep bug

Changeset: 3aa081b8b9851df83e717e0d7f10f2da19069167

[Michael Reuter]

4D MDEW to rebinned/integrated 3D MDHW no longer report time steps so that the animation controls in the simple interface are disabled.

[Stuart Campbell]

This ticket has been transferred to github issue ​5411