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.

Sign up for GitHub

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

Jump to bottom

Use all runs in FindPeaksMD #11843

Closed
VickieLynch opened this issue Feb 2, 2015 · 1 comment
Closed

Use all runs in FindPeaksMD #11843

VickieLynch opened this issue Feb 2, 2015 · 1 comment
Labels
Framework Issues and pull requests related to components in the Framework
Milestone
Release 3.4

Comments

@VickieLynch
Copy link
Contributor

This ticket is blocks : TRAC11056

From SNS user: After I merge md workspace using the following command, I obtained the mdqsamp.

mdqsamp=MergeMD(mdqsampparts)

If I use FindpeaksMD to get peaks, only the first run of all merged runs is used to find peak. Is it a bug in the algorithm? Ideally we should get peaks from all runs.

Line from FindPeaksMD that should loop over runs:

  ExperimentInfo_sptr ei = ws->getExperimentInfo(0);
@VickieLynch VickieLynch added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@VickieLynch VickieLynch added this to the Release 3.4 milestone Jun 3, 2015
@VickieLynch
Copy link
Contributor Author

This issue was originally trac ticket 11004

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Framework Issues and pull requests related to components in the Framework
Projects
None yet
Milestone
Release 3.4
Development

No branches or pull requests
1 participant
@VickieLynch