Content Comparison

11:32

Words from Randy

Randy

• Going to go to “Level 3” for COVID risk matrix. Not yet official.

• Not a big impact on us. More summit presence. More project work at summit.

• Likely starting next week.

• We can go up for instrument or AO work.

• HQ will be more open.

• Still limited vehicle situation, but >1 per car.

• A and B summit teams will continue

• Contracting someone to do testing for us

• Still need to register to go in to HQ to facilitate contact tracing

• Level 3 expected to be a long term situation (months)

11:41

Words from John

John

• Nothing to add

11:42

Engineering Plan

Randy

• Engineering coming up on K1 and K2. Summarized schedule.

11:50

Review Action Items

Greg

• Collection of Pajama Mode thoughts is for long term considerations. Some demand is likely to continue after COVID is over

• Josh pushed out v1.1 of Remote Observing software, new test system, so be aware that observers should run their tests slightly differently.

12:02

Build and Deploy

Kyle

• FACSUM, MET, and Rose UIs don’t need to be run on instrument VMs, could be run on kNobs

• Having compass rose next to instrument data is important

• Kyle prefers not to SSH forward interfaces: less efficient, less reliable

• Consensus is for flexibility, but could run them on kNobs if needed.

12:12

• QACITS and Vortex support

Carlos

• Clarify discussion about support of QACITS from yesterday’s coffee discussion

• QACITS was written elsewhere, but has been officially supported by Keck since 2017

• QACITS is still not something we know intimately, uncertainty in s/w group on how to handle tickets or questions

• QACITS takes information on residuals from star on vortex to determine centering of PSF on vortex. Runs PID loop to keep star centered on vortex.

• Very complicated to do that. UI is poor: users edit hardcoded values in source and restart software.

• Jim: Wasn’t QACITS put in to KROOT? Yes. Avoids conking. One IDL subroutine is needed, so it is conked in home directory.

• Randy: When capabilities are added to instrument, it should be the goal to make it a facility grade capability.

• Do we need guidance or policy on “specialty modes”?

• QACITS works with both SH and PyWFS.

• Carlos: QACITS is not to standard needed for typical users.

12:41

Newsletter

Luca

• We skipped two issues of newsletter

• Should we re-evaluate the format? Is monolithic newsletter every 6 months best? Something more agile?

• Go annual and link to Keck Science Meeting?

• Will bring up again.

12:44

ToO Policy?

Randy

• What to do with ToOs in “pajama mode” observing

• Randy proposal:

  • no instrument switches (reduced burden on day crew)

    • only can use instrument which is scheduled during that time, even on nights with 2 classically schedules instruments

  • requests must be in my certain time in afternoon

• Carlos: PJ mode is overwhelming

• Can we pre-set up ToO observers to avoid last minute configuration burden?

• Place limitations on the number of observers per night? per progid? per run?

1:10

Pau!