Ticket #6531 (closed: duplicate)

Opened 8 years ago

Last modified 5 years ago

SANS: allow gui to load time sliced event data directly

Reported by: Anders Markvardsen Owned by: Gesner Passos
Priority: critical Milestone: Release 2.5
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Nick Draper

Description

This ticket follows #6530.

The details of this ticket of may change with further feedback from instrument scientists.

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

Attachments

SANS2d_event_to_hist_4.py (5.8 KB) - added by Gesner Passos 8 years ago.
Richard offered his scripts being used to slice and rebin event data.

Change History

comment:1 Changed 8 years ago by Anders Markvardsen

From meeting today with sans inst scientists.

  1. Until told otherwise time slicing must only be applied to data specified in the Scattering-Sample input box (top left hand corner input file)
  1. 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

  1. 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.
  1. 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

comment:2 Changed 8 years ago by Gesner Passos

  • Priority changed from major to critical

Changed 8 years ago by Gesner Passos

Richard offered his scripts being used to slice and rebin event data.

comment:3 Changed 8 years ago by Gesner Passos

Note the trick used (around line 47) to avoid losing precision on the values of the time since the start of the run.

comment:4 Changed 7 years ago by Gesner Passos

  • Status changed from new to accepted

comment:5 Changed 7 years ago by Gesner Passos

  • Status changed from accepted to verify
  • Resolution set to duplicate

I was implementing this ticket on #6530. And I had have some commmits... So I will deal with it there, and I'm marking this one as duplicate. Sorry for the confusion. Now thre previous #6530 became #6928.

comment:6 Changed 7 years ago by Nick Draper

  • Status changed from verify to verifying
  • Tester set to Nick Draper

comment:7 Changed 7 years ago by Nick Draper

  • Status changed from verifying to closed

approved

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 7377

Note: See TracTickets for help on using tickets.