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

Allow ExtractSingleSpectrum to work with the spectumNum as well as with workspaceNum #9841

Closed
abuts opened this issue Feb 12, 2014 · 3 comments
Closed

Allow ExtractSingleSpectrum to work with the spectumNum as well as with workspaceNum #9841

abuts opened this issue Feb 12, 2014 · 3 comments
Assignees
@abuts
Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@abuts
Copy link
Member

abuts commented Feb 12, 2014

This issue was originally TRAC 8998

and make this amendment to the reduction.

as current reduction has to assume that workspaceIndex = SpectrumID-1 ant this is not always correct.
@abuts
Copy link
Member Author

abuts commented Feb 14, 2014

@NickDraper (2014-02-14T11:07:58):
bulk move to assigned at the into of the triage step

@abuts abuts added Low Priority Things that you don't ever want to be done. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@abuts abuts self-assigned this Jun 3, 2015
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@stale
Copy link

stale bot commented Mar 3, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abuts abuts

Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abuts