SANS Gui to slice Event mode data

[Gesner Passos]

This ticket with #8535 will implement what was required in #6530. I'm opening a new ticket because the commits for that ticket were abandoned, and would cause confusion.

Add the right of the the Multi-period tick box a input text box for a user to specify time slicing.

If this input text box is filled, and a user has specified an event data set, time-slice the event data

Report from meeting with sans inst scientists.

Until told otherwise time slicing must only be applied to data specified in the Scattering-Sample input box (top left hand corner input file)

Suggest is on the 'Run Numbers' tab to have the interface

Have a tick box called 'Time slicing' to the right of 'Multi-period' tick box, which if clicked allows the following lines on the 'Run Numbers' tab

From (sec) to (sec) Events (muA)

Whole file: 0.0 246.0 46

Input time range: 3.0 12.0 1.32

If slice range selected so small that either over less than one frame of data or less than 0.01 muA of neutrons counted then pop up a warning window telling the user about this, and ignore this reduction, but otherwise continue as normal. The latter is important when processing a batch file.

When time slicing is used add to the end of the workspace name _t3.0_12.0, where in this example 3.0 is the from time and 12.0 is the to time

Richard offered his scripts being used to slice and rebin event data. And pointed the trick used (around line 47) to avoid losing precision on the values of the time since the start of the run.

[Gesner Passos]

Tester: follow the instructions in ​http://trac.mantidproject.org/mantid/ticket/6530#comment:9.

Besides, it is worth checking that the results are the same expected using the script that the user provided.

[Gesner Passos]

Here is how to check the results:

• Execute the file: ​http://trac.mantidproject.org/mantid/attachment/ticket/6530/SANS2d_event_to_hist_4.py

• change to single mode, and change the sample for: SANS2D00017523_003.nxs

• Run the reduction

• compare the result 3rear_1D_1.75_16.5 with the output 17523rear_1D_1.75_16.5_t5000.00_T10000.00.
• change the sample to SANS2D00017523_001.nxs
• compare the result with 17523rear_1D_1.75_16.5_t0.00_T30.00

[Gesner Passos]

Besides, this ticket speaks about having a GUI to provide slicing capabilities.

Change the sample to 17523 and press Load.

You will open this GUI by pressing the pushbutton: Time slicing inside the SANS Interface.

It will open a GUI that will allow you to slice workspaces, and it will tell you the charge in the original workspace and inside the sliced one.

The combobox will allow you to select any event workspace. The labels will tell you the charges and the time of the experiment. You will be able to select limits from/to and by clicking in apply, you will create a workspace sliced. The output workspace is a histogram workspace.

[Gesner Passos]

Tester, there is one issue with this GUI, that after applying the slices it ends up showing histograms workspaces. This issue was raised in the ticket #8558. And the correction of that error will fix this issue here. Hence, don't bother in it.

[Gesner Passos]

It seems to have lost the commits against this ticket. Follow this link to check what was done:

​https://github.com/mantidproject/mantid/compare/feature;8545_gui_to_slice_data

[Peter Parker]

Merge remote-tracking branch 'origin/feature/8545_gui_to_slice_data'

Full changeset: ​f14717bc3c28e53e9666e75d2dcb3cdb789186ae

[Stuart Campbell]

This ticket has been transferred to github issue ​9389