2024-07-18 Meeting notes

1:02

Words from John

John

• SSC meeting ISE was interesting

  • Can’t reveal yet, needs board approval, but recommendation from SSC is actionable

  • Need text by Aug 5 for call for proposal

• White paper discussion

  • Also waiting on approval for details

  • Generally, focus on does something support strategic plan? KASM, KPF-K2

  • Lots of discussion about Keck hours, but FY25 not mapped out

  • Lots of AO adjacent proposals interesting in context of AO-dev vs AO-ops issues discussed recently

  • “I hope to demystify this as soon as possible” (waiting on Board)

• Board meeting was the week prior (opposite of usual ordering)

  • Board visit to summit was useful to help give them a better understanding of issues

1:15

Words from Jim

Jim

• Still working on SA schedule

  • Sharepoint link is still the same and up to daye

  • Up through September now

• SA recruitment going well

  • Short list of 6, doing zoom interviews (4/6 so far)

  • Still impressed with these candidates

  • Will do onsite interviews with short short list

• Had some issues during the day where small mistakes have come up. Need to keep an eye on things to make sure we don’t have bigger incident.

  • Be aware. Jim “has a feeling”

  • John also concerned, discussion in SLT

  • Beware of groups being overloaded leading to lack of focus

  • Grant: some practices from the past aren’t being followed as closely as before (e.g. checklists)

  • Grant: Often there are days with only one support tech ST which can be a lot as ST’s are pulled in to a lot of small tasks even if no reconfigs

  • Carolyn: there are safety cards at HQ and summit for non-incidents, these are for input

• AO continues to be a mess

  • Jim appreciates the sentiment of the AO pause, but no additional resources seem to be getting applied to ops.

  • Just the statement of ops being the higher priority is good

  • Max: some of Marcos’s time got applied to ops

  • Jim: keep writing tickets

• Keck Science Meeting

  • Several from this group on tentative list to go

1:43

Summit power outages, UNO, AFP, and instruments

Jim

• Previous solution in power outages was to open various panels and doors for cooling

  • During UNO will not have people on the summit to do this

  • Jim wants minimum viable power state for instruments

  • Can we develop script and documentation for instruments to enter low power mode?

• Should this run automatically?

  • Maybe … depends on instrument

  • If we lose network, should AFP run this?

• Kyle: could also be run based on temperature threshold instead of power

• Computer room servers will be powered down by AFP

  • Should this be done for all? Maybe some things should be left on to preserve telemetry

  • We should define which computers should be left on

  • Jim: think about what should be left on, both in your instrument and in computer room

• Discuss this at next SA meeting

2:01

HQ power outages in the UNO Era

Josh

• HELCO PSPS convers Keck HQ

  • We have “4 hours” of UPS run time at HQ, but in the past, the limitation has been overheating in ~30 minutes kills the network.

• What is plan for outages at HQ

  • May not maintain ability for OAs to go to summit

  • Server room UPS now keeps network online for much longer than 30 min

• Remote Ops UPS covers plug in floor not in walls

  • Re-arragement in RO will clean up some of this

• OAs have codes to open computer room doors

2:10

Using our fun budget for???

Rosalie

• lego wall decoration for Kohala wing that we each build a part of? Milky Way Galaxy

• lunch at Merrimans or MOA or Fish and the Hog? Food for a SA+fam beach picnic?

• special SA swag like… jackets? vests?

• Consensus on Lego + catered work session

2:26

Pau!

Next meeting lead: Rosalie