Ticket #149 (closed: fixed)
Create an Instrument Data Service (IDS)
Reported by: | Nick Draper | Owned by: | Laurent Chapon |
---|---|---|---|
Priority: | major | Milestone: | Iteration 9 |
Component: | Keywords: | ||
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
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.
Change History
Note: See
TracTickets for help on using
tickets.