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.

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

PythonAlgorithms: Error from WorkspaceFactory.create when fed output from other Python algorithm #7997

Closed
martyngigg opened this issue May 21, 2013 · 3 comments
Assignees
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@martyngigg
Copy link
Member

This issue was originally TRAC 7151

James Lord has spotted:


I have a simple algorithm (attached) to add a linear correction to the data in a workspace. It's fine with a freshly loaded run file but fails with a strange error if I run it on the output of "ConjoinSpectra()":

Error in execution of algorithm Apply2DLinearCorrection:
__class__ assignment: 'MatrixWorkspace' object layout differs from 'MatrixWorkspace'
 at line 18 in 'C:/MantidInstall/UserAlgorithms/Apply2DLinearCorrection.py'

What's wrong? The offending line is simply
                ows=WorkspaceFactory.create(iws)
as I want a copy of the workspace with the same axis labels, number of bins, etc.

(I was actually using my hacked version of ConjoinSpectra which makes the Y (spectrum) axis numeric, for doing 2D plots, and which I'll upload to the Script Repository soon, but have reproduced the same behaviour with the standard one)

James Lord.

And also

Follow up to this: if I feed the offending workspace from ConjoinSpectra() through Transpose() I can now run my algorithm on it successfully, so that seems to clear up the different object layout or whatever. I haven't done a thorough search of which algorithms cause or cure this bug.
@martyngigg
Copy link
Member Author

@martyngigg (2013-07-15T08:46:45):
Batch move to 2.7


@NickDraper (2014-02-14T11:04:59):
Bulk move to assigned at the introduction of the triage step

@martyngigg martyngigg added the Framework Issues and pull requests related to components in the Framework label Jun 3, 2015
@martyngigg martyngigg self-assigned this Jun 3, 2015
@stale
Copy link

stale bot commented Feb 24, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. If you feel this is incorrect please comment to keep it alive, with a reason why.

To prevent closure, e.g. for long-term planning issues, add the "Never Stale" label.

@stale stale bot added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Feb 24, 2021
@stale
Copy link

stale bot commented Mar 3, 2021

This issue has been closed automatically. If this still affects you please re-open this issue with a comment so we can look into resolving it.

@stale stale bot closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Framework Issues and pull requests related to components in the Framework Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Development

No branches or pull requests

1 participant