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

PythonAlgorithm history bug #8228

Closed
martyngigg opened this issue Jun 28, 2013 · 3 comments
Closed

PythonAlgorithm history bug #8228

martyngigg opened this issue Jun 28, 2013 · 3 comments
Labels
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 7382

class SimulateMuonData(PythonAlgorithm):
        def PyInit(self):
                self.declareProperty("Instrument","HIFI",doc="Instrument to simulate")
                self.declareProperty(WorkspaceProperty("OutputWorkspace","",Direction.Output),"Simulated Data")
                self.declareProperty(lots of other parameters to describe sample, etc)

        def PyExec(self):
                InstName=self.getProperty("Instrument").value
                ws = CreateSimulationWorkspace(InstName,(0.0,BinWidth,BinWidth*NBins))
                for h in range(ws.getNumberHistograms()):
                        for j in range(NBins):
                                ws.dataY(h)[j]=...
                                ws.dataE(h)[j]=...
                self.setProperty("OutputWorkspace",ws)

It does work, however...

When I look at the History of the output workspace it only contains the CreateSimulationWorkspace call and no reference to SimulateMuonData - and therefore no record of all the other parameters I used.

@martyngigg
Copy link
Member Author

@NickDraper (2013-07-26T13:55:01):
Moved to backlog at the code freeze for R2.6


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

@stale
Copy link

stale bot commented Feb 28, 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 28, 2021
@stale
Copy link

stale bot commented Mar 7, 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 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

4 participants