Time | Item | Who | Notes |
---|---|---|---|
5min | 1. News & announcements | Everyone |
|
20min | 2. Activities on each instrument branch | ||
NIRISS activities. Nestor Espinoza mentions his work on re-visiting target for NIS-034. Not decided yet, but have some candidates. Sarah Kendrew asks why not use an eclipsing binary (EB); Nestor Espinoza answers that the overall plan is to test the instrument for SOSS's niche, which will be transiting exoplanets. The latter also provide a much simpler analysis of the physical signal (EBs might have extra out-of-transit signals, you have to deal with two limb-darkened stars, etc.). Overall, he mentions that as long as the team does its due diligence (don't ask to observe targets which will be observed by other teams), and select targets with the very worst prospects for transmission spectroscopy, then that's OK. The point is to not sneak any science, but of course one can only do so good (even for EBs). | |||
NIRSpec activities. No TSO-related activities so far. | |||
MIRI activities. We had a meeting with the MIRI ramps-to-slopes group, which goes all around the MIRI consortium (US+Europe); led by Jane Morrison. They have been worried about detector issues at large. MIRI detectors have some important behavior that one has to take care of. One of the examples was first and last frame for MIRI, which is not used in non-TSO observations; but for TSO observations is being used by the pipeline. For relative measurements, this seems okay. But if you want absolute flux calibration, including the last frame impacts on this as this one drops down, so you bias your slopes. The ETC does drop the last frame (so not consistent with the pipeline). Might want to request the ETC to change this (which would increase SNR a bit). Everyone agrees on doing this. | |||
NIRCam activities. Brian Brooks starting to work on task 3.1 of FY2021 plan. There is a WG that actually has information on this; in particular, this WG was tasked with compiling information on the ground testing data and their objective (i.e., popylating the Z_GOAL keyword). This in theory is in MAST, but you need sign-offs from Scott Friedmann + leads of the data in order to retrieve the data — other than that, data is accessible. From the NIRCam side, however, they still have data stored internally, so it is possible to compile TSO-like data. Tony Keyes mentions that NIRSpec has also a lot of data internally, although not sure how much of that was retained. Nikolay Nikolov mentions that, in general, it appears they don't have data from subarrays, but just using the full frame to cut subarrays works for our analyses. Nikolay Nikolov also mentions work he has been doing with Nestor Espinoza and Sarah Kendrew on some TSO Helpdesk tickets. All being covered by the team! | |||
30min | 3. FY2021 work | ||
Everyone |
| ||
5min | 5. Closing remarks of the meeting |
|