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

Instrument geometry loads incorrectly for duplicate sample log values #7606

Closed
stuartcampbell opened this issue Mar 21, 2013 · 1 comment
Closed
Assignees
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone

Comments

@stuartcampbell
Copy link
Collaborator

This was noticed on HYSA. The msd log value affects the incident flight path (L1), if the raw data file has more than one value of msd at exactly the same time then a zero is used for the value of msd when the geometry is loaded.

If we modify the time of one of the values by even a very small amount (e.g. 1e-6) then it all works fine.

HYSPECA runs 18497 and 18498 have this issue.

If you look at the log values from within MantidPlot then all looks ok.

@stuartcampbell
Copy link
Collaborator Author

This issue was originally trac ticket 6760

@stuartcampbell stuartcampbell added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Mantid labels Jun 3, 2015
@stuartcampbell stuartcampbell self-assigned this Jun 3, 2015
@stuartcampbell stuartcampbell added this to the Release 2.5 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

1 participant