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

PeakIntegration: option not to limit by Run Number #5343

Closed
mantid-builder opened this issue Jan 13, 2012 · 1 comment
Closed

PeakIntegration: option not to limit by Run Number #5343

mantid-builder opened this issue Jan 13, 2012 · 1 comment
Assignees
@VickieLynch
Labels
Low Priority Things that you don't ever want to be done.
Milestone
Release 2.1

Comments

@mantid-builder
Copy link
Collaborator

Original Reporter: @jzikovsky

It might also be nice to have an option to NOT restrict by run number; maybe two runs were at the same goniometer setting but different temperature and you want to compare.

As a more general note, your code relies on the PeaksWorkspace to be sorted by run number, which is not guaranteed.
@mantid-builder
Copy link
Collaborator Author

This issue was originally trac ticket 4496

@mantid-builder mantid-builder added Low Priority Things that you don't ever want to be done. Mantid labels Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 2.1 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@VickieLynch VickieLynch

Labels
Low Priority Things that you don't ever want to be done.
Projects
None yet
Milestone
Release 2.1
Development

No branches or pull requests
2 participants
@VickieLynch @mantid-builder