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

TOSCA finds bad nexus files in archive search #10828

Closed
mantid-builder opened this issue Jul 24, 2014 · 3 comments
Closed

TOSCA finds bad nexus files in archive search #10828

mantid-builder opened this issue Jul 24, 2014 · 3 comments
Assignees
Labels
Indirect/Inelastic Issues and pull requests related to indirect or inelastic Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@mantid-builder
Copy link
Collaborator

This issue was originally TRAC 9986

Original Reporter: Samuel Jackson

Reported by Stewart Parker. When searching for the run 9426 from the archive for TOSCA it finds a .nxs file, but the file is in a bad format. However, if you use the .raw file instead it works fine.

~~One solution would be to force TOSCA to use .raw files instead.

Best approach here would be to follow Nick's advice in the first comment:

I disagree with the approach on this one. If the Nexus file is "bad" then it should be removed from the archive, or recreated correctly. Talk to Freddie Akeroyd about this if this is the case.

@mantid-builder
Copy link
Collaborator Author

@NickDraper (2014-07-25T09:46:21):
I disagree with the approach on this one. If the Nexus file is "bad" then it should be removed from the archive, or recreated correctly. Talk to Freddie Akeroyd about this if this is the case.


@NickDraper (2014-12-08T10:25:36):
Moved to the backlog at the code freeze of R3.3


@NickDraper (2015-04-27T08:10:34):
Moved to R3.5 at the R3.4 code freeze

@mantid-builder mantid-builder added the Indirect/Inelastic Issues and pull requests related to indirect or inelastic label Jun 3, 2015
@mantid-builder mantid-builder added this to the Release 3.5 milestone Jun 3, 2015
@DanNixon DanNixon assigned ElliotAOram and unassigned DanNixon Jul 30, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@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
Indirect/Inelastic Issues and pull requests related to indirect or inelastic 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

6 participants