| DRP | | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
| key | DLP-493 |
|---|
|
| W16 | Pool and/or scatter/gather below top-level driver. |
| DRP | | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
| key | DLP-523 |
|---|
|
| Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
| key | DLP-483 |
|---|
|
| W18 | Detailed pipeline parallelization and distribution systems. We anticipate that the middleware ported from HSC (see short term requirements description, | Jira |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
| key | RFC-68 |
|---|
|
, | Jira |
|---|
| showSummary | false |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
| key | DM-2983 |
|---|
|
), or equivalent home-grown LSST functionality, will provide adequate parallelization and distribution capabilities for the next 2-3 years of development. However, we do not imagine that this middleware will be deployed into production. Instead, production pipeline topology will depend on the results of ongoing and upcoming algorithmic development as well as hardware procurement and the processing control middleware capabilities which will be developed as part of 02C.07.We foresee the definition of this system as being the result of continued discussion between the interested parties. DRP will stand ready to provide input to these discussions in the form of descriptions of potential processing topologies that suit our algorithmic requirements, with the level of detail and confidence increasing with time, culminating in the finalized interfaces described in DLP-523 and DLP-483. |
| AP | | Jira |
|---|
| server | JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 9da94fb6-5771-303d-a785-1b6c5ab0f2d2 |
|---|
| key | DLP-263 |
|---|
|
| S16 | The full focalplane background modeling will need access to the scatter/gather APIs. |