2021-06-03 Meeting notes

1:06

Notes from Jim

Jim

Rita Morris has joined and been writing night log tickets. Currently at full OA capacity.

1:08

Keck Science Meeting

Sherry

SAs should sign up. https://kecksciencemeeting.org

1:10

Nightlog Ticket Discussion

• Known issues that aren’t going to be fixed should have nightlog tickets that are noted. Example: MOSFIRE Bad Reads.

• Grant: Be mindful that tickets may want to be data mined.

• Jim: Do we lose track of tickets? Do we need to prod for nightlog tickets? What models works best for the next step?

• Percy: Important to keep track of time loss, in particular to monitor if progress is getting worse. Instrument scientist is responsible for tickets for that instrument and can delegate.

• Greg: Instrument scientist should be in charge of tickets

• Josh: Nightlog system with free-form text isn’t ideal for logging.

• Sherry: People on support may be too exhausted to quickly follow up on tickets. Should be the instrument scientist to follow up.

• Jim: Nightlog ticket priority impacts the circle back time. Critical should be looked at the next day, but

• Josh: Proposal of going through nightlog tickets by instrument.

1:26

MOSFIRE Ticket Review

Josh

Discussion of recent tickets

K1-30694 - discussion of ticket and troubleshooting steps that were attempted

K1-30596 - time lost but not during nighttime (ticket closed)