This meeting is triggered by two things: expected operation of Fermi past the initial 10 year goal; and sharp reduction in DOE support when that happens. The FSSC has already got engaged in Mission Planning. The goals of the meeting are:
- identify shortfalls in effort from the DOE ramp down at SLAC
- bring the LAT, FSSC and HEASARC efforts closer together and eliminate duplications if possible
- plan for the long haul - shore up support and look to see what, if any, modernization is appropriate for long term support
- smooth out any existing wrinkles in the FSSC taking on Mission Planning
Proposed date: week of Feb 6
Possible Session Blocks (see Scope below):
- Overview of SAS-related activities
- scope of support
- already known areas of shortfall
- Mission Planning tagup (Date/Time: Monday Feb 6, 10AM - 12noon. Location: TBD).
- optimization of ongoing transition
- walkthrough/demo of weekly planning
- review of documentation
- ISOC software
- Code development infrastructure
- python distributions
- release management
- code distribution
- Science Tools
- external packages
- fermiPy support
- L1 processing & halfpipe
- operational support
- system tests, new version validation and approval
- VMs, containers
- RHEL6 is end of road for GR
- automatic creation of VMs (do we need containers too?)
- Data Issues
- change datasets delivered to FSSC?
- are data servers at SLAC still needed?
- change of storage model at SLAC?
- GlastRelease futures
- GR code development
- any issues on long term support of ROOT files etc?
- ISOC/Ops/Planning software
- Robin, Jerry and Elizabeth will be at SLAC and can hopefully resolve some of the connectivity issues we’re having
- Face-to-face training for planning process
- Decide on a timeline to perform shadow operations
- Discuss leap second process since no shadowing occurred this time
- SAS development
- Incorporating more python
- Removing external packages
- Repositories, Issue Tracking, Release Managers, etc.
- Data retention
- Discuss sending critical data sets (like electron data) to GSFC for long-term retention
- Future reprocessing
- Potential change of storage model at SLAC (more tape reliant)
- L1 Pipeline
- Monitoring & issue resolution
- Test process as updates are required
- Misc items
- All systems - update for new OSs? Or maintain current on VMs?
- Data server - Only at GSFC?
- GLEAM (aka reconstruction chain)
- System Tests
- Investigating conda and conda-forge as a distribution channel for the STs
- Using docker for software distribution
- Universal linux binaries for Science Tools (i.e. distribution agnostic)
- Cloud-based CI services (Travis, CircleCI) for compiling and/or testing
- Should have lots of time for breakouts. Spread topics across multiple days. Working meeting. Not lots of presentations.
- Use SLACK channel for discussion. Make new channel. Name?
- List people being lost and their tasks, people still available. Map tasks to names as appropriate.
- Coordinate the meeting through the existing DRSC list. Seems to hold most of the important members. Add as needed. Or software mailing list.
Richard Dubois, Elizabeth Ferrara, Robin Corbet, Jerry Bonnell, Julie McEnery, Jeremy Perkins, HEASARC representative, Matt Wood, Eric Charles, Nicola Omedei, Giacomo Vianello, Troy Porter, Jim Chiang, Steve Tether, Heather Kelly, Tom Glanzman, Warren Focke, Tony Johnson, Brian Van Klaveren, Max Turri, Charlotte Hee, Maria-Elena Monzani, Seth Digel, Regina Caputo, Alex Reustle, Joe Asercion, Don Horner, Mattia DiMauro, Simone Maldera, Elisabetta Cavazzuti, Michael Kuss, Samuel Viscapi, Joanne Bogart, Gregg Thayer, Rob Cameron, Luca Baldini, new FSSC software hire (?), Leon Rochester, Tracy Usher