Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Decide on rotation of lead and scribe for these meetings.

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

01

02:

00

03

Words From Randy

Randy

JohnO on travel

01:10

  • All Staff Meeting had lots of new information about all the new Chiefs. Any clarification needed?

  • Rosalie: Is there more info coming about portal to portal?

    • Randy: no / I don’t know.

    • Rosalie: Concern about problems identified after 4:20pm.

    • Jim: Let that play out. Figure out what procedures are source of problems.

    • Randy: will be more problems discovered after day crew departure

    • Rosalie: can we move telescope release up by 15 min?

    • Carolyn: Feedback: Communication around this was poorly executed. Night Attendants not considered in this plan.

    • Randy: This was an HR/DAC decision, not council.

    • DAC = Hilton, John, Peter, Margarita, Rich, Andrew (as CoS going forward)

    • Council = larger group, maybe 15 people. DAC + department managers. Randy, John B., Andrew, Jason C, Megan, etc.

    • Jim: Use Nightlog reporting system as “bully pulpit” if there are problems

    • Percy: If they need to stay longer, is approval needed? Answer: No.

    • Jim: summit to Waimea is more than 1:10. Hitting 10 hours (+30min for lunch) is 7am to 530pm, is still challenging even with this.

2:16

Running SA meetings

Jim

How do we want to rotate the meeting duties?

  • Automatic reminders about lead and scribe for these meetings expired at end of January. Do we want to keep same rotation?

01:20
  • Greg/Carlos: ok to keep old way

  • Randy: rolling facilitator encourages individuals to seek out topics and talk to teammates

  • Jim: will fill out next months of schedule. Used to be Gloria filling this out.

    • Link is on wiki page, will put on Confluence as well

2:21

Calibration communication

Jim

Review guidelines for dome calibrations

  • Whiteboard

  • dcs.DOMECALS keyword

  • When will the lights come on?

1:40

  • Recent communications problems on morning cals

  • Solution that we came up with is observer stays on Zoom and can talk to day crew.

  • But was problem this morning, dome lights on during observer flats

  • Keyword is not visible at the moment, can we set it reliably?

  • Jim has put it in to ESI calibration scripts.

  • Some instruments are difficult.

2:36

22B instrument availability

Randy / Carolyn

ToO inst switches

VVC on NIRC2 ….with PyWFS

PyWFS updates

At home observing

  • What needs to be in call for proposals which is about to go out?

  • Currently instrument switches for ToOs are not allowed, based on COVID restrictions on day crew. Should we change it?

    • Josh: day crew burden is primary concern, defer to them

  • Josh: will remove nominal 2

:00
  • observer restriction on at home observing

  • Jim: should we try to find a way to test guiders without process of changing instruments (impacts K1DM3)?

    • Would need Shui’s input

    • Current process means tonight’s instrument would be last selected, so delays release a bit unless we change this process.

    • Carlos: what instruments available?

    • Randy: on K2 only NIRES (and perhaps NIRC2) were described as available. We don’t look at what is on RNAS.

    • Carlos: config forms don’t require a long slit if we want DEIMOS available for ToOs.

2:59

Engineering nights in 22B

Randy/ Carolyn

inst commissioning, AO projects, Pier repair

  • K1 will have 10 night shut down for gout repair in September

  • K1 KAPA AO 6.5 half nights

  • K2 telescope engineering is more typical (K1 is high)

  • K2 KCRM is asking for 6 nights

  • Asks are big, much higher than average

3:10

Pau!

✅ Action items

  •  Instrument Scientists: look at your cal scripts and tools and see if dcs.DOMECALS keyword is a good solution.
  •  

⤴ Decisions