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

Due to an hardware issue, s1w fields are missing #7176

Closed
JeanBilheux opened this issue Dec 19, 2012 · 3 comments
Closed

Due to an hardware issue, s1w fields are missing #7176

JeanBilheux opened this issue Dec 19, 2012 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@JeanBilheux
Copy link
Contributor

This issue was originally TRAC 6330

This crash the reduction. Catch error and let the code continue

@JeanBilheux
Copy link
Contributor Author

@JeanBilheux (2012-12-19T19:43:40):
Fixed issue of missing S1W. Need to be tested by Jim. this refs http://trac.mantidproject.org/mantid/ticket/6330
d2ddd51


@JeanBilheux (2013-01-09T16:01:35):
Fixed issue of missing S1W. Need to be tested by Jim. this refs http://trac.mantidproject.org/mantid/ticket/6330
7223026


@NickDraper (2013-01-28T09:23:22):
Moved at the code freeze for release 2.4


@NickDraper (2013-04-29T09:49:55):
Moved to r2.6 at the end of r2.5


@NickDraper (2013-07-26T13:55:00):
Moved to backlog at the code freeze for R2.6


@NickDraper (2014-02-14T11:04:58):
Bulk move to assigned at the introduction of the triage step

@JeanBilheux JeanBilheux added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@JeanBilheux JeanBilheux 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
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

1 participant