[INSTRM-572] Track "real" pfsConfigId when taking odd and even quartz flats. Created: 17/Nov/18 Updated: 13/Aug/21 |
|
| Status: | Open |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | PFI, SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
The 2d pipeline expects to match science exposures to their flat and arc calibration exposures using their common pfsConfigId. But when taking odd and even fiber quartz exposures, half the cobras will be behind the spots so the actual configId will be wrong. Either lie about the configId, or, almost certainly better, include a card with the configId for the full field. Oh, `W_PFIDFL` or something equally ncmprhnsbl. |
| Comments |
| Comment by rhl [ 21/Mar/19 ] |
|
I'm not sure that the premise of this ticket is correct. We build flats and traces from odd/even flats and then declare them to be valid in the calibration database. So the lookup is done via visit or equivalently time stamp, not via pfsConfigId. I was expecting the cobra config to take even/odd spots to have different pfsDesignID s (and different pfsConfigID s too) |
| Comment by hassan [ 13/Aug/21 ] |
|
cloomis: I think we can close this ticket as 'wont fix', correct? It no longer makes sense as we have the FiberStatus.BLACKSPOT enumeration available in PfsConfigs. |