[DAMD-109] Include pfsConfig elements in pfsArm Created: 09/Mar/21 Updated: 10/Mar/21 Resolved: 10/Mar/21 |
|
| Status: | Won't Fix |
| Project: | Data Model |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Normal |
| Reporter: | price | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
It would be helpful to have a subset of elements from the pfsConfig in the pfsArm. Most important are targetType and fiberStatus, but we may as well include everything from the DESIGN table part of pfsConfig. This should be stored in memory as a pfsConfig, but with empty flux columns. |
| Comments |
| Comment by price [ 10/Mar/21 ] |
|
This was proposed as a means to easily line up pfsArm and the important pfsConfig elements, but |