[INSTRM-1164] Incorporate DCB collimator change to the beam config date Created: 21/Jan/21 Updated: 29/Jan/21 Resolved: 29/Jan/21 |
|
| Status: | Done |
| Project: | Instrument control development |
| Component/s: | ics_ccdActor, ics_hxActor |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | cloomis | Assignee: | cloomis |
| Resolution: | Done | Votes: | 0 |
| Labels: | SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Story Points: | 1 | ||||||||||||
| Description |
|
Add new DCB collimator change date keyword to W_SBEMDT beam config change date. This would also add a FITS card for the DCB config. |
| Comments |
| Comment by cloomis [ 29/Jan/21 ] |
|
Our single-date scheme is breaking down a bit. We currently have beamDate = latest(fpaDate, slitDate, gratingDate). Adding the dcbDate(s) would add churn to SMs which are not using a DCB. The spsActor tracks the light source for each SM; this ticket's logic should, I think, only use one of the the dcbDates if a DCB is connected. We are fine with using the single dcbDate for a few more weeks.... Is there something like a sps.smLight=PFI,PFI,DCB2,None key? |
| Comment by cloomis [ 29/Jan/21 ] |
|
Merged at 72643d2 |