Ticket #8848 (closed: invalid)

Opened 7 years ago

Last modified 5 years ago

Check SANS reduction with different time regimes

Reported by: Gesner Passos Owned by: Peter Parker
Priority: critical Milestone: Release 3.4
Component: SANS Keywords:
Cc: peter.parker@… Blocked By: #8931
Blocking: #8921 Tester: Nick Draper

Description

Richard will provide some data to check if the reduction works correct with monitors having more time channels.

Attachments

allow_run_simulation_data_reduction.patch (2.4 KB) - added by Gesner Passos 7 years ago.

Change History

comment:1 Changed 7 years ago by Gesner Passos

  • Blocking 8921 added

comment:2 Changed 7 years ago by Gesner Passos

First of all, Richard provided a simulated data created by Freddie using the new detector and the new time regime.

Changed 7 years ago by Gesner Passos

comment:3 Changed 7 years ago by Gesner Passos

  • Blocked By 8931 added

comment:3 Changed 7 years ago by Gesner Passos

  • Blocked By 8931 removed

The file is in Babylon in Freddie's folder, and it is SANS2D800024183.nxs (It just add the log to the file Freddie created).

To allow the file to go through it was necessary to apply the patch allow_run_simulated_data_reduction.patch.

Two issues were raised here:

1 - #8906 problem in getting the monitors by guessing its path 2 - The need of a definition of the time channels to Rebin the data and get sensible results.

The purpose of having more time channels for the monitor is that when they are to be normalized in wavelenght, the data in the monitors and the data in the detectors will be compatible (wavelenght depends on the TOF and the geometry). Hence, what is important, is to keep the monitors as they are till the conversion to wavelenght.

The process will be the following:

1 - Allow the users to specify the binnings for the event mode data - #8931. 2 - Ensure that NormalizeToMonitor and TransmissionCalc will be working correctly using the Monitors with more time channels.

comment:4 Changed 7 years ago by Nick Draper

  • Status changed from new to assigned

Bulk move of tickets out of triage (new) to assigned at the introduction of the triage state

comment:5 Changed 7 years ago by Gesner Passos

  • Blocked By 8931 added

comment:6 Changed 7 years ago by Gesner Passos

Peter: By having #8931 implemented, you will probably be able to close this one as well.

comment:7 Changed 7 years ago by Nick Draper

  • Owner changed from Gesner Passos to Peter Parker

Ownership handed over to Peter

comment:8 Changed 6 years ago by Peter Parker

  • Priority changed from major to critical

comment:9 Changed 6 years ago by Peter Parker

  • Milestone changed from Release 3.2 to Release 3.3

comment:10 Changed 6 years ago by Peter Parker

  • Milestone changed from Release 3.3 to Release 3.4

comment:11 Changed 5 years ago by Peter Parker

  • Status changed from assigned to verify
  • Resolution set to invalid

Feedback from the scientists in today's catchup meeting was that this ticket is now redundant. Closing.

comment:12 Changed 5 years ago by Nick Draper

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

comment:13 Changed 5 years ago by Nick Draper

  • Status changed from verifying to closed

comment:14 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 9692

Note: See TracTickets for help on using tickets.