Ticket #5434 (assigned)
Extend functionality of outline="yes" in IDF
Reported by: | Anders Markvardsen | Owned by: | Karl Palmen |
---|---|---|---|
Priority: | minor | Milestone: | Backlog |
Component: | MantidPlot | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
During demo with Rob Bewley of tube (PSD) calibration script it was highlighted that when outline="yes" then:
- calibration is not visible in the instrument view since any calibration of pixel positions along a tube is ignored, which is confusing when calibrating an instrument. Also for any user and instrument scientist looking at data it is not clear from visual inspection if a dataset is calibrated
This ticket is to investigate if it is possible to keep the acceleration achieved by using outline="yes" while allowing the pixels along a tube to not be equally spaced along the tube and that the individual tube lenghts can reflect the actually calibrated lenght of a tube
Change History
comment:1 Changed 8 years ago by Anders Markvardsen
- Status changed from new to assigned
- Owner set to Karl Palmen
comment:2 Changed 8 years ago by Karl Palmen
I note that this applies only to the 3D view of the instrument. If a 2D view is selected, then calibration is visible.
comment:3 Changed 8 years ago by Anders Markvardsen
Could you update the wiki www.mantidproject.org/IDF to explain in more detail the effect of outline in instrument view and that it in only applies to 3D view please
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:7 Changed 8 years ago by Karl Palmen
This ticket has been changed to minor, because the desired effect can be got by viewing the instrument in 2D view (cyclindrical Y) and this has been documented in the wiki page.
It may be worth investigating possible improvement of the way tube length is obtained for the 3D view with the aim of using calibrated instrument rather than base instrument.
comment:8 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to release 2.4
comment:9 Changed 8 years ago by Karl Palmen
- Milestone changed from Release 2.4 to Release 2.5
Do we still need this?
comment:12 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to the Backlog after the code freeze for R2.6
comment:13 Changed 7 years ago by Nick Draper
- Status changed from new to assigned
bulk move to assigned at the into of the triage step
comment:14 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 6280
To get started ask Roman - he is the expert