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

Linux LoadSQW Segfault #6885

Closed
OwenArnold opened this issue Oct 30, 2012 · 1 comment
Closed

Linux LoadSQW Segfault #6885

OwenArnold opened this issue Oct 30, 2012 · 1 comment
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@OwenArnold
Copy link
Contributor

User has reported a Seg fault while trying to load an SQW file into mantid:

"Loading certain kinds of SQW file from Horace. I’ve uploaded onto Babylon5 (\olympic\Babylon5\Public\Russell Ewings\VATES) a Matlab script and the output from it where I take the SQW file that I created earlier from the output of Tobyfit (an SPE file, which you already have), and take a very narrow cut from it so that the output has only a very small number of detector pixels. I then use Horace to save this object as a new SQW file. My aim was then to read this back into Mantid and compare to a similar cut from the VATES-generated simulation. However I reliably get a segmentation violation when I try to load this particular SQW file. I suspect it is something to do with the way the SQW file was generated, i.e. not in the normal way. Perhaps you will be able to tell what the problem is by looking at the file?"

@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 6039

@OwenArnold OwenArnold added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Mantid labels Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 2.3 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Development

No branches or pull requests

2 participants