Ticket #5310 (closed: fixed)
New python is not completely overwriting the old one in MantidPlot
Reported by: | Martyn Gigg | Owned by: | Martyn Gigg |
---|---|---|---|
Priority: | major | Milestone: | Release 2.1.1 |
Component: | Mantid | Keywords: | PatchCandidate,Released |
Cc: | Blocked By: | ||
Blocking: | Tester: | Anders Markvardsen |
Description
Change History
comment:3 Changed 8 years ago by Martyn Gigg
- Status changed from accepted to verify
- Keywords PatchCandidate added
- Resolution set to fixed
comment:4 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.1.1
Moved for inclusion in the 2.1.1 patch
comment:5 Changed 8 years ago by Martyn Gigg
Make sure new Python API overwrites old in MantidPlot. Refs #5310 (cherry picked from commit 14bdf82e785dff055e9f8a2110de61d463dcba31)
Changeset: 8aecc17d9571c50bac914c59d51edb0aa4611048
comment:6 Changed 8 years ago by Anders Markvardsen
- Status changed from verify to verifying
- Tester set to Anders Markvardsen
comment:7 Changed 8 years ago by Anders Markvardsen
- Status changed from verifying to closed
To test I did
- loaded GEM38370_Focussed_Legacy.nxs
- renamed this ws to 'k'
- executed the following python
ws = mtdk?
det = ws.getDetector(2)
print det.getTwoTheta(V3D(0,0,0), V3D(0,0,1))
which returned the number 0.61133...
This would have failed previously but is now passing OK
Note: See
TracTickets for help on using
tickets.
Make sure new Python API overwrites old in MantidPlot. Refs #5310