Ticket #9062 (assigned)
FakeWorkspace2DFromPeaks for SCD testing
Reported by: | Owen Arnold | Owned by: | Owen Arnold |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | Diffraction | Keywords: | |
Cc: | Blocked By: | #9374 | |
Blocking: | Tester: |
Description
A very useful algorithm, which I think we are missing would be to generate TOF peaks on top of a workspace generated by load instrument. Inputs would be a PeaksWorkspace and a IDF. This could be used in Unit tests, as well as in many other locations for testing and as part of the development cycle. One of the benefits of this approach are that you could create reasonably sized workspaces around very large instruments such as WISH.
Change History
comment:1 Changed 7 years ago by Stuart Campbell
- Status changed from new to infoneeded
- Owner changed from Anyone to Owen Arnold
comment:2 Changed 7 years ago by Owen Arnold
- Status changed from infoneeded to new
Hmm. Good question. We have an algorithm created by Janik which does something slightly more primitive for MDWorkspaces called FakeMDEventData, so in keeping with that, a good name might be FakeWorkspace2DFromPeaks - Open to suggestions.
comment:3 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
- Summary changed from Useful Algorithm for SCD testing to FakeWorkspace2DFromPeaks for SCD testing
comment:4 Changed 7 years ago by Owen Arnold
Spoke to Roman about the possibility of using different Peak functions to generate the fake peaks. He suggests that for the Peak functions, we only need to specify the PeakFunction and the Width (FWHM) as inputs. The rest of the information can be determined by the Peak Intensity (if present) and the peak position.
comment:7 Changed 6 years ago by Owen Arnold
I cant do this until there is a way to generate a PeakFunctionMD on a MatrixWorkspace. In order to Create a 2D peak function on a MatrixWorkspace, the iterators will need to use the MatrixWorkspace NearestNeighbour map.
comment:9 Changed 6 years ago by Nick Draper
- Milestone changed from Release 3.2 to Backlog
Moved to Backlog at the code freeze of release 3.2
comment:10 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 9905
What would be an appropriate name for this algorithm?