| | | |
|---|
1:00 | Words from Jim | Jim | |
n/a | Words from John | John | |
1:06 | Computer/network work complete? | All | MS: More warning in the future on the work? IT will be opening up visibility of the ticketing system Can view things within a group (e.g. AO) Will help visibility, improve duty cycle Not clear when, but should be happening
IT proposed having a ticket for every task. Not clear how serious this is. IT doesn’t monitor Slack, but posting there can help to see if others are experiencing it. RM: Are they respecting timescales that the ticketing system describes? Will SysAdmin move under Jacques? Jim will circle back to them in a couple weeks and try to be consistent in messaging. Are we keeping track of time lost? Jim has communicated that weekday work is preferred. KL: Prioritizing impacts at HQ seems to be happening, rather than impacts to night ops / summit. TLT has met with the SysAdmin group to express concerns Hold up night log tickets as example, so we should try to close tickets. This is also how we demonstrate responsibility and honesty about reporting problems and being ok with visibility about problems.
|
1:40 | Return to Science Reflection | All | Still haven't been on sky with MOSFIRE and KPF So far so good with other instruments Lots of laser closures (also hitting Robo-AO)
|
1:47 | Preethi Training | All | KCWI training Help from all of us please JW: Train on 2 instruments? Double the opportunities to shadow people. Chance to see what is the same across instruments and what is different. Next week is probably quite full for Preethi, so we’ll want people to meet with her, probably the week after.
|
2:01 | Inst Checkouts | Randy | Trying to get instruments earlier SAs determine science readiness Hand back to summit for guider/cryo Goal is to get better communications and get earlier releases PG: Sometimes support techs are stretched thin (especially on weekends), will we need to think about summit staffing.
|
2:30 | Pau! | | Next lead: @Michael Lundquist |
