...
- Allows for subTasks within Tasks, ie: logical groupings of TaskProcesses into a subTask
- Such a subTask could conditionally depend on status of 'sibling' TaskProcesses within it's Parent Task
- And TaskProcesses within parent Task could depend on the 'sibling' child Task or upon the TaskProcesses contained within said child Task
- Every Task (including subTasks) can have many implementations (formerly called runs)
- Every TaskProcess can have many instances per implementation of it's parent Task (formerly called TPInstances, of which only one instance could occur per implementation of it's parent Task)
- A TaskProcess (or subTask) can depend on the conditional completion of one or all of another TaskProcess or subTask instances.
- Igor presents the notion that parallel TPInstances may want to inter-communicate. Judement is reserved on the issue.
Additional Notes:
- Dan has requested a new Oracle username/tablespace, GLAST_DP_TEST, on GLASTP
- Dan has created a new CVS package, Pipeline, initially with a subdirectory, DB, containing the most current Pipeline I DB schema and stored procedures definition files