Date
Attendees
Meeting agenda:
- News & announcements.
- Updates on ground-testing Dark frame data & 1/f noise.
- Activities on each instrument branch (all).
- Closing remark
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
1. News & announcements | Everyone | ||
20min | 2. Updates on ground-testing Dark frame data & 1/f noise | ||
NIRISS. | |||
NIRSpec. Unknown User (birkmann) pointed Diane Karakla and Tony Keyes to how to get the data. Diane Karakla summarized her search for the data on the OTIS campaign/data. This morning she got some data from the archive — she's getting more data than she was requesting to the database; she's trying to make sense of this data. Unknown User (birkmann) mentions the fact that for the smallest subarrays, the correlation might be between columns, and in this case perhaps the 1/f noise reduction might be better on a moving-average basis rather than on a column-by-column. This is something to study as well. | |||
MIRI. Sarah Kendrew reached out to Mike Reagan about this — and it appears 1/f is a smaller concern over there than for the close NIR. Unknown User (birkmann) suggests this is because of the ASIC feature — given MIRI does not use this, then 1/f noise is not such a big issue. | |||
NIRCam. Currently compiling the data they have on NIRCam. One detail is that analyses have been done on full frame only. | |||
30min | 3. Activities on each instrument branch (all) | ||
NIRISS activities. Discussion on uncertainties on the ephemerides (especially for eclipses, where eccentricity and argument of periastron might be a problem). | |||
NIRSpec activities. There are some concerns about the total duration of the visit. Should be a discussion point on the next meeting. | |||
MIRI activities. There is a good discussion on very long exposures. There seems to be some limitations we might need to discuss/understand. Jira ticket: . Should be a discussion point on the next meeting. | |||
NIRCam activities. Nikolay Nikolov has been doing some tests on limits on the wavelength limits for the 1D extraction for the pipeline. However, when you have a multi-segment TSO — the time-series is fine in terms of time-stamps. However, when you run it through the pipeline, and you check the time-stamps, the second segment does not continue from the first segment. This might be a TSO3 issue, but not sure yet; doing some checks right now. These segments are "artificial" from the data-creation side, which are made so you don't work with very large data volumes. | |||
5min | 4. Closing remarks of the meeting | ||