[PIPE2D-695] Scattered flux amplitude Created: 13/Jan/21  Updated: 29/Jan/22  Resolved: 20/Feb/21

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

Type: Task Priority: Normal
Reporter: ncaplar Assignee: ncaplar
Resolution: Done Votes: 0
Labels: scatter
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File summary_PIPE2D_695.png    
Issue Links:
Relates
relates to PIPE2D-783 Estimate scatter properties in SM1 Done
Story Points: 2
Sprint: 2DDRP-2021 A
Reviewers: hassan

 Description   

When doing long exposure with a lot of flux even the empty regions of the detector collect some amount of flux. JEG is very interested (conversation January 12, 2021) in how does this amount of scattered flux depend as a function of total flux on the detector.



 Comments   
Comment by ncaplar [ 20/Feb/21 ]

The main result: 1 count on average in the empty region per 2x10**9 total counts on the whole image.

The procedure used, i.e., explanation of the figure.

In the top left I show median flux in the empty region as a function of the total flux in the image. The line is the linear fit to the points with flux above 0.5x10**9. I excluded low flux points as they skew the result. The discrepancy between different arc lamps is because they use different exposure times and we do not control that absouletly perfectly. The panels on the right show the result if we don't use darks in reduction, where the ``extra flux'' is then dominated by exposure time.
In the bottom left we can see that dependence of median flux in the empty region is not strongly dependent on exposure time if we detrend with darks (although Neon is behaving somewhat oddly at exposure times of several hundred seconds.)

As such, I conclude that darks are of sufficient quality that the main effect seen in the top left panel is due to scattered light, and I report the value shown in gray dotted lines.

 

 

 

 

 

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