Ticket #2380 (closed: fixed)
Mockups for fitting tab for MuonAnalysis interface
| Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 29 |
| Component: | MantidPlot | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Stuart Campbell |
Description
Create Balsamiq mockups with Muon instrument scientists for analysis tab for MuonAnalysis interface
Change History
comment:3 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 28 to Iteration 29
Bulk move of tickets at the end of iteration 28
comment:4 Changed 9 years ago by Anders Markvardsen
Mockup created in two step. Copy of 'final' version can be found Documents\Design\Mockups\muon\Fitting-tab.bmml
comment:6 Changed 9 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to fixed
Note: See
TracTickets for help on using
tickets.
In the context of creating these Balsamiq mockups also take into considering the following comment by Francis:
"This needs to match the way a level crossing musr experiment actually progresses to be usable for typical experiments involving large multipoint scans. In an experiment involving a field scan the user want to observe a plot that evolves as new field points are taken in a sequence up to and including the current run. Currently the whole sequence has to be respecified and reanalysed each time, which is very slow and inefficient when sequences may consist of many tens or hundreds of runs. The musr convention is that run zero is the current run, therefore if a run sequence starting at run 21700 is specified as say 21700-0, then this means that the wanted sequence comprises all runs from 21700 up to and including the current run . An intelligent version of PlotAsymmetrybyLogValue should have a ‘replot sequence’ button that should recognise the additional new points since the last plot iteration and analyse these runs and add them to the asymmetry table and remake the plot. The whole sequence should only really be reanalysed from scratch if a parameter such as the binning range or grouping is changed."
I.e. to what extend should the current PlotAsymmetryByLogValue functionality be used by the MuonAnalysis interface and with what improvements to these.