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

Create MoveInstrumentComponent Algorithm #1220

Closed
NickDraper opened this issue Jan 21, 2009 · 1 comment
Closed

Create MoveInstrumentComponent Algorithm #1220

NickDraper opened this issue Jan 21, 2009 · 1 comment
Assignees
@mantid-roman
Labels
High Priority An issue or pull request that if not addressed is severe enough to postponse a release.
Milestone
Iteration 15

Comments

@NickDraper
Copy link
Contributor

Parameters
- Workspace (in/out) (mandatory)
- Component Name (string)
- Detector id (integer)
- X
- Y
- Z
- Relative Position (bool) (mandatory) default yes

The algorithm will find the identified component and apply rthe change through the instrument parameter map.
@NickDraper
Copy link
Contributor Author

This issue was originally trac ticket 372

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

@mantid-roman mantid-roman

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

No branches or pull requests
2 participants
@NickDraper @mantid-roman