[PIPE2D-389] Populate COVAR2 coarse covariance matrix Created: 09/Mar/19  Updated: 03/Jul/23

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

Type: Story Priority: Normal
Reporter: hassan Assignee: Masayuki Tanaka
Resolution: Unresolved Votes: 0
Labels: flux-calibration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by PIPE2D-74 Calculate COVAR2 entry in the pfsObje... Won't Fix
Story Points: 8
Epic Link: flux calibration

 Description   

The coarse 10x10 covariance matrix, COVAR2, of the 1-D spectrum output from the 2D DRP is defined in https://github.com/Subaru-PFS/datamodel/blob/master/datamodel.txt and is used to model the spectrophotometric errors.

As part of the flux calibration activities, generate COVAR2 and populate the corresponding pfsObject HDU with that information.



 Comments   
Comment by Masayuki Tanaka [ 11/Mar/19 ]

Could you please elaborate on this?  Covariance from what process/procedure?

Comment by rhl [ 11/Mar/19 ]

The datamodel specifies a non-sparse covariance matrix COVAR2 which is supposed to capture the large-scale behaviour of the spectrophotometry (there's also a banded covariance matrix COVAR that captures the pixel-to-pixel errors and covariances).   If we had an optical spectrograph covering grizy, then I'd think of this as a 5x5 matrix with components that roughly correspond to the e.g. <(g - <g)>)(z - <z>)> – i.e. the large scale errors in the spectrophotometry. These could come from the uncertainty in the spectrophotometric standards, from the corrections due to guiding/fibre centring errors, the mismatch between the extended object and resolve object PSFs (and thus extraction errors), and other things that I don't yet understand!

I don't have a concrete proposal for how to measure these, e.g. what is the rôle of the fibre magnitudes, but the flux calibration work seems to be the place to put this.

 The COVAR2 matrix is currently 10x10 because we have c. 5 optical photometric bands and sometimes some NIR information (J) and a factor of c. 2 oversampling seemed wise.

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