2024-10-10 Meeting notes

1:02

Words from Jim

Words from Greg

Jim
Greg

• Pass

1:03

Words from John

John

• SSC and NIKUG meetings upcoming

  • Both coming to HQ

  • Sent notional schedule to Jim, will send to SA slack

  • Instrument updates: “if there’s not much to say, don’t say much”

  • Carolyn to ID an OA to present something

  • As usual, NIKUG presentations will be shorter

  • SSC is 5th, NIKUG is 15th

• FY25 planning is largely complete

• Off island next week with Rich meeting with Bruce and Chris at UCSC

• Will be lots of spirited debate around NIRES retirement

• For SSC and NIKUG: highlight operational pressures on observatory

  • Brainstorm metrics for this

  • Sherry: Instrument vs. AO metrics?

    • Try to separate AO only issues from instrument

  • How are things changing?

• Will hopefully get permission to submit PyWFS probably to WFS

• KASM/GEO proposal also likely to be submitted

• Still waiting on news about Liger funding

  • Likely is last chance for Liger (at NSF) in current form ($25M)

  • Starts to become coupled to future of TMT

• Team Keck time: will look at proposals soon

• Got contribution for KVSP

  • Shored up for a number of years

1:18

upcoming SSC instrument reports on Nov 5?

Josh

• Michael: LRIS + DEIMOS

• Carlos: NIRC2

• Greg: NIRSPEC + HIRES + KCWI

• Josh: MOSFIRE + KPF

• Sherry: HIRES + OSIRIS

• Percy: AO (Max for NIKUG) + NIRES

• Jim: ESI

• Dry run in 2 weeks? on Oct 24 meeting

1:26

AO update

Percy

• K1 rotator had issues

  • OK now

  • Don’t standby init it, won’t home itself correctly

• Also found loose weights, not properly secured

• K2 is working reasonably well

  • GD: How often should RTC be rebooted?

  • No need to reboot preemptively at start of cals

  • MS: Only do during troubleshooting, not preemptively

• Percy will try to make a web page with recent issues (instead of big spreadsheet of tickets maintained by team)

• Have been some false alarms for laser closure. Treat all alarms as real for now.

• Check that tip tilt star is within allowed range, observers have gotten this wrong on star list. Check when processing list.

1:34

UNO ATS procedures

Percy

All Lakeshores on UPS?
All heaters on UPS?
Procedures to recover with and without servers back
Order for recovering the servers?

UNO instrument readiness, particularly whether the project has met the instrument temperature monitoring requirement.  

• Team wants procedures to follow from us

• We have the possibility to have things on UPS

• Every instrument scientist to provide recovery procedure for two cases:

  • If server is back online

  • If server is not online

  • And a procedure/checklist for before power is out

  • Is there an order for servers to come back on?

  • Does the instrument server bring up all daemons?

2:05

UNO Instrument Alarms

Carolyn

• Do we get instrument (e.g. temperature) alarms in time to do something about it in an UNO world where it takes 2 or more hours to get someone to summit.

• Event Notifier is dead/on life support

  • OAs did not find it useful

  • We have’t heard much, did not find it useful in an early demo

• Carolyn is ok to mark this as a requirement not met and needs a replan

• Will be policy to have someone (minimum 2) on call to drive up

• When is UNO coming?

  • Unclear.

  • Electrical work on 6th is necessary step

  • Will then enable AFP testing

  • Then could move to Phase 2

    • All project reqs are met and documented

  • AFP testing will be at night on both telescopes (simulate power outage)

2:22

Pau!

Next lead: Carlos