Ticket #6530 (closed: duplicate)
SANS: allow gui to load time sliced event data directly
Reported by: | Anders Markvardsen | Owned by: | Gesner Passos |
---|---|---|---|
Priority: | critical | Milestone: | Release 3.1 |
Component: | SANS | Keywords: | SANS |
Cc: | anders.markvardsen@… | Blocked By: | #7221, #7635 |
Blocking: | Tester: | Roman Tolchenov |
Description (last modified by Gesner Passos) (diff)
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.
Attachments
Change History
comment:3 Changed 7 years ago by Gesner Passos
Add EventSlicing widget to deal with ISIS SANS event slicing
re #6530
Changeset: 9c0d158b8c04596ea6eacc701403f0b74aead4c7
comment:4 Changed 7 years ago by Gesner Passos
Extend SANSRunWindow to deal with EventSlicing widget
re #6530
Changeset: bd29f62c975e4b33a23e028f13684eef10e5dd3a
comment:5 Changed 7 years ago by Gesner Passos
Extend SANS Batch mode to support slicing events
re #6530
Changeset: d3acb83353d00d4f0a4c2da8bff9f8d9d81fc771
comment:6 Changed 7 years ago by Gesner Passos
Extend SANSRunWindow to support event slicing for Batch Mode
re #6530
Changeset: 8189e75ff3d4dceaa22cacada376ab7f1cb332fd
comment:7 Changed 7 years ago by Gesner Passos
Extend SANSRunWindow to support Event Slices for SingleMode
re #6530
Changeset: b8281f65a09aba315723246763e7bd3430e26264
comment:8 Changed 7 years ago by Gesner Passos
- Keywords SANS added
- Cc anders.markvardsen@… added
- Description modified (diff)
- Blocked By 6711 removed
- Summary changed from SANS: allow gui to load event data directly to SANS: allow gui to load time sliced event data directly
Changed 7 years ago by Gesner Passos
- Attachment Kinetic_plot.pdf added
The result given by the scientist
comment:9 Changed 7 years ago by Gesner Passos
Tester:
To test the default procedure, do the following:
- Open SANS INTERFACE (Menu->Interfaces->SANS ISIS)
- Change the instrument to SANS2D
- Load the MaskFile: Masksans2d_125O_4m_12mm_Brooks
- Change to BatchMode
- Load the ​event_mode.csv file
- Under the EventSlicing groupbox, write the following at the lineEdit: 0-30,5000-10000
- Run 1D Reduce
- As a result, you will have: 17523_batch_t0.0_t30.0_rear, 17523_batch_t5000.0_t10000.0_rear
- The same result you should see changing to SingleMode and executing Run 1D Reduce, but the names will be: 17523rear_1D_1.75_16.5_t0_t30, 17523rear_1D_1.75_16.5_t5000_t10000
- The files are found at cycle_12_5 (SANS2D instrument)
Plot both results (with errors), and change the axes to log(x)/log(y). You will see the same result reported from the scientist:
The attached plot shows that as time increases the intensity of the curve should decrease and a ‘bump’ should appear at high Q (the black line is the 1st 30 seconds and the red line 5000 to 10000 seconds).
comment:10 Changed 7 years ago by Gesner Passos
Correct the issue of applying slice to Batch mode
re #6530
Changeset: 84cb0527006ddd465d60689b9d05b6dd7e38dac0
comment:11 Changed 7 years ago by Gesner Passos
Disable temporarily the test to reload to allow the Batch mode
re #6530
Changeset: 0e415b95da1d1304a8457948f9ff48a1bf8e41dc
comment:12 Changed 7 years ago by Gesner Passos
Disable Event Slicing for LOQ data
currently, LOQ does not have event mode data. It is useless (and may confuse) let the widget available to users.
re #6530
Changeset: 75d49bc76c2bfd806723c0ed76004f505382db49
comment:13 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.5 to Release 2.6
comment:19 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to the Backlog after R2.6
comment:20 Changed 7 years ago by Gesner Passos
- Description modified (diff)
- Milestone changed from Backlog to Release 3.0
comment:23 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.0 to Backlog
Moved out to backlog as not enough time in R3.0
Changed 7 years ago by Gesner Passos
- Attachment SANS2d_event_to_hist_4.py added
Richard offered his scripts being used to slice and rebin event data.
comment:25 Changed 7 years ago by Gesner Passos
- Status changed from new to verify
- Resolution set to duplicate
8545
comment:28 Changed 7 years ago by Roman Tolchenov
- Status changed from verify to verifying
- Tester set to Roman Tolchenov
comment:29 Changed 7 years ago by Roman Tolchenov
- Status changed from verifying to closed
It is a duplicate of 8545. This ticket's branch was deleted without merging.
comment:30 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 7376