[DM-33659] AuxTel observing sequence for Feb 2022 run - Jira

XML

Word

Printable

Details

Type: Improvement
Status: Done
Resolution: Done
Fix Version/s: None
Component/s: ts_aos
Labels:
- AOS
- UW

Story Points:
1
Team:
Telescope and Site

Description

Propose the observing sequence for upcoming auxTel run, including needed calibration files.

Attachments

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Krzysztof Suberlak added a comment - 11/Feb/22 9:44 PM - edited

The draft notebook https://github.com/suberlak/AOS/blob/main/AOS_DM-33111_auxTel_data_reduction.ipynb. It will be updated to work on the `develop` branch of `ts_wep` once PR121 is merged, and then moved to https://github.com/lsst-ts/ts_analysis_notebooks/tree/develop/notebooks/auxtel

The ISR for November observations used collections in `LATISS/raw/all,LATISS/calib,u/czw/~~DM-28920~~/calib.20210720`, which included the following ISR settings:

isr:

        class: lsst.ip.isr.isrTask.IsrTask

        config:

          connections.outputExposure: postISRCCD

          doApplyGains: false

          doBias: true

          doBrighterFatter: false

          doCrosstalk: false

          doDark: true

          doDefect: false

          doFlat: true

          doFringe: true

          doInterpolate: true

          doLinearize: false

          doNanMasking: false

          doOverscan: true

          doVariance: false

          python: OverscanCorrectionTask.ConfigClass.fitType = 'MEDIAN_PER_ROW'

Show

Krzysztof Suberlak added a comment - 11/Feb/22 9:44 PM - edited The draft notebook https://github.com/suberlak/AOS/blob/main/AOS_DM-33111_auxTel_data_reduction.ipynb . It will be updated to work on the `develop` branch of `ts_wep` once PR121 is merged, and then moved to https://github.com/lsst-ts/ts_analysis_notebooks/tree/develop/notebooks/auxtel The ISR for November observations used collections in `LATISS/raw/all,LATISS/calib,u/czw/ DM-28920 /calib.20210720`, which included the following ISR settings: isr: class : lsst.ip.isr.isrTask.IsrTask config: connections.outputExposure: postISRCCD doApplyGains: false doBias: true doBrighterFatter: false doCrosstalk: false doDark: true doDefect: false doFlat: true doFringe: true doInterpolate: true doLinearize: false doNanMasking: false doOverscan: true doVariance: false python: OverscanCorrectionTask.ConfigClass.fitType = 'MEDIAN_PER_ROW'

Hide

Permalink

Krzysztof Suberlak added a comment - 11/Feb/22 9:53 PM - edited

Thus ideally for calibration we would have Bias, Dark, Flats. If flats are not available, then we can use the `doApplyGains` instead.

There are three ways to detect donuts, depending on the fidelity of the WCS information attached to the exposure.

1) WCS is within ~10 px - can use that directly to get sources from the reference catalog : only defocal images needed
2) WCS is within ~100 px + rotation > 6deg - too much as a starting point for astrometry : need in-focus image to run sourceDetectionTask and find WCS from astrometryTask. The donuts at defocal images are used at that positions
3) WCS is within or more than 100 px off (or not available at all) - use donut template fitting: only defocal images needed

Suggested sequence would be in-focus, extra-focal, intra-focal, similar to https://confluence.lsstcorp.org/display/LSSTCOM/2021-11-04+Aux-Tel+Night+Log . Since in cases 1) and 2) the in-focus source position is used for selecting defocal donut location, it would be ideal to minimize the telescope movement between in-focus and defocal exposures (i.e. take several in-focus+defocal sequences:

intra-focal #1, extra-focal #1, in-focus #1
intra-focal #2, extra-focal #2, in-focus #2

etc.

Rather than
intra-focal #1, intra-focal #2, intra-focal #3,
in-focus #1, in-focus #2, in-focus #3,
extra-focal #1, extra-focal #2, extra-focal #3
etc.

(unless in the latter case the pointing does not dither drastically)

Show

Krzysztof Suberlak added a comment - 11/Feb/22 9:53 PM - edited Thus ideally for calibration we would have Bias, Dark, Flats. If flats are not available, then we can use the `doApplyGains` instead. There are three ways to detect donuts, depending on the fidelity of the WCS information attached to the exposure. 1) WCS is within ~10 px - can use that directly to get sources from the reference catalog : only defocal images needed 2) WCS is within ~100 px + rotation > 6deg - too much as a starting point for astrometry : need in-focus image to run sourceDetectionTask and find WCS from astrometryTask. The donuts at defocal images are used at that positions 3) WCS is within or more than 100 px off (or not available at all) - use donut template fitting: only defocal images needed Suggested sequence would be in-focus, extra-focal, intra-focal, similar to https://confluence.lsstcorp.org/display/LSSTCOM/2021-11-04+Aux-Tel+Night+Log . Since in cases 1) and 2) the in-focus source position is used for selecting defocal donut location, it would be ideal to minimize the telescope movement between in-focus and defocal exposures (i.e. take several in-focus+defocal sequences: intra-focal #1, extra-focal #1, in-focus #1 intra-focal #2, extra-focal #2, in-focus #2 etc. Rather than intra-focal #1, intra-focal #2, intra-focal #3, in-focus #1, in-focus #2, in-focus #3, extra-focal #1, extra-focal #2, extra-focal #3 etc. (unless in the latter case the pointing does not dither drastically)

People

Assignee:: Krzysztof Suberlak

Reporter:: Krzysztof Suberlak

Reviewers:: Tiago Ribeiro

Watchers:: Andrew Connolly, Krzysztof Suberlak, Patrick Ingraham, Tiago Ribeiro

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Due:: 14/Feb/22

Created:: 11/Feb/22 9:39 PM

Updated:: 01/Mar/22 6:52 PM

Resolved:: 01/Mar/22 6:52 PM

Start date:: 11/Feb/22

Jenkins

No builds found.

Data Management