[PIPE2D-1333] check IIS lamps (engineering fibers) state in the lamp detection code Created: 21/Nov/23  Updated: 02/Feb/24

Status: Open
Project: DRP 2-D Pipeline
Component/s: obs_pfs
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: arnaud.lefur Assignee: price
Resolution: Unresolved Votes: 0
Labels: EngRun
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Story Points: 1
Sprint: EDR+AIT, PreEngRun15Mar

 Description   

Check IIS lamps which illuminate engineering fibers in the lamp detection code,
FITS keys are the following, (ignore the second part of the tuple)

Key('hgar', FITS=('W_ENIISH', 'ENU_IIS_HGAR')),
Key('argon',FITS=('W_ENIISA', 'ENU_IIS_ARGON')),
Key('neon', FITS=('W_ENIISN', 'ENU_IIS_NEON')),
Key('krypton',FITS=('W_ENIISK', 'ENU_IIS_KRYPTON')),
Key('halogen',FITS=('W_ENIISC', 'ENU_IIS_HALOGEN')),


 Comments   
Comment by price [ 22/Nov/23 ]

One could imagine using these to provide reference points for detectorMap adjustment of a science exposure (e.g., in the blue, where there aren’t a lot of other reference points). Is that something we’re considering? If so, I’d need to restructure things to separate the science and engineering fibers (or having the engineering fiber lamps on would make the pipeline think that it’s an arc exposure rather than sky). Otherwise, all I have to do is add them to the code that identifies lamps from the header, and if the engineering lamp is on, it is an arc exposure.

Generated at Sat Feb 10 16:06:14 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.