This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
uc:uc20221206_december_6_2022 [2022/12/06 21:29] nchanove |
uc:uc20221206_december_6_2022 [2022/12/06 22:25] (current) nchanove |
||
---|---|---|---|
Line 12: | Line 12: | ||
* BYU - nothing to report | * BYU - nothing to report | ||
* JHU - nothing to report | * JHU - nothing to report | ||
- | * Washington - Eric recently had a new user asking about our TOO policies and discovered that it is challenging or impossible to find that information on the APO web site - Nancy took the action to make sure that the TOO policy is findable on the web site (also investigate site search issue) and that any links from the APO web site to the TDAWG report point to the new(er) wiki, docu-wiki | + | * Washington - Eric recently had a new user asking about our TOO policies and discovered that it is challenging or impossible to find that information on the APO web site - Nancy took the action to make sure that the TOO policy is findable on the web site (also investigate site search issue) and that any links from the APO web site to the TDAWG report point to the new(er) wiki, docu-wiki |
* Oklahoma - nothing to report (by email) | * Oklahoma - nothing to report (by email) | ||
* Georgia State - nothing to report | * Georgia State - nothing to report | ||
Line 70: | Line 70: | ||
=== KOSMOS update === | === KOSMOS update === | ||
- | We recently discovered an issue with the bias levels on KOSMOS. In a small number of images, there is a change of bias level during readout of an image. This occurs in both amplifiers and there are bias variations by row, but not always all the way across a given row, i.e. not always into the overscan. We are currently investigating how often it occurs, and for what percentage of those times it is not possible to fix the problem with the overscan. There may be a pattern where it occurs early in night but not clear yet. Looking at some approaches. Ultimately | + | We recently discovered an issue with the bias levels on KOSMOS. In a small number of images, there is a change of bias level during readout of an image. This occurs in both amplifiers and there are bias variations by row, but not always all the way across a given row, i.e. not always into the overscan. We are currently investigating how often it occurs, and for what percentage of those times it is not possible to fix the problem with the overscan. There may be a pattern where it occurs early in night but that is not clear yet. Ultimately |
---- | ---- | ||
Line 76: | Line 76: | ||
=== Q4 3.5m scheduling === | === Q4 3.5m scheduling === | ||
- | Have 2 open dates coming soon Dec 13B (brightish) and Dec 16B (grey), also Dec 17B - requested, and then some dark slots (short, but still 4 hrs since long nights) on 27-29, 31 Dec (5 slots total, 2 requests received so far). No schedule update until finish | + | We have two open dates coming |
- | + | ||
- | + | ||
- | Regarding the remainder of the OPEN/DD time in Q4, Nov 15B will be assigned to Jeff Bary (NAPG). The rest of the available time is in December, and there is a lot of it. Interested users are reminded to look for OPEN and DD01 blocks listed in the Q4 schedule and request it if desired, especially if they can make use of small blocks of time, especially with ARCES or Agile (for which no instrument change would be required). | + | |
---- | ---- | ||
Line 85: | Line 82: | ||
=== Q1 3.5m scheduling === | === Q1 3.5m scheduling === | ||
- | Schedule | + | The Q1 schedule |
---- | ---- | ||
Line 91: | Line 88: | ||
=== Q4 ARCSAT scheduling === | === Q4 ARCSAT scheduling === | ||
- | All unassigned | + | All of the time after December |
---- | ---- | ||
Line 97: | Line 94: | ||
=== ARC Board of Governors Meeting Recap === | === ARC Board of Governors Meeting Recap === | ||
- | + | The ARC Board of Governors meeting | |
- | + | * Chip Kobulnicky (UWy) has agreed | |
- | The ARC Board of Governors meeting | + | * The Science Highlights |
+ | * The Board approved a request to move forward with a conceptual design for a new echelle spectrograph. | ||
+ | * The Board approved our 2023 budget! | ||
---- | ---- | ||
Line 105: | Line 104: | ||
=== AAS 241 Meeting === | === AAS 241 Meeting === | ||
- | xxx | + | The January 2023 AAS meeting will be 8-12 January in Seattle. |
- | + | Several APO staff members will be in attendance this year, and it would be good to have a mix of APO staff and users at the booth through the meeting. Nancy will order stickers to give to people for their badges to indicate that they are presenting results from APO observations. Also, a digital | |
- | The January 2023 AAS meeting will be 8-12 January in Seattle. | + | |
- | We will discuss this further at our December UC meeting. | ||
---- | ---- | ||
Line 120: | Line 117: | ||
New action items from this meeting: | New action items from this meeting: | ||
- | * xxx | + | * Nancy: make sure that the APO web site gets updated to address the issues reported by Eric B. |
+ | * UC reps: distribute information about the AAS meeting and our request for participation/ | ||
+ | * Nancy: send out a new calendar invitation with the UC meeting dates for 2023. | ||
---- | ---- | ||
Line 132: | Line 131: | ||
=== Next meeting === | === Next meeting === | ||
- | The next meeting will be on xxx Jan 3 or Feb 7? xxx | + | The next meeting will be on **Tuesday |
---- | ---- |