Ticket #491 (closed: fixed)
Understand separation of LoadDAE and UpdateDAE
| Reported by: | Martyn Gigg | Owned by: | Roman Tolchenov |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 24 |
| Component: | Keywords: | ||
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Peter Peterson |
Description (last modified by Nick Draper) (diff)
Is there a reason why LoadDAE cannot just run itself in a loop instead using UpdateDAE to do this?
Please explain this to Nick
Change History
comment:2 Changed 11 years ago by Nick Draper
- Milestone changed from Iteration 17 to Iteration 18
Moved as part of iteration end
comment:3 Changed 11 years ago by Nick Draper
- Milestone changed from Iteration 18 to Iteration 19
Moved as part of iteration 18 end
comment:4 Changed 11 years ago by Nick Draper
- Milestone changed from Iteration 19 to Iteration 20
Moved as part of the end of Iteration 19
comment:5 Changed 11 years ago by Nick Draper
- Owner set to Roman Tolchenov
- Status changed from new to assigned
- type changed from enhancement to task
- Description modified (diff)
comment:7 Changed 10 years ago by Roman Tolchenov
- Status changed from assigned to testing
- Resolution set to fixed
comment:8 Changed 10 years ago by Nick Draper
- Status changed from testing to verify
Moved to verify state
comment:9 Changed 10 years ago by Peter Peterson
- Status changed from verify to verifying
- Tester set to Peter Peterson
comment:10 Changed 10 years ago by Peter Peterson
- Status changed from verifying to closed
Since the ISIS beam is down for a long shutdown during the testing phase and the DAE cannot be accessed from offsite I am closing the ticket based on a review of the code itself. See #1539 for documentation work that was discovered while reviewing this code.
comment:11 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 1339
Note: See
TracTickets for help on using
tickets.
Batch move of tickets to Iteration 17