Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: validate_drp
-
Labels:None
-
Story Points:0.25
-
Epic Link:
-
Team:SQuaRE
Description
Adapt validate_drp to run on new obs_lsstCam package.
1. [x] Add 'detector' to list of CCD names in validate_drp.utli.getCcdKeyName
2. [x] Check that this works through running on obs_lsstCam data, which
I think that's it.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Risk Score | 0 |
Status | To Do [ 10001 ] | In Review [ 10004 ] |
Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
Resolution | Done [ 10000 ] | |
Status | Reviewed [ 10101 ] | Done [ 10002 ] |
Description |
Adapt validate_drp to run on new obs_lsstCam package.
1. [ ] Add 'detector' to list of CCD names in {{validate_drp.utli.getCcdKeyName}} 2. [ ] Chack that this works through running on obs_lsstCam data, which I think that's it. |
Adapt validate_drp to run on new obs_lsstCam package.
1. [x] Add 'detector' to list of CCD names in {{validate_drp.utli.getCcdKeyName}} 2. [x] Check that this works through running on obs_lsstCam data, which I think that's it. |
Quick review.
This is a trivial one-line change to add 'detector' to the list of equivalent Ccd Key Names to the code in validate_drp loading that needs to figure out how to assign a unique integer identifier to the object send to multiMatch. The new obs_lsstCam packages makes this easy with the detector name. I just added that along with the 'ccd', 'ccdname', 'camcol', etc.
I used this to analyze DESC Data Challenge 2 Run-1.2p-test data and it works there.
It passes Jenkins (which doesn't actually have any test that would use 'detector' explicitly, but at least it doesn't break existing things):
https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/28316/pipeline