...
- 1.5 FTEs after 2018, down from 3 FTEs. Needs to be complete by end of FY ’18. Gradual ramp-up and transition desired.
- Hardware purchasing? Server infrastructure, databases, etc.
- IFC still funding hardware purchases
- Hardware will come to stay at SLAC
- ORACLE server migration soon
...
/afs/slac/g/glast/ground/releases/calibrations/TKR/
ACD calibration code location: /nfs/farm/g/glast/tak/releases/GR-20-09-10.
ASP Discussion (Jim Chiang):
...
- Julie: No path to having anyone other than SLAC supporting flight software
LAT On-board Configuration:
If we desired to change the on-board configuration, what happens?
- Jim Panetta knew the most about that. Took knowledge with him. But see this link.
- Gregg Thayer can do that nominally.
- Handshake in ISOC and GlastRelease has to be done as well
- MOOT/MOOD Table where the key is stored before it’s transmitted to flight software.
- Seems like it takes a while for the ground system to catch up before we can use on instrument.
...
- Forming the input to the configuration build system is the least remembered part
- System for turning the crank and building configurations is fine
- Instructions for turning crank may need work
- Then need to check content of product before upload
- May 2010: Halt in data processing due to MOOT key mismatch with MPT
- Do we know how to handle the MPT?
- Gregg…yes.
...
- Gregg…yes.
Mission Planning/Flight Operations
Actions:
- Finalize and document list of needed permissions on the ISOC Mission Planning page
- Get Fermi Sharepoint access for NASA people (SLAC windows account is not enough)
- Robin/Elizabeth/Jerry to propose round robin schedule for weekly mission planning
- document support cron scripts for SAA checks and planning product generation
- document occasional mission-week-boundary LAT command scheduling problem
- NASA planners to take over LCI calibrations planning, effective immediately
- FSSC to consider having LAT operations workstation/tool installation
...
September 2017 Actions:
- any?
Routine Flight Operations Tasks
- Monitoring, Trending, Reporting: for Weekly LAT Science reports and Quarterly LAT Science reports
Actions:
- improve documentation in Confluence
- make use of API to Google sheets for auto-updating LAT SSR usage and LAT trigger histories
- move LAT monitoring tools and data files from /afs/slac/u/gl/rac/LATmetrics/ to /afs/slac/g/glast/isoc/flightOps/LATmetrics/ for easier shared use and support
- Fix known bugs in agepoly.pl and x4saa.pl
- re-discover use of the LAT Configuration GUI tool, and document it
- migrate other Excel spreadsheet usage to non-Excel implementations
- TKR on-board and ground bad strip history trending: need a solution (ipython notebook?) that makes time plots, and also 4x4 grid-based info output
- CAL light output history trending
Mission Planning notes from Elizabeth:
...