Anders-Markvardsen
commented
9 years ago This issue was originally trac ticket 8860
Closed Anders-Markvardsen closed 9 years ago
Anders-Markvardsen
commented
9 years ago This issue was originally trac ticket 8860
Anders-Markvardsen
commented
9 years ago http://trac.mantidproject.org/mantid/raw-attachment/ticket/8860/emu00030604.nxs (uploaded by @Anders-Markvardsen on 2014-02-04T09:19:18)
http://trac.mantidproject.org/mantid/raw-attachment/ticket/8860/emu00034997.nxs (uploaded by @Anders-Markvardsen on 2014-02-04T09:19:34)
http://trac.mantidproject.org/mantid/raw-attachment/ticket/8860/emu_192_grouping.xml (uploaded by Arturs Bekasovs on 2014-02-28T11:24:15)
This ticket is blocked by :
Steve have come across a case that we may not have tested/considered before that is loading: same instrument data in succession where the number of histogram varies.
Make muon interface handle this according to Steve's email below:
There seems to be a new problem with the grouping in the Muon Analysis interface. When loading a run with x histograms and then a run with y histograms, the group table is not updated correctly when the second run is loaded if x
<>y and the interface becomes unusable. Try this with the attached files … 30604 has 192 histograms and 34997 has 96 histograms. Load 30604 and create four groups, 1: 1-48, 2: 49-96, 3: 97-144, 4: 145-192, and a two pairs (1-2) and (3-4). All works fine. Now try and load the second file and there’s an error ‘Unable to group loaded workspace’ … if the number of histograms has changed the previous grouping should be abandoned. In fact, you still end up with all the groups showing, so I’m not sure what’s going on inside at this stage (which probably explains why it seems to stop working). I got into trouble with this bug earlier today going the other way, i.e. I loaded a run with 32 detectors and then a run with 96 detectors … it carried over the grouping from the first run to the second which made the data look very strange.