[PIPE2D-255] Modify ingestion to include the pfsConfigId Created: 17/Oct/17 Updated: 17/Oct/17 Resolved: 17/Oct/17 |
|
| Status: | Done |
| Project: | DRP 2-D Pipeline |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | rhl | Assignee: | rhl |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
It is currently possible to read/write a pfsConfig file once you know the pfsConfigId and dateObs, but you cannot get this information while reading a pfsArm file. The simplest solution is to include the pfsConfigId in the registry (arguably this is the correct solution too!) |