Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wrong API identified in MantidPlot #7991

Closed
OwenArnold opened this issue May 20, 2013 · 2 comments
Closed

Wrong API identified in MantidPlot #7991

OwenArnold opened this issue May 20, 2013 · 2 comments
Assignees
@martyngigg
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Release 3.1

Comments

@OwenArnold
Copy link
Contributor

During the process of converting the CalibrateRectangularDetectors algorithm to the new version of the API http://trac.mantidproject.org/mantid/ticket/7143, we encountered a bug that seems only to affect MantidPlot. The call to LoadEventNexus always seemed to revert to the old API, even when from mantid.simpleapi import * was used at the top of the script. Running the script directly in Mantid did not cause the same error. Could be down to the order of the imports in MantidPlot.
@OwenArnold
Copy link
Contributor Author

This issue was originally trac ticket 7145

@OwenArnold
Copy link
Contributor Author

http://trac.mantidproject.org/mantid/raw-attachment/ticket/7145/CalibrateRecSysTest.py
(uploaded by @OwenArnold on 2013-05-20T11:40:54)

@OwenArnold OwenArnold added High Priority An issue or pull request that if not addressed is severe enough to postponse a release. Python labels Jun 3, 2015
@OwenArnold OwenArnold added this to the Release 3.1 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@martyngigg martyngigg

Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Projects
None yet
Milestone
Release 3.1
Development

No branches or pull requests
2 participants
@martyngigg @OwenArnold