- Sarah Kendrew
- Brian Brooks
- Arpita Roy
- Leonardo Ubeda
- Diane Karakla
- Loic Albert
- Stephan Birkmann
- Tony Keyes
- Nikolay Nikolov
- News & announcements.
- Oulier detection algorithm
- Labour schedule for 2021
- Updates on ongoing work per branch
1. News & announcements
2. Outlier detection algorithm
The step is part of calwebb_tso3, supposed to flag cosmic rays. This ste should identify cosmic rays or other outliers that were missed by the jump_step in stage 1 of the pipeline.
The algorithm is flagging a lot of in-transit pixels. NE discovered that although the docs says the step is using a "custom algorithm for TSOs" this is not the case.
Proposed solution is what Nikolay Nikolovdeveloped for HST data, using a "difference image filter". Use the time series of slope images to construct a master difference image. Using the master difference image, then identify outlier pixels using spatial median. Uses only 3 parameters: number of images before & after to create master diff image; the box size for spatial median; the sigma level to mark outliers.
What in case of glancing CRs that cause a trail? NN uses detector rows or columns (direction along dispersion) instead of pixel boxes.
How handle HGA move jitter? NN did see residuals in the HST data from thermal breathing pointing variations so again this was mitigated by looking at entire detector rows/columns (dispersion direction). SK - should put in some kind of mitigation in teh algorithm until we know what these pointing variations will look like.
In the case of steep flux decline (short sudden transit), could the algorithm erroneously flag pixels due to this? NN - yes that is a risk, though depends on the thresholds we set for detection & shoudl be driven by the data.
What should the algorithm do with the outliers? NE- was long discussion in the CalWG and ultimately should be the job of the next step (extraction) to "do something". The outlier_detection step should just flag the pixels.
What is required for moving forward? Should test and approve.
Kendrew and Nikolov will work on a python version of the function for testing purposes.
|30min||3. Labor schedule for 2021|
See Espinoza's slides for estimate of deadline and timelines for various tasks. These deadlines are self-imposed so please provide feedback or speak up if not achievable.
Plans for a transiting exoplanet ERS bootcamp in the summer.
Major work item is the 1/f noise.
Non-linearity impact: for Q3 of the fiscal year (starting ~ April)
High efficiency modes: this requires community input, so is scheduled around the time of the ERS bootcamp. If this science push for it is sufficient then we can work it in the project for implementation in cycle 2.
Difference imaging pipeline: Nikolov the natural person to work on this bc of past experience with HST. But will require testing for all instruments.
Action to all: please check with your other branch duties to assess feasibility of this work? Share with branch manager as needed. Please flag any concerns in next 2 weeks - Nestor will reach out.