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

Create an Instrument Data Service (IDS) #997

Closed
NickDraper opened this issue May 28, 2008 · 1 comment
Closed

Create an Instrument Data Service (IDS) #997

NickDraper opened this issue May 28, 2008 · 1 comment
Milestone

Comments

@NickDraper
Copy link
Contributor

Instruments should be ‘Owned’ by a data service (IDS) in a similar way to Workspaces.

The Load Instrument Algorithm should check that a suitable intstrument has not already been loaded with the data service before loading it fresh.

Also we need to add a fuinction to an Intrument (or workspace) to create an unique copy of the instrument for this workspace. This would:
- Copy the existing instrument to a new one (all the way down the tree)
- Register the new instrument into the IDS
- Clear the IDS when the framework manager clear command occurs
- Check that all new workspace creations in all algorithms pass on the reference to the instrument as appropriate.

@NickDraper
Copy link
Contributor Author

This issue was originally trac ticket 149

@NickDraper NickDraper added this to the Iteration 9 milestone Jun 3, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant