Ticket #5774 (assigned)
Ensure Input/Output Properties are consistent for LoadLiveData
Reported by: | Stuart Campbell | Owned by: | Stuart Campbell |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | Framework | Keywords: | ADARA |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
The LoadLiveData algorithm was only looking for properties called InputWorkspace and OutputWorkspace.
This has been modified so that for the processing step, if there is not a InputWorkspace property, then the first input workspace property will be used,
There are a couple of outstanding issues:
- Decide what should be done for the output workspace property
- Do we need to do something similar for post processing ?
This is mentioned in a TODO section at LoadLiveData.cpp:192.
Change History
comment:2 Changed 8 years ago by Stuart Campbell
refs #5773 & #5774. Add logic for selecting InputWorkspace Property.
If there is not a property called InputWorkspace, then we will use the first input workspace property.
Changeset: 771fa05cf97d734b4dc1c1443bbcd722a091b813
comment:3 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to milestone 2.4
comment:4 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:7 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to backlog at the code freeze for R2.6
refs #5773 & #5774. Add logic for selecting InputWorkspace Property.
If there is not a property called InputWorkspace, then we will use the first input workspace property.