| | | |
|---|
1:03 | Words | Jim | SA Job closes tomorrow. Closing in on 80 applicants. Jim has to do quarterly reviews of everyone who works under him Summit reorganization announced this week Process for scheduling tasks on the summit will change. Be ready for whatever the new process is Joe Killian will be new summit lead (will not lead ETs, now they report to Josh LaPinta) Still no instrument group on summit Tod Von Bockmann will be scheduler Has been announced at summit
Shui is working on instrument and guider checkouts Jim looking at how we can coordinate Get engineering requests to Carolyn. Both short term and next semester.
|
1:09 | Words | John | Email from Rich about recent executive orders and impact on observatory. Our operational funding is unaffected. Some NSF funding will see schedule changes Power outage on Saturday was learning experience, expect more outages SSC is at end of February, Jim will circulate agenda Board meeting here on Feb 27-28 Working on 5 year planning. TLT did a lot of heavy lifting on informing plan. Working toward prioritized list for instrument projects. Talking to all members at town halls and meetings. Full version to be delivered to board at November meeting No major changes to operations budget in plan, focus is on other section of budget
John in San Diego for NASA review panel next week
|
1:20 | Post-Pier Repair | All | If pier repair finishes on time, there will be ~10 days to fill. Ideas? HIRES vs. KPF Josh: KPF tip tilt re-comissioning (if parts arrive in time) Josh+Leo: MOSFIRE CSU and FCS investigations (mostly during day) Grant: Check defining points and rotator alignment Grant: Check HIRES illumination pattern using bright star at night using NVGs
Identify ideas and pick best ones to pursue/plan at next SA meeting
|
1:33 | Cherry Blossom Festival | Jim | Saturday is festival. Josh and John P will be doing solar viewing, Jim will be there as well. Another event Feb 22. NASA at My Library Asked for solar viewing Leo is interested
|
1:35 | Power outage procedure | All | Gaps in https://www.keck.hawaii.edu/draw/CARA/9114/9114-CA0501.pdf There are subtleties between power is out, we expect power to be out for a while, power is out and we are abandoning summit, etc. Category 1: power is out and we need this done immediately Other decision trees should be enumerated. Factor in UNO considerations, what if no one at the summit.
Jim to ask John or Leslie for editable version, John might have redlined version we haven’t seen Kyle: some systems should be configured to set how they comes back. Computers and PDUs have settings about what to do when power is restored. Everyone look at instruments you have primary or secondary responsibility for and decide on possible changes to this doc. Carolyn: K1 instrument cooling should now come back on after power is restored
|
1:52 | Visibility of instrument alarms | Carlos | Recent incidents including a NIRC2 CCR failure which didn’t trigger an alarm and a DEIMOS detector warm up Kevin T mentioned DCS keywords corresponding to EPICS channels. 15 keywords for each instrument to send alarms to CSS alarm handler. UNO Event Notifier? Need to separate decision making on whether there is an alarm and how we distribute that info to people. CSS can do the former if we have a path to set it from the decision making entity. Departure screen only checks instrument CCRs which are scheduled for tonight (we think) EMIR and old keywords: old keywords don’t like being monitored constantly (e.g. LRIS and MOSFIRE)
|
2:30 | Pau! | | Next lead = @Leo Alcorn |