Ticket #5410 (closed: fixed)
MUON: Fix crash when opening period data as the current run.
| Reported by: | Robert Whitley | Owned by: | Robert Whitley |
|---|---|---|---|
| Priority: | major | Milestone: | Release 2.2 |
| Component: | Mantid | Keywords: | |
| Cc: | anders.markvardsen@… | Blocked By: | |
| Blocking: | Tester: | Peter Parker |
Description
At the moment the current run for EMU is period data. When trying to load this using the muon interface Mantid crashes.
This doesn't happen if you load the period data using the browse button or entering the run number manually.
Change History
comment:2 Changed 8 years ago by Robert Whitley
Refs #5410. Add check to see if period data.
Changeset: c69d052e112010ea9e3d83e0e1492359a1f442ca
comment:4 Changed 8 years ago by Robert Whitley
- Status changed from accepted to verify
- Resolution set to fixed
comment:5 Changed 8 years ago by Robert Whitley
Refs #5410. Add check to see if period data.
Changeset: c69d052e112010ea9e3d83e0e1492359a1f442ca
comment:6 Changed 8 years ago by Robert Whitley
Refs #5410. Add check to see if period data.
Changeset: c69d052e112010ea9e3d83e0e1492359a1f442ca
comment:7 Changed 8 years ago by Peter Parker
- Status changed from verify to verifying
- Tester set to Peter Parker
Note: See
TracTickets for help on using
tickets.
When loading current data the run number isn't known and a search through the workspace's run details has to be done. Now that it is period data it stores the periods in separate workspaces under one group. Currently this group is named the same as the workspace when using non-period data. This causes a problem because Mantid can't make a matrix workspace pointer point to a group workspace and find its run details.