Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Story Points:4
-
Epic Link:
-
Team:Data Release Production
-
Urgent?:No
Description
Original ticket title: Investigate amp background level offsets in DECam postISRCCDs
This ticket updates the DECam ISR overscan correction config parameter fitType='MEDIAN_PER_ROW'. A large body of evidence (see comments below) point towards this being a superior approach at handling overscan corrections with DECam. This also brings Science Pipelines data processing in-line with the DECam Community Pipeline, which also fits per row.
Original ticket efforts by Kenneth Herner, original description below:
If you scroll through here, the problem is immediately apparent
https://lsst.ncsa.illinois.edu/~lskelvin/hits2014/
Hat-tip to Lee Kelvin for noticing this problem and plotting the images. This feels very familiar to when ISR order of operations was inconsistent regarding when assembleCcd happens, but I don't remember the resolution.
Possibly relevant and/or wrong: https://community.lsst.org/t/a-change-to-the-order-of-operations-for-isr/3060
Attachments
Issue Links
- relates to
-
DM-30703 Reprocess DECam HiTS data from scratch with background fixes
- Done
-
DM-33096 Enable empirical read noise calculation for DECam ISR
- Done
-
DM-35252 Add DECam config overrides into cpBias and cpFlat pipelines
- Done
-
DM-15152 crosstalk correction was moved above assembleCcd, which broke it
- Done
-
DM-30495 Troubleshoot DECam ISR failures
- Done
- split to
-
DM-33126 Investigate cpFlatNormalization level settings in DECam postISRCCD
- To Do
Activity
Labels | SciencePipelines | SciencePipelines ap-analysis |
Assignee | Meredith Rawls [ mrawls ] |
Assignee | Meredith Rawls [ mrawls ] |
Attachment | merian_bias_01.png [ 50087 ] | |
Attachment | merian_bias_35.png [ 50088 ] | |
Attachment | merian_bias_45.png [ 50089 ] |
Attachment | merian_flat_01.png [ 50158 ] |
Attachment | merian_flat_05.png [ 50159 ] |
Attachment | merian_flat_25.png [ 50160 ] |
Attachment | merian_flat_35.png [ 50161 ] |
Attachment | merian_flat_45.png [ 50162 ] |
Attachment | merian_flat_55.png [ 50163 ] |
Attachment | merian_flat_01.png [ 50158 ] |
Attachment | merian_flat_05.png [ 50159 ] |
Attachment | merian_flat_25.png [ 50160 ] |
Attachment | merian_flat_35.png [ 50161 ] |
Attachment | merian_flat_45.png [ 50162 ] |
Attachment | merian_flat_55.png [ 50163 ] |
Attachment | merian_flat_01.png [ 50164 ] | |
Attachment | merian_flat_05.png [ 50165 ] | |
Attachment | merian_flat_25.png [ 50166 ] | |
Attachment | merian_flat_35.png [ 50167 ] | |
Attachment | merian_flat_45.png [ 50168 ] | |
Attachment | merian_flat_55.png [ 50169 ] |
Assignee | Meredith Rawls [ mrawls ] |
Assignee | Meredith Rawls [ mrawls ] | Kenneth Herner [ kherner ] |
Epic Link |
|
|
Sprint | AP F21-2 (July) [ 1102 ] | |
Team | Alert Production [ 10300 ] |
Sprint | AP F21-2 (July) [ 1102 ] | AP F21-3 (August) [ 1109 ] |
Rank | Ranked higher |
Sprint | AP F21-3 (August) [ 1109 ] | AP F21-4 (September) [ 1113 ] |
Rank | Ranked higher |
Sprint | AP F21-4 (September) [ 1113 ] | AP F21-5 (October) [ 1119 ] |
Rank | Ranked higher |
Sprint | AP F21-5 (October) [ 1119 ] | AP F21-6 (November) [ 1124 ] |
Rank | Ranked lower |
Sprint | AP F21-6 (November) [ 1124 ] | AP S22-1 (December) [ 1126 ] |
Rank | Ranked lower |
Sprint | AP S22-1 (December) [ 1126 ] | AP S22-2 (January) [ 1130 ] |
Rank | Ranked lower |
Epic Link |
|
|
Sprint | AP S22-2 (January) [ 1130 ] | |
Story Points | 2 | 4 |
Team | Alert Production [ 10300 ] | Data Release Production [ 10301 ] |
Assignee | Kenneth Herner [ kherner ] | Lee Kelvin [ lskelvin ] |
Description |
If you scroll through here, the problem is immediately apparent
[https://lsst.ncsa.illinois.edu/~lskelvin/hits2014/] Hat-tip to [~lskelvin] for noticing this problem and plotting the images. This feels very familiar to when ISR order of operations was inconsistent regarding when assembleCcd happens, but I don't remember the resolution. Possibly relevant and/or wrong: [https://community.lsst.org/t/a-change-to-the-order-of-operations-for-isr/3060] |
{panel:title=update}
Original ticket title: Investigate amp background level offsets in DECam postISRCCDs This ticket updates the DECam ISR overscan correction config parameter {{fitType='MEDIAN_PER_ROW'}}. A large body of evidence (see comments below) point towards this being a superior approach at handling overscan corrections with DECam. This also brings Science Pipelines data processing in-line with the DECam Community Pipeline, which also fits per row. Original ticket efforts by [~kherner], original description below: {panel} If you scroll through here, the problem is immediately apparent [https://lsst.ncsa.illinois.edu/~lskelvin/hits2014/] Hat-tip to [~lskelvin] for noticing this problem and plotting the images. This feels very familiar to when ISR order of operations was inconsistent regarding when assembleCcd happens, but I don't remember the resolution. Possibly relevant and/or wrong: [https://community.lsst.org/t/a-change-to-the-order-of-operations-for-isr/3060] |
Issue Type | Bug [ 1 ] | Story [ 10001 ] |
Summary | Investigate amp background level offsets in DECam postISRCCDs | Switch DECam overscan correction to median per row |
Reviewers | Kenneth Herner [ kherner ] |
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Description |
{panel:title=update}
Original ticket title: Investigate amp background level offsets in DECam postISRCCDs This ticket updates the DECam ISR overscan correction config parameter {{fitType='MEDIAN_PER_ROW'}}. A large body of evidence (see comments below) point towards this being a superior approach at handling overscan corrections with DECam. This also brings Science Pipelines data processing in-line with the DECam Community Pipeline, which also fits per row. Original ticket efforts by [~kherner], original description below: {panel} If you scroll through here, the problem is immediately apparent [https://lsst.ncsa.illinois.edu/~lskelvin/hits2014/] Hat-tip to [~lskelvin] for noticing this problem and plotting the images. This feels very familiar to when ISR order of operations was inconsistent regarding when assembleCcd happens, but I don't remember the resolution. Possibly relevant and/or wrong: [https://community.lsst.org/t/a-change-to-the-order-of-operations-for-isr/3060] |
{panel:title=update Jan 2022}
Original ticket title: Investigate amp background level offsets in DECam postISRCCDs This ticket updates the DECam ISR overscan correction config parameter {{fitType='MEDIAN_PER_ROW'}}. A large body of evidence (see comments below) point towards this being a superior approach at handling overscan corrections with DECam. This also brings Science Pipelines data processing in-line with the DECam Community Pipeline, which also fits per row. Original ticket efforts by [~kherner], original description below: {panel} If you scroll through here, the problem is immediately apparent [https://lsst.ncsa.illinois.edu/~lskelvin/hits2014/] Hat-tip to [~lskelvin] for noticing this problem and plotting the images. This feels very familiar to when ISR order of operations was inconsistent regarding when assembleCcd happens, but I don't remember the resolution. Possibly relevant and/or wrong: [https://community.lsst.org/t/a-change-to-the-order-of-operations-for-isr/3060] |
Status | In Progress [ 3 ] | In Review [ 10004 ] |
Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
Resolution | Done [ 10000 ] | |
Status | Reviewed [ 10101 ] | Done [ 10002 ] |