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

IntegrateMDHistoWorkspace, account for number of events #12475

Closed
1 task done
OwenArnold opened this issue Apr 28, 2015 · 1 comment
Closed
1 task done

IntegrateMDHistoWorkspace, account for number of events #12475

OwenArnold opened this issue Apr 28, 2015 · 1 comment
Assignees
Labels
Framework Issues and pull requests related to components in the Framework High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Vates
Milestone

Comments

@OwenArnold
Copy link
Contributor

This ticket is blocked by :

Thus far, the contribution to each output bin is based on overlap with input bins. The fraction overlap is calculated, and used to assign a weight, which the signal and error_sq of each contributing bin is multiplied through by. I have not accounted for the number of pixels. Clearly the number of events from contributing bins needs to be accounted for.

After discussion with scientists (namely Andrei) on this, it would seem that the best way to handle this is to simply multiply the n_events from each contributing bin by the weight and assign the output to the n_events array in the output workspace. MDHisto workspace already have the n_events array concept, so we merely need to sum (n_events * weight) for each contributing bin.


Keywords: vates

@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 11637

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

No branches or pull requests

1 participant