Content Comparison

1:02

Words from Randy

Randy

• All Staff Meeting yesterday + email about changed in OID

  • was a surprise. Situation with Grant is changing, will do more work directly on instruments in the future.

  • Remains to be seen what that role will be.

  • We may be able to shape it.

  • Won’t change Instrument Scientist role or commissioning roles we play

  • Grant will be working under John O’Meara and more with us.

  • New to Randy as well.

• Kyle: what motivated transition?

  • Randy doesn’t know any more than what was in emails and all staff.

  • Grant will be in a position to help with instrument engineer position

• Jim: overlaps with Instrument Engineer and Project Engineer/Manager roles?

  • How does this fit in with hires?

• Josh: overlap with Marc’s role with Instrument Task List?

  • Randy: Can offload and/or coordinate with Marc

• Josh: will be be on summit or at HQ?

  • Randy: We don’t know.

• Will be part of “Instrument Program Office” with Marc

• Decision was at DAC level (Director Advisory something-or-other) not at council level

• We should do a get together … scheduling as always is hard

• CI Projects: will be well resourced, take advantage of it

• Jim: where are hours coming from

  • Randy: off the top, but low priority CIs are cut to balance if they have high demand resources

• Carlos: why was there precipitous drop in CI effort in last few years?

  • Randy: Not allocated ahead of time, so CIs came in after projects got resources. Hence the strategy of setting aside CI resources first.

• Carlos: how should we do observing support after June 1?

  • Randy: do it as you think best. If observers are at HQ, do afternoon and start of night in person – that is preferred model.

  • Clarification from Randy and John: When observers are at HQ, support should be at HQ.

  • Non-support work on normal schedule is expected to be at HQ

• Rosalie: air circulation in Kohala was bad recently, will that be fixed?

1:35

Science Software Tasks

Luca

• Luca had discussion with Jeff on how to proceed. There are ~600 hours allocated in this FY, only ~15% used, so we have resources which are unused. Mostly Kyle and some Matt.

• We should make use of that allocation.

• List is not closed, keep adding ideas

• Notes on discussion captured in SSS board

• We selected several projects for development in this FY

2:15

ASIVA + MASS/DIMM future

Jim

• The MASS/DIMM (former TMT site testing equipment) and ASIVA camera will no longer be supported by CFHT in a couple of years

• UNO will be adding an all sky camera (visible), level of software support is TBD. Not sure how much will be implemented under UNO

  • Requirements Josh collected from SAs for UNO are here: /wiki/spaces/~362166519/pages/711327748

• TMT will have their own monitoring tools

• ASIVA is on lunchroom roof

• Jim is collecting our needs

2:27

Pau!