-
Notifications
You must be signed in to change notification settings - Fork 122
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
Support for multiple detectors in MDNormSXD #73
Conversation
* Start to functionalise the algorithm * Follow coding standard for member variables names Refs #10470
This gives a speed gain ~80% Refs #10470
This avoids 2 loops over the same data. Also, the non-HKL dimension values don't change with each intersection so only copy them over once. Refs #10470
For workspaces with grouped detectors it now only considers the first one from the group in the main loop but calculates the intersections using the whole group. Refs #10470
Conflicts: Code/Mantid/Framework/MDAlgorithms/inc/MantidMDAlgorithms/MDNormSXD.h Code/Mantid/Framework/MDAlgorithms/src/MDNormSXD.cpp Refs #10470
Conflicts: Code/Mantid/Framework/MDAlgorithms/src/MDNormSXD.cpp Refs #10470
Unfortunately it gives errors. I am updating the script and files in the dropbox so you can test it. The detectors are not grouped at all in the MDdata or solidAngle. I get
|
ExperimentInfo throws if no mappings are defined. Refs #10470
It should be fixed now. |
retest this please |
1 similar comment
retest this please |
The code is not doing what is supposed to. If I group the detectors in big enough chunks (say 256x256 spectra in TOPAZ per spectrum) only a few trajectories appear in the MD data (as expected), but the normalization contains all detectors, and not only where the group is |
Could you send me the script that you're testing with? |
The method is most often called in a loop so floods the log messages. Refs #10470
retest this please |
…sxdnorm Support for multiple detectors in MDNormSXD
Fixes issue #10470
Tester: The usage tests here but with grouping added to the data step should now work