Ticket #1669 (closed: fixed)
Create "ElasticWindow" Algorithm
Reported by: | Michael Whitty | Owned by: | Michael Whitty |
---|---|---|---|
Priority: | major | Milestone: | Iteration 25 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Michael Reuter |
Description
To perform the task of Elwin in the indirectAnalysis UI and provide a simple front end to users.
Inputs: Workspace (units in Energy transfer/mev), time range start and end, optional background range start and end
Outputs: Two workspaces of intensity / q and intensity over q2
This will replace the current Elwin PythonAlgorithm, while also giving both outputs requested, and hopefully performing better
Change History
comment:10 Changed 10 years ago by Michael Whitty
comment:11 Changed 10 years ago by Michael Whitty
comment:12 Changed 10 years ago by Michael Whitty
comment:13 Changed 10 years ago by Michael Whitty
comment:14 Changed 10 years ago by Michael Whitty
comment:15 Changed 10 years ago by Sofia Antony
comment:16 Changed 10 years ago by Michael Whitty
- Status changed from accepted to verify
- Resolution set to fixed
mark complete
comment:17 Changed 10 years ago by Michael Reuter
- Status changed from verify to verifying
- Tester set to Michael Reuter
comment:18 Changed 10 years ago by Michael Reuter
- Status changed from verifying to reopened
- Resolution fixed deleted
It looks like in the section where the background range is used that the range 1 integration values are not used to perform the integration step. Is it the intention of the algorithm that the background range and main integration range always be the same? If so, this could be handled by a check box instead of a second set of redundant parameters. Otherwise, the range 1 integration values need to be used in the background subtraction section.
comment:19 Changed 10 years ago by Michael Whitty
- Status changed from reopened to verify
- Resolution set to fixed
comment:21 Changed 10 years ago by Michael Reuter
- Status changed from verifying to closed
OK, now it looks like everything is in order with this algorithm.
comment:22 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 2516