Screen Shot 2020-12-30 at 12.10.32.png
[INSTRM-1151] Add an obvious indicator of the optical bench thermal stability Created: 06/Jan/21 Updated: 15/Jan/22 |
|
| Status: | Open |
| Project: | Instrument control development |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | arnaud.lefur | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | SPS | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
Screen Shot 2020-12-30 at 12.10.32.png
|
| Story Points: | 3 |
| Sprint: | SM1PD-2020 N, SM1PD-2021 A 12 |
| Description |
|
While red shutter was pulled off from SM1, the SCR temperature got an huge gradient which was big enough to affect the thermal stability of the optical bench(see attached plot). |
| Comments |
| Comment by rhl [ 07/Jan/21 ] |
|
eric: we'll add some display to the PFS gui to make it obvious to the user that the data being taken is going to be bad, but we can imagine that this'll happen during routine PFS operations so we'd like a way to tell Gen2 that PFS is safe, but that the data shouldn't be used for science. How would you like to handle this? We don't think that STS is the right answer, unless we add a category, as it isn't an emergency. |
| Comment by eric [ 07/Jan/21 ] |
|
It would be best if a keyword could be written in to the FITS header, the way HSC does with the T_PURPOS keyword. That way it can be detected way downstream in the data flow. Gen2 checks FITS keywords and could pop up an audio and/or visual warning in the alarm handler.
|