Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DetectorEfficiency needs to average over the number of detectors within each spectrum #5346

Closed
martyngigg opened this issue Jan 13, 2012 · 2 comments
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@martyngigg
Copy link
Member

The algorithm currently corrects each spectrum by an efficiency factor based on the detector geometry of each contributing pixel within the group. For instruments where the number of pixels per group is different across the instrument you see a different overall correction for some parts of the instrument vs others.

See image attached of MERLIN. The shortubes are hardware grouped at 8:1 per spectrum whereas the long tubes are 4:1. The final pattern shows the obvious error in the region around the beam.

@martyngigg
Copy link
Member Author

This issue was originally trac ticket 4499

@martyngigg
Copy link
Member Author

@martyngigg martyngigg added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Mantid labels Jun 3, 2015
@martyngigg martyngigg self-assigned this Jun 3, 2015
@martyngigg martyngigg added this to the Release 2.0 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

No branches or pull requests

1 participant