| | | |
|---|
1:03 | Words from John | John | preparing for SSC and board meetings excited about KCRM arriving draft of strategic plan is released actively working on 5 year plan John will be in CA next week for SSC and Board, on vacation following week
|
1:08 | Words from Randy | Randy | Weather has been “quite poor” Carolyn checked history and is one of the worst continuous stretches of lost time due to weather Flexible work policy was distributed Waiting for people planner to get released Maybe that will read support schedule and populate it Wed is company wide collaboration day 2pm Wed for Coffee?
With loss of engineering time, will be rescheduling some of that. About to send out draft support schedule for rest of semester FY ends at end of September, travel budget rolls over then, so contact randy about travel plans
|
1:20 | Observer’s data access portal | Chien-Hsiu | Real Time Ingestion GUI Now hosted at IPAC, in testing phase before release @Chien-Hsiu Lee (Unlicensed) link here: http://vmkoatest.ipac.caltech.edu:8092/feed/login
(private for now, need KOA login: rtitest/pasadena) Demo of interface Session will restart at 0h UT (2pm HST) KOA web page has documentation on “Observers Data Access Portal”
http://vmkoatest.ipac.caltech.edu:8000/UserGuide/odap_help.html
(private for now, need KOA login: rtitest/pasadena) Observers on telescope schedule should get KOA access, but need to have a KOA ID first. Looking at providing ability for PI to add access … (still working on it) Will eventually remove access to sdata disks, but still need to figure out transition time and handover criteria (~ a semester long overlap) Also adding Co-Is to permitted KOA users for data Access permissions same for standard KOA and real time Once released, need to update instrument pages to tell PIs to grant access and add instruction to start this before taking calibration data RTI is available until 0h UT There is also pykoa notebooks on KOA web page to do sophisticated queries Still considering adding columns to make the a full KEOLA replacement. SAs should make sure they have individual KOA IDs
|
1:45 | New people calendar | Josh | Josh beta tester for new people calendar Calendar defaults to put us all on HQ Mon through Fri Possible to use the API to create a personal calendar Would it be possible to populate the fields automatically based on the support schedule? Support nights from 4pm to 11am? Calendar reads from the operations schedule Can the calendar support several locations How do we represent compensation time for overwork? How precise the information needs to be? Can you include contact information? One could use a set of personalized defaults
|
2:03 | | | Proposals for 22B Team Keck proposals on Aprli 10, but Greg is going to confirm. John would like to have a discussion about our thoughts on the Strateginc Plan
|
2:06 | Identify next meeting lead | All | Greg |
2:07 | Pau | | |