[PIPE2D-335] Provide dichroic transmission curves Created: 07/Feb/19  Updated: 08/Mar/19  Resolved: 01/Mar/19

Status: Done
Project: DRP 2-D Pipeline
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0

Type: Task Priority: Normal
Reporter: hassan Assignee: Kiyoto Yabe
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

For the R/B/N arm merging exercise (PIPE2D-316), dichroic transmission curves need to be prepared.


Issue Links:
Blocks
blocks SIM2D-99 Build blue-arm data in simulator Done
blocks PIPE2D-316 Demonstrate arm merging Done
Story Points: 2
Epic Link: Arm merging
Sprint: 2019 B
Reviewers: price

 Comments   
Comment by cloomis [ 07/Feb/19 ]

All such reference data are curated by Kiyoto Yabe, from both designs and measured elements.

drp_instdata has {{data/dichroics/}, which contains the measured values from Winlight (? has French column names). But I do not believe we should be using those directly: I added them without going through Yabe-san.

Comment by hassan [ 07/Feb/19 ]

Issue re-assigned to Kiyoto Yabe to provide official reference data.

Comment by rhl [ 08/Feb/19 ]

Aren't these in the ETC? We need to make sure that we are using the identical curves. Actually, of course, they should be in some product that both SIM2D and ETC use – but it may not be worth implementing that now.

Comment by cloomis [ 09/Feb/19 ]

ETC (spt_ExposureTimeCalculator) does not break out the individual components of the final throughput (detector QE, camera optics, dichroic, fibers, telescope, etc). There are columns for some of these, but they are all 1.0.

Comment by Kiyoto Yabe [ 10/Feb/19 ]

PO has not determined yet whether/when we should replace the current dichroic transmission in ETC to the actual measurement. So, I think we should use the same curve as ETC for now. I will try to push the data to the repository.

Comment by price [ 01/Mar/19 ]

Rebased and merged to master at Kiyoto Yabe's request.

Generated at Sat Feb 10 15:51:22 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.