The software week goal is to facilitate coordination between communication and collaboration between everyone as we move forward extended support for Fermi. FSSC members will be available at SLAC all week for group discussions and one-on-one meetings. In addition to targeted topics, we encourage attendees with broad or cross-cutting interests to join the various discussions. There will be plenty of work, so we'll need everyone to take part in this transition.

Previous Software Weeks: Fall 2017,  Winter 2017, Winter 2018

Dates: Late February or early March 2020 (see below)

Location: SLAC

Attendees

If you are interested in attending, please use the table below to indicate which of the weeks works for you, and we'll try to find a time that works best for the most people.  If you can't attend in person, hopefully we can work out remote attendance.

Possible Agenda Items

Below are some possible agenda items or things that could actually be done during the week.  I've tried to include possible participants and what might be discussed or done.

SLAC Infrastructure Related

• Move to containers.  Maybe done before software week?
  • Tom, Brian, Heather, Joanne(?),
  • Create the containers and move pipeline to containers to run on Centos7.
  • Do the process together and test. 
• Change in batch system.
  • Have Tom, Brian and ?
  • Work on moving to the new batch system.
  • Have Tom develop contacts with infrastructure staff.
• Halfpipe & L1 pipeline documentation
  • Tom, Michael, and Maria Elena, others?
  • Go through current documentation to update (and remove old information).
  • Get together to discuss and write document pipeline how-tos and fixes.
  • Update re-piping documentation. 
  • Document database schema.
• Data reprocessing documentation
  • Tom, Maria Elena, Nicola
  • Nicola knows about FT1 reprocessing.  Are the steps documented?
  • Document how to do FT2 reprocessing.
• GLASTRelease and Jenkins
  • Heather, Alex, Joe, Joanne
  • Make sure GR builds with Jenkins.  
  • Is Heather's knowledge about build and deployment documented?

• ISOC tasks

  • Don, Tom, Steve Tether, ?

  • Progess on this list: Regular and semi-regular manual ISOC tasks

  • Update this page: Software Master List

  • Fastcopy future support.  Will it need to be containerized?
• ASP
  • Does anyone besides Jim know how to maintain it?
  • Any more documentation that this: ASP How-To Guide?
• Data catalog
  • Is Brian the only one who knows how to deal with it?
• Other infrastructure
  • Paging
  • Spread messaging system?
  • Web apps
  • Skimmer
• Update this page: SLAC to FSSC transition questions

Fermitools Related

• Fermitools maintenance and development
  • Joe, Alex, Don, Tom, Phillipe, Eric?
  • Package ownership (e.g., who to contact about gtobssim). 
    • Update this page: ScienceTools Package Author Review
  • How to use Github, Conda, and Azure pipeline.
  • Update this page: 10 Yr Software Transition Dashboard.

  • What does the C&A group need that isn’t being provided by the FSSC (and vice-versa).

  • Develop a Fermitools "how to collaborate" presentation for the collaboration?

• Fermitools/Fermipy interface

  • Alex, Joe, Mattia, Phillipe

  • Discuss and work on improving interface between Fermitools and Fermipy.

  • Modularizing the Fermtiools?

• Fermitools testing

  • Don, Phillipe, Giacomo, Joe

  • C&A group role?

  • Jupyter notebooks for analysis threads
• Pointlike
  • How long will Toby support it?  What should we do after that?
• Switch to CMake instead of SCons?
• Fit convergence issues.  See Jean's 12/2/19 C&A presentation.

Other possible topics

• Adding capabilities to the FSSC data server
  • The FSSC data server is being moved to new, better hardware.
  • New filtering?
  • Allow all sky searches?
  • New data sets?
• Staffing
  • Who is even there anymore and what is their availability?
  • It's hard for FSSC personnel to take over on infrastructure that we don't use regularly.
  • How much can we rely on collaboration people? 
  • Where can external folk inject the most help?
  • Can we create a list of who to contact for various infrastructure issue?