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
LoadSQW will fail when loading sqw file with image not aligned with lab frame #11056
Labels
Framework
Issues and pull requests related to components in the Framework
Milestone
Comments
abuts
added
the
Framework
Issues and pull requests related to components in the Framework
label
Jun 3, 2015
The issue is actually a bit deeper as there are subtle differences in data loading procedure which generate MD workspaces slightly different from SQW workspaces. The differences should be rectified. |
The way |
martyngigg
added a commit
that referenced
this issue
Nov 26, 2015
martyngigg
added a commit
that referenced
this issue
Dec 2, 2015
martyngigg
added a commit
that referenced
this issue
Dec 2, 2015
martyngigg
added a commit
that referenced
this issue
Dec 2, 2015
martyngigg
added a commit
that referenced
this issue
Dec 2, 2015
Avoids any issues with the file changing in the future. Refs #11056
martyngigg
added a commit
that referenced
this issue
Dec 3, 2015
martyngigg
added a commit
that referenced
this issue
Dec 3, 2015
martyngigg
added a commit
that referenced
this issue
Dec 7, 2015
martyngigg
added a commit
that referenced
this issue
Dec 7, 2015
martyngigg
added a commit
that referenced
this issue
Dec 7, 2015
martyngigg
added a commit
that referenced
this issue
Dec 7, 2015
martyngigg
added a commit
that referenced
this issue
Dec 9, 2015
The underlying can memory order be specified by an enum. Refs #11056
martyngigg
added a commit
that referenced
this issue
Dec 9, 2015
martyngigg
added a commit
that referenced
this issue
Dec 9, 2015
martyngigg
added a commit
that referenced
this issue
Dec 9, 2015
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
This loads everything but the pixel data. Refs #11056
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
martyngigg
added a commit
that referenced
this issue
Dec 11, 2015
martyngigg
added a commit
that referenced
this issue
Jan 7, 2016
martyngigg
added a commit
that referenced
this issue
Jan 7, 2016
martyngigg
added a commit
that referenced
this issue
Jan 7, 2016
martyngigg
added a commit
that referenced
this issue
Jan 7, 2016
It is a bug in clang - https://llvm.org/bugs/show_bug.cgi?id=21629 Refs #11056
martyngigg
added a commit
that referenced
this issue
Jan 7, 2016
It appears the warning happens for assignment as well as initialisation. Refs #11056
Merged
martyngigg
added a commit
that referenced
this issue
Jan 7, 2016
martyngigg
added a commit
that referenced
this issue
Jan 15, 2016
This prevents the memory requirements exploding as the number of events pile up in the top box. Refs #11056
martyngigg
added a commit
that referenced
this issue
Jan 15, 2016
martyngigg
added a commit
that referenced
this issue
Feb 3, 2016
martyngigg
added a commit
that referenced
this issue
Mar 3, 2016
The dimension limit information is now read from the pax/iint fields. The Q_lab frame as also been removed as it is not a sensible choice. Refs #11056
martyngigg
added a commit
that referenced
this issue
Mar 3, 2016
This allows the caller to detector if an event was dropped from the grid box. Refs #11056
martyngigg
added a commit
that referenced
this issue
Mar 3, 2016
martyngigg
added a commit
that referenced
this issue
Mar 4, 2016
martyngigg
added a commit
that referenced
this issue
Mar 4, 2016
Conflicts: Framework/DataObjects/inc/MantidDataObjects/MDBox.h Framework/DataObjects/inc/MantidDataObjects/MDBox.tcc Framework/DataObjects/inc/MantidDataObjects/MDGridBox.h Refs #11056
martyngigg
added a commit
that referenced
this issue
Mar 4, 2016
martyngigg
added a commit
that referenced
this issue
Mar 4, 2016
martyngigg
added a commit
that referenced
this issue
Mar 9, 2016
It was ignoring the initial sign of the value and so sometimes the value would move in the wrong direction. Refs #11056
martyngigg
added a commit
that referenced
this issue
Mar 9, 2016
The MDEventWorkspace needs to know the full extent of the pixels to avoid dropping any events when reading. The only surefire way is to compute the coordinate limits from the pixels themselves. Refs #11056
martyngigg
added a commit
that referenced
this issue
Mar 9, 2016
Conflicts: Framework/DataObjects/test/MDBoxBaseTest.h Refs #11056
martyngigg
added a commit
that referenced
this issue
Mar 9, 2016
martyngigg
added a commit
that referenced
this issue
Mar 9, 2016
martyngigg
added a commit
that referenced
this issue
Mar 9, 2016
martyngigg
added a commit
that referenced
this issue
Mar 11, 2016
martyngigg
added a commit
that referenced
this issue
Mar 11, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was originally TRAC 10214
subj.
Currently LoadSQW will not load a sqw file with DND image not aligned according to "lab frame ?" coordinates (not sure the term is correct). The pixels (MD events) in SQW file are expressed in these coordinates.
The algorithm will formally work, but the result will be incorrect.
The purpose of the ticket is to modify load SQW to load data properly.
The text was updated successfully, but these errors were encountered: