Ticket #4077 (closed: fixed)
LoadEventNexus needs to set X boundaries even if no events are loaded
Reported by: | Russell Taylor | Owned by: | Russell Taylor |
---|---|---|---|
Priority: | minor | Milestone: | Release 2.0 |
Component: | Mantid | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: | Jose Borreguero |
Description
LoadEventNexus outputs an EventWorkspace with 1 bin, where boundaries are set to the smallest and largest TOF values within the events loaded. Internally, the algorithm starts out setting these values to very large and very small values respectively - these values remain in the resulting workspace if no events are loaded.
I got bitten by this on an MPI run, where if you split up the jobs by bank it's quite possible that some banks will have no events. In [9e1f6b01] a check was added to ConvertUnits which made things fail in this case.
Change History
comment:2 Changed 9 years ago by Russell Taylor
The ticket took longer to write than the fix. Re #4077.
Changeset: 71c598d4d96a5b3734255ae4640026af1572e6bc
comment:3 Changed 9 years ago by Russell Taylor
- Status changed from accepted to verify
- Resolution set to fixed
comment:4 Changed 9 years ago by Russell Taylor
The ticket took longer to write than the fix. Re #4077.
Changeset: 71c598d4d96a5b3734255ae4640026af1572e6bc