Ticket #3201 (closed: fixed)
PlotAsymmetryByLogValue issues
| Reported by: | Nick Draper | Owned by: | Anders Markvardsen |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 29 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Roman Tolchenov |
Description
reported by James Lord
The following bug seems to be reproducible (with HiFi muon data at least): start MantidPlot (I'm using 1.28.11227, Windows XP) execute algorithm "PlotAsymmetryByLogValue". Select data files. from the drop-down box of log values select one that is not numeric (eg. run_start, or in HiFi data Field_X_Ready) click OK MantidPlot crashes with a Windows "MantidPlot has encountered a problem and needs to close" box.
While trying to reproduce this with some EMU data (which had 2 periods) I got a more sensible error in the Results Log pane saying something like <log value> does not exist or is not numeric - but I did crash MantidPlot twice, perhaps by other bugs?
Normally plotting versus a non-numeric parameter doesn't make sense but I was using this as a short cut to extract the non-numeric logs from a large number of runs to see if they corresponded at all to some odd features in the data. Time of day may have been useful (likely to be related to the temperature of the instrument and its detectors, and presence of users).
Also - the drop down box fills in the log values available from the last-used starting run when the dialog opens and then adds in extra log values from the newly entered run, leaving all the old ones there as well (including duplicates). This is noticeable when changing between instruments, or data taken with different sample environment.
Change History
comment:2 Changed 9 years ago by Anders Markvardsen
- Status changed from new to accepted
To test, in ISIS, e.g. open HIFI data from
hifi\data, and select as log e.g. 'nspectra'. Try also to swap between say argus and emu and log file updated
comment:3 Changed 9 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to fixed
For the bit:
Normally plotting versus a non-numeric parameter doesn't make sense but I was using this as a short cut to extract the non-numeric logs from a large number of runs to see if they corresponded at all to some odd features in the data. Time of day may have been useful (likely to be related to the temperature of the instrument and its detectors, and presence of users).
a separate ticket #3225 has been created.
comment:4 Changed 9 years ago by Roman Tolchenov
- Status changed from verify to verifying
- Tester set to Roman Tolchenov
(In [12780]) In PlotAsymmetryByLogValues
1) display message when loading none numeric log for single period muon data 2) also improved when swapping between data 'log-combobox' updated appropriately
re #3201